rect
You are viewing an archived version of CBSE 1999. This page has been archived via the Internet Archive Wayback Machine for the ICSA conference series history. Some links on this page might not work.
← return to the ICSA homepage.
General Navigation Buttons - Home | Search | Contact Us | Site Map | Whats New
engineering graphic
Engineering Practices
Welcome
Architecture Tradeoff Analysis
CERT Coordination Center
COTS-Based Systems
Overview
Activity Areas
Products and Services
CBS Team
References
Events
What's New
Opportunities to work with us
Briefings, Courses, and Workshops
Spiral Development Workshops
CURE (COTS Usage Risk Evaluation)
COTS-Based Systems Monographs
COTS_Spot Column
Little Red Book
Dependable System Upgrade
Information Repositories
Personal & Team Software Process
Product Line Practice
Software Engineering Measurement & Analysis (SEMA)
Complete Technical Project List
Common Acronyms
Featured Publications
Technical Initiatives
Courses
Conferences
About SEI|Mgt|Eng|Acq|Collaboration|Prod.& Services|Pubs
Rollover Popup Hints for Topic Navigation Buttons above
Specification:


Next: Implementation: Up: Process Model for Componentware Previous: Technical Design:

Specification:

The main results Business Design and Technical Design are concerned with two fundamentally different views on the developed system. The Specification main result merges and refines both views, thereby resulting in complete and consistent Architecture and Component Specifications.

As said above, both Business Design and Technical Design cover an evaluation of existing components from the business and technical point of view, resulting in a preselection of potentially suitable components for the system. The Specification subresult Component Test contains the results and test logs of these components with respect to the user requirements and the chosen system architecture. Note that such tests should be performed as soon as the specification of a component is available in order to avoid problems during system integration.

Some of the desired components may simply be ordered whereas other components are not available at all and must be developed. The Component Assignment subresult specifies which components are to be developed in the current project and which components are ordered from external component suppliers or in-house profit centers. If a component is to be developed outside of the current project, a new, separate result structure has to be set up. Note the close correspondence between Architecture Specification and Component Specification on the one hand, and Interaction Analysis and Responsibility Analysis on the other hand. It allows for a clear hand-over of a component specification to a component developer outside the project.


Next: Implementation: Up: Process Model for Componentware Previous: Technical Design:
Andreas Rausch
3/22/1999
 

 

 

 

contact the organizers
download the PDF file


The Software Engineering Institute (SEI) is a federally funded research and development center sponsored by the U.S. Department of Defense and operated by Carnegie Mellon University.

Copyright 2001 by Carnegie Mellon University
URL: http://www.sei.cmu.edu/papers/41/node8.html
Last Modified: 27 September 2000