1. © Telelogic AB 1 Managing Change From Customer Request to Implementation Jean-Louis Vignaud & Dominic Tavassoli

2. © Telelogic AB 2 Change is inevitable All Projects are subject to change… a high risk challenge –Increasing number of contributors & stakeholders –Agility needs reactivity –Usability is key Change may impact the agreed baseline of Requirements –Need a formal organization-tuned process, –Assess, decide, communicate Change traceability –Relate project Development activities to Requirements and Change Management decisions –Establish a full audit trail –Need to record and manage change impacting all project artifacts

3. © Telelogic AB 3 DOORS/Change empowers your Requirements Change Request Process Predefined, customizable Lifecycles, allowing assignment, multiple reviewers, electronic signatures –Web-based submission, transitions, analysis history, reporting –Work on the Requirements is carried out inside DOORS Changes are proposed against requirements Proposed Changes are assessed and approved Proposed Changes are applied

4. © Telelogic AB 4 Controlling Requirement Changes The Requirements Engineer works inside DOORS Selects an assigned Requirement Change Request Works inside DOORS –Business as usual Delivers the work for review The integration automatically packages the changes together Changes are not in the module until they are approved & applied Identify RCR Propose Changes Send for approval

5. © Telelogic AB 5 Working against a Requirement Change Request Setting the default RCR indicates that all changes are to be tracked against this context –DOORS/Change builds the traceability report automatically –Enforced process control can be activated

6. © Telelogic AB 6 Unrivalled usability DOORS/Change brings critical enterprise functionality with no additional learning curve Users work as they normally would in DOORS –Changes are automatically tracked Effortless, intuitive change control of: –Requirements edition, creation, removal –Link creation and deletion –Document restructuring No constraints - multiple people may propose changes against a same DOORS module –DOORS Shareable edit & Exclusive edit modes

7. © Telelogic AB 7 Streamlining the Review & Approval process Notifications, reports and in-tool lists of changes improve communication Automatically created change-focused views for easier review in DOORS Web views provide powerful, intuitive enterprise-wide review Designated reviewers can each indicate approval and feedback

8. © Telelogic AB 8 Applying a Requirements Change Request Once approved, Requirement Change Requests can be applied The changes then appear in DOORS for all users

9. © Telelogic AB 9 Lifecycle Change Management DOORS/Change provides organizations with much more than a requirement change process It provides you with a best-in-class, proven, Enterprise-wide Lifecycle Change Management solution! –Powerful –Flexible –Scalable –Easy-to-Use Powered by award-winning Telelogic SYNERGY

10. © Telelogic AB 10 Providing a global view of change System Change Request Process System Change Request Requirements Change Request Process Changes Requirement Change Request The Lifecycle Change Management Audit trail provides visibility into the complete change across the Enterprise

11. © Telelogic AB 11 System Change Management Telelogics Lifecycle Change Management solution allows you to implement a central, high-level, system change process across engineering & business –Record and manage Change Requests that will potentially impact all project artifacts –Software, hardware, documentation, UML models, test cases… –May lead to a change of requirements –May lead to implementation activities System Change Request Process

12. © Telelogic AB 12 Submitting a System Change Request Forms and attributes are adaptable to your needs Controlled, mandatory fields in Red List box selection for ease of use

13. © Telelogic AB 13 High level change process Implement your corporate process –Capture critical information from key team members across the globe Information captured during the process Authorized transition steps

14. © Telelogic AB 14 Powerful Parent-Child hierarchy Requirement Change Requests can be children of a System CR (or submitted stand-alone) History log is automatically maintained Associated Requirement CRs are indicated Comments and discussions can also be captured

15. © Telelogic AB 15 Integrated Requirements Gathering DOORS/Change also provides a best-in-class Web interface for the request capture and review process –Personalized Web forms –Trace and document decisions –Requirements organized in DOORS and allocated to specific releases –Captures the original voice of the customer Product Review Board Process Customer Needs… User Needs Requirements

16. © Telelogic AB 16 Approved requests are included in DOORS Important information is captured, displayed and traceability is maintained

