Danh mục

Lecture Introduction to software engineering - Week 6: Architectural design

Số trang: 63      Loại file: pdf      Dung lượng: 1.38 MB      Lượt xem: 22      Lượt tải: 0    
Xem trước 7 trang đầu tiên của tài liệu này:

Thông tin tài liệu:

Lecture Introduction to software engineering - Week 6: Architectural design. In this chapter, you will learn to: Architectural design decisions, architectural views, architectural patterns, application architectures.
Nội dung trích xuất từ tài liệu:
Lecture Introduction to software engineering - Week 6: Architectural design Week 6: Architectural Design Nguyễn Thị Minh Tuyền Adapted from slides of Ian Sommerville CuuDuongThanCong.com https://fb.com/tailieudientucntt Architectural Design 1. What is it? 2. Who does it? 3. Why is it important? 4. What are the steps? 5. What is the work product? 6. How do I ensure that I’ve done it right? CuuDuongThanCong.com https://fb.com/tailieudientucntt Topics covered 1. Architectural design decisions 2. Architectural views 3. Architectural patterns 4. Application architectures 3 CuuDuongThanCong.com https://fb.com/tailieudientucntt Software architecture £ The design process for identifying the sub-systems making up a system and the framework for sub- system control and communication is architectural design. £ The output of this design process is a description of the software architecture. 4 CuuDuongThanCong.com https://fb.com/tailieudientucntt Architectural design £ Is an early stage of the system design process. £ Represents the critical link between specification and design processes. £ Often carried out in parallel with some specification activities. £ Involves identifying major system components and their communications. 5 CuuDuongThanCong.com https://fb.com/tailieudientucntt Architecture of a packing robot control system Vision system Object Arm Gripper identification controller controller system Packaging selection system Packing Conveyor system controller 6 CuuDuongThanCong.com https://fb.com/tailieudientucntt Architectural abstraction £ Architecture in the small is concerned with the architecture of individual programs. p At this level, we are concerned with the way that an individual program is decomposed into components. £ Architecture in the large is concerned with the architecture of complex enterprise systems that include other systems, programs, and program components. p These enterprise systems are distributed over different computers, which may be owned and managed by different companies. 7 CuuDuongThanCong.com https://fb.com/tailieudientucntt Advantages of explicit architecture £ Stakeholder communication p Architecture may be used as a focus of discussion by system stakeholders. £ System analysis p Means that analysis of whether the system can meet its non-functional requirements is possible. £ Large-scale reuse p The architecture may be reusable across a range of systems. 8 CuuDuongThanCong.com https://fb.com/tailieudientucntt Architectural representations £ Simple, informal block diagrams showing entities and relationships are the most frequently used method for documenting software architectures. £ But these have been criticized because they p lack semantics, p do not show the types of relationships between entities nor the visible properties of entities in the architecture. 9 CuuDuongThanCong.com https://fb.com/tailieudientucntt Box and line diagrams £ Very abstract p they do not show the nature of component relationships nor the externally visible properties of the sub-systems. £ However, useful for communication with stakeholders and for project planning. 10 CuuDuongThanCong.com https://fb.com/tailieudientucntt Use of architectural models £ Facilitating discussion about the system design p A high-level architectural view of a system is useful for communication with system stakeholders and project planning because it is not cluttered with detail. p Stakeholders can relate to it and understand an abstract view of the system. They can then discuss the system as a whole without being confused by detail. £ Documenting an architecture that has been designed p The aim here is to produce a complete system model that shows the different components in a system, their interfaces and their connections. 11 CuuDuongThanCong.com https://fb.com/tailieudientucntt Topics covered 1. Architectural design decisions 2. Architectural views 3. Architectural patterns 4. Application architectures 12 ...

Tài liệu được xem nhiều: