How Polarion supports Systems Engineering, based on ISO 15288

1. Systems Engineering using Polarion
Mithun Training & Consulting BV
Contact: Harry Julsing
M: +31(0)6-511 30380
T: +31(0)33-457 0840
E: harry.julsing@mithun.nl
I: www.mithun.nl

2. Leidraad SE
The “Leidraad SE” is the Dutch industry
standard for infra projects using Systems
Engineering
Partners Leidraad:
Prorail,
Rijkswaterstaat,
NL Ingenieurs,
Bouwend Nederland,
de Vereniging van Waterbouwers and
Uneto VNI

3. Background Leidraad
A National initiative between contracting
parties and contractors in the
Infrastructure market
The Leidraad SE offers for a company
specific implementation a common
framework, using uniformal concepts and
processes
Source: www.leidraadse.nl

4. What is SE for Infra?
Start from the system view
A phased approach based on (ISO 15288)
to come to an integral verified and
validated solution from an initial customer
requirements.
Source: www.leidraadse.nl

5. ISO 15288
Systems and software engineering –
system life cycle process
Not a straitjacket but an open framework
Offers:
Clear role definitions
Fits in current way of working practices
Aimed at continuous improvement

6. Processes in ISO 15288
Specification stakeholder requirements
Requirements analysis
Architecture design
Implementation
Integration
Verification
Validation

7. Polarion
Application Life Cycle Solution
Supports any process
Comes with wealth of knowledge, template
examples, additional functionality
Easy to configure: Absolute minimum of
scripting required
Leading to the lowest cost of ownership in
the market
Quick start possible

8. Polarion solution:
V-Model Extension
Based on ISO/IEC 15288 & IEEE 1220-2005
Framework based on a workflow engine, to automatically
create derived workitems
Enforce tracearbility from requirements to testcases
For both agile and waterval (V-Model) approaches.
.
For more information and download template:
http://extensions.polarion.com/extensions/182-v-model-project-template

9. Structure Template
Commercial req’s
System req’s &
Validation tests
Customer view
System view
Hardware req’s &
Verification tests
Mechatr. req’s &
Verification tests
Software req’s &
Verification tests
Subsystem
view
Design
view
Hardw. design &
Verification tests
Mechatr. req’s &
Verification tests
Software req’s &
Verification tests
Documentation
Testing

10. Document View

11. Detail View

12. Traceability matrix

13. Project Status

14. How it works
The template uses tasks to:
Assign tasks to engineers, from draft to implemented
Consequently the requirement is handed over to QA engineers for
verification and validation.
In case of an issue, a defect is automatically created, which needs to
be resolved before the requirement can receive the status verified
Only then, the requirement can be released as a package for
production.

15. Next Steps
Live Product presentation, using template
Proof of concept
Go/no go
Implementation (training and
implementation support package)
Pilot project