Bookshelf Home | Contents | Index | Search | PDF

Siebel Field Service Guide > Release Manager >

Example Process Flow for Release Manager

---

This section presents an example process flow for setting up, using, and maintaining the Release Manager module.

Administrator Setup Procedures

Before end users can begin working with Release Manager, the administrator must set it up. The tasks applications administrators perform to set up Release Manager are listed below. It is recommended that you do them in the order shown.

Set up releases. (See Setting Up Releases.)
Set up the access list. (See Setting Up the Access List.)
Set up project teams. (See Setting Up Project Teams.)
Set up activity templates. (See Setting Up Activity Templates.)
Set up lists of values. (See Setting Up Lists of Values.)

Product Marketing End-User Procedures

After the administrator has set up Release Manager, Product Marketing begins its work. The tasks that Product Marketing personnel perform when using Release Manager are listed below. It is recommended that end users do them in the order shown.

Create features and subfeatures. (See Creating Features and Subfeatures.)
Create MRDs. (See Adding MRDs.)
Associate features with MRDs. (See Associating Features With an MRD.)

Engineering End-User Procedures

When Product Marketing has created features, Engineering begins its work. The tasks that Engineering personnel perform when using Release Manager are listed below. It is recommended that end users do them in the order shown.

Add engineering tasks and associating features. (See Adding Engineering Tasks and Linking Features.)
Adding Subtasks. (See Adding a Subtask to an Engineering Task.)

Quality Assurance End-User Procedures

When Engineering has implemented tasks, Quality Assurance begins its work. The tasks that Quality Assurance personnel perform when using Release Manager are listed below. It is recommended that end users do them in the order shown.

Create test plans and associate features. (See Creating Test Plans and Linking Features.)
Create test strategies. (See Creating Test Strategies.)
Associate test plans with test strategies. (See Associating a Test Plan with a Test Strategy.)
Record test pass results. (See Recording a Test Pass and Linking a Test Plan.)
Associate change requests with test passes. (See Associating Change Requests with a Test Pass.)
View test plan results. (See Viewing Test Plan Results.)

Technical Publications End User Procedures

When Product Marketing has written MRDs, Technical Publications begins its work. The tasks that Technical Publications personnel perform when using Release Manager are listed below. It is recommended that end users do them in the order shown.

Creating technical documents and linking features. (See Creating Technical Documents and Linking Features.)
Add activity plans to technical documents. (See Adding Activity Plans to Technical Documents.)

Administrator Maintenance Procedures

While end users are working with Release Manager, the administrator must maintain it. The tasks applications administrators and release administrators perform to maintain Release Manager are listed below. You can do them as needed, in any order.

Add product prototypes. (See Adding Product Prototypes.)
Add new area and subarea combinations. (See Adding New Area/Subarea Combinations.)
Update test plans and test strategies. (See Updating Test Plans and Test Strategies.)

Bookshelf Home | Contents | Index | Search | PDF