Effective management of system capability is crucial for business success and sustenance of a competitive advantage. Architecture needs to address the relative balance between rapidly changing technology; dynamic business scenario, and integration with diverse systems without increasing the cost of software development and the complexity of software systems.
Architectural thinking is not expressed effectively to represent business concerns such as:
• How to modernize the hardware and software environments (reduce complexity in IT infrastructure)
• Increase the portability of applications
• Security challenges associated with the integration of multiple applications, devices, and data sources
• How a system can effectively communicate the change in a scenario or generate a new idea via multiple channels to the right stakeholders
• Monitoring the capability usage of system features and resources
The practice of system development can provide benefits in terms of quality and cost gains from adherence to architectural guidelines. A key premise of this logic is that important decisions may be made early in system development in a manner similar to the early decision-making found in the development of civil architecture projects.
Bhavna offers the following
To these ends, Bhavna recommends an approach that reflects the generally accepted practices for architectural description and provides a technical framework for further evolution in this area.
Bhavna initiates a criteria-based selection approach to describe how the system or product will be constructed; what the critical components are; and their fitment from a high-level, logical perspective. Mapping such selection against available templates helps to consider architecture principles for defining the system architecture, which addresses the visibility, changeability, and collaborates to meet defined quality expectations by the customers.
The activity performed by Bhavna can be described as follows:
• Key system or product scenarios are analyzed
o Domain, industry practices, and statistics
o Tools and technology usage
o Costs and timelines
o Learnings from a similar system
• Before starting architecture, we ensure that the following points are identified
o Architectural principles applicable
o Best practices to be followed
o Quality of Service (QoS) to be achieved
o Integration need
o Commercial off-the-shelf (COTS) product consideration
• Besides standard description, sections included in the output are
o Behavior facts or metrics of the existing environment along with the structural integration and operational behavior of an organization
o How the concerns raised by various stakeholders are addressed and mapping metrics
o Rationale behind the selection of architectural principles and tradeoff considerations
o Metrics about the expected and targeted quality if architecture description is followed