29-05-2017, 01:20 PM
Softwate architecture
|
aradhya notes for software architecture
|
Softwate architecture
30-05-2017, 10:01 AM
Software architecture refers to the high-level structures of a software system, the discipline of creating such structures, and documentation of these structures. These structures are necessary to reason about the software system. Each structure comprises software elements, relationships between them, and properties of both elements and relationships. The architecture of a software system is a metaphor, analogous to the architecture of a building.
Software architecture is to make fundamental structural choices that are costly to change once implemented. Software architecture options include structural options specific to the possibilities in software design. For example, the systems controlling the launch vehicle of the space shuttle were required to be very fast and very reliable. Therefore, an appropriate real-time computing language would have to be chosen. In addition, to meet the need for reliability, one could choose to have multiple redundant and independently produced copies of the program, and to run these copies on standalone hardware while checking the results.
Software architecture documentation facilitates communication among stakeholders, captures early decisions about high-level design, and allows reuse of design components among projects.
History
The comparison between software design and (civil) architecture was first drawn in the late 1960s, but the term software architecture became predominant only in the early 1990s. The field of computer science had encountered problems associated with complexity since its formation. Previous problems of complexity were solved by developers choosing the right data structures, developing algorithms and applying the concept of separation of concerns. Although the term "software architecture" is relatively new to the industry, the fundamental principles of the field have been applied sporadically by software engineering pioneers since the mid-1980s. Early attempts to capture and explain the software architecture of a system were imprecise and disorganized, often characterized by a set of box and line diagrams.
Software architecture as a concept has its origins in the research of Edsger Dijkstra in 1968 and David Parnas in the early seventies. These scientists emphasized that the structure of a software system matters and that the correct structure is critical. During the 1990s, there was a concerted effort to define and codify fundamental aspects of the discipline, with research works focusing on architectural styles (patterns), architectural description languages, architectural documentation and formal methods.
Research institutions have played a prominent role in fostering software architecture as a discipline. Mary Shaw and David Garlan of Carnegie Mellon wrote a book entitled Software Architecture: Perspectives on an Emerging Discipline in 1996 that promoted software architecture concepts such as components, connectors, and styles. The University of California, Irvine's Software Research Institute's efforts in software architecture research are primarily focused on architectural styles, architectural description languages, and dynamic architectures.
IEEE 1471-2000, Recommended Practice for Architecture Description of Intensive Software Systems, was the first formal standard in the area of software architecture. It was adopted in 2007 by ISO as ISO / IEC 42010: 2007. In November 2011, IEEE 1471-2000 was replaced by ISO / IEC / IEEE 42010: 2011, Systems and Software Engineering - Architecture Description (jointly published by IEEE And ISO).
In IEEE 1471, the software architecture referred to the architecture of "software-intensive systems", defined as "any system in which software contributes essential influences to the design, construction, implementation and evolution of the system as a whole", the 2011 Edition It goes further by including ISO / IEC 15288 and ISO / IEC 12207 definitions of a system, which encompass not only hardware and software, but also "human beings, processes, procedures, facilities, materials and natural entities." This reflects the relationship between software architecture, enterprise architecture and solution architecture.
|
« Next Oldest | Next Newest »
|
Important Note..!
If you are not satisfied with above reply ,..PleaseASK HERE
So that we will collect data for you and will made reply to the request....OR try below "QUICK REPLY" box to add a reply to this page
| Possibly Related Threads... | |||||
| Thread | Author | Replies | Views | Last Post | |
| Beautician course notes in hindi | 0 | 5,810 |
24-02-2020, 04:31 AM Last Post: |
||
| Report and ppt on dynamic architecture | 0 | 738 |
14-02-2019, 07:36 AM Last Post: |
||
| software testing lab viva questions and answers vtu | 0 | 5,362 |
30-10-2018, 02:09 AM Last Post: Guest |
||
| maruti suzuki dms software download | 0 | 2,536 |
22-10-2018, 09:46 PM Last Post: Guest |
||
| techmax ebooks activation code for computer architecture and organization | 0 | 765 |
21-08-2018, 08:54 PM Last Post: Guest |
||
| computer graphics notes hindi pdf free download | 1 | 1,369 |
21-08-2018, 05:07 PM Last Post: Dharmesh Sankhla |
||
| arunkumar network security vtu ece notes pdf | 0 | 914 |
19-08-2018, 12:01 AM Last Post: Guest |
||
| vtu 7th sem cse ashok kumar notes pdf embedded computing system | 0 | 1,285 |
16-08-2018, 07:25 PM Last Post: Guest |
||
| medha spoken english full notes pdf | 0 | 955 |
09-08-2018, 12:45 PM Last Post: Guest |
||
| rnsit java notes download | 0 | 763 |
08-08-2018, 10:23 PM Last Post: Guest |
||