Architecture business cycle ( abc )
The document discusses the definition of software architecture as comprising the structure of a system including its software elements, externally visible properties, and relationships between elements. It notes that software architecture is influenced by technical, business, and social factors such as immediate business investments, long-term infrastructure investments, strategic investments, and current environmental standards. The architecture affects the developing organization's structure and goals as well as customer requirements for future systems, and the development process can influence the architect's experience on subsequent projects and potentially the software engineering culture. The key steps in architecting a system are outlined as creating the business case, understanding requirements, creating/selecting an architecture, documenting/communicating it, analyzing/evaluating it, implementing based on the architecture
Architecture business cycle ( abc )
- 1. Dr. Reeja S R Associate Professor CSE DEPT., SJEC
- 2. The software architecture is the structure of the system, which comprise •software elements, •externally visible properties of those elements and •relationships among them.
- 6. Immediate business investment (ex. existing architecture) Long-term business investment (ex. long term infrastructure) Strategic investment (ex. subcontracting, skills of employees)
- 8. Current environment will influence architecture standard industry practices or software engineering techniques
- 10. 1. Architecture affects structure of developing organization 2. Architecture can affect goals of developing organization 3. Can affect customer requirements for next system 4. Process of system building will affect architect’s experience with subsequent systems 5. Sometimes will influence and sometimes change software engineering culture
- 11. 1. Creating the business case for the system 2. Understanding the requirements 3. Creating or selecting the architecture 4. Documenting and communicating the architecture 5. Analyzing or evaluating the architecture 6. Implementing the system based on architecture 7. Ensuring that the implementation conforms to architecture 11
Editor's Notes
- #11: 1 – Architecture prescribes structure for a system – especially units of software to be implemented & integrated into system. Teams formed for individual software units – development, testing, & integration activities revolve around units Schedules & budgets allocate resources in chunks to the units. 2 – A successful system can enable a company to establish a foothold in a particular market area. Can provide opportunities for production & deployment of similar systems. 3 – Architecture can affect customer requirements for next system by giving customer opportunity to receive a system in a more reliable, timely, and economical manner. 4 – System building will add to corporate experience base. 5 – Technical environment in which system builders operate can change due to the system being developed – relational db, compiler models, prototyping, etc