Software Design vs Software Architecture (2)
After explaining about Software Design in previous post, we can continue part 2, Sofware Architecture..
The software architecture of a system is the set of structures needed to reason about the system, which comprise software elements, relations among them, and properties of both.The term also refers to documentation of a system’s software architecture. Documenting software architecture facilitates communication between stakeholders, documents early decisions about high-level design, and allows reuse of design components and patterns between projects. (Wikipedia)
The field of computer science and complexity of the problem encountered related to the formation from it. Complex by the developer to solve the problem earlier by selecting the right data structure, the development of algorithms and by applying the concept of separation of concerns. Although the term “software architecture” is relatively new to the industry, the fundamental principle of the field scattered by the pioneer of software engineering to apply from the mid-1980s. Early attempts to capture and explain the system’s software architecture is inaccurate and confusing, often depicted as a box and line diagram. In the 1990s has been concentrated during the definition and compilation of the results of the fundamental aspects of discipline.
Initial set of design patterns, styles, best practices, describe the language and form of management is learning to be developed at that time. Software architecture discipline in reducing complexity through abstraction and concern around the idea of ??separation. The answer is still on the term “software architecture” is not a precise definition of the protocol. However, this does not mean that individuals without their own definitions of what software architecture is. Because many people use the same language to describe the different ideas, which leads to problems. As there is no clear charter of a mature discipline in the right way to establish the system design software architecture is still a mixture of art and science.
Software architecture of the “art” aspect is, as a commercial software system supports some aspect of business or mission. System supports key business drivers through the scene described how, when not running the system requirements, also known as quality attributes, how to determine system performance. This can be thought of as parallel to the mission statement and business strategy in the value system. Each system is unique due to the nature of its support business drivers, such as a system of quality attributes such shortcomings on display tolerance, reverse compatibility, extensibility, reliability, maintainability, availability, safety, practicality, and so Other – ilities will vary with each implementation. To bring software architecture user ‘s perspective to the software architecture, the software architecture can be said that the direction to take steps and to do so in each user’ involved in the task; that s areas of expertise and stakeholder interest in software systems, software developers, software operations support team, software maintenance specialists, deployer, testers and enterprise end-users [citation needed]. This truly is the system software architecture is always multi-perspective of the merger. The fact that several different points of view can be pooled into the software architecture as software architecture alongside the needs and justify the creation of the defense, get in the maturity of software development projects before.
Comments
Leave a Reply
