Polarion ALM Application Lifecycle Management

Transcription

1 Polarion ALM Demo 1

2 Polarion ALM Application Lifecycle Management Management Test & Quality Management Audits, Metrics, & Reports Risk Management Polarion Variant Management Change Management Issue & Defect Management Project Management 2

3 Why to invest in ALM? Talouselämä A leading business magazine in Finland. Mika Helenius, Vice-Chairman of The Finnish Information Processing Association, FIPA (TIVIA) wrote: Gartner says that 90 % percent of corporate investments go to business ICT systems and solutions. Why? Because those ICT systems are taken into use to beat the competition. It's not a cost. It's an investment to productivity. 3

4 What kind of productivity? 1) Saving work effort Individual people doing their work faster. (working smarter, not harder!) 2) Cutting time-to-market Shortening project and delivery time Collaboration Parallel work Completing project phases faster 3) Improving quality Doing the right things: products that bring maximum value and delight to customers Doing them right from the start Avoiding errors and mistakes 4

5 Typical way of collaboration today Specifications Defects Changes Defect Fixes User Stories Tasks Testing Reports Technical Specifications Progress Status 5

6 Sets of tools to manage all this Specifications Changes Testing & QA Issue Tracker & Agile Tool Task & Project Management 6

7 Polarion ALM Principle 7

8 Annual work days Cost of investing to productivity Bar chart to give proportions during the first year Numbers in the figure are equivalent in work days per person using the tool. Cost of one person for the employer per year is in the order of 80 k. Polarion license purchase cost is between depending on license type and use of floating licenses. For simplicity, 1000 /person is estimated on the average.

9 Annual work days First Year: Comparing Polarion (~1.3 %) cost to Taking it (or any new process/tool) into use: estimated Low...High Effort Productivity boost (estimated ~5 % during the first year) 9

10 Annual work days Second Year Cost is only Polarion maintenance (optional) Effort decreases from the first year Productivity boost estimated to be modest 10 % 10

11 Annual work days Third Year Cost is only Polarion maintenance (optional) Effort in taking new tool/processes into use continues to decrease Productivity boost estimated to be 20 % 11

12 Annual work days Third Year Big Picture Productivity boost shows up Tool cost and effort are both insignificant 12

13 Summary of Cost vs. Productivity The effort of taking any new process or tool(s) into use can easily dominate the tool cost The cost of the tool itself is not significant, and it continues to lose importance in the long run Both costs are not significant but productivity boost is Conclusion: better to choose a tool with High productivity boost potential Flexibility to use it in the long term without changing again 13

14 Polarion Demo vs. Polarion Use 14

15 Part A SW Project Introduction to Polarion and its concepts Working mainly in Work Items view Intro to Live Documents Demo Flow Part B Systems Engineering Workflow Approvals & Signatures Risk Management Part C Useful Features For regulatory compliance, usabilility & productivity, etc. + Questions & Answers! 15

16 Pay attention! What s special in Polarion? 1. Generic work item 2. Features for key processes: Reqs, Test Mgmt, Changes, PM, agile, Risks 3. Traceability 4. Live Document (patented!) 5. Wiki for reporting 16

17 Let s keep it simple! Two process areas: management & agile project planning (scrum) Implements User Stories Define some high-level for a software product. Specify more details and plan towards implementation with User Stories 17

18 Basic Concepts of Polarion 18

19 Adding another process area: Testing & Test Management Verifies Test Cases Implements User Stories Verifies Test Cases 19

20 What is the typical way of managing the traceability between process areas? Excel Verifies Test Cases Implements User Stories Verifies Test Cases Managing traceability alone can take 25 % or more of project time. This can be reduced to 5-10 % by using Polarion. 20

21 Yet another process area: Defect/Issue Management verifies Test Cases implements User Stories verifies Test Cases is triggered by Defects 21

22 Change Requests It s gettting better and better! Change Management is impacted by verifies Test Cases implements User Stories verifies Test Cases is triggered by Defects 22

23 Live Document You don t have to give up specs although working with a tool. No double work needed! Import from Word Word round-trip Supports workflow, review-approval process, commenting and signatures Easily reusable Document templates Polarion VARIANTS gives even more possibilities for controlling product variability 23

24 Systems Engineering Change Requests System SW / Mech. / Electr. / Requirement System Test Cases SW / Mech. / Electr. Test Cases Work Packages Tasks Defects Unit Test Cases 24

25

26 Change Requests Systems Engineering Introducing Risk Assessment Risks System SW / Mech. / Electr. / Requirement System Test Cases SW / Mech. / Electr. Test Cases Work Packages Tasks Defects Unit Test Cases 26

27 The safety of a complex system can only be assessed based on its documentation. Major part of the electronic/programmable system is totally invisible! More than 70 % of software work consist of documentation (in safety-related environment) If the documentation along with evidence can be recorded while doing, the productivity boost is huge!

28 One real-life example what excel approach leads to Product development project 3-4 years Project Documentation, traceability, audits Parsing the validation matrix afterwards takes 6-8 months (+20 %)

29 Certified Tool Makes Validation Easier The Only ALM Tool Certified for IEC / ISO Templates for FDA, ISO, IEC, FAA, CMMI, SPICE etc. "We re just thrilled about Polarion s tool qualification for ISO This saves us a lot of time and money in our own qualification process. - Maria Eugenia Zuniga, Quantum Technologies

30 Did you notice the key things? 1. Generic work item 2. Features for key processes: Reqs, Test Mgmt, Changes, PM, agile, Risks 3. Traceability 4. Live Document (patented!) 5. Wiki for reporting 30

31 Important tool capabilities in the long run 1. Scalability and performance 2. Flexibility for changing and evolving needs 3. Open interfaces, integrations, connectors 4. Community and extensions See: 31

32 See more at: