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
PORE: Procurement-Oriented Requirements Engineering Method for the Component-Based Systems Engineering Development Paradigm


Figure 1: The Basic Overview of the PORE Process Model












Figure 2: Overview of the PORE�s iterative process. Requirements acquisition enables product selection and product selection informs requirements acquisition. As the number and detail of requirements increases, the number of candidate products decreases












Figure 3: PORE�s templates within the iterative process stages. Because of this iterative nature of the process, this means that each template can be used several times. Also shown in the figure process goals that each template must achieve and these are explained below.












Figure 4: A route map showing PORE�s high-level generic processes for achieving each essential goal












Figure 5: The structure of the situation model, and the relationships between the requirement, product and compliance sub-models.












Figure 6: The three levels of process guidance which form the PORE process triplet. The current process goal is inferred from the process model. The technique to achieve this process is inferred from properties of the situation model. The focus of this technique's application is inferred from properties of the situation model content












Figure 7: A meta-model for the software product showing the primitive concepts and relationships with which to model each software product












Figure 8: The requirement model and its meta-concepts.












Figure 9: A vision of shared knowledge as the cornerstone for the future success of the CBSE paradigm.












 

 

 

 

contact the organizers


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/11/figures.html
Last Modified: 27 September 2000