For the past several months the author has focused on designing a software architecture. The author has talked about requirements gathering, documentation, integration with the development process, and more. One thing he hasn't discussed, however, is the benefits of the software architecture. The author explains the benefits of the software architecture in two ways: first with regard to how it works with the overall design and development process, and second with regard to how it benefits various stakeholders in the final product, including investors, managers, and the development team. The paper concludes with a simple overview of these benefits, which one can use as a guide for integrating architectural design into ones company's development process.
Did you find this white paper useful?
Related white papers
Pipelined Broadcast on Ethernet Switched Clusters
This paper considers unicast-based pipelined broadcast schemes for clusters connected by multiple Ethernet switches. By splitting a large broadcast message into segments and broadcasting the segments in a pipelined fashion,...
Reliability Centered Maintenance & Optimization for SAP Service and Asset Management
The Gladstone alumina refinery operated by Queensland Alumina Limited (QAL) is the largest in the world, with a maximum annual rated capacity of 3.8 million tonnes. Queensland Alumina had attempted...
Momentum Webcast: Can Process Improvement and Application Lifecycle Management Really Improve Your Business? (Level 100)
The term Application Lifecycle Management (ALM) is attracting significant attention from tool vendors, research groups, and industry thought leaders. Although proactively managing the application throughout the life cycle seems to...
Extended Description Techniques for Security Engineering
There is a strong demand for techniques to aid development and modelling of security critical systems. Based on general security evaluation criteria, we show how to extend the system structure...
Modeling the Performance of Software Processes Quantitatively
Three distinct approaches have been used to quantitatively model software development projects. They are Analytic Summary Models, Analytic Structural Models, and Process Models. Most existing quantitative models are analytic summary...
An Assessment Process for Software Reuse
Each organization is unique in that they have different cultures and maturity with software processes and thus each organization should have a reuse plan specifically designed for their purposes. Therefore...
Object-Oriented Project Management
Object-orientation is a way of looking at the world as "classes" of "objects" in order to model the real world more effectively than traditional structured software engineering or other methods...
