L10-TEXT (CH 10)

Flashcards detailing key concepts, definitions, and terms related to Architectural Design and its processes in software engineering.

Architectural Design Resolution Process

• Develop Design Alternatives

• Evaluate Altnernatives

• Selection Architectural Resolution

• Finalize Into SAD

Developing Architectural Design Alternatives Steps

1. Develop Functional Components

2. Determine Components Based on Quality Attributes

3. Modify An Existing Architecture (If Possible)

4. Elaborate an Architecture Style

5. Transform Conceptual Model

Software Requirements Specification, a document that describes what the software will do.

SRS

Is architectural design better as a team or individually?

Better done individually at first and then bringing together alternatives for evaluation as a team.

Evaluating Architectural Design Alternatives Steps

• Does it satisfy functional requirements.

• Does it satisfy quality attributes.

• Will the architecture result in a great user interface.

• Will the architecture “delight” the customer and users.

Architectural Evaluation Techniques

Profiles, Prototypes

Profiles for EvaluationTechniques

Utilize a “profile,” which is a set of scenarios generated to fit the characteristics of interest.

• Usage profile

• Reliability profile

• Performance profile

Each architecture is evaluated by going through the scenarios in the profile and assessing whether the architecture, if implemented, would satisfy the profile.

Usage Profile

Is a set of scenarios that describes the user requirements (sometimes known as “business” workflow).

Reliability Profile

Is a set of scenarios that portrays the non-functional requirement of how a system behaves to under adverse situations.

Performance Profile

A set of scenarios that portrays the non-functional requirements of how a system behaves under time limit constraints or capacity limit constraints.

Utility Tree

A hierarchical structure mapping out functionalities and scenarios for testing system components.

Advantages / Disadvantages of Prototypes for Architecture Evaluation

Advantages: Can provide measurements and experiential feedbacks

Disadvantages: Prototypes takes resources and time

Scenario

A specific and detailed sequence of events used to explore how a system behaves in particular conditions.

Desk Check

A review method where the author checks their own work for accuracy.

Walkthrough

An informal review conducted by peers to discuss the design.

Inspection

A formal review process involving a team meeting led by a moderator.

Audit

An independent review performed by experts not involved in the original design.

Active Review

A focused inspection that targets specific elements of the design.

Feedback

Information or criticism given to improve design effectiveness.

Adverse Situations

Challenging scenarios that test a system's reliability and performance.

Selecting Architectural Design Alternatives Steps

Evaluate the Pros and Cons of each of the alternatives

Multi-dimensional Analysis/ Scoring Table

SAD

Software Architectural Document, the definitive description of an architecture.

Finalizing SAD Architectural Design Alternatives Steps

The process of ensuring the completed SAD is comprehensive and meets all requirements; satisfies basic design principles and is well-formed, complete, clear, and consistent.

Prototyping Advantages

The benefits derived from creating early versions of a product including usability feedback.

Prototyping Disadvantages

The downsides associated with building prototypes, including time and resource consumption.

Evaluation Profiles

Scenarios used to assess specific characteristics or behaviors of a system.

Review Types

Desk Check, Walkthrough, Inspection, Audit, Active Review