1. QPack Application Lifecycle Management The key for successful project management

2. Presentation Scope About Orcanos QPack Concept and methodology Requirements Management Change Management Test Management Defect Tracking Reports Implementation

3. About Orcanos Develop and implement QPack unified ALM system Focus and Experts in the ALM domain, with proven and successful best practices Short delivery time for change requests Industry based solutions: Software/Medical Device… Support regulation compliance (ISO, FDA, TL9000…)

4. Diverse Industry Solution Software SW/HW Medical

5. Successful Implementations Navotek has tremendously reduced the development process time using QPack for FDA documents generation Tradertools used QPack to improved the release management and tracking procedures Flashnetworks used QPack to comply with TL9000 Alvarion use QPack to improve collaboration for ALM activities across continents

6. The Challenge of ALM Market Definition Develop Test Test Results

8. Poor visibility of impact of change

9. No reuse of data/Duplicated data

10. Time spent looking for info

11. Multiple repositoriesTest Results

12. QPack ALM Solution Scope QPack Business Definition Test Develop ALM Analytics (Based on Siebel Analytics) S O A Source Control IDE Office Automation

13. QPack ALM Methodology Market Definition Develop Test Design/Tasks Test Plan Definition Business requirements Development Requirements 2.0 1.0 Changes/ Defects Risk Management Test Execution Customer Defect Reporting

14. QPack Main Advantages Unified ALM platform – business and development requirements, test management and defects Full traceability – Requirements->testing->defects Regulatory compliance (ISO, FDA…) with Document generation Automated processes reduces manual work Change management for better visibility of change impact Easy to use user interface with short learning curve

15. QPack Concept Main screen

16. QPack Concept Application Lifecycle Your Projects/Products

17. QPack Methodology Solution and Projects Hierarchy

18. Manage Integrated Products Software Version 2.0

19. Project Version and Solution Solution/parent project(2.2) Sub Project #1 Version 1.0 Requirement A Requirement B Version 2.1 Requirement A’ Requirement C Sub Project #2 Version 3.2 Requirement D Requirement E

20. Project Version and Solution

21. QPack Methodology Business Requirements

22. Business Requirements Document Document structure based on regulation (can be imported)

23. Business Requirements Traceability Cover Business Requirement with multiple Low-level requirement

24. Business Requirements Traceability

25. Requirements Traceability Chart Manage logical relations Change in specific item might affect other places

26. Embed Traceability Report In Doc

27. Generate Market Requirements Document

28. Generated Traceability Matrix

29. QPack Methodology Requirements Management

30. Requirements Tree

31. Requirements Version Management Project A Version 1.0 Requirement A (1.0) Requirement B (1.0) Requirement C (1.0)

32. Requirements Version Management Project A Version 1.0 Project A Version 1.0.1 Requirement A (1.0) Requirement A’ (1.0) Requirement B (1.0) Requirement B (1.0) Requirement C (1.0) Requirement C (1.0) Requirement D (1.0)

33. Requirements Version Management Project A Version 2.0 Project A Version 1.0 Project A Version 1.0.1 Requirement E (2.0) Requirement A (1.0) Requirement A’ (1.0) Requirement A’ (2.0) Requirement B (1.0) Requirement B (1.0) Requirement B (1.0) Requirement C (1.0) Requirement C (1.0) Requirement C (1.0) Requirement D (1.0)

34. Requirements Version Management Project A Version 3.0 Project A Version 2.0 Project A Version 1.0 Requirement B (1.0) Requirement E (2.0) Project A Version 1.0.1 Requirement E (2.0) Requirement F (3.0) Requirement A (1.0) Requirement A’ (2.0) Requirement A’ (1.0) Requirement A’ (2.0) Requirement C (1.0) Requirement B (1.0) Requirement B (1.0) Requirement B (1.0) Requirement C (1.0) Requirement C (1.0) Requirement C (1.0) Requirement D (1.0)

35. Project Version and Requirements

36. Requirement Lifecycle (Workflow)

37. Business Requirements Coverage

38. Requirements Tracking – Status Breakdown

39. Requirements By User and Status

40. Requirements By Project and Status

41. QPack Methodology Change Management

42. Change Management Manage changes in a disconnected repository Evaluate change before implementation Manage change workflow Customers Change Requests Internal Change Requests Project Roadmap (Pool)

43. Change Management Process 1. Add change to pool

44. Change Management Process 2. Approve change

45. Change Management Process 3. Implement change Added from change management repository

46. Change Management Process 4. Cover change with test case

47. Change Management Report

48. Requirements Management Summary Manage various type of requirements Change management using versions mechanism and change request repository Use workflow to automate requirements lifecycle Full Traceability from market to R&D, across projects Full Office Integration Comply with your regulation (ISO9001, FDA…)

49. QPack Methodology Risk Management

50. Risk Management (FMEA) Reduce project risk Relate risk objects to ALM artifacts Generate Risk Management Document Easily track high-risk features

51. Risk Management Tracking Tale Automatically generated from QPack

52. QPack Methodology Test Management

53. Test Plan And Coverage Plan tests according to requirements to assure requirements are tested Build testing tree Use test parameters for complex testing configurations Manage test type

54. Cover Requirements By Test Cases

56. WinXP Pro

57. Windows Vista

58. Linux

59. Browser type

60. Explorer 6

62. Business Requirements Coverage

63. Requirement Coverage By Test Cases

64. Test Execution – Test work plan Easily build test run suites (work plans) for QA team Report defects from test run improves QA and development team communication Automatic traceability of requirements by defects and test results Track test results for better decision making and quality assurance

65. Execute Tests – QPack Test Execution Assign tests to execute Test configuration (parameters)

66. Test Run Screen Pass/Fail test on step level Run tests by steps Parse test data by parameters

67. Automatic Defect Report On Test Fail Report defect from test on step failure Defect automatically connected to the tests Defect automatically routed to specific developer Defect contains found version, severity, priority, etc. Defect contains test data Embedded Screen Capture

68. Automatic Defect Report On Test Fail Steps from test inserted to defect Including test parameters

69. Business Requirements Coverage

70. Last Run Results By Feature

71. Test Run Results By Work Plan

72. Failure Probability Report

73. Test Run Effectiveness

74. QA Team Effectiveness

75. QPack Methodology Defect Tracking

77. Convert defect to test case

79. Defect Traced To Specific Requirement

80. Business Requirements Coverage

81. Open vs Fix Rate of Defects

82. Internal/Customer Defects Create and store filters by release, status, execution sets, etc.

83. Defects Per Build

84. Defects Average Fix Time

85. QPack Methodology ALM Analytics

86. Full Coverage Matrix

87. User Dashboard Personalized views Easily add charts, and filters

88. Release Manager Track changes on each release Monitor release quality Monitor test execution progress

89. Implementing QPack Organization Analysis Organization structure, users and roles Products and solutions Process mapping Existing tools Existing working methodologies Implementation and training Standards and documents management Business requirements processes Development requirements processes Coverage and traceability processes Test plan and execution processes Defects tracking processes Reporting and alerts Administration

90. Thank You www.orcanos.com