1. Chapter 7-- Software Engineering 7.5 Tools of the Trade 楊家愉 應數一 100701014

2. Introduction In this section, we introduce : Modeling techniques ( 設計程式的技術 / 方法 ) Notational systems ( 標誌系統 )

3. Some Old Friends Although the imperative paradigm seeks to build software in terms of procedures, a way of identifying those procedures is to consider the data to be manipulated rather than the procedures themselves. The theory is that by studying how data moves through a system, one identifies the points at which either data formats are altered or data paths merge and split.

4. Some Old Friends Dataflow diagram means of representing the information gained form such dataflow studies. Arrows – represent data paths Ovals- represent points at which data manipulation occur Rectangles – represent data sources and stores

5. Affect of data flow diagram Not only assist in identifying procedures during the design stage of software development, but also useful when trying to gain an understanding of the proposed system during the analysis stage.

6. Data Flow Diagram

7. Data dictionary Has been used for years by software engineers Is a central repository of information about the data items appearing throughout a software system. Information of it Constitutes: 1.Valid entries in each item 2.Where the item is stored 3.Where the item is referenced in the software

8. Data dictionary Goal: – Improve communication between the stakeholders of a software system and the software engineer. – Converting all of the stakeholder needs into a requirements specification. – Helps ensure that the fact that part numbers are net really numeric will be revealed. – To establish uniformity throughout the system.

9. Unified Modeling Language Dataflow diagrams and data dictionaries Tools in the software engineering arsenal well before emergence of the object-oriented paradigm Continued to find useful roles even though the imperative paradigm

10. Has been developed with the object-oriented paradigm in mind. The tool that attempts merely to capture the image of the proposed system from the user’s point of view Unified Modeling Language

11. Use Case Diagram Depicts the proposed system as a large rectangle in which interactions between the system Its users are represented as ovals and users of the system are represented as stick figures.

12. Use Case Diagram

13. Class diagram Is a notational system for representing the structure of classes and relationships between classes. It can indicate how many instances of one class may be associated with instances of another

14. One-to-one relationship

15. One-to-many relationship

16. Many-to-many relationship

17. Interaction diagrams Sequence diagram Depicts the communication between the individuals that are involved in performing a task. Each rectangle together with its dashed line is called a life line.

18. Interaction diagram

19. Interaction fragments Are used to represent alternative sequences within one diagram. CRC (class-responsibility-collaboration) cards Is simply a card, on which the description of an object is written

20. Design Patterns Predeveloped model for solving a recurring problem in software design Adapter pattern provides a solution to a problem that often occurs when constructing software from prefabricated modules.

21. Design Patterns Decorator pattern means of designing a system that performs different combinations of the same activities depending on the situation at the time

22. Design Pattern The results of progress in design pattern development are reflected in the library of tools provided in today’s software development packages such as the Java programming environments provided by Oracle and the.NET Framework provided by Microsoft.

23. Design Pattern The origins of design patterns lie in the research of Christopher Alexander ( 克里斯托弗‧亞歷山 大 ) in traditional architecture. His goal was to identify features. Today, many of his ideas have been incorporated into software design and his work continues to be an inspiration for many software engineers.