ASEP Architectural Design 2 — Questions and Answers
Question 1: Which architectural view is primarily concerned with depicting the allocation of software components to hardware nodes?
- Logical view
- Deployment view (Correct answer)
- Process view
- Development view
Correct answer: Deployment view
The deployment view maps software artifacts to hardware infrastructure, showing which components run on which physical or virtual nodes.
In systems architecture, the deployment view (also called the physical view) specifically addresses how software components are allocated to hardware nodes. The logical view shows functional decomposition, the process view shows concurrency and synchronization, and the development view shows the organization of the actual software modules. The deployment view is critical for understanding performance, availability, and security constraints.
Question 2: What is the primary purpose of an Interface Control Document (ICD) in systems engineering?
- To define the project schedule
- To formally specify interfaces between system elements (Correct answer)
- To document test procedures
- To list stakeholder requirements
Correct answer: To formally specify interfaces between system elements
An ICD formally defines and controls the interfaces between two or more system elements, ensuring interoperability and compatibility.
An Interface Control Document (ICD) is a formal specification that defines the interface between two or more system elements. It includes physical connections, data formats, protocols, electrical characteristics, and other interface parameters. ICDs are essential for configuration management and ensuring that independently developed subsystems can integrate successfully. They serve as binding agreements between development teams working on different system components.
Question 3: In a modular architecture, what does 'high cohesion' within a module indicate?
- The module has many dependencies on other modules
- The module's internal elements are strongly related and focused on a single purpose (Correct answer)
- The module is large and complex
- The module interfaces with external systems
Correct answer: The module's internal elements are strongly related and focused on a single purpose
High cohesion means the elements within a module are closely related and work together toward a single, well-defined purpose.
High cohesion is a desirable design property where all elements within a module contribute to a single, well-defined task or responsibility. This contrasts with low cohesion, where a module performs many unrelated functions. High cohesion, combined with low coupling (few dependencies between modules), leads to systems that are easier to understand, maintain, test, and modify. The INCOSE Systems Engineering Handbook emphasizes these principles as fundamental to good architectural design.
Question 4: What architectural pattern is most appropriate when a system must process data through a series of sequential transformations?
- Client-server pattern
- Pipe-and-filter pattern (Correct answer)
- Publish-subscribe pattern
- Layered pattern
Correct answer: Pipe-and-filter pattern
The pipe-and-filter pattern processes data through a chain of sequential processing steps (filters) connected by data channels (pipes).
The pipe-and-filter architectural pattern is ideal for systems requiring sequential data transformations. Each filter performs one transformation, and pipes connect filters to pass data from one stage to the next. This pattern promotes reusability (filters can be rearranged), parallelism (independent filters can execute concurrently), and maintainability (filters are self-contained). Examples include signal processing chains, compiler pipelines, and data ETL processes.
Question 5: Which analysis technique evaluates the impact of a single component failure on overall system functionality?
- Fault Tree Analysis (FTA)
- Failure Mode and Effects Analysis (FMEA) (Correct answer)
- Monte Carlo simulation
- Design Structure Matrix (DSM)
Correct answer: Failure Mode and Effects Analysis (FMEA)
FMEA systematically examines each potential failure mode of every component and assesses its effect on the overall system.
Failure Mode and Effects Analysis (FMEA) is a bottom-up analysis technique that systematically identifies potential failure modes for each component and evaluates their effects on subsystem and system-level performance. Unlike Fault Tree Analysis (FTA), which works top-down from a system failure to find root causes, FMEA starts at the component level and traces effects upward. FMEA also assesses severity, occurrence probability, and detection capability to prioritize risks using a Risk Priority Number (RPN).
Question 6: What is the main benefit of defining architectural 'views' according to the ISO/IEC/IEEE 42010 standard?
- It reduces the number of required documents
- It addresses the concerns of different stakeholders through targeted representations (Correct answer)
- It eliminates the need for trade studies
- It guarantees the system will meet performance requirements
Correct answer: It addresses the concerns of different stakeholders through targeted representations
ISO/IEC/IEEE 42010 uses views and viewpoints to address specific stakeholder concerns, ensuring each audience gets the information relevant to their needs.
ISO/IEC/IEEE 42010 (Systems and software engineering — Architecture description) establishes a framework where an architecture description consists of multiple views, each conforming to a viewpoint that frames specific stakeholder concerns. This ensures that operators see operational views, developers see structural views, and managers see schedule and cost views. The standard recognizes that no single representation can adequately address all stakeholder concerns, making multiple targeted views essential for effective architecture communication.
ASEP Architectural Design 2
Which architectural view is primarily concerned with depicting the allocation of software components to hardware nodes?