The page is intended to summarize all the requirements for Dublin Release.

These requirements have been prioritized by the TSC to realistically fit within the Dublin Release Timeline.

The Release Scope was finalized during the M1 Release Planning milestone at the TSC on January 31st.

The Requirements extracted from SP lists of priorities for Dublin are covered either by the Use Case, the functional requirements, the non functional requirement or within a project scope of work.

TSC Prioritization (Ranking)

RANK #0 – Special GO - fully covered by involved companies
RANK #1 – GO “Must Have”
RANK #2 - GO “Continuity of previous releases”
RANK #3 – GO if PTLs are OK since the impacted applications are less “stretched” i.e. CLAMP, Policy, DCAE etc.
RANK #4 – NO GO – Mostly new requirements/features/projects

Use Cases

M1 Scorecard:

Green: Use Case will be fully implemented and tested
Yellow: Use Case will be partially implemented. It is possible to identify capabilities for this use case that can be tested (phasing approach).
Red: Use Case can not be partially delivered, min. requirements can not be met in order to define a testing strategy.

T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team

M1 Scorecard:

Green: The functional requirement will be fully implemented and tested
Yellow: The functional requirement will be partially implemented. It is possible to identify capabilities for this functional requirement that can be tested (phasing approach).
Red: The functional requirement can not be partially delivered, min. requirements can not be met in order to define a testing strategy

T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team

M1 Scorecard:

Green: The non-functional requirement will be fully implemented and tested
Yellow: The non-functional requirement will be partially implemented. It is possible to identify capabilities for this non-functional requirement can be tested (phasing approach).
Red: The non-functional requirement can not be partially delivered, min. requirements can not be met in order to define a testing strategy

T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team

POC Definition - (In Progress)

T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team