Prototypes and Proof-of-Concept Systems
Prototypes and proof-of-concept systems are used to help evaluate an architecture.
They are most often used to:
- Reduce technical risks when a new or unfamiliar technology or technique is being considered.
- Help design the user interface.
Prototype
A prototype is a functional subset of the system.
It implements part of the proposed system to help explore or evaluate selected aspects of the design.
Purpose of Prototypes
Prototypes can help stakeholders examine aspects of the proposed system before completing the full implementation.
Generally Some prototypes need sufficiently sophisticated scalability to produce meaningful results.
Such prototypes can be expensive and time-consuming to develop.
Proof-of-Concept System
A proof-of-concept system consists of code designed to demonstrate that a risky element of the proposed architecture is feasible.
It also helps identify potential problems and pitfalls.
Purpose of Proof-of-Concept Systems
- Demonstrate the feasibility of a proposed architectural element.
- Investigate new or unfamiliar technologies and techniques.
- Identify problems before committing to the complete implementation.
- Reduce technical risks.
Prototype vs Proof-of-Concept System
| Aspect | Prototype | Proof-of-Concept System |
|---|---|---|
| Definition | A functional subset of the system. | Code designed to demonstrate the feasibility of a risky architectural element. |
| Main Purpose | Explore aspects of the proposed system and help design the user interface. | Test feasibility and identify potential problems or pitfalls. |
| Scope | A subset of the system’s functionality. | A particular risky element of the proposed architecture. |
| Limitation | May require sophisticated scalability to produce meaningful results. | Focuses on demonstrating feasibility rather than implementing the entire system. |
Skeleton Systems
A skeleton system implements the architectural structure of a system while containing only a minimal subset of its functionality.
Skeleton systems as the ultimate form of architectural validation.
Purpose of Skeleton Systems
A skeleton system helps verify whether the overall system structure is sound.
The minimal functionality should allow a small amount of end-to-end processing to occur.
This allows the architecture to be evaluated through an executable system structure rather than only through documents or individual components.
Characteristics of Skeleton Systems
- Implements the system’s architectural structure.
- Contains only a minimal subset of functionality.
- Supports a small amount of end-to-end processing.
- Helps demonstrate that the overall structure is sound.
- Represents the most expensive form of architectural validation discussed in the lecture.
Comparing Architectural Validation Techniques
| Technique | Main Purpose | Cost or Limitation |
|---|---|---|
| Presentation | Communicate the proposed architecture and encourage discussion. | Only shallow analysis is possible. |
| Formal Review | Examine documents, discuss concerns, and agree on actions. | Requires preparation and a structured review meeting. |
| Scenario-Based Assessment | Evaluate architectural decisions against scenarios and quality attributes. | Requires relevant scenarios and architectural analysis. |
| Prototype | Explore a functional subset of the system. | Can be expensive and time-consuming when sophisticated scalability is required. |
| Proof-of-Concept System | Demonstrate the feasibility of a risky architectural element. | Focuses on selected technical risks rather than the complete system. |
| Skeleton System | Validate the overall architectural structure through limited end-to-end processing. | The most expensive form of architectural validation in the lecture. |
Summary
Architectural validation can range from informal presentations to building an executable skeleton system.
- Presentations communicate architectural decisions.
- Formal reviews provide structured examination and discussion.
- Scenario-based assessment evaluates architecture against quality attributes.
- Prototypes explore a functional subset of the system.
- Proof-of-concept systems investigate the feasibility of risky architectural elements.
- Skeleton systems validate the overall architecture through minimal end-to-end processing.