Viewpoints and perspectives
•Download as PPTX, PDF•
0 likes•128 views
The document describes a typical profile of an "architecture offender" as someone who puts engineering before other concerns, practices CV-driven development, employs defensive programming, thinks documentation skills are unimportant, fails to consider alternatives, and does not believe in architecture definition methodologies. It then discusses using viewpoints and perspectives to better define architecture, presenting an architectural framework and describing common viewpoints like context, functional, information, and deployment. It notes the importance of addressing cross-cutting concerns like security, performance, and evolution through perspectives.
Recommended
More Related Content
Similar to Viewpoints and perspectives
Similar to Viewpoints and perspectives (20)
More from Vidas Vasiliauskas
More from Vidas Vasiliauskas (11)
Recently uploaded
Recently uploaded (20)
Viewpoints and perspectives
- 1. USING VIEWPOINTS AND PERSPECTIVES TO DEFINE ARCHITECTURE
- 3. • Puts engineering in front of everything else TYPICAL ARCHITECTURE OFFENDER PROFILE
- 4. • Puts engineering in front of everything else • Practices CV driven development TYPICAL ARCHITECTURE OFFENDER PROFILE
- 5. • Puts engineering in front of everything else • Practices CV driven development • Employs defensive programing for own good TYPICAL ARCHITECTURE OFFENDER PROFILE
- 6. • Puts engineering in front of everything else • Practices CV driven development • Employs defensive programing for own good • Thinks that whiteboard and documentation skills are for losers TYPICAL ARCHITECTURE OFFENDER PROFILE
- 7. • Puts engineering in front of everything else • Practices CV driven development • Employs defensive programing for own good • Thinks that whiteboard and documentation skills are for losers • Does not consider alternatives TYPICAL ARCHITECTURE OFFENDER PROFILE
- 8. • Puts engineering in front of everything else • Practices CV driven development • Employs defensive programing for own good • Thinks that whiteboard and documentation skills are for losers • Does not consider alternatives • Does not believe in architecture definition methodologies TYPICAL ARCHITECTURE OFFENDER PROFILE
- 10. ARCHITECTURE AS A TEAM EFFORT
- 12. INCREASING SUCCESS OF ARCHITECTURE DEFINITION VIEWPOINTS AND PERSPECTIVES
- 13. INCREASING SUCCESS OF ARCHITECTURE DEFINITION VIEWPOINTS AND PERSPECTIVES by Nick Rozanski and Eoin Woods
- 20. ARCHITECTURAL FRAMEWORK SystemArchitecture Architectural description Stakeholder Concern 1..N 1..N0..N Documents architecture for 1..N Has an
- 22. CLASS OBJECT
- 24. VIEWPOINTS
- 32. VIEW AS AN OUTPUT IS ARCHITECTURAL MODELS
- 36. ARCHITECTURAL FRAMEWORK SystemArchitecture Architectural description Stakeholder Concern 1..N 1..N0..N Documents architecture for 1..N Has an
- 37. ARCHITECTURAL FRAMEWORK SystemArchitecture Architectural description Stakeholder ConcernView 1..N 1..N0..N Documents architecture for 1..N 1..N Has an
- 38. ARCHITECTURAL FRAMEWORK SystemArchitecture Architectural description Stakeholder ConcernViewpointView 1..N 1..N0..N Documents architecture for 1..N 1..N 0..N Has an
- 39. ARCHITECTURAL FRAMEWORK SystemArchitecture Architectural description Stakeholder ConcernViewpointView 1..N 1..N0..N Documents architecture for 1..N 1..N 0..N N..M Has an
- 40. PERSPECTIVES
- 42. PERSPECTIVES Information view Functional view Deployment view SECURIT Y
- 44. CROSS CUTTING CONCERNS = NON-FUNCTIONAL REQUIREMENTS
- 45. CROSS CUTTING CONCERNS = NON-FUNCTIONAL REQUIREMENTS = QUALITY PROPERTIES
- 46. CROSS CUTTING CONCERNS = NON-FUNCTIONAL REQUIREMENTS = QUALITY PROPERTIES = PERSPECTIVES
- 47. PERSPECTIVES
- 50. PERSPECTIVES Security Performance and Scalability Availability and Resilience
- 51. PERSPECTIVES Security Performance and Scalability Availability and Resilience Evolution
- 52. ARCHITECTURAL FRAMEWORK SystemArchitecture Architectural description Stakeholder ConcernViewpointView 1..N 1..N0..N Documents architecture for 1..N 1..N 0..N N..M Has an
- 53. ARCHITECTURAL FRAMEWORK SystemArchitecture Architectural description Stakeholder ConcernViewpointView Perspectives 1..N 1..N0..N Documents architecture for 1..N 1..N 0..N N..M 0..N Has an
- 54. ARCHITECTURAL FRAMEWORK SystemArchitecture Architectural description Stakeholder ConcernViewpointView Perspectives 1..N 1..N0..N Documents architecture for 1..N 1..N 0..N N..M 0..N Has an N..M
- 55. 5+2 RULE
- 56. 4 KEY METRICS OF SUCCESSFUL ARCHITECTURE AND ORGANIZATION BEHIND IT
- 57. 4 KEY METRICS OF SUCCESSFUL ARCHITECTURE AND ORGANIZATION BEHIND IT • LEAD TIME
- 58. 4 KEY METRICS OF SUCCESSFUL ARCHITECTURE AND ORGANIZATION BEHIND IT • LEAD TIME • DEPLOYMENT FREQUENCY
- 59. 4 KEY METRICS OF SUCCESSFUL ARCHITECTURE AND ORGANIZATION BEHIND IT • LEAD TIME • DEPLOYMENT FREQUENCY • MEAN TIME TO RESTORE (MTTR)
- 60. 4 KEY METRICS OF SUCCESSFUL ARCHITECTURE AND ORGANIZATION BEHIND IT • LEAD TIME • DEPLOYMENT FREQUENCY • MEAN TIME TO RESTORE (MTTR) • CHANGE FAIL PERCENTAGE