slide_04_Analysis_Design microsoft powerpoint

nguyencraft01 13 views 21 slides Sep 04, 2024
Slide 1
Slide 1 of 21
Slide 1
1
Slide 2
2
Slide 3
3
Slide 4
4
Slide 5
5
Slide 6
6
Slide 7
7
Slide 8
8
Slide 9
9
Slide 10
10
Slide 11
11
Slide 12
12
Slide 13
13
Slide 14
14
Slide 15
15
Slide 16
16
Slide 17
17
Slide 18
18
Slide 19
19
Slide 20
20
Slide 21
21

About This Presentation

Analysis_Design


Slide Content

Object- Oriented Analysis and Design Lecture 4: Analysis and Design Overview

Objectives: Analysis and Design Overview Object Oriented Analysis and Design 2 Review the key Analysis and Design terms and concepts Introduce the Analysis and Design process, including roles, artifacts and workflow Explain the difference between Analysis and Design

Analysis and Design in Context The purposes of Analysis and Design are to: Transform the requirements into a design of the system- to- be. Evolve a robust architecture for the system. Adapt the design to match the implementation environment, designing it for performance. Object Oriented Analysis and Design 3

Supplementary Specification Use- Case Model Design Model Data Model Architecture Document Analysis and Design Analysis and Design Overview Glossary Object Oriented Analysis and Design 4

Analysis & Design Overview Topics Key Concepts Analysis and Design Workflow Object Oriented Analysis and Design 5

Analysis Versus Design Object Oriented Analysis and Design 6 Analysis Focus on understanding the problem Idealized design Behavior System structure Functional requirements A small model Design Focus on understanding the solution Operations and attributes Performance Close to real code Object lifecycles Nonfunctional requirements A large model

Design Classes Subsystems Analysis and Design Are Not Top- Down or Bottom- Up Analysis Classes Bottom Up Top Down Use Cases (Define a middle level) Analysis and Design Object Oriented Analysis and Design 7

What Is Architecture? Object Oriented Analysis and Design 8 Software architecture encompasses a set of significant decisions about the organization of a software system. Selection of the structural elements and their interfaces by which a system is composed Behavior as specified in collaborations among those elements Composition of these structural and behavioral elements into larger subsystems Architectural style that guides this organization Grady Booch, Philippe Kruchten, Rich Reitman, Kurt Bittner; Rational (derived from Mary Shaw)

Architecture Constrains Design and Implementation Architecture involves a set of strategic design decisions, rules or patterns that constrain design and construction. Architecture decisions are the most fundamental decisions, and changing them will have significant effects. Architecture Design Implementation Code Object Oriented Analysis and Design 9

Logical View Use-Case View Implementation View End- user Functionality Programmers Software management Process View System integrators Performance Scalability Throughput Deployment View System engineering System topology Delivery, installation communication Analysts/Designers Structure Object Oriented Analysis and Design 10 Software Architecture: The “4+1 View” Model

Analysis & Design Overview Topics Key Concepts Analysis and Design Workflow Object Oriented Analysis and Design 11

Analysis and Design Workflow Analysis Design [Early Elaboration Iteration] [Inception Iteration (Optional)] Define a Candidate Architecture Perform Architectural Synthesis Analyze Behavior Refine the Architecture Define Components Design the Database (Optional) Object Oriented Analysis and Design 12

Analysis and Design Workflow H oạt động phân tích Hoạt động thiết kế [ Đầu pha chi tiết ] [ Pha Inception ( Tùy )] Định nghĩa 1 kiến trúc (có thể có) Tiến hành tổng hợp phần tử kiến trúc Phân tích các hành vi Làm mịn kiến trúc Thiết kế các thành phần Thiết kế CSDL ( Tùy ) Object Oriented Analysis and Design 13

Analysis and Design Activity Overview Architect Designer Object Oriented Analysis and Design 14

Software Architect’s Responsibilities Architect Software Architecture Document The Software Architect leads and coordinates technical activities and artifacts. Reference Architecture Analysis Model Design Model Deployment Model Object Oriented Analysis and Design 15

Designer’s Responsibilities Designer Use- Case Realization Package/ Subsystem Class The designer must know use- case modeling techniques, system requirements, and software design techniques. Object Oriented Analysis and Design 16

Review: Analysis and Design Is Use- Case Driven Use cases defined for a system are the basis for the entire development process. Benefits of use cases: Concise, simple, and understandable by a wide range of stakeholders. Help synchronize the content of different models. Check Balance Customer Withdraw Money Object Oriented Analysis and Design 17

What Is a Use- Case Realization? Class Diagrams Use Case Use- Case Model Design Model Use Case Use-Case Realization Collaboration Diagrams Sequence Diagrams Object Oriented Analysis and Design 18

Analysis and Design in an Iterative Process Iteration n Use Case A Scenarios 1 & 2 Use- Case Realization A Start of iteration End of iteration Use Case B Scenario 1 Use- Case Realization A Use Case A Scenario 3 Use- Case Realization B Iteration n + 1 Object Oriented Analysis and Design 19

Review: Analysis and Design Overview Object Oriented Analysis and Design 20 What is the purpose of the Analysis and Design Discipline? What are the input and output artifacts? Name and briefly describe the 4+1 Views of Architecture. What is the difference between Analysis and Design? What is architecture?

Object Oriented Analysis and Design 21
Tags