how much architecture
DESCRIPTION
Iasa UK Ignite presentation from Chris Cooper-Bland, EndavaTRANSCRIPT
![Page 1: How much architecture](https://reader035.vdocuments.net/reader035/viewer/2022062511/54c218294a7959657c8b45f2/html5/thumbnails/1.jpg)
Chris Cooper-bland
10/09/2012
Architecting – Possible?
![Page 2: How much architecture](https://reader035.vdocuments.net/reader035/viewer/2022062511/54c218294a7959657c8b45f2/html5/thumbnails/2.jpg)
In most projects, even agile, you have to do some formal Architecture, the question is how much?
Just Enough Architecture
![Page 3: How much architecture](https://reader035.vdocuments.net/reader035/viewer/2022062511/54c218294a7959657c8b45f2/html5/thumbnails/3.jpg)
If you don’t, you might end up with
the Vasa
Sank on maiden voyage of less than 2Km – added new deck after hull had been built
![Page 4: How much architecture](https://reader035.vdocuments.net/reader035/viewer/2022062511/54c218294a7959657c8b45f2/html5/thumbnails/4.jpg)
Want to avoid BUFD – or being sick
But can you know how much is “Just enough”
![Page 5: How much architecture](https://reader035.vdocuments.net/reader035/viewer/2022062511/54c218294a7959657c8b45f2/html5/thumbnails/5.jpg)
*Making decisions
*Documenting decisions
*Communicating decisions
The key activities in doing Architecture
![Page 6: How much architecture](https://reader035.vdocuments.net/reader035/viewer/2022062511/54c218294a7959657c8b45f2/html5/thumbnails/6.jpg)
Each project is different
What factors in a project influence the amount of these activities needed
![Page 7: How much architecture](https://reader035.vdocuments.net/reader035/viewer/2022062511/54c218294a7959657c8b45f2/html5/thumbnails/7.jpg)
* Spoke to architects – not those ones
* Looked at some papers/books e.g. Royce
Informal Research identified following factors
![Page 8: How much architecture](https://reader035.vdocuments.net/reader035/viewer/2022062511/54c218294a7959657c8b45f2/html5/thumbnails/8.jpg)
a large number of distinct functions mean more time should be spent on developing a loosely coupled, highly cohesive set of components.
Functional requirements
![Page 9: How much architecture](https://reader035.vdocuments.net/reader035/viewer/2022062511/54c218294a7959657c8b45f2/html5/thumbnails/9.jpg)
The more challenging the constraints, such as: cost control, schedule, resourcing, team distribution, means the architecture needs to be more explicitly understood for planning.
Business constraints
![Page 10: How much architecture](https://reader035.vdocuments.net/reader035/viewer/2022062511/54c218294a7959657c8b45f2/html5/thumbnails/10.jpg)
The presence of mandated technologies means these must be explicitly accommodated in the architecture.
Technical constraints
![Page 11: How much architecture](https://reader035.vdocuments.net/reader035/viewer/2022062511/54c218294a7959657c8b45f2/html5/thumbnails/11.jpg)
The more challenging the performance, scalability, and the distribution of the system are means there are greater architecturally significant risks which need to be addressed early in the project.
Runtime qualities
![Page 12: How much architecture](https://reader035.vdocuments.net/reader035/viewer/2022062511/54c218294a7959657c8b45f2/html5/thumbnails/12.jpg)
Things like maintainability and portability must be addressed before development starts in earnest otherwise extensive re-factoring will be required.
Non-runtime qualities
![Page 13: How much architecture](https://reader035.vdocuments.net/reader035/viewer/2022062511/54c218294a7959657c8b45f2/html5/thumbnails/13.jpg)
The larger the team means the architecture must be clearly documented to prevent misunderstandings
The size of the development team
![Page 14: How much architecture](https://reader035.vdocuments.net/reader035/viewer/2022062511/54c218294a7959657c8b45f2/html5/thumbnails/14.jpg)
The newer the system, either form a technology or business perspective means that there will be greater emphasis on prototyping.
The novelty of the system
![Page 15: How much architecture](https://reader035.vdocuments.net/reader035/viewer/2022062511/54c218294a7959657c8b45f2/html5/thumbnails/15.jpg)
the process being followed may mandate architectural activities and artifacts, this may be a customer requirement.
The method being followed
![Page 16: How much architecture](https://reader035.vdocuments.net/reader035/viewer/2022062511/54c218294a7959657c8b45f2/html5/thumbnails/16.jpg)
the longer the anticipated lifetime of the system the more cost effective spending time on defining and describing the architecture becomes
Target lifetime of the system
![Page 17: How much architecture](https://reader035.vdocuments.net/reader035/viewer/2022062511/54c218294a7959657c8b45f2/html5/thumbnails/17.jpg)
Group into
*Size and Longevity
*Complexity Factors
The factors work together -
Size and Longevity
System Complexity
Loads of Architecture
![Page 18: How much architecture](https://reader035.vdocuments.net/reader035/viewer/2022062511/54c218294a7959657c8b45f2/html5/thumbnails/18.jpg)
*Making decisions
* Documenting decisions
* Communicating decisions
- to impact on the architecture activities
![Page 19: How much architecture](https://reader035.vdocuments.net/reader035/viewer/2022062511/54c218294a7959657c8b45f2/html5/thumbnails/19.jpg)
Two projects with different factors
Can we visualise this?
![Page 20: How much architecture](https://reader035.vdocuments.net/reader035/viewer/2022062511/54c218294a7959657c8b45f2/html5/thumbnails/20.jpg)
Thank-you!
Discussion …