Pressman_ch_9_design_engineering.ppt
- 1. 1 Purpose of Design âą Design is where customer requirements, business needs, and technical considerations all come together in the formulation of a product or system âą The design model provides detail about the software data structures, architecture, interfaces, and components âą The design model can be assessed for quality and be improved before code is generated and tests are conducted â Does the design contain errors, inconsistencies, or omissions? â Are there better design alternatives? â Can the design be implemented within the constraints, schedule, and cost that have been established? (More on next slide)
- 2. 2 Purpose of Design (continued) âą A designer must practice diversification and convergence â The designer selects from design components, component solutions, and knowledge available through catalogs, textbooks, and experience â The designer then chooses the elements from this collection that meet the requirements defined by requirements engineering and analysis modeling â Convergence occurs as alternatives are considered and rejected until one particular configuration of components is chosen âą Software design is an iterative process through which requirements are translated into a blueprint for constructing the software â Design begins at a high level of abstraction that can be directly traced back to the data, functional, and behavioral requirements â As design iteration occurs, subsequent refinement leads to design representations at much lower levels of abstraction
- 3. 3 From Analysis Model to Design Model âą Each element of the analysis model provides information that is necessary to create the four design models â The data/class design transforms analysis classes into design classes along with the data structures required to implement the software â The architectural design defines the relationship between major structural elements of the software; architectural styles and design patterns help achieve the requirements defined for the system â The interface design describes how the software communicates with systems that interoperate with it and with humans that use it â The component-level design transforms structural elements of the software architecture into a procedural description of software components (More on next slide)
- 4. 4 From Analysis Model to Design Model (continued) Data/Class Design (Class-based model, Behavioral model) Architectural Design (Class-based model, Flow-oriented model) Interface Design (Scenario-based model, Flow-oriented model Behavioral model) Component-level Design (Class-based model, Flow-oriented model Behavioral model)
- 5. 5 Task Set for Software Design 1) Examine the information domain model and design appropriate data structures for data objects and their attributes 2) Using the analysis model, select an architectural style (and design patterns) that are appropriate for the software 3) Partition the analysis model into design subsystems and allocate these subsystems within the architecture a) Design the subsystem interfaces b) Allocate analysis classes or functions to each subsystem 4) Create a set of design classes or components a) Translate each analysis class description into a design class b) Check each design class against design criteria; consider inheritance issues c) Define methods associated with each design class d) Evaluate and select design patterns for a design class or subsystem (More on next slide)
- 6. 6 Task Set for Software Design (continued) 5) Design any interface required with external systems or devices 6) Design the user interface 7) Conduct component-level design a) Specify all algorithms at a relatively low level of abstraction b) Refine the interface of each component c) Define component-level data structures d) Review each component and correct all errors uncovered 8) Develop a deployment model ï§ Show a physical layout of the system, revealing which components will be located where in the physical computing environment
- 7. 7 Design Quality's Role âą The importance of design is quality âą Design is the place where quality is fostered â Provides representations of software that can be assessed for quality â Accurately translates a customer's requirements into a finished software product or system â Serves as the foundation for all software engineering activities that follow âą Without design, we risk building an unstable system that â Will fail when small changes are made â May be difficult to test â Cannot be assessed for quality later in the software process when time is short and most of the budget has been spent âą The quality of the design is assessed through a series of formal technical reviews or design walkthroughs
- 8. 8 Goals of a Good Design âą The design must implement all of the explicit requirements contained in the analysis model â It must also accommodate all of the implicit requirements desired by the customer âą The design must be a readable and understandable guide for those who generate code, and for those who test and support the software âą The design should provide a complete picture of the software, addressing the data, functional, and behavioral domains from an implementation perspective "Writing a clever piece of code that works is one thing; designing something that can support a long-lasting business is quite another."
- 9. 9 Design Quality Guidelines 1) A design should exhibit an architecture that a) Has been created using recognizable architectural styles or patterns b) Is composed of components that exhibit good design characteristics c) Can be implemented in an evolutionary fashion, thereby facilitating implementation and testing 2) A design should be modular; that is, the software should be logically partitioned into elements or subsystems 3) A design should contain distinct representations of data, architecture, interfaces, and components 4) A design should lead to data structures that are appropriate for the classes to be implemented and are drawn from recognizable data patterns (more on next slide)
- 10. 10 Quality Guidelines (continued) 5) A design should lead to components that exhibit independent functional characteristics 6) A design should lead to interfaces that reduce the complexity of connections between components and with the external environment 7) A design should be derived using a repeatable method that is driven by information obtained during software requirements analysis 8) A design should be represented using a notation that effectively communicates its meaning "Quality isn't something you lay on top of subjects and objects like tinsel on a Christmas tree."
- 11. 11 Design Concepts âą Abstraction â Procedural abstraction â a sequence of instructions that have a specific and limited function â Data abstraction â a named collection of data that describes a data object âą Architecture â The overall structure of the software and the ways in which the structure provides conceptual integrity for a system â Consists of components, connectors, and the relationship between them âą Patterns â A design structure that solves a particular design problem within a specific context â It provides a description that enables a designer to determine whether the pattern is applicable, whether the pattern can be reused, and whether the pattern can serve as a guide for developing similar patterns (more on next slide)
- 12. 12 Design Concepts (continued) âą Modularity â Separately named and addressable components (i.e., modules) that are integrated to satisfy requirements (divide and conquer principle) â Makes software intellectually manageable so as to grasp the control paths, span of reference, number of variables, and overall complexity âą Information hiding â The designing of modules so that the algorithms and local data contained within them are inaccessible to other modules â This enforces access constraints to both procedural (i.e., implementation) detail and local data structures âą Functional independence â Modules that have a "single-minded" function and an aversion to excessive interaction with other modules â High cohesion â a module performs only a single task â Low coupling â a module has the lowest amount of connection needed with other modules (more on next slide)
- 13. 13 Design Concepts (continued) âą Stepwise refinement â Development of a program by successively refining levels of procedure detail â Complements abstraction, which enables a designer to specify procedure and data and yet suppress low-level details âą Refactoring â A reorganization technique that simplifies the design (or internal code structure) of a component without changing its function or external behavior â Removes redundancy, unused design elements, inefficient or unnecessary algorithms, poorly constructed or inappropriate data structures, or any other design failures âą Design classes â Refines the analysis classes by providing design detail that will enable the classes to be implemented â Creates a new set of design classes that implement a software infrastructure to support the business solution
- 14. 14 Types of Design Classes âą User interface classes â define all abstractions necessary for human- computer interaction (usually via metaphors of real-world objects) âą Business domain classes â refined from analysis classes; identify attributes and services (methods) that are required to implement some element of the business domain âą Process classes â implement business abstractions required to fully manage the business domain classes âą Persistent classes â represent data stores (e.g., a database) that will persist beyond the execution of the software âą System classes â implement software management and control functions that enable the system to operate and communicate within its computing environment and the outside world
- 15. The Design Model Data/Class Design Architectural Design Interface Design Component-level Design
- 16. Process Dimension (Progression) Abstraction Dimension Data/Class Elements Interface Elements Architectural Elements Component-level Elements Deployment-level Elements Dimensions of the Design Model Analysis model Design model Low High
- 17. 17 âą The design model can be viewed in two different dimensions â (Horizontally) The process dimension indicates the evolution of the parts of the design model as each design task is executed â (Vertically) The abstraction dimension represents the level of detail as each element of the analysis model is transformed into the design model and then iteratively refined âą Elements of the design model use many of the same UML diagrams used in the analysis model â The diagrams are refined and elaborated as part of the design â More implementation-specific detail is provided â Emphasis is placed on âą Architectural structure and style âą Interfaces between components and the outside world âą Components that reside within the architecture (More on next slide)
- 18. 18 âą Design model elements are not always developed in a sequential fashion â Preliminary architectural design sets the stage â It is followed by interface design and component-level design, which often occur in parallel âą The design model has the following layered elements â Data/class design â Architectural design â Interface design â Component-level design âą A fifth element that follows all of the others is deployment-level design Data/Class Design Architectural Design Interface Design Component-level Design
- 19. 19 Pattern-based Software Design âą Mature engineering disciplines make use of thousands of design patterns for such things as buildings, highways, electrical circuits, factories, weapon systems, vehicles, and computers âą Design patterns also serve a purpose in software engineering âą Architectural patterns â Define the overall structure of software â Indicate the relationships among subsystems and software components â Define the rules for specifying relationships among software elements âą Design patterns â Address a specific element of the design such as an aggregation of components or solve some design problem, relationships among components, or the mechanisms for effecting inter-component communication â Consist of creational, structural, and behavioral patterns âą Coding patterns â Describe language-specific patterns that implement an algorithmic or data structure element of a component, a specific interface protocol, or a mechanism for communication among components ï