- The Architect's Mindset
- The Architecture Process
- Working with System Requirements
- Types of Applications
- Selecting Technology Stack
- Meet the *-ilities
- Component's Architecture
- Design Patterns 101
- System Architecture
- External Considerations
- Architecture Document
- Case Study
- Advanced Architecture Topics
- Soft Skills
- Infrastructure Architect ( Servers, VMs, Network, Storage)
- Software Architect, Solution Architect or System architect ( to be discussed later)
- Enterprise Architect ( Works with CEO,CIO.... Streamlines the IT to support business)
Developers Knows What CAN Be Done
Architect Knows What SHOULD Be Done.
Baseline Requirements:
- Fast (Throughput)
- Secure (Security)
- Reliable ( No single point of failure)
- Easy to maintain (Scalability)
-
Understand the System's Requirements (What should the system do?)
-
Understand the Non-Functional Requirements (Define Technical & Service Level Attributes # of Users,Loads,Volumes,Performance)
-
Map the Componenets (Represent the Tasks of the System. 2 Goals - System Functionality, Communicate your undertanding to the client, Non-Technical)
-
Select the Technology Stack (Back End, FrontEnd , Data Store)
-
Design the Architecture
-
Write the Architecture Document
-
Support the Team
-
what the system should do (Funcional requirements).
-- business flow.
-- business services.
-- user interfaces. -
what should the system deal with.(Non-functional Requirements).
-- Performance.
-- Load
-- Data Volume.
-- Concurrent Users.
-- SLA.
What is the required performane for this system? Fast...
- Latency.
-- How much time does it take to perform a single task (1 second). - Through put
-- how many users can be saved in the database in a minute. (well designed app -1000usrs/min). - Load
-- Quantity of work without crashing. ( 5000 usrs without crashing) - Data Volume --