Appendix A. Summary of Workers

Appendix A. Summary of Workers

This appendix summarizes the workers involved in the Rational Unified Process. Remember that a worker is not an individual but rather represents a role that individuals or teams play and their responsibilities for artifacts (see Chapter 3). They are listed in alphabetical order.

Any Worker  

Any of the workers identified in the Rational Unified Process can be given access privileges to "check-in" and " check-out " any product- related artifact for maintenance in the configuration control system.

Architect  

The architect leads and coordinates technical activities and artifacts throughout the project. The architect establishes the overall structure for each architectural view: the decomposition of the view, the grouping of elements, and the interfaces between these major groupings.

Architecture Reviewer  

The architecture reviewer plans and conducts the formal reviews of the software architecture in general.

Business Designer  

The business designer details the specification of a part of the organization by describing the workflow of one or several business use cases. This worker details the specification of a part of the organization by describing the workflow of one or several business use cases. He or she specifies the business workers and business entities needed to realize a business use case and distributes the behavior of the business use case to them. The business designer defines the responsibilities, operations, attributes, and relationships of one or several business workers and business entities.

Business-Model Reviewer  

The business-model reviewer participates in formal reviews of the business use-case model and business object model.

Business-Process Analyst  

The business-process analyst leads and coordinates business use-case modeling by outlining and delimiting the organization that is being modeled .

Capsule Designer  

The capsule designer focuses on ensuring that the system is able to respond to events in a timely manner, in accord with the concurrency requirements.

Change Control Manager  

The change control manager (worker) oversees the change control process. This role is usually played by a Configuration (or Change) Control Board (CCB), which should consist of representatives from all interested parties, including customers, developers, and users. In a small project, a single person, such as the project manager or software architect, may play this role.

Code Reviewer  

A code reviewer is responsible for ensuring the quality of the source code and for planning and conducting source code reviews.

Configuration Manager  

A configuration manager is responsible for providing the overall CM infrastructure and environment for the product development team. The CM function supports the product development activity so that developers and integrators have appropriate workspaces to build and test their work and that all artifacts are available as required. The configuration manager ensures that the CM environment facilitates product review, change, and defect tracking activities. The configuration manager is also responsible for writing the CM plan and reporting change- request-based progress statistics.

Course Developer  

The course developer develops training material to teach users how to use the product. He or she creates slides, student notes, examples, tutorials, and so on to enhance their understanding of the product.

Database Designer  

The database designer defines the tables, indexes, views, constraints, triggers, stored procedures, tablespaces or storage parameters, and other - database-specific constructs needed to store, retrieve, and delete persistent objects.

Deployment Manager  

The deployment manager is responsible for plans to transition the product to the user community. These tasks are documented in deployment plans.

Design Reviewer  

The design reviewer plans and conducts the formal reviews of the design model.

Designer  

The designer defines the responsibilities, operations, attributes, and relationships of one or several classes and determines how they should be adjusted to the implementation environment. In addition, the designer may have responsibility for one or more design packages or design subsystems, including classes owned by the packages or subsystems.

Implementer  

An implementer is responsible for developing and testing components in accordance with the project's adopted standards so that they can be integrated into larger subsystems. When test components, such as drivers or stubs, must be created to support testing, the implementer is also responsible for developing and testing the test components and corresponding subsystems.

Process Engineer  

The process engineer is responsible for the software development process itself. This includes configuring the process before project start-up and continuously improving the process during the development effort.

Project Manager  

The project manager allocates resources, shapes priorities, coordinates interactions with the customers and users, and generally tries to keep the project team focused on the right goal. The project manager establishes a set of practices to ensure the integrity and quality of project artifacts.

Project Reviewer  

The project reviewer is responsible for evaluating project planning artifacts and project assessment artifacts, at major review points in the project lifecycle.

Requirements Reviewer  

The requirements reviewer plans and conducts the formal review of the use-case model.

Stakeholder  

A stakeholder is anyone who is materially affected by the outcome of the project.

System Administrator  

The system administrator maintains the development environment ”both hardware and software ”and is responsible for system administration, backup, and so on.

System Analyst  

The system analyst leads and coordinates requirements elicitation and use-case modeling by outlining the system's functionality and delimiting the system.

System Integrator  

Implementers promote their tested components into an integration area, where system integrators combine them to produce an internally released build. A system integrator is also responsible for planning the integration of the system.

Technical Writer  

The technical writer produces end-user support material, such as user guides, help texts , release notes, and so on.

Test Designer  

The test designer is responsible for the planning, design, implementation, and evaluation of testing, including generation of the test plan and test model, implementation of the test procedures, and evaluation of test coverage, test results, and effectiveness.

Tester  

The tester is responsible for executing testing, including test setup and execution; evaluating test execution and recovering from errors; and assessing the results of test and logging identified defects.

Tool Specialist  

The tool specialist is responsible for the supporting tools in the project. This includes assessing the need for tool support and selecting and acquiring tools.

Use-Case Specifier  

The use-case specifier details the specification of a part of the system's functionality by describing the requirements aspect of one or several use cases. The use-case specifier can also be responsible for a use-case package and for maintaining the integrity of that package. The use-case specifier responsible for a use-case package is also responsible for its contained use cases and actors.

User-Interface Designer  

The user-interface designer leads and coordinates the prototyping and design of the user interface by capturing requirements on the user interface, including capturing usability requirements; building user-interface prototypes ; involving other stakeholders of the user interface, such as end users, in usability reviews and use testing sessions; and reviewing and providing the appropriate feedback on the -final implementation of the user interface.



The Rational Unified Process. An Introduction
The Rational Unified Process: An Introduction (3rd Edition)
ISBN: 0321197704
EAN: 2147483647
Year: 1998
Pages: 176

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net