The ideas and findings in this report should not be construed as an official DoD position. It is published in the interest of scientific and technical information exchange.

Public reporting burden for the collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to a penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number.

ii | CMU/SEI-2010-TR-031iii | CMU/SEI-2010-TR-031 List of Tables Table 1: Goals and Objectives for the First Architecture Iterations 6 Table 2: Overview of the TSP Launch for the Architecture Phase 8 Table 3: Role of the Lead Architect 9 Table 4: Role of the TSP Managers 11 Table 5: Scenario / Component Mapping 12 Table 6: Effort Estimation Table 14 Table 7: Example Scenario Effort Estimation Table 15 Table 8: TSP Quality Guidelines Standard Planning Factors 17 List of Figures AbstractThis report contains a description of an architecture-centric life-cycle model that uses the Carnegie Mellon Software Engineering Institute's architecture-centric engineering (ACE) methods embedded in a Team Software Process (TSP) framework and of our experience in piloting the approach in an actual development effort. Combining ACE and TSP provides an iterative approach for delivering quality systems on time and within budget. TSP provides the infrastructure in estimation, planning, measurement, and project management. ACE provides the means for designing, evaluating, and implementing a system so that it will satisfy its business and quality goals. Bringing these approaches together results in something that is much more than the sum of the parts. The combined approach offers help to organizations to set an architecture/developer team in motion using mature, disciplined engineering practices that produce quality software quickly.

No abstract

No abstract