2015-05-17 How to optimize the management of requirements by taking into account the business need in an ALM approach? Friday 15 May 2015 CONTENTS 1. Key Concepts 2. Benefits of taking into account the business processes and requirements engineering in a vision ALM 3. Process Steps of : Business Process - Requirements - Tests 4. Management of change requests with ALM tools 5. Good Practices 6. Conclusion 2 1 2015-05-17 CONTENTS 1. Key Concepts 2. Benefits of taking into account the business processes and requirements engineering in a vision ALM 3. Process Steps of : Business Process - Requirements - Tests 4. Management of change requests with ALM tools 5. Good Practices 6. Conclusion 3 1. Key Concepts • ALM Application Lifecycle Management (ALM) is a continuous process of managing the entire application lifecycle. ALM is based on the complete traceability between business processes, functional and technical requirements, technical components, testing and related data sets that allow us to assess further the impact of changes. ALM is an industrial response to the desire to reduce costs and time by ensuring the coherence of all stakeholders activities in the software production chain. ALM is a response to the technological and geographical complexity associated with cultural differences of resources and stakeholders involved into the realization of applications. 4 2 2015-05-17 1. Key Concepts • Business Process and Requirement A Business Process is a sequence of activities with the object to produce a final result which is definite, specific, concrete, measurable, implemented by an organized group of resources (people, material resources, information, etc…). A Requirement corresponds to the common structured language, that allows us to express the need or expectation, formulated by a client or a user, and which should be understood by all project stakeholders. Reminder ISO 9000 definitions - Process : A set of interacting activities that transform inputs into outputs elements. - Requirement : need or expectation expressed, usually implied or imposed. 5 1. Key Concepts • Requirement Engineering Based ABB - Westfall 2005, Base Wiegers 2003 6 3 2015-05-17 CONTENTS 1. Key Concepts 2. Benefits of taking into account the business processes and requirements engineering in a vision ALM 3. Process Steps of : Business Process - Requirements - Tests 4. Management of change requests with ALM tools 5. Good Practices 6. Conclusion 7 2. Benefits of taking into account the business processes and requirements engineering in a vision ALM • Benefits 1 : Optimisation of each project task effort Source RUP 8 Modeling business is an activity that exists throughout the life cycle of an application. It is necessary to ensure traceability of business processes with requirements, testing and technical components derived from them, in order to take optimal account changes and impacts. 4 2015-05-17 2. Benefits of taking into account the business processes and requirements engineering in a vision ALM Benefits 2 : Have an integrated workflow management applications for changing business needs 1 Request changes validated 2 Analyse d’impact Référentiel des Processus Métier Business Process 1 Business Process 2 ….. Business Process n 3 4 Getting impacts visibility and modifications to achieve Référentiel des Exigences Référentiel des Tests Test 1 Requirement 1 Requirement 2 ….. Identification of tests to modify and test campaigns run Test 2 ….. Requirement n Test n 9 2. Benefits of taking into account the business processes and requirements engineering in a vision ALM • Benefits 3 :A double level of quality (Verification and Validation) Verification, is to verify that the product : Works as expected. Meet the functional and technical specification. Fits correctly in the information system Integrate IT Production System Test Goal : Check the operation of the product and its interfaces between applications Validation, is to validate that the product : Meet User Needs Meet the functional requirements Fits correctly in the business process Acceptance Test Goal : Validate good functioning of the product with business process The consideration of business processes and requirements defining the system can associate their tests improving the quality of the delivered system 5 2015-05-17 CONTENTS 1. Key Concepts 2. Benefits of taking into account the business processes and requirements engineering in a vision ALM 3. Process Steps of : Business Process - Requirements - Tests 4. Management of change requests with ALM tools 5. Good Practices 6. Conclusion 11 3. Process step of : Business Process – Requirement – Test • Different views of IT system Business Strategy Clients Suppliers Clients Business Partners I n f o r m a t i o n Process Event Organization Functional Interface Function Use Case Application Application Component Technical Technical Infrastructure S o s f y t s w t a e r m e s y s t e m Business view: mapping of organizational business processes. Functional view: description of the functionality (services) offered by the information system to support business processes. Application View: description of all elements of the computer system implementing the services urbanized form of software components. Technical view : description of the operation of infrastructure software elements of the computer system. Technological change 6 2015-05-17 3. Process step of : Business Process – Requirement – Test • Requirement Repository Structure Business Process Activities Acceptance Test Package of Use Case Business view Use Case Business rules Application TP Functionality Functionel Rules Batch Functional Architecture System Test Batch Coponent Batch Component No functional Requirement Performance 3. Process step of : Business Process – Requirement – Test Different step Business Process Establish Business Process AMOA Requirement Engineering Establish Activities Develop Requirement AMOA MOA, MOE, architect, integrator, etc.. Establish traceability between requirements Content (relevance, completeness) Traceability attributes (priority) MOA, MOE, architect, integrator, etc.. MOA, MOE, architect, integrator, etc.. Check Requirement Repository Business Repository Validate Requirement Establish and maintain the repository. Content (relevance, completeness) Traceability attributes (priority) Requirement Responsable Requirement Responsable Publish the requirements in the test management tools and technical components Requirement Responsable Component Technical Management Allocate requirements to components MOE Complete and integrate components MOE Test Management Write test cases Analyst testeur Establish traceability between requirements and tests Analyst testeur 7 2015-05-17 3. Process step of : Business Process – Requirement – Test Different step Business Process Change Business Process AMOA Requirement Engineering Change Activities Modify Requirement AMOA MOA, MOE, architect, integrator, etc.. Check impact of requirements Validate Requirement Content (relevance, completeness) Traceability attributes (priority) MOA, MOE, architect, integrator, etc.. MOA, MOE, architect, integrator, etc.. Check Requirement Repository maintain the repository. Content (relevance, completeness) Traceability attributes (priority) Référentiel Métier Requirement Responsable Requirement Responsable Change (Business Strategy) Publish the requirements in the test management tools and technical components Requirement Responsable Component Technical Management Allocate requirements to components MOE Modify and integrate components MOE Test Management Modify test cases Analyst testeur Establish traceability between requirements and tests Analyst testeur CONTENTS 1. Key Concepts 2. Benefits of taking into account the business processes and requirements engineering in a vision ALM 3. Process Steps of : Business Process - Requirements - Tests 4. Management of change requests with ALM tools 5. Good Practices 6. Conclusion 16 8 2015-05-17 4. Management of change requests with ALM Tools Tools must be synchronize Non Conformity Tools Modeling tool of business processes Management tool change requests Manage Requirement Tools Testing Tools Business Process Acceptance Tools • Use Case • Business Rules Requirements development tool Technical components management tool Functionality • Function • IT Rules • Batch Technical Test • Quartier technique • Feuilles de style • Composant • Use Case • Business Rules System Test • Function • IT Rules • Batch Component Test • Component Test Configuration / Baseline Tools 4. Management of change requests with ALM Tools Tools must be synchronize Outil de gestion des non conformités Outil de modélisation des processus métiers Outil de développement des exigences Outil de gestion des demandes de modification Outil de gestion des composants techniques Outil de gestion des exigences Outil de gestion des tests Processus métier Tests d’Acceptation • Cas d’utilisation • Règles de gestion métier • Cas d’utilisation • Règles de gestion métier Fonctionnalités Tests Systèmes et d’intégration • Fonctions • Règles de gestion IT • Batch Composants techniques • Quartier technique • Feuilles de style • Composant • Fonctions • Règles de gestion IT • Batch Tests de Composants • Tests de composant Outil de gestion de configuration / Baseline 9 2015-05-17 CONTENTS 1. Key Concepts 2. Benefits of taking into account the business processes and requirements engineering in a vision ALM 3. Process Steps of : Business Process - Requirements - Tests 4. Management of change requests with ALM tools 5. Good Practices 6. Conclusion 19 5. GOOD PRACTICES Capitalize on Business Process - Modify only process the tool representing the repository profession. - Expand the use cases to validate the activities of business processes. Structuring and typing of Requirements - Structuring the repository requirements by type. - Structure the reference tests identical to that of the requirements. - Adopt adequate nomenclature. Manage Configuration - Place under the validated configuration requirements from business processes. - Extract Baseline at each major milestone of the project (or on request) Manage change requests - Manage change requests priority by analyzing the impact on business processes. Manage traceability - Ensure traceability between requirements and exhaustively Requirements and Test Case / Technical Components 20 10 2015-05-17 CONTENTS 1. Key Concepts 2. Benefits of taking into account the business processes and requirements engineering in a vision ALM 3. Process Steps of : Business Process - Requirements - Tests 4. Management of change requests with ALM tools 5. Good Practices 6. Conclusion 21 CONCLUSION • With this presentation, we hope to have shared with you the steps and benefits associated with the implementation of requirements management by taking into account the business need in an ALM approach. • Although the appearance setting up a requirements engineering process may seem complex and lengthy, the return on investment has proven even that it offers the ability to integrate a lot of changes. • The intense rhythm of product deliveries corresponds to the current rhythm of our customers’ needs and makes us acquire methods and tools enabling the implementation of best practices. • Finally, being itself based on a requirements development, linking the project stakeholders from the beginning, it remains fully compliant with the AGILE methods. 22 11
© Copyright 2024