We recognize the contribution of
trial-and-error development process style over the deficiencies of a waterfall approach to building
bulky software implementations. Thus the definition of software architecture keeps morphing
because of the fundamental shift in the way we understand what actually a software system is
and what are its chief ingredients.
In the early 1990s, the recognition that a software system must be inspected and viewed
from different perspectives in order to fully understand its overall capabilities and its contribution
to a viable business or technological solution was indeed an important trend in computer
science. Technology theorists, engineers, and developers finally acknowledged that the traditional
approach to the software development process, which was quite myopic, did not contribute much
to the collaborative efforts of silo organizations to build effective solutions. This shortsightedness
often prevented various enterprise stakeholders??”such as executives, business personnel, business
analysts, and even managers??”from participating in the construction of vital software products.
Their potential contributions to the development process were typically ignored.
In 1995, in his article ???Architecture Blueprints: The ???4 + 1??™ View Model of Software
Architecture,??? Philippe Kruchten introduced a model for describing an architecture of a software
system.
Pages:
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530