CSE681 - Software Modeling and Analysis

../CSE681summer/Lectures/cse681codeL1.xml code.xml#CSE681 Syllabus ../CSE681summer/Projects

../cse681/BestFinalProjects/Fall04  Vijay Appadurai, Bassem El Karablieh
../cse681/BestFinalProjects/Fall03  Rohit Jhangiani, Carmen Vaca Ruiz, Ghanashyam Namboodiripad, Priyaa Nachimuthu
../cse681/BestFinalProjects/Fall02  Riddhiman Ghosh, Saket Satta

This course is concerned with modeling software - especially large distributed systems - including architecture, design, and implementation. To do this we introduce: UML diagrams: activity, dataflow, class, event-trace, structure charts, and state. Analysis based on load models and some queuing theory. Prototype code, using C# and the .Net Framework Class Libraries. One major focus is the representation of software and software systems with means other than code, although we do develop code in this course.

Five projects are required that are progressively more challenging. The first and second projects are concerned with describing the architecture needed to realize a set of requirements and its implementation, respectively. The third and fourth projects repeat this for a more complex, distributed, system. The final project requires the creation of an architecture for a large, complex, distributed system.

The use of C# and the .Net Framework Class Libraries are required. This is covered by the class text and in help sessions conducted by the instructor and teaching assistants. A lot of work outside of class is expected. Students that complete this course with good grades will understand how to lay the foundations for the successful development of large, distributed systems.

Programming Microsoft .Net, Jeff Prosise, Microsoft Press, 2002, ISBN 0-7356-1376-1
We will use parts I and III only. Class Notes, available on www.ecs.syr.edu/faculty/fawcett/handouts/cse681 bdn.borland.com/article/0,1410,31863,00.html www.gotdotnet.com ../coretechnologies www.bearcanyon.com/dotnet/ Five ../CSE681summer/projects are required: three require creation of an Operational Concept Document (OCD) to record a software architecture. Two require code to implement the systems of the first two OCDs.

Students are expected to have a good working knowledge of the C Programming Language. No prior knowledge of C# is required.