System

Product Information

Mgates Product Name* Hoboken 1.0

Metric Reporting Month-Year May-09

Product PMR Author: Joe Marketeer

Document Details for Reporting Release

DCX3200/DCX3200-M P2 Digital Client
Document Title Product Functional Specification (PFS)

Document Author Edward Boris

Digitalcm Document Number x.3

Digitalcm Document Version 365-095-09205

Digitalcm release date 10/21/2009

Is this a Post M7 Release? (Y or N) n

Document Details for Prior Release

Digitalcm release date 10/21/2009

PFS Revision Number (for Previous
Release): x.2

Color Legend

Auto-populated from Tools

 Entered by Manager/Author

Calculated Values

Template Version: 1.2

 Systems Engineering Document Metrics Record

Reserved For Manager Use Only:

Do NOT directly edit these fields

Document/Product Information Schedule Metrics Summary

PFS Product Name
PFS Version Planned
(M7 version bolded) PLM/SE

Hoboken 1.0 365-095-09205 Joe Marketeer/Edward Boris 1.0

REMEMBER

Fill out All Blue Items

Fill Out All Green items (they may be auto-populated)

Make sure to fill out Schedule Tab always
ord

Schedule Metrics Summary Document Churn Summary

Actual Variance Overall PMR Modify New Delete Clarify

1.0 0.00%
 Report
Review Cycle Time Summary
Date
Not (Month-
Planned Actual Variance
Implemented Year)

5.0 5.0 0.00% May-09

> Threshold Analysis
 Systems Engineering Document Metrics Reco

Threshold Analysis is required when schedule variance >30% a

Schedule Variance review cycle time variance >20%
# Days Planned 1
# Actual Days 1.0 Explanation of threshold exceeding variance
Schedule Variance 0.00%

REVIEW CYCLE TIME METRICS

Planned Cycle Time
(days) 5.0
Actual Cycle Time
(days) 5.0
RCT Variance 0.00%
ment Metrics Record

n schedule variance >30% and/or

Exceeds
0
Threshold?

variance
 Systems Engineering Document Me

% of Total % of Total
Churn Metrics Number Baseline Reqs
Reqs Change Values from
Diff Tool

Total Number of Reqs (Previous

Release): 1 0

TOTAL Requirement Changes 1 100.00% 100.00% 0

CLARIFY Requirement Changes 0.00% 0.00%

MODIFY Requirement Changes* 0.00% 0.00% 0

PMR Requirement Changes 0.00% 0.00%

ADD Requirement Changes** 0.00% 0.00% 0

DELETE Requirement Changes*** 0 0.00% 0.00% 0

NOT IMPLEMENTED Requirement
Changes 0.00% 0.00%
TOTAL 0 Should = 0

Churn Category Notes

* MODIFY - Requirements should be counted as "MODIFY" if there was a change to the requirement because it wa
release of the PFS. If not, it should be counted as "CLARIFY".

** ADD - Requirements should be counted as "ADD" if they were missed in a previous release of the PFS. If not, th
"PMR" if they were added because of a change to the PMR or counted as "CLARIFY" if requirements were added b
clarify an existing requirement.

*** DELETE - Requirements should be counted as "DELETE" if they were erroneously included in the PFS. If not, t
counted as "NOT IMPLEMENTED" or counted as "PMR" as a result of a change to the PMR.
 ering Document Metrics Record

Total Requirement
Churn Value

Baseline Requirements: 1

Update Requirement
1
Changes:
Total Churn Percentage: 100.00%

Post M7
n

Threshold Analysis is required when churn >20% AND Post M7

Exceeds
Threshold?

Explanation of threshold exceeding churn

e to the requirement because it was wrong in the previous

vious release of the PFS. If not, they should be counted as

RIFY" if requirements were added because of a request to

ously included in the PFS. If not, they should either be

to the PMR.
0
 Schedule
Metrics
FR/TR RATIOS Needed? n

Review
Cycle
Time
(RCT)
Metric
Total FRs 1 Needed? n
Churn
Metrics
Total TRs 0 Needed? y
Total FR/TR #DIV/0!
Total FR:TR 1:0
New FRs 0
New TRs 0
New FR/TR #DIV/0!
New FR:TR 0

Manager Use Only:

TOTAL NEW
TOTAL FRs TOTAL TRs FR:TR DFRs DTRs FR
1 0 1:0 0 0 0
NEW New
TR FR:TR
0 0