17. © Telelogic AB 17 Driving and Tracking Implementation System Change Request Process System Change Request Tasks & changes Implementation Requests Implementation Process Implementation carried out under CM control: SYNERGY/CM, ClearCase…

18. © Telelogic AB 18 Requirements Implementation Process Create implementation requests and engineering tasks directly from the requirements Complete traceability from needs to code –Impact analysis –Communication Better project control –Ensure you're doing the right thing –Real-time Reporting on progress, coverage –Building your knowledgebase

19. © Telelogic AB 19 Complete traceability and visibility Reporting available when development is under SYNERGY/CM control

20. © Telelogic AB 20 DOORS/Change implements process improvement best practices DOORS/Change helps you stay in control! Requirements Change Control –Scalable, enforceable CMMI change process (company-wide change control board…) –Impact analysis and traceability of a System Change Request Requirements Gathering –Implement a open to all, formal, repeatable but easy to use process Requirements Driven Development –Offshore development process control –Quality initiatives certification (CMMI…) –Regulatory certification (DO178B, Sarbanes-Oxley…)

21. © Telelogic AB 21 Integrated Requirements Gathering Raw Information Extending Lifecycle Change Management Requirements Driven Development Integrated Defect Management Requirements Driven Testing User Requirements Specification Functional Specification Design System Build Integration testing System testing Acceptance testing Change

22. © Telelogic AB 22 DOORS/Change Key Benefits Reduce project risks and increase customer confidence –Clear impact assessment and understanding Improve productivity with focused development teams and reduced rework risk –Clearly defined and communicated requirements changes Improve process control –Trusted repeatable CMMI process and automatic traceability between requirements and related development activities –Information is available for specialized, distributed teams Reduce scope creep and streamline development –Real-time visibility of the relationships between requirements and development activities –Track System Change Requests all the way to the impact to Requirements base and implementation information

23. © Telelogic AB 23 Key Benefits by Role Management –Extended Change Management covers the full lifecycle, preventing loss or miscommunication of fundamental requirements changes Analyst & DOORS user –Intuitive change control without the productivity hit or learning gap –Early impact analysis of requirements changes involving all relevant stakeholders –Reliable requirement change propagation after approval Developer –Relevant information available fast –Approved requirements changes are clearly and efficiently communicated, reducing risk of rework

24. © Telelogic AB 24 Key Benefits by Role QA/Tester –Approved requirements changes are clearly and timely communicated to the Test team, improving efficiency Administrator –Company-wide access for submission, discussion, review and reporting –State-of-the-art features such as electronic signature, user-tuned interfaces and multiple reviewer system, as well as the security and process control levels, out of the box

25. © Telelogic AB 25 Additional slides

26. © Telelogic AB 26 Full Web-based interface Complete with predefined reports & process templates Customizable workflow, submission, and transition forms Approval management Attachment support History & Discussion logs Advanced querying & full text search Built In Reporting & Open API Trend analysis Distributed team support Powered by SYNERGY/Change

27. © Telelogic AB 27 Enterprise Scalability No Restriction for platform support (UNIX or Windows) Everything on one server class machine Server Tuning to ensure good performance over a large user base (3000 total users, 200 simultaneous active users) No dependency on web technologies (ASP or IIS) to limit performance, viral infection, or security breaches Supports HTTPS secure connections LDAP support Multi-lifecycle/process support

28. © Telelogic AB 28 Predefine process template that is both extendible & customizable through the web-based interface –Add / modify / delete attributes –Add / modify / delete lifecycle state –Create multiple lifecycles based on the request type –Add / modify / delete forms Process Flexibility SYNERGY/Change API –Integrations –Data Migration –Notification Built-in Process Control and Management to ease administration

29. © Telelogic AB 29 Built-In Reporting, Querying, and Charting Pre-defined or user-defined reporting consistency on every platform –Report and Query builder allow each user to easily create and share reports and queries –No dependency on 3 rd party report tool (i.e. Crystal Reports) Reporting and Query into CM database Provides built-in Full Text Search capability that can be used across multiple databases Support to allow charting of groups of states –(Open v.s. Closed trend) Promote predefined charts for reports (matrix, pie) Charts and Reports are platform independent