tailieunhanh - Lecture Software design and architecture – Chapter 21

Lecture 21 – Functional modeling. Models are used during the requirements engineering process to help derive the requirements for a system, during the design process to describe the system to engineers implementing the system and after implementation to document the system’s structure and operation. | SOFTWARE DESIGN AND ARCHITECTURE LECTURE 21 Review ANALYSIS PHASE (OBJECT ORIENTED DESIGN) Functional Modeling Use case Diagram Description Outline ANALYSIS PHASE (OBJECT ORIENTED DESIGN) Functional Modeling Activity Diagrams System Modeling System modeling is the process of developing abstract models of a system, with each model presenting a different view or perspective of that system. System modeling has generally come to mean representing the system using some kind of graphical notation, which is now almost always based on notations in the Unified Modeling Language (UML). System Modeling Models are used during the requirements engineering process to help derive the requirements for a system, during the design process to describe the system to engineers implementing the system and after implementation to document the system’s structure and operation. Analysis Models At an early stage in the specification of a system, we need to decide on the system boundaries. This involves working | SOFTWARE DESIGN AND ARCHITECTURE LECTURE 21 Review ANALYSIS PHASE (OBJECT ORIENTED DESIGN) Functional Modeling Use case Diagram Description Outline ANALYSIS PHASE (OBJECT ORIENTED DESIGN) Functional Modeling Activity Diagrams System Modeling System modeling is the process of developing abstract models of a system, with each model presenting a different view or perspective of that system. System modeling has generally come to mean representing the system using some kind of graphical notation, which is now almost always based on notations in the Unified Modeling Language (UML). System Modeling Models are used during the requirements engineering process to help derive the requirements for a system, during the design process to describe the system to engineers implementing the system and after implementation to document the system’s structure and operation. Analysis Models At an early stage in the specification of a system, we need to decide on the system boundaries. This involves working with system stakeholders to decide what functionality should be included in the system and what is provided by the system’s environment. We need to decide that automated support for some business processes should be implemented but others should be manual processes or supported by different systems. Modeling System Interactions All systems involve interaction of some kind. user interaction, which involves user inputs and outputs, interaction between the system being developed Modeling user interaction is important as it helps to identify user requirements. Modeling System interactions For modeling system interactions we can use Use case modeling, which is mostly used to model interactions between a system and external actors (users or other systems). Activity diagram Activity Diagram Activity diagrams are for modeling business processes, workflows, data flows, and complex algorithms. Based on data flow models – a graphical representation (with a Directed Graph) of how data move around

• Đồ họa - Thiết kế - Flash
• Software design
• Software design and architecture
• Software architecture
• Software architectural design
• Object oriented design
• Software development
• Software design methods
• Distributed software architecture
• Data flow software architecture
• Software requirement specification
• Software development activities
• Component based software engineering