17-655 Architectures for Software Systems

Units: 12.0 Department: Software Engineering Special permission: Yes Cross-listed: 17-755 Notes: Student should have worked on a significant software system in their courses o. in industry. If student has this experience, he will need to write to the inst. uctor (garlan@cs.cmu.edu) for admittance to the course stating their experience. Exceptio Successful design of complex software systems requires the ability to describe, evaluate, and create systems at an architectural level of abstraction. This course introduces architectural design of complex software systems. The course considers commonly-used software system structures, techniques for designing and implementing these structures, models and formal notations for characterizing and reasoning about architectures, tools for generating specific instances of an architecture, and case studies of actual system architectures. It teaches the skills and background students need to evaluate the architectures of existing systems and to design new systems in principled ways using well-founded architectural paradigms. After completing this course, students will be able to: 1. describe an architecture accurately 2. recognize major architectural styles in existing software systems 3. generate architectural alternatives for a problem and choose among them 4. construct a medium-sized software system that satisfies an architectural specification 5. use existing definitions and development tools to expedite such tasks 6. understand the formal definition of a number of architectures and be able to reason about the properties of those architectures 7. use domain knowledge to specialize an architecture for a particular family of applications REQUIREMENT: Experience with at least one large software system, either through industrial software development experience or an undergraduate course in software engineering, compilers, operating systems, or the like. Instructor wants each student who want to take his Architectures class to have worked on a significant software system in their courses or in industry. If they have, they will need to write to (garlan@cs.cmu.edu) for admission into the course stating the experience they have had.

Popularity index Rank for this semester: #723 Rank in this department: #3   Students also scheduled 95-760 Decision Making Under Uncertainty 17-653 Managing Software Development 17-657 Communication for Software Engineer... 17-654 Analysis of Software Artifacts 18-749 Fault-Tolerant Distributed Systems 17-672 Software Development Studio II 95-711 Financial Analysis 11-792 Software Engineering for Informatio... 95-710 Economic Analysis 17-615 Software Process Definition

Spring 2005 times

Sec	Time	Day	Instructor	Location
A	5:30 - 6:50 pm	M	Lattanze, Garlan	NSH 1305
		W	Lattanze, Garlan	NSH 1305