1 / 12

Concept of Requirements Management Tool

Concept of Requirements Management Tool. International Workshop on Challenges in methodology, representation, and tooling for automotive embedded systems 24 – 25 September 2012 Berlin Markus Kelanti (markus.kelanti@oulu.fi), Pasi Kuvaja (pasi.kuvaja@oulu.fi). Contents. Motivation

yaholo
Télécharger la présentation

Concept of Requirements Management Tool

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Concept of Requirements Management Tool International Workshop on Challenges in methodology, representation, and tooling for automotive embedded systems 24 – 25 September 2012 Berlin Markus Kelanti (markus.kelanti@oulu.fi), Pasi Kuvaja (pasi.kuvaja@oulu.fi)

  2. Contents • Motivation • Requirements Management concepts • Requirements Management Workflow • Requirements Management activities • Task based approach with views • RE item data structure • RMT prototype • RMT prototype example screenshots

  3. Motivation • Based on previous experience and interviews, we have following main problems in Requirements Management: • Methodology related • Understanding the original request • Information content of RE items • Unclear concepts and different stakeholders have different understanding of concepts • Large number of requirements (over 10000) in complex systems • Tool related • Support for co-operation in distributed development • Traceability to original customer requirements • Seamless editing of RE items in multi-user environments • Support for Requirements Management • There is a clear need to rethink practices in Requirements Management

  4. Requirements Management Concepts • Request • All incoming needs, requirements and demands are recorded as requests. • RMT is designed to ensure every incoming request is described from the original stakeholder’s point of view • Requests are always analysed in Problem Domain • Requirement • Requirements are derived from requests • Requirements are used to describe how a request can be realised in a Solution Domain system • Requirements are always analysed in Solution Domain • Feature • Features are derived from requirements and requests linked to them • Features describe what the produced system should do, based on requests and requirements

  5. Requirements Management Workflow Request Request Request Requirement Requirement Requirement Requirement Requirement Feature Feature

  6. Requirements Management activities • Each RE item in RMT has an owner and contributor(s) • Owner is responsible for the RE item and can assign contributors for a RE item • Contributors are other users who can participate to analyse, write or comment a RE item • After a RE item owner considers the itemto be ready, he submits it for a decision making process • Responsible people in this process decide whether to accept, reject or return it back for additional analysis • Accepted RE items shall be sent to a next phase in a process

  7. Task based approach with views • Tasks are part of activities belonging to a development process and describe what should be done in the process • Views can be customised to support any task in the RE • The goal is to show only the relevant information for a task • Users can access a same RE item but use different or same data using different views Elicitation Analysis RE Activities … Task … Request input Comment requests Reporting view Decison making … View

  8. RE item data structure • Each RE item has a similar basic description: • The origin stakeholder • The system in focus • RE item description • Interest to system • Request value • Impact to system • Rest of the information is divided into: • System information • Business information • Organisational and process relevant information • Item specific information • Additional content: • Attachments • History • Comments and notes

  9. RMT prototype • Requirements Management Tool (RMT) prototype supports the RE phase in AMALTHEA Design Flow • The purpose of RMT is to guide the user to record incoming requests and supportrequirement and feature development. • RMT provides a semi-structured data format for recording requests, requirements and features. • RMT is designed to be a task based tool that utilises different views in order to enable: • Co-operation between users • Work support for new users • Customisable process and tailored tasks/views • RMT supports data traceability.

  10. Example screenshot 1: General tool GUI

  11. Example screenshot 2: Request data content

  12. Questions,comments? • Contact information: • Pasi Kuvaja, University of Oulu • pasi.kuvaja@oulu.fi • Markus Kelanti, University of Oulu • markus.kelanti@oulu.fi

More Related