These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Architectural Design based on Chapter 10 - Software Engineering: A Practitioner’s Approach, 6/e Architectural Design based on Chapter 10 - Software Engineering: A Practitioner’s Approach, 6/e copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University Use Only May be reproduced ONLY for student use at the university level when used in conjunction with Software Engineering: A Practitioner's Approach. Any other reproduction or use is expressly prohibited.

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Modified Waterfall model 1 [aka Royce1970] Systems Engineering Software Req. Analysis Project Planning Design Implementation Testing/Verification Release Operation/Maintenance Separate and distinct phases of specification and development Architectural Detailed

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001,

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Why Architecture? The architecture is not the operational software. Rather, it is a representation that enables a software engineer to: (1) analyze the effectiveness of the design in meeting its stated requirements, (2) consider architectural alternatives at a stage when making design changes is still relatively easy, and (3) reduce the risks associated with the construction of the software.

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Architectural Styles Data-centered architectures Data-centered architectures Data flow architectures Data flow architectures Call and return architectures Call and return architectures Object-oriented architectures Object-oriented architectures Layered architectures Layered architectures Each style describes a system category that encompasses: (1)a set of components (e.g., a database, computational modules) that perform a function required by a system, (2)a set of connectors that enable “communication, coordination and cooperation” among components, (3)constraints that define how components can be integrated to form the system, and …

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Data-Centered Architecture Communication between software? Centralized or distributed? Any exemplary?

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Data Flow Architecture Constraints? Any exemplary?

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Call and Return Architecture Relationship to DFDs?Any exemplary?

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Layered Architecture Constraints? Any exemplary?

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Architectural Context UML? DFD? What are small rectanlges?

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Component Structure

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Refined Component Structure

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Analyzing Architectural Design. Describe the architectural styles/patterns that have been chosen to address the scenarios and requirements: module view module view process view process view data flow view data flow view. Evaluate quality attributes by considering each attribute in isolation. easier to test easier to test easier to maintain easier to maintain propagation of fewer side effects propagation of fewer side effects easier to extend easier to extend Is this list enough? Relationship of this list to requirements?

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Omitted Slides

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Partitioning the Architecture “horizontal” and “vertical” partitioning are required “horizontal” and “vertical” partitioning are required function 1 function 2 function 3 decision-makers workers

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Data Design At the architectural level … At the architectural level … Design of one or more databases to support the application architecture Design of one or more databases to support the application architecture Design of methods for ‘mining’ the content of multiple databases Design of methods for ‘mining’ the content of multiple databases At the component level … At the component level … refine data objects and develop a set of data abstractions refine data objects and develop a set of data abstractions implement data object attributes as one or more data structures implement data object attributes as one or more data structures review data structures to ensure that appropriate relationships have been established review data structures to ensure that appropriate relationships have been established simplify data structures as required simplify data structures as required