Introduction to Software Engineering (2+1 SWS) Winter Term 2009 / 2010 Dr. Michael Eichberg Vertretungsprofessur Software Engineering Department of

Transcription

1 Introduction to Software Engineering (2+1 SWS) Winter Term 2009 / 2010 Dr. Michael Eichberg Vertretungsprofessur Software Engineering Department of Computer Science Technische Universität Darmstadt

2 Dr. Michael Eichberg Fachgebiet Software Engineering Department of Computer Science Technische Universität Darmstadt Introduction to Software Engineering System Models

3 Artifacts That May Be Started In the Elaboration Phase Domain Model Visualization of the domain concepts Design Model Description of the logical design using class diagrams, object interaction diagrams, package diagrams... Software Architecture Document Summary of key architectural issues and their resolution in the design Data Model E.g., database schemas, mapping strategies between object and nonobject representations Repetition OOA/D - Case Studies - Setup 3 } (System Models)

4 System models are used to document technical system requirements. Excursion - System Models 4 System models represent the system from a specific perspective and are abstractions of the system being studied These models usually use graphical notations which are more understandable than detailed natural language descriptions System models are often a bridge between analysis and design.

5 High-level Architectural Models describes the environment of a system; i.e. those systems with which the system under construction communicates. Excursion - System Models 5 The main purpose of a highlevel architectural model is to determine the system s boundaries; these models typically use informal notations and are often drawn using boxes and lines. Search Functionality University Website Personnel administration system Alumni system E.g. the website uses a personnel administration system to provide information about the current staff.

6 Data-flow models show how data is processed by a system. Data-flow models are often used when designing business systems that are primarily driven by data. dox Excursion - System Models Will be discussed in one of the following lectures. 6 functional processing Data A doy data movement Data B StoreV data stores

7 Data-flow models show how data is processed by a system. Data-flow models are often used when designing business systems that are primarily driven by data. Order details and blank order form Complete order form Excursion - System Models 7 Example completed order form Validate order Send to supplier checked and signed order and notification signed order form signed order form Record order signed order form Adjust available budget order details order amount and account details Orders file Budget file

8 State machine models describe how a system responds to internal or external events. A model shows system states and events that cause transitions from one state to another. State machine models are often used for modeling real-time systems. Idle initial state action / event keypressed finished final state shutdown Running Excursion - System Models Will be discussed in one of the following lectures. 8 name state

9 Entity-Relationship Models are used for the design of the high-level conceptual data model (they are still used but today UML is more common). Excursion - System Models 9 Number of Employees Name Department Number 1 1 WORKS FOR N 1 SUPERVISION N MANAGES 1 Start Date Employee Name Address Salary SSN Sex

10 Petri Nets are a formal, graphical, executable technique for the specification and analysis of concurrent, discrete-event dynamic systems. Excursion - System Models 10 Petri nets are used for modeling systems with concurrency and resource sharing. P1 send message receive ack receive message send ack P2

11 Modeling 11 In the following, we primarily introduce the UML notation for modeling the static structure and the dynamic behavior of a program. After that we discuss how to assign responsibilities to classes during modeling using the UML notations.

12 Modeling 12 In the following, we primarily introduce the UML notation for modeling the static structure and the dynamic behavior of a program. After that we discuss how to assign responsibilities to classes during modeling using the UML notations. To model the static structure we will primarily use: UML Class Diagrams

13 Modeling 13 In the following, we primarily introduce the UML notation for modeling the static structure and the dynamic behavior of a program. After that we discuss how to assign responsibilities to classes during modeling using the UML notations. To model the dynamic behavior we will primarily use: UML Sequence Diagrams, Communication Diagrams, Object Diagrams,...