1.★ Midterm Spring 2010Lecture 225 marks
comparison of software architecture and Building architecture
Show answerJawab dekhein
Software architecture is similar to building architecture. When a house is built, the architect, general contractor, electrician, plumber, interior designer and landscaper each have a different view of the structure; the views are drawn differently but are related, and together they describe the building's architecture. In the same way, software architecture establishes the overall structure of a software system and is described through several related views for different stakeholders (for example logical, process, development and physical views). In both cases the architecture is decided early, is expensive to change later, and must satisfy functional and non-functional needs. A difference is that software is intangible and easier to change, so its architecture can be refined iteratively.
2.★ Midterm Spring 2010Lecture 225 marks
Narrate some of the architectural design guidelines that can help in addressing non-functional requirements challenges.
Show answerJawab dekhein
Software architecture must address non-functional as well as functional requirements. Guidelines: Performance - localise operations to minimise sub-system communication, i.e. use self-contained modules so inter-module communication is minimal. Security - use a layered architecture with critical assets in the inner layers. Safety - isolate safety-critical components (keep them in a small number of sub-systems). Availability - build in redundancy, with redundant components in the architecture. Maintainability - keep the architecture simple, using fine-grain, self-contained components.
3.★ Midterm 2006Lecture 22
Discuss briefly the architectural attributes of software?
Show answerJawab dekhein
Software architecture must address non-functional as well as functional requirements. Guidelines: Performance - localise operations to minimise sub-system communication, i.e. use self-contained modules so inter-module communication is minimal. Security - use a layered architecture with critical assets in the inner layers. Safety - isolate safety-critical components (keep them in a small number of sub-systems). Availability - build in redundancy, with redundant components in the architecture. Maintainability - keep the architecture simple, using fine-grain, self-contained components.
4.★ Final term Fall 2004Lecture 2210 marks
What is Software Architecture? What is its importance? Describe briefly.
Show answerJawab dekhein
Software architecture is the high-level structure of a software system: the system decomposed into components (architectural elements: processing, data and connecting elements), the externally visible properties of those components and the relationships/interactions between them, organized according to an architectural style. It is the result of the architectural design process, which identifies the subsystems and the framework for their control and communication. Importance: it is a vehicle for communication among stakeholders (a shared, high-level view of the system); it captures early design decisions that strongly affect performance, robustness, security, maintainability and distributability, so it allows analysis of whether the system can meet its non-functional requirements before it is built; it guides the division of work and development, since teams can build subsystems against defined interfaces; it supports large-scale reuse, because a good architecture can be reused across systems with similar requirements; and it helps manage complexity and change over the system's life.