In this issue:Reports and Studies
Sponsors:
.infoReader Editor: Gary J. Dickelman
© 2001-2004 EPSScentral LLC. All rights reserved.
Publications and articles referenced here are copyrighted works of their respective owners. The .infoREADER banner is used strictly as a navigational device for linked content and does not imply origin or ownership unless explicitly stated.
| Reports and Studies -------------------- Abstract: This paper reflects a successful effort to apply commercial off-the-shelf (COTS)-based engineering principles to a software acquisition by the Financial and Business Services (FABS) and Information Technology (IT) departments at the Software Engineering Institute. The team responsible for the execution of the project was guided by the principles taught in the "COTS-Based Systems for Program Managers" and "COTS Software Evaluation for Practitioners" training programs conducted by the COTS-Based Systems Initiative at the Software Engineering Institute. Some of the major expectations set and realized included precise comprehension of requirements and preferences, ability to identify weak links in the proposed solutions, support for the "buy versus build" decision and the product recommendation, the promise of a shorter implementation phase, and brimming confidence based on a well-informed project approach.
Abstract: Comparing software architectures for any nontrivial system is a difficult task. Software architectures are designed with particular requirements and constraints, and are often poorly documented. However, organizations often need to select a software architecture for future development from several candidate architectures. The Software Architecture Comparison Analysis Method (SACAM) was created to provide the rationale for an architecture selection process by comparing the fitness of architecture candidates for required systems. The SACAM compares architectures based on a set of criteria derived from the business goals of an organization. SACAM was developed in a technical reuse context where an organization investigated architectural commonalities and differences to explore architectural designs for a software product line architecture. This report outlines a first version of the method and its underlying concepts.
|
|