软件工程实践者的研究方法chapter08.ppt

These slides are designed to accompany Software Engineering:A Practitioners Approach,7/e(McGraw-Hill,2009).Slides copyright 2009 by Roger Pressman.1Chapter 8nArchitectural DesignSlide Set to accompanySoftware Engineering:A Practitioners Approach,7/e by Roger S.PressmanSlides copyright 1996,2001,2005,2009 by Roger S.PressmanFor non-profit educational use onlyMay be reproduced ONLY for student use at the university level when used in conjunction with Software Engineering:A Practitioners Approach,7/e.Any other reproduction or use is prohibited without the express written permission of the author.All copyright information MUST appear if these slides are posted on a website for student use.These slides are designed to accompany Software Engineering:A Practitioners Approach,7/e(McGraw-Hill,2009).Slides copyright 2009 by Roger Pressman.2Why Architecture?analyze the effectiveness of the designconsider architectural alternativesreduce the risksThese slides are designed to accompany Software Engineering:A Practitioners Approach,7/e(McGraw-Hill,2009).Slides copyright 2009 by Roger Pressman.3Why is Architecture Important?nRepresentations of software architecture are an enabler for communication between all parties(stakeholders)interested in the development of a computer-based system.nThe architecture highlights early design decisions that will have a profound impact on all software engineering work that follows and,as important,on the ultimate success of the system as an operational entity.nArchitecture“constitutes a relatively small,intellectually graspable mode of how the system is structured and how its components work together”BAS03.These slides are designed to accompany Software Engineering:A Practitioners Approach,7/e(McGraw-Hill,2009).Slides copyright 2009 by Roger Pressman.4Architectural DescriptionsnThe IEEE Computer Society has proposed IEEE-Std-1471-2000,Recommended Practice for Architectural Description of Software-Intensive System,IEE00nto establish a conceptual framework and vocabulary for use during the design of software architecture,nto provide detailed guidelines for representing an architectural description,and nto encourage sound architectural design practices.nThe IEEE Standard defines an architectural description(AD)as a“a collection of products to document an architecture.”nThe description itself is represented using multiple views,where each view is“a representation of a whole system from the perspective of a related set of stakeholder concerns.”These slides are designed to accompany Software Engineering:A Practitioners Approach,7/e(McGraw-Hill,2009).Slides copyright 2009 by Roger Pressman.5Architectural GenresnGenre implies a specific category within the overall software domain.nWithin each category,you encounter a number of subcategories.nFor example,within the genre of buildings,you would encounter the following general styles:houses,condos,apartment buildings,office buildings,industrial building,warehouses,and so on.nWithin each general style,more specific styles might apply.Each style would have a structure that can be described using a set of predictable patterns.These slides are designed to accompany Software Engineering:A Practitioners Approach,7/e(McGraw-Hill,2009).Slides copyright 2009 by Roger Pressman.6Architectural StylesnData-centered architecturesnData flow architecturesnCall and return architecturesnObject-oriented architecturesnLayered architecturesset of componentsset of connectors constraintssemantic modelsThese slides are designed to accompany Software Engineering:A Practitioners Approach,7/e(McGraw-Hill,2009).Slides copyright 2009 by Roger Pressman.7Data-Centered ArchitectureThese slides are designed to accompany Software Engineering:A Practitioners Approach,7/e(McGraw-Hill,2009).Slides copyright 2009 by Roger Pressman.8Data Flow ArchitectureThese slides are designed to accompany Software Engineering:A Practitioners Approach,7/e(McGraw-Hill,2009).Slides copyright 2009 by Roger Pressman.9Call and Return ArchitectureThese slides are designed to accompany Software Engineering:A Practitioners Approach,7/e(McGraw-Hill,2009).Slides copyright 2009 by Roger Pressman.10Layered ArchitectureThese slides are designed to accompany Software Engineering:A Practitioners Approach,7/e(McGraw-Hill,2009).Slides copyright 2009 by Roger Pressman.11Architectural PatternsnConcurrencyapplications must handle multiple tasks in a manner that simulates parallelism n operating system process management patternntask scheduler patternnPersistenceData persists if it survives past the execution of the process that created it.Two patterns are common:na database management system pattern that applies the storage and retrieval capability of a DBMS to the application architecturenan application level persistence pattern that builds persistence features into the application architecturenDistribution the manner in which systems or components within systems communicate with one another in a distributed environment