Chapter 6 – Architectural Design

1. Chapter 6 – Architectural Design Chapter 6 Architectural design

2. Topics covered • Architectural design decisions • Architectural patterns • Application architectures Chapter 6 Architectural design

3. 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 thesoftware architecture. Chapter 6 Architectural design

4. Architectural design • An early stage of the system design process. • Represents the link between specification and design processes. • It involves identifying major system components and their communications. Chapter 6 Architectural design

5. Example: The architecture of a packing robot control system • This robotic system can pack different kinds of object. • It uses a vision component to pick out objects on a conveyor, • identify the type of object, and select the right kind of packaging. • The system then moves objects from the delivery conveyor to be packaged. It places packaged objects on another conveyor. • The architectural model shows these components and the links between them. Chapter 6 Architectural design

6. Architectural abstraction • You can design software architectures at two levels of abstraction: • Architecture in the small is concerned with the architecture of individual programs. 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. These enterprise systems are distributed over different computers Chapter 6 Architectural design

7. Software architecture importance • Software architecture is important because it affects the performance, robustness, distributability, and maintainability of a system • Individual components implement the functional system requirements. • The nonfunctional requirements influenced by: • The system architecture—the way in which these components are organized and communicate>>> (primary influence) • Individual components >>> (secondary influence) Chapter 6 Architectural design

8. Advantages of explicit architecture • Stakeholder communication • The architecture is a high-level presentation of the system that may be used as a focus for discussion by a range of different stakeholders • System analysis • Means that analysis of whether the system can meet its non-functional requirements is possible. • Large-scale reuse • The system architecture is often the same for systems with similar requirements and so can support large-scale software reuse Chapter 6 Architectural design

9. Block diagrams • System architectures are often modeled using simple block diagrams • Each box in the diagram represents a component. • Boxes within boxes indicate that the component has been decomposed to sub-components. • Arrows mean that data and or control signals are passed from component to component in the direction of the arrows. Chapter 6 Architectural design

10. Architectural representations • Simple, informal block diagrams showing entities and relationships are the most frequently used method for documenting software architectures. • But block diagrams have been criticized because they do not show the types of relationships between entities . • block diagrams are useful for : • communication with stakeholders • project planning. • Block diagram’s problem (/Cons) • Block diagram’s pros Chapter 6 Architectural design

11. Use of architectural models • As a way of facilitating discussion about the system design • 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. 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. • As a way of documenting an architecture that has been designed • The aim here is to produce a complete system model that shows the different components in a system, their interfaces and their connections. Chapter 6 Architectural design

12. Architectural design decisions • Architectural design is a creative process so the process differs depending on the type of system being developed. • It is therefore useful to think of architectural design as a series of decisions to be made rather than a sequence of activities. • During the architectural design process, system architects have to make a number of structural decisions that profoundly affect the system and its development process. Chapter 6 Architectural design

13. Some Architectural design decisions • Is there a generic application architecture that can be used? • How will the system be distributed across a number of cores or processors? • How will the system be decomposed into modules? • How will the architectural design be evaluated? • How should the architecture be documented? Chapter 6 Architectural design

14. Architecture reuse • Systems in the same domain often have similar architectures that reflect domain concepts. • E.g.: Application product lines are built around a core architecture with variants that satisfy particular customer requirements. • The architecture of a system may be designed around one of more architectural patterns or ‘styles’. • An architectural pattern is a description of a system organization such as a client–server organization or a layered architecture. • You should be aware of common patterns, where they can be used, and their strengths and weaknesses Chapter 6 Architectural design

15. Architecture and system characteristics • Performance • Localise critical operations and minimise communications. Use large rather than fine-grain components. • Security • Use a layered architecture with critical assets in the inner layers. • Availability • Include redundant components • Maintainability • Use small, replaceable components. Chapter 6 Architectural design

16. Architectural patterns • Patterns are a means of representing, sharing and reusing knowledge. • An architectural pattern is a stylized description of good design practice, which has been tried and tested in different environments. • Patterns should include information about when they are and when the are not useful. • Patterns may be represented using tabular and graphical descriptions. • Definition Chapter 6 Architectural design

17. Layered architecture • Used to model the interfacing of sub-systems. • Organises the system into a set of layers (or abstract machines) each of which provide a set of services. • Supports the incremental development of sub-systems in different layers. When a layer interface changes, only the adjacent layer is affected. • As layered systems localize machine dependencies in inner layers, this makes it easier to provide multi-platform implementations of an application system. • Only the inner, machine-dependent layers need be re-implemented to take account of the facilities of a different operating system or database. • However, often artificial to structure systems in this way. Chapter 6 Architectural design

18. The Layered architecture pattern Chapter 6 Architectural design

19. A generic layered architecture Chapter 6 Architectural design

20. Example:Thearchitecture of the LIBSYS system Chapter 6 Architectural design

21. As businesses have much in common, their application systems also tend to have a common architecture that reflects the application requirements. E.g. all phone companies need systems to connect calls, manage their network, issue bills to customers, etc.. These commonalities have led to the development of software architectures that describe the structure and organization of particular types of software systems. Application architectures encapsulate the principal characteristics of a class of systems. Definition>>> A generic application architecture is an architecture for a type of software system that may be configured and adapted to create a system that meets specific requirements. Application architectures Chapter 6 Architectural design

22. As a starting point for architectural design. If you are unfamiliar with the type of application that you are developing As a design checklist. If you have developed an architectural design for an application system, you can compare this with the generic application architecture. As a way of organizing the work of the development team. As a means of assessing components for reuse. As a vocabulary for talking about application types. If you are discussing a specific application or trying to compare applications of the same types Use of application architectures Chapter 6 Architectural design

23. Focus here is on transaction processing Transaction processing systems examples: E-commerce systems; Reservation systems. Application type examples Chapter 6 Architectural design

24. Process user requests for information from a database or requests to update the database. From a user perspective a transaction is: Any coherent sequence of operations that satisfies a goal; for example - find the times of flights from London to Paris. Users make asynchronous requests for service which are then processed by a transaction manager. Transaction processing systems • Multiple operations = one goal Chapter 6 Architectural design

25. Transaction processing systems… • An example of a transaction is a customer request to withdraw money from a bank account using an ATM. This involves many operations: • getting details of the customer’s account • checking the balance • modifying the balance by the amount withdrawn • sending commands to the ATM to deliver the cash • Until all of these steps have been completed, the transaction is incomplete and the customer accounts database is not changed. Chapter 6 Architectural design

26. The structure of transaction processing applications a user makes a request to the system through an I/O processing component. The request is processed by some application specific logic. A transaction is created and passed to a transaction manager transaction manager ensured that the transaction is properly completed, it signals to the application that processing has finished. Chapter 6 Architectural design

27. Key points • A software architecture is a description of how a software system is organized. • Architectural design decisions include decisions on the type of application, the distribution of the system, the architectural styles to be used. • Architectural patterns are a means of reusing knowledge about generic system architectures. They describe the architecture, explain when it may be used and describe its advantages and disadvantages. Chapter 6 Architectural design

28. Key points • Models of application systems architectures help us understand and compare applications, validate application system designs and assess large-scale components for reuse. • Transaction processing systems are interactive systems that allow information in a database to be remotely accessed and modified by a number of users. Chapter 6 Architectural design