The document outlines the roles and responsibilities of an architect in developing software, including facilitating communication between stakeholders, defining functional and non-functional requirements, designing the overall architecture and system core, eliciting customer feedback, and making decisions that affect the entire lifetime of a system from inception to maintenance. The architect is responsible for problem definition, data modeling, architecture design, and ensuring the system meets requirements through acceptance tests.

3. •
•
•
•
•
•
•
•
•

7. •
•
•
•
•
•

8. Customer
Architect
Marketing
Developer
Modeler
Perduce
Manager
Role of
Architect
Facilitate
Communication

9. •
•
•

10. •
•
•
•

11. •
•
•
•
•

12. •
•
•
•

13. •
•

15. •
•
•
•
•
Architecture

16. Problem
Definition
Functional
Requirements
Non-functional
Requirements
Data Models
Code
Acceptance
Tests
Architecture
Design
Problem Solution

17. Software
concept
Preliminary
requirements
analysis
Develop
a version
Deliver a
version
Design of
architecture
and system core
Elicit
customer
feedback
Incorporate
customer
feedback

18. Architecture
Death
AlterationVision
Inception
Operation
Development
Legacy
operation
Maintenance
Architectural decisions
affect the whole lifetime
of a system

19. Structure
Behavior
Interaction
Deployment
Non-functional
Decision
Implementation