Dr. Mika Karaila
Metso Automation / PAS RTD
Metso experiences with Polarion:Requirement handling process &Safety aspects / certification
Polarion day 18.4.2013
© Metso
Metso Experiences
• Background / history
• Polarion usage in:-Design process-Safety process
• Motivation & Summary
© Metso
Background
• HW / SW design process done with Word orother textual document
• Requirement, specification, technical detail levelin own separated documents
• A lot of information not documented• Documents approved as a whole (in one or twoapproval sessions)
© Metso
Design Process
• A new design process created• First evaluation to find out possible bottlenecksor customization needs
• During evaluation tuning and training with actualusers and real project
• New design process is more fine grained:-Each requirement / specification is individual item-Status & approval runs parallel-All changes are stored into workitem history
© Metso
Design Process
• Requirements, specifications etc. can be linkedtogether=> traceability & coverage reports / checklists
• Requirements are verified in specification phase=> process is iterative and convergates
• Information model can be customized=> tuning each item type allows flexibility
• Project people can work parallel andsimultaniously even distributed different locations
© Metso
Safety process
•Safety process-Workflow & FMEA
•Workitems <-> documentation-History & baselines
•Progress, phases:-Agility <-> change management-Status, checklists & traceability
© Metso
Workflow example• Immediate checks and actions
© Metso
FMEA introduction 1/3•FMEA with links, traceability & coverage
© Metso
FMEA introduction 2/3
© Metso
FMEA introduction 3/3
© Metso
FMEA links & custom properties
© Metso
Document baseline•Excellent with document compare feature
Automatic table, all baselines visible
Manually filled part
© Metso
Dashboard trends•Frozen requirements•Change management -> peaks
© Metso
Dashboard trends•Specification progress visible
© Metso
Dashboard trends• Implementation architecture•Phases v0, v1 and v2 can be seen from the curve shape
v2v1
v0
© Metso
Overall status•Everything is inside one tool:
© Metso
Traceability example
© Metso
Traceability- Linking work items with different link roles
Available link roles between work item types depicted
© Metso
Traceability table• #includeForm("/macros.TraceabilityTable")
• #TraceabilityTableCommits("type:requirement AND NOT(status:heading OR status:closed)" "checked""type:specification AND (module:Functional Specification)" "checked" "type:design" "checked" "id,title,status")
© Metso
Polarion & safety process•Basic properties with custom properties
- Safety relation- SIL level- Etc.
•FMEA•Baseline for major releases / phases•Approvals•Traceability tables:
- Requirement coverage- Properties checked with status lists (with safety, SIL3 custom properties)- Backlinks to show chain:
• Requirement -> Specification -> Design -> Test case• All features required are implemented & tested
© Metso
Polarion usage in certification
•Process transparent and visible•Each user action can be identified•History and baseline•Evidence of workflow:
-Draft -> Ready -> Approved & Approved by person(s)
•Traceability:-Required to show that all requirements are met and
will be tested
All are helping in certification and transparency &automated macros are giving evidence.
© Metso
Certification evidencies
• Approvals
• Version control management == History &baselines
• Baseline ”freezing”, V-model phases
• PDF printouts (for archiving certified / reviewed”documents”)
© Metso
Motivation
• Everything is separated to own workitem
• Easier to handle and progress can be done stepby step
• Transparent visibility to all stake holders
• Automation in multiple places -> correct data
© Metso
Summary
• Design process is taken into use• Project team ”social design process” workingtogether
• Faster process• Traceability and other solutions are reusable• Higher quality in each level• Supports certification• Evidences needed for certification !!!
© Metso