Scribd
Upload
58 views10 pages

S4 - The Architecture Process

The document outlines the architecture process which includes understanding requirements, mapping components, selecting technology, designing architecture, documenting it, and supporting the team. It emphasizes understanding non-functional requirements and unknown scenarios early.

Uploaded by

Hussein Said
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
58 views10 pages

S4 - The Architecture Process

The document outlines the architecture process which includes understanding requirements, mapping components, selecting technology, designing architecture, documenting it, and supporting the team. It emphasizes understanding non-functional requirements and unknown scenarios early.

Uploaded by

Hussein Said
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 10

The Architecture

Process

Memi Lavi
www.memilavi.com
The Understand the System’s Requirements

Architecture Understand the Non-Functional Requirements

Process Map the Components

Select the Technology Stack

Design the Architecture

Write Architecture Document

Support the Team


Understand the System’s Understand the System’s Requirements
Requirements

Understand the Non-Functional


Requirements
• …right after setting the goals…
Map the Components

• Requirements = What the System Should Do


Select the Technology Stack

• Usually Defined by the System Analyst


Design the Architecture

Write Architecture Document

Support the Team


Understand the System’s Understand the Non-Functional Requirements
Requirements

Understand the Non-Functional


Requirements
• Define Technical & Service Level Attributes
Map the Components

• ie. # of Users, Loads, Volumes, Performance


Select the Technology Stack

• Not Always Known to the Client or Analyst


Design the Architecture
• Much More Important Than Regular Requirements
Write Architecture Document

Support the Team


Understand the System’s Map the Components
Requirements

Understand the Non-Functional


Requirements
• Represent the Tasks of the System
Map the Components

• Two Goals:
Select the Technology Stack

• Understand the System Functionality


Design the Architecture
• Communicate Your Understanding to the Client
Write Architecture Document
• Non-Technical
Support the Team
Understand the System’s Select the Technology Stack
Requirements

Understand the Non-Functional


Requirements

Map the Components

Select the Technology Stack

Design the Architecture

Write Architecture Document


• Usually for Back End, Front End, Data Store
Support the Team
• A Lot of Factors, Choose Wisely!
Understand the System’s
Requirements

Understand the Non-Functional


Requirements

Map the Components

Select the Technology Stack

Design the Architecture


Design
the
Write Architecture Document Architecture
Support the Team
Understand the System’s
Requirements

Understand the Non-Functional


Requirements

Map the Components • Describes the Process and the Architecture

Select the Technology Stack • Must be Relevant for All Participants

Design the Architecture


Write
the
Write Architecture Document Architecture
Support the Team
Document
Understand the System’s
Requirements

Understand the Non-Functional


Requirements

Map the Components


Support
Select the Technology Stack the
Design the Architecture
Team
•
Write Architecture Document The Architecture will change a lot

Support the Team


• Make sure it will stay relevant
Conclusion Understand the System’s Requirements

Understand the Non-Functional Requirements

Map the Components

Select the Technology Stack

Design the Architecture

• Learn about Unknown


Write Architecture Document
Scenarios Early

• Grow Ambassadors Support the Team

You might also like