|
Next: Process Model for Componentware
Up: Componentware - Methodology and Process
Previous: Requirements for a Component-Oriented
The distinction between the roles of Component Vendors and Component Users is a key aspect of a component-oriented development process. It is a necessary prerequisite for the rise of a market for specialized, reusable components of high quality that are needed to build large, reliable and highly complex systems. Other, more mature industrial branches have known this separation for a long time [Hin97]. We expect the following, specialized roles to evolve in the context of component-oriented software development:
- Component Developer:
- Components are supplied by specialized component
developers or by in-house reuse centers as a part of large enterprises. The responsibilities of a
Component Developer are to recognize the common requirements of many customers
or users and to construct reusable components accordingly. If a customer requests
a particular component, the Component Developer offers a tender and sells the component.
- Component Assembler:
- Usually, complicated components have to be adapted
to match their intended usage. The Component Assembler adapts and customizes pre-built standard components
and integrates them into the system under development.
- System Analyst:
- As in other methodologies, a System Analyst elicits the
requirements of the customer. Concerning componentware, he also has to be aware
of the characteristics and features of existing systems and business-relevant
components.
- System Architect:
- The System Architect develops a construction plan and
selects adequate components as well as suitable Component Developers and Component Assemblers .
During the construction of the system, the System Architect supervises and reviews
the technical aspects and monitors the consistency and quality of the results.
- Project Coordinator:
- A Project Coordinator as an individual is usually
only part of very large projects. He supervises the whole development process, especially
with respect to its schedule and costs. The Project Coordinator is responsible
to the customer for meeting the deadline and the cost limit.
Next: Process Model for Componentware
Up: Componentware - Methodology and Process
Previous: Requirements for a Component-Oriented
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/node3.html
Last Modified: 27 September 2000
|
