02 architectures in_context
•Download as PPT, PDF•
1 like•1,033 views
The document discusses several key points about software architecture: 1. Every application has an architecture and at least one architect. Architecture is not just a phase of development but foundational to software design. 2. Requirements analysis and design must be considered together. Existing architectures provide context for requirements and help assess feasibility. 3. The implementation phase aims to faithfully represent the architectural design in code. Deviations from the architecture can undermine its benefits. 4. Architecture centric development sustains focus on the architectural model through all phases from requirements to evolution. This helps manage quality and complexity over the system's lifetime.
![Fundamental Understanding ,[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Recommended
More Related Content
What's hot
What's hot (19)
Viewers also liked
Similar to 02 architectures in_context
Similar to 02 architectures in_context (20)
More from Majong DevJfu
More from Majong DevJfu (20)
Recently uploaded
Recently uploaded (20)
02 architectures in_context
- 1. Architectures in Context Software Architecture Lecture 2
- 8. The Twin Peaks Model
- 19. How It All Fits Together Software Architecture: Foundations, Theory, and Practice ; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; © 2008 John Wiley & Sons, Inc. Reprinted with permission.
- 27. The Turbine Model Coding Design Requirements Testing Simplistic Waterfall, Side perspective “ Core” of project artifacts Radius of rotor indicates level of staffing at time t Gap between rotors indicates no project activity for that t t i Software Architecture: Foundations, Theory, and Practice ; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; © 2008 John Wiley & Sons, Inc. Reprinted with permission. time
- 28. Cross-section at time t i Software Architecture: Foundations, Theory, and Practice ; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; © 2008 John Wiley & Sons, Inc. Reprinted with permission. Design (activity) Requirements Design doc
- 29. The Turbine Model Software Architecture: Foundations, Theory, and Practice ; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; © 2008 John Wiley & Sons, Inc. Reprinted with permission. Waterfall example, Angled perspective time
- 30. A Richer Example S 1 Design/Build/ Requirements Test/Build/ Deploy Assess/… Requirements/Architecture assessment/Planning Build/Design/ Requirements/Test Software Architecture: Foundations, Theory, and Practice ; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; © 2008 John Wiley & Sons, Inc. Reprinted with permission. time
- 31. A Sample Cross-Section Software Architecture: Foundations, Theory, and Practice ; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; © 2008 John Wiley & Sons, Inc. Reprinted with permission.
- 32. A Cross-Section at Project End Software Architecture: Foundations, Theory, and Practice ; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; © 2008 John Wiley & Sons, Inc. Reprinted with permission.
- 33. Volume Indicates Where Time was Spent Design/Build/ Requirements Test/Build/ Deploy Assess/… Requirements/ Architecture Assessment / Planning Build/Design/ Requirements/Test Software Architecture: Foundations, Theory, and Practice ; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; © 2008 John Wiley & Sons, Inc. Reprinted with permission.
- 34. A Technically Strong Product-Line Project Assessment Parameterization Customization Deployment Capture of new work Other Software Architecture: Foundations, Theory, and Practice ; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; © 2008 John Wiley & Sons, Inc. Reprinted with permission.
Editor's Notes
- Rotors are the activities. Core are the artifacts. Time goes upward. Volume of rotor represents cost. Volume of core represents information content. Wide rotor represents lots of investment of (people) resources.
- Rotor 1: Reqts 50%; Architecture assessment 30%; Project planning 20%. Rotor 2: Design: 50%; Impl. 25%; Reqts 12.5%; Other 12.5% Rotor 3: Design 15%; Impl. 50%; A&T: 25%; Reqts 5%; Other 5% Rotor 4: Impl. 15%, A&T 50%; Deployment 20%; Other 15% Rotor 5: Analysis of lessons learned: 85%; Other 15% GAP rotor (i.e. some amount of the core sticks out above the top rotor
- Rotor 1: Reqts 50%; Architecture assessment 30%; Project planning 20%. Rotor 2: Design: 50%; Impl. 25%; Reqts 12.5%; Other 12.5% Rotor 3: Design 15%; Impl. 50%; A&T: 25%; Reqts 5%; Other 5% Rotor 4: Impl. 15%, A&T 50%; Deployment 20%; Other 15% Rotor 5: Analysis of lessons learned: 85%; Other 15% GAP rotor (i.e. some amount of the core sticks out above the top rotor
- Lots of substance coming in. Small volume (cost) in the rotors. Rotor 1: Assessment: 100% Rotor 2: Parameterization: 50% Customization: 50 Rotor 3: Deployment: 50 Capture: 30 Other: 20 Capture is the work to take what was customization here and package it so that it is reusable in future projects.