Download to read offline
Uploaded bySandun Perera
iUpgradable
This document discusses upgradability concerns for software architecture. It identifies three levels of concerns: architectural, developer, and upgrading phase concerns. It lists common architectural styles like monolithic, n-tier, SOA, microservices, and SaaS. It also lists common "ilities" or quality attributes for software like adaptability, agility, and upgradability. The document then discusses strategies for upgrading different parts of the software like components, services, platform services, code behind, libraries, and user interfaces. It emphasizes techniques like refactoring, dependency injection, separating files and classes. It also cautions against modifying external libraries and to wrap them instead. Finally, it provides examples of referral projects that demonstrate upgrad
More Related Content
iUpgradable
- 1.
- 2. About • Architecturalconcerns • Developer level concerns • Upgrading phase concerns
- 3. What is your software architecture? Monolithicn-Tier SOA Microservices SaaS Script / Desktop / Web / Mobile / Embedded
- 4. Ilities adaptability agility customizability degradabilityevolvability extensibility flexibility interchangeability maintainability manageability modifiability modularity reusability scalability upgradability
- 5.
- 6. Component • Refactor toseparate functions • Refactor to separate files • Refactor to separate assembly
- 7.
- 8. Platform Services •Cloud resources • Infrastructure access • External vendor service access
- 9. Code Behind • Encapsulation •Separation of concern • Docker
- 10. Libraries • Extensions • Thirdparty plugins • UI libraries
- 11.
- 12. The bulb • Nevermodify external libraries • Isolate versatile implementations • Avoid direct usage of external libraries • Wrap by your own implementation
- 13. Referral Projects •ANU LRP (Web) • DGR Hub (Microservices and Mobile)
- 14.
- 15.
Editor's Notes
- #3 Architectural concerns Developer level concerns Upgrading phase concerns
- #4 Monolithic n-Tier SOA Microservices SaaS Script / Desktop / Web / Mobile / Embedded
- #6 Component Service Platform services Code behind Libraries User Interface
- #7 Refactor to separate functions Refactor to separate files Refactor to separate assembly
- #8 Dependency Injection Separate file Separate class
- #9 Cloud resources Infrastructure access External vendor service access
- #10 Encapsulation Separation of concern Docker
- #11 Extensions Third party plugins UI libraries
- #12 Desktop Web Mobile Front-end applications
- #13 Never modify external libraries Isolate versatile implementations Avoid direct usage of external libraries Wrap by your own implementation
- #14 ANU LRP (Web) DGR Hub (Microservices and Mobile)