D4 SPRDB

D4 SPRDB
Use Case Specification: Approve

Version SPRDB Schema 56

D4 SPRDB Version: SPRDB Schema 56
Approve Date: 03/July/2008
Approve.UCS

Revision History
Date Version Description Author
07/August/2007> 1.0 Initial Maritza Roldan
03/July/2008 SPRDB New Requirements. Maritza Roldan
Schema 56

©LSEC, 2007 ii
D4 SPRDB Version: SPRDB Schema 56
Approve Date: 03/July/2008
Approve.UCS

Table of Contents
1. Brief Description 1

2. Actors 1
2.1 Primary Actors 1
2.1.1 SEWG group 1
2.1.2 D4_SE group 1
2.1.3 Senior_Authority group 1
2.1.4 DND_Admin group 1

3. Flow of Events 1
3.1 Basic Flow 1
3.1.1 Start of Use Case 1
3.1.2 Access Control by Group 1
3.1.3 Access Control by Field User 1
3.1.4 Behavior for Mandatory Fields 1
3.1.5 Behavior for Optional Fields 2
3.1.6 Behavior for Read-Only Fields 3
3.1.7 Email Notification 3
3.1.8 Use Case Ends 3
3.2 Alternative Flows 3
3.2.1 Add an Attachment File 3
3.2.2 Cancel SEWG Approval 4
3.2.3 CQWeb Session Time out 4

4. Special Requirements 4

5. Pre-Conditions 4
5.1 The CQWeb user has logged on to the system. 4
5.2 Build numbers have been created on the system. 4
5.3 Priorities have been created on the system. 4
5.4 System Releases have been created on the system. 4
5.5 Vendor OEM’s have been created on the system. 4
5.6 SPR’s have been created on the system. 4

6. Post-Conditions 4

©LSEC, 2007 iii

D4 SPRDB Version: SPRDB Schema 56
Approve Date: 03/July/2008
Approve.UCS

Use Case Specification: Approve

1. Brief Description
The Software Engineering Working Group reviews the proposal and decided to approve the modification
request. The CQWeb authorized active user uses the Modification Request record in order to approve the
MR.

2. Actors
2.1 Primary Actors

2.1.1 SEWG group

2.1.2 D4_SE group

2.1.3 Senior_Authority group

2.1.4 DND_Admin group

3. Flow of Events
3.1 Basic Flow

3.1.1 Start of Use Case

This use case starts when the active user selects a Modification Request record from the
Awaiting_SEWG_Approval state and tells the system to change the state to SEWG_Approved by using the
Approve action.

3.1.2 Access Control by Group

The system allows only active users member of the
SEWG group,
D4_SE group,
Senior_Authority group,
DND_Admin group
to perform the action Approve.
The system will then make the MR form available for editing.

3.1.3 Access Control by Field User

The system shall NOT allow the Assigned DND_OPI authorized active user to perform the action Approve.
3.1.4 Behavior for Mandatory Fields
The system identifies the following fields as MANDATORY on the form and enforces the active user to
enter appropriate information:
• Title
• Vendor OEMs (The system allows the user to select one or more values from the available list.)

©LSEC, 2007 1
D4 SPRDB Version: SPRDB Schema 56
Approve Date: 03/July/2008
Approve.UCS

3.1.5 Behavior for Optional Fields

The system identifies the following fields as OPTIONAL on the form and allows the active user to enter
appropriate information:
• Additional Operational Information
• Additional Programmatic Information
• Approval Date (Optional for SEWG and D4_SE active members. The system allows the user to
select a date by presenting a calendar. The user then selects the required date.)
• Approval State (Optional for SEWG and D4_SE active members. The system sets the value
“Sanctioned”.)
• Associated MRs
• Attachments (The system allows CQWeb authorize active users to attached files with size no
greater than 5 MB.)
• DND OPI
• Follow Up Comments
• Modification Type
• MR Phase (Optional for D4_SE active members.)
• MR Phase Date (The system must identify any change done to the ‘MR Phase’ filed and capture
the Date/Time from the system clock and use that data to populate automatically this field.)
• MR Priority
• OEM OPIs (The system allows the user to select one or more values from the available list. The
system will generate the list based on the active members of the ‘OPI List’ field of the selected
related vendor OEM.)
• Problem Description
• Proposed Changes
• Relevant SPRs
• Select MR Associated
• Select Relevant SPRs
• SEWG Date (Optional for SEWG and D4_SE active members. The system allows the user to
select a date by presenting a calendar. The user then selects the required date.)
• SEWG Decision (Optional for SEWG and D4_SE active members. The system allows the user to
enter a textual detail decision.)
• Target Delivery Build
• Target Release (Optional for SEWG and D4_SE active members.)
• TCMS OPNET
• TCMS OPNET Impact
• TCMS TAC TB
• TCMS TAC TB Impact

©LSEC, 2007 2
D4 SPRDB Version: SPRDB Schema 56
Approve Date: 03/July/2008
Approve.UCS

3.1.6 Behavior for Read-Only Fields

The system identifies the following fields as READ-ONLY on the form so does not allow an active user to
modify these fields:
• Approval Date (Read only for the rest of users.)
• Approval State (Read only for the rest of users.)
• Follow Up Comments Log
• MR Number
• MR Phase (Read only for the rest of users.)
• MR Status (Open if the MR is on the state: SEWG_Approved)
• Rework Comments
• Rework Comments Log
• SEWG Date (Read only for the rest of users.)
• SEWG Decision (Read only for the rest of users.)
• Target Release (Read only for the rest of users.)
• TCMS OPNET
• TCMS OPNET Log
• TCMS TAC TB
• TCMS TAC TB Log

3.1.7 Email Notification

The active user tells the system to save the Modification Request. The system will respond by validating
and saving the changes done.
The system then will send an E-MAIL NOTIFICATION only to the following active users:
• Senior_Authority group
• D4_SE group
• Assigned DND_OPI
• Assigned OEM_OPIs

3.1.8 Use Case Ends

The system will make available the changes done to the Modification Request for other active users to view
them from a query.

3.2 Alternative Flows

3.2.1 Add an Attachment File

The active user tells the system to add an attachment file. The system will allow the user to browse to the
location where the file resides and select it. The system will then attach the file to the modification request
if the file size is not greater than 5 MB. The use case resumes at Basic Flow “Behavior for Optional
Fields”.

©LSEC, 2007 3
D4 SPRDB Version: SPRDB Schema 56
Approve Date: 03/July/2008
Approve.UCS

3.2.2 Cancel SEWG Approval

The system will allow the active user to cancel the SEWG approval of the Modification Request at any
time. The system will not save any entries made in the form. The use case ends.

3.2.3 CQWeb Session Time out

The system times out after 30 minutes (default) of inactivity and changes already made will not be saved.
The system will logs itself automatically out and will be asking your password again if you want to
continue. The use case ends.

4. Special Requirements
Not Applicable.

5. Pre-Conditions
5.1 The CQWeb user has logged on to the system.

5.2 Build numbers have been created on the system.

(See Create Build_Number use case)

5.3 Priorities have been created on the system.

(See Create Priority use case)

5.4 System Releases have been created on the system.

(See Create System_Release use case)

5.5 Vendor OEM’s have been created on the system.

(See Create Vendor_OEM use case)

5.6 SPR’s have been created on the system.

(See Submit SPR use case)

6. Post-Conditions
Not Applicable.

©LSEC, 2007 4