A) False B) False C) False D) True E) True F) False

Postel’s law, also known as the robustness principle, is a guideline in software engineering that advises to " be conservative in what you do, be liberal in what you accept from others " 1 . This principle has implications for system design and interaction with external interfaces:

A) Response time of the system is reduced : This is false. Postel’s law does not directly relate to the response time of a system 1 .

B) Implementation effort increases : This is false. Being liberal in what is accepted can actually simplify implementation because the system is designed to handle a wider range of inputs without failure 1 .

C) Usability of the system is reduced : This is false. Postel’s law aims to increase robustness and interoperability, which can enhance usability by making the system more resilient and accommodating 1 .

D) Robustness of the system is increased : This is true. By being conservative in outputs and liberal in inputs, the system becomes more robust, handling a variety of inputs without error 1 .

E) The integrity of the data transferred via interfaces is increased : This is true. Accepting a wide range of inputs and adhering strictly to output specifications helps maintain data integrity across different systems 1 .

F) Availability of the system is reduced due to potentially bad quality of input data : This is false. Postel’s law suggests that the system should be designed to handle poor quality input data gracefully, thus maintaining availability 1 .

Applying Postel’s law helps create systems that are more tolerant of input variations and strict in their outputs, contributing to overall system robustness and reliability 1 .

Considering that the requirements are still being determined, designing components with specific attributes can ensure adaptability and maintainability of the architecture.

B : Weak coupling makes individual components less dependent on each other, enhancing the flexibility and scalability of the system.

C : Strong cohesion ensures that components are designed with a clear purpose and functionality, improving the system ' s integrity and ease of maintenance.

D : Making components open for extension but closed for modification supports the adaptability of the system to changing requirements without disrupting existing functionality.

The Architecture Tradeoff Analysis Method (ATAM) helps evaluate architecture decisions with respect to quality attributes by producing several key artifacts:

B: The concrete quality tree illustrates and organizes the quality attributes specific to the architecture being evaluated, showing how generic quality attributes are refined into measurable scenarios.

C: Description of quality scenarios specifies and documents the scenarios under which the architecture ' s responses are tested against the desired quality attributes.

G: List of the architectural risks identifies potential risks in the architecture that may threaten the system’s ability to meet its quality goals, aiding in proactive risk management.

In template-based architecture documentation, the most important fields are: A. To describe module structures (white boxes) - This involves detailing the internal structure of modules, which is crucial for understanding how software components are implemented and how they interact internally. B. To describe individual architectural modules and their external interfaces (black boxes) - This focuses on the interfaces and interactions of modules with external components, essential for understanding system integrations and dependencies. D. To use a standardized document structure - Standardization in documentation facilitates consistency, readability, and maintainability of documents, which is critical for long-term project management and new team member onboarding.

A) Incorrect B) Correct C) Incorrect D) Incorrect E) Incorrect

In the context of building a tool chain for continuous architecture evaluation and analysis, the following statements can be assessed:

A) Tools for static code analysis do not find all dependencies in the source code. They can find many, but not necessarily all, especially if dynamic programming techniques are used 1 .

B) Several tools for static code analysis can be used to verify compliance with architectural rules. This is one of the primary uses of static code analysis tools 1 .

C) Tools for static code analysis cannot reliably measure cohesion because cohesion is a qualitative aspect of modules that depends on the context and design intent, which static analysis alone cannot fully capture 1 .

D) Tools for static code analysis are not typically used to optimize runtime efficiency . They are more focused on code quality, security, and compliance with coding standards 1 .

E) Tools for dynamic analysis, such as profilers, can be used to optimize static structures . They provide runtime information that can inform decisions about the static structure of the code 1 .

These assessments are based on the iSAQB® SOFTWARE ARCHITECTURE – FOUNDATION LEVEL documents, which provide guidelines on the selection and use of tools for software architecture evaluation and analysis 1 .

A) True B) False C) True D) True

A) The project plan from management is influenced by architectural decisions.

True. Architectural decisions often have significant implications on the project plan, including timelines, resource allocation, and technical approaches 1 .

B) Cost estimates are primarily the responsibility of the architect.

False. While architects may contribute to cost estimates, especially regarding design-related expenses, it is typically the management’s responsibility to oversee and finalize cost estimates for the entire project 2 .

C) Architects advise project management on the definition of work packages.

True. Architects play a crucial role in defining work packages, particularly in ensuring that the technical aspects of the project are accurately captured and planned for 1 .

D) Management and architects cooperate on handling of technical risks.

True. Both management and architects need to work closely to identify, assess, and manage technical risks throughout the project 2 .

A) False B) True C) True D) False

A)  Architectural objectives and project objectives need to be identical.

This is false.  Architectural objectives are concerned with the technical goals and quality attributes of the system, while project objectives are broader and include timelines, budgets, and overall project deliverables 1 2 .

B)  Most of the time, architectural objectives are of a more long-term nature than project objectives.

This is true.  Architectural objectives often focus on the sustainability and maintainability of the system, which are long-term considerations, whereas project objectives may be more immediate and focused on the project’s completion 1 2 .

C)  Architectural objectives and project objectives need to be negotiated between the concerned parties.

True.  Both sets of objectives should align with the stakeholders’ needs and the project’s overall goals, and thus require negotiation to ensure that all parties’ interests are addressed 3 .

D)  Architectural objectives are a subset of project objectives.

This is false. Architectural objectives are not necessarily a subset but are related and should support the project objectives.  They deal specifically with the architecture of the system, which is one aspect of the project