CSC2103H ECE450H David A. Pennypenny@cs.toronto.edu An introduction to the development of system-level architectures and class-level object-oriented designs for software systems. This course places special emphasis on the study of architecture and design patterns: the core of solutions to commonly occurring design problems. Other topics include representations of design/architecture (with emphasis on the use of UML as a class-level design notation), architectural assessment, product lines, architecture extraction, and re-factoring. The course does not have a major project, but does have a series of smaller design and architecture exercises requiring some programming. A knowledge of UML as used for requirements analysis and a working knowledge of both the C++ and Java languages is assumed. Even once we fully understand the requirements for a software system it is rarely clear how to begin the programming task (except for the most trivial of programs). The steps in-between requirements and coding are first architecture and then design. Architecture involves specifying the construction of the system at the highest level. What are the major modules? What are the major processes? How do the processes communicate with one another? Design involves specifying the construction of a single module or program at the class level. What classes should we have? What are their responsibilities? With what other classes should they collaborate? What methods should they contain? This course teaches students how to come up with and then descirbed system-level architectures and class-leve designs. CSC340H teaches UML for OOA Good to understand requirements before design CSC378H teaches ADTs so that students have a solid understading of encapsulation to get past this course, students must have gone through Java and C++ general programming maturity CGPA 2.00 Learn to be better software architects and designers Learn to represent an OOA using UML Learn the process of doing an OOA Learn to represent an OOD using UML Learn the process of doing an OOD learn how to learn patterns Learn the GofF design patterns Learn how to represent a system architecture (informally) Learn a standard set of architectural patterns Introduction to software architecture and design the place of design and architecture in the software development process definition of architecture the importance of architecture architecture process steps architecture process steps quality attributes affected by architecture the existence of multiple architectural structures in software The roots of modularity and information hiding Parnas paper: KWIC case study Introduction to Object-Oriented Design Coad and Yourdon OOD process steps Design patterns Introduction purpose of design patterns how design patterns are described a taxonomy of design patterns using design patterns inheritance, composition, and delegation LEXI case study Detailed description of selected patterns System-Level Architecture guest lecturer from industry monolithic systems components (e.g., JavaBeans) client/server systems RDBMS-based systems distributed objects (e.g., CORBA, EJB) n-tiered systems architecture assessment product lines architecture extraction architecture re-factoring architecture description languages Gamma et. al. Addison-Wesley (Professional Computing Series) 1995 1st 0-201-63361-2 Booch et. al. Addison-Wesley 1998 1st 0-201-57168-4 UNIX Java UML (for design) UML Drawing Tool (e.g., Rational Rose) given a simple problem, come up with a class design in UML using patterns and then code it in Java given a more advanced problem, come up with a class design in UML using patterns and then code it in Java given the description of a system's requirements, produce a system-level architecture document for it