Architect Role

Get Started. It's Free
or sign up with your email address
Rocket clouds
Architect Role by Mind Map: Architect Role

1. Outline the Architecture

1.1. Input

1.1.1. Requirements

1.1.1.1. Functional requirements

1.1.1.2. Non-functional requirements

1.1.1.2.1. Performance

1.1.1.2.2. Security

1.1.1.2.3. Scalable

1.1.2. Use Case

1.1.3. Use Case Model

1.1.4. Glossary

1.2. Steps

1.2.1. Identify architectural goals

1.2.2. Identify architecturally significant requirements

1.2.3. Identify constraints on the architecture

1.2.3.1. Network topology

1.2.3.2. Database vendor

1.2.3.2.1. Oracle

1.2.3.2.2. MS SQL

1.2.3.2.3. MySQL

1.2.3.2.4. DB2

1.2.3.3. Web environment

1.2.3.4. Servers

1.2.3.4.1. Hardware

1.2.3.4.2. OS

1.2.4. Identify key abstractions

1.2.4.1. Domain Object

1.2.5. Identify reuse opportunities

1.2.5.1. Architectural frameworks

1.2.5.2. Architectural mechanisms

1.2.5.3. Architectural decisions

1.2.5.4. Constraints

1.2.5.5. Applications

1.2.5.6. Components

1.2.6. Define approach for partitioning the system

1.2.6.1. N-Layer

1.2.7. Define approach for deploying the system

1.2.7.1. Network

1.2.8. Identify architectural mechanisms

1.2.8.1. Persistence

1.2.8.2. Communication

1.2.8.2.1. Protocol

1.2.8.2.2. Size of message

1.2.8.2.3. Latency

1.2.8.2.4. Synchronicity

1.2.9. Identify interfaces to external systems

1.2.10. Verify architectural consistency

1.2.11. Capture and communicate architectural decisions

1.3. Output

1.3.1. Technical Notebook

2. Refine the Architect

2.1. Input

2.1.1. Technical Notebook

2.1.2. Requirements

2.1.3. Use Case

2.1.4. Use Case Model

2.1.5. Domain Object

2.1.6. Glossary

2.2. Steps

2.2.1. Refine architectural goals and architecturally significant requirements

2.2.2. Identify architecturally and significant design elements

2.2.2.1. Components

2.2.2.2. Classes

2.2.2.3. Design Patterns

2.2.2.4. External Interface

2.2.3. Refine architectural mechanisms

2.2.4. Identify additional reuse opportunities

2.2.5. Validate the architecture

2.2.6. Map the software to the hardware

2.2.7. Communicate decisions

2.3. Output

2.3.1. Technical Notebook

2.3.1.1. Deployment Diagram

2.3.1.2. Component Diagram

2.3.1.3. Sequence Diagram

2.3.1.4. Class Diagram

2.3.1.5. Data Model

2.3.1.6. UI Specification

2.3.1.7. Glossory