This discussion further galvanized the debate of exactly what constitutes software architecture
and how these disciplines are relevant to today??™s service-oriented life cycle. Today, practitioners
are still challenged by the most rudimentary questions that have occupied computer scientists
during the past two decades: Is the traditional comparison to civil architecture structures??”such
as houses, shops, hotels, offices, industrial buildings, theaters, and museums??”still relevant to
today??™s service-oriented software architecture paradigm? Are architecture and design the same
thing? Is the conceptualization and discovery and analysis disciplines part of the architecture process,
or are software architecture addresses different challenges during a life cycle of a software
product?
This Part introduces fundamental best practices of the service-oriented software architecture,
which recognize the contributions of traditional system architecture tenants. But this Part
faces not only the questions that have remained unanswered over the decades but also the intrinsic
promise of service-oriented architecture (SOA) and its contribution to the service-oriented
development life cycle. Readers may have guessed that these major imperatives, among others,
are asset reuse, consolidation, consumption, orchestration, interoperability, and loose coupling.
Service-oriented software architecture modeling efforts must also accentuate strong ties with the
business organization and, just as important, with the business strategies and the business model
of the organization.
Pages:
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532