Scribd
Upload
80 views11 pages

The Architecture Process: Memi Lavi

The architecture process involves understanding the system's requirements and non-functional requirements, mapping the components, selecting the technology stack, designing the architecture, writing an architecture document, and supporting the team. The key steps are understanding requirements, mapping components to communicate system functionality, selecting appropriate technologies, designing the architecture, documenting it, and ensuring it remains relevant as the system changes.

Uploaded by

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

The Architecture Process: Memi Lavi

The architecture process involves understanding the system's requirements and non-functional requirements, mapping the components, selecting the technology stack, designing the architecture, writing an architecture document, and supporting the team. The key steps are understanding requirements, mapping components to communicate system functionality, selecting appropriate technologies, designing the architecture, documenting it, and ensuring it remains relevant as the system changes.

Uploaded by

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

The Architecture

Process

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

Process Understand the Non-Functional Requirements

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

Map the Components


• …right after setting the goals…

• 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

Map the Components


• Define Technical & Service Level Attributes

• 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

Map the Components


• Represent the Tasks of the System

• 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 Scenarios


Write Architecture Document
Early
Support the Team
• Grow Ambassadors
The Architecture Understand the System’s Requirements

Process Understand the Non-Functional Requirements

Map the Components

Select the Technology Stack

Design the Architecture

Write Architecture Document

Support the Team

You might also like