Support for requirement traceability the tropos case
This presentation is the property of its rightful owner.
Sponsored Links
1 / 35

Support for Requirement Traceability: The Tropos Case PowerPoint PPT Presentation


  • 82 Views
  • Uploaded on
  • Presentation posted in: General

Support for Requirement Traceability: The Tropos Case. Rosa Pinto, Carla Silva, Jaelson Castro. {rccp, ctlls, [email protected] Outline. Motivation Requirements traceability Meta-model Tropos framework The Requirements Traceability Process Case Study Conclusions. Motivation.

Download Presentation

Support for Requirement Traceability: The Tropos Case

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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Support for requirement traceability the tropos case

Support for Requirement Traceability: The Tropos Case

Rosa Pinto, Carla Silva, Jaelson Castro

{rccp, ctlls, [email protected]

Universidade Federal de Pernambuco - Centro de Informatica


Outline

Outline

  • Motivation

  • Requirements traceability Meta-model

  • Tropos framework

  • The Requirements Traceability Process

  • Case Study

  • Conclusions


Motivation

Motivation

  • In complex systems there are quite complex web of relationships

  • Methodologies supporting requirement traceability can develop higher quality software with fewer costs

  • Agent Oriented Development Software


Requirements traceability

Requirements Traceability

  • Requirements traceability refers to the ability to describe and follow the life of a requirement, in both a forwards and backwards direction (i.e., from its origins, through its development and specification, to its subsequent deployment and use, and through all periods of on-going refinement and iteration in any of these phases) [Pinheiro 2003]


Our proposal

Tracing

Agents

Tropos

Our Proposal


Requirements traceability reference model

Requirements Traceability Reference Model

  • [Toranzo 2002 e 2005]

    • Requirement Management sub-model

    • Design sub-model

    • Rational model


Requirement management sub model

Requirement Management sub-model


Design sub model

Design sub-model


Rational model

Rational Model


Tropos framework

Requirements-driven Software development

Detailed

design

Detailed

design

Architectural

design

Architectural

design

Early

requirements

Early

requirements

Late

requirements

Late

requirements

DEPENDER

DEPENDUM

DEPENDEE

Tropos Framework

  • Concepts and Phases


Support for requirement traceability the tropos case

Estudo de Caso: Media Shop

Universidade Federal de Pernambuco - Centro de Informatica


Requirements traceability process

Requirements Traceability Process

  • Stages of process

    • 1. Information Gathering (IG):

      • identify the information to be traced

  • 2. Information Structuring (ST) used to:

    • achieve the proper structuring of the information identified before

    • defined the set of valid values for association instances

  • 3. Definition of the Traceability Matrixes (TM):

    • guide the construction of the appropriate traceability matrixes


  • Requirements traceability process1

    Requirements Traceability Process

    • Stage 1. Information Gathering (IG)

      • IG1. Requirement Management sub-model classes from SD diagram of the actor representing the system

        • Rule 1. Actor which has some dependency relationship with

          • System actor  STAKEHOLDER class


    Support for requirement traceability the tropos case

    SD Diagram for Medi@ System

    STAKEHOLDERS

    Universidade Federal de Pernambuco - Centro de Informatica


    Requirements traceability process2

    Requirements Traceability Process

    • Stage 1. Information Gathering (IG)

      • IG1. Requirement Management sub-model classes from SD diagram of the actor representing the system

        • Rule 2. System actor is dependee of softgoal, resource or task

          • the dependum  REQUIREMENT class


    Support for requirement traceability the tropos case

    DEPENDER

    DEPENDUM

    DEPENDEE

    SD Diagram for Medi@ System

    STAKEHOLDERS

    REQUIREMENTS

    Universidade Federal de Pernambuco - Centro de Informatica


    Requirements traceability process3

    Requirements Traceability Process

    • Stage 1. Information Gathering (IG)

      • IG1. Requirement Management sub-model classes from SD diagram of the actor representing the system

        • Rule 3. System actor is dependee of a goal dependency of the actor representing the organization

          • The depedum  ORGANIZATIONAL OBJECTIVES class


    Support for requirement traceability the tropos case

    DEPENDER

    DEPENDUM

    DEPENDEE

    SD Diagrama for Medi@ System

    STAKEHOLDERS

    REQUIREMENTS

    ORGANIZATIONAL OBJECTIVE

    Universidade Federal de Pernambuco - Centro de Informatica


    Requirements traceability process4

    Requirements Traceability Process

    • Stage 1. Information Gathering (IG)

      • IG1. Requirement Management sub-model classes from SD diagram of the actor representing the system

        • Rule 4. System actor is depender of a goal dependency of the actor does not represent the organization

          • The goal  SYSTEM OBJECTIVES class


    Support for requirement traceability the tropos case

    DEPENDER

    DEPENDUM

    DEPENDEE

    SD Diagrama for Medi@ System

    Organizational Map

    STAKEHOLDERS

    REQUIREMENTS

    ORGANIZATIONAL OBJECTIVE

    SYSTEM OBJECTIVE


    Requirements traceability process5

    Requirements Traceability Process

    • Stage 1. Information Gathering (IG)

      • IG1. Requirement Management sub-model classes from SD diagram of the actor representing the system

        • Rule 5. System actor is depender of goal, softgoal, resource or task

          • The dependum  EXTERNAL class


    Sd diagrama for medi@ system

    DEPENDER

    DEPENDUM

    DEPENDEE

    SD Diagrama for Medi@ System

    Organizational Map

    STAKEHOLDERS

    REQUIREMENTS

    ORGANIZATIONAL OBJECTIVE

    SYSTEM OBJECTIVE

    EXTERNAL


    Requirements traceability process6

    Requirements Traceability Process

    • Stage 1. Information Gathering (IG)

      • IG2. Requirement Management sub-model classes from SR diagram of the actor representing the system

        • Rule 1. Goal  SYSTEM OBJECTIVES class

        • Rule 2. Task  REQUIREMENT class

        • Rule 3. Softgoal  REQUIREMENT class

        • Rule 4. Resource  REQUIREMENT class


    Support for requirement traceability the tropos case

    DEPENDER

    DEPENDUM

    DEPENDEE

    SR Diagrama for Medi@ System

    SYSTEM OBJECTIVE

    REQUIREMENTS


    Requirements traceability process7

    Requirements Traceability Process

    • Stage 1. Information Gathering (IG)

      • IG3. Rational model classes from the process for selecting the proper architectural style

        • Rule 1. SUBJECT class  issue on which a decision must be taken

        • Rule 2. POSITION class  alternative solutions for the SUBJECT

        • Rule 3. ARGUMENT class  some criteria used for choosing the proper solution


    Requirements traceability process8

    Requirements Traceability Process

    • Stage 1. Information Gathering (IG)

      • IG3. Rational model classes from the process for selecting the proper architectural style

        • Rule 4. ASSUMPTION class  facts that must be taken into account for choosing

        • Rule 5. CONSTRAINT class  limitations/restrictions that must be taken into account for deciding the proper solution

        • Rule 6. DOCUMENT class  some information used as reference for choosing the proper solution


    Requirements traceability process9

    Requirements Traceability Process

    • Stage 1. Information Gathering (IG)

      • IG4. Design Sub-model classes from the architectural design model

        • Rule 1. Each architectural component  SUBSYSTEM class


    Requirements traceability process10

    Requirements Traceability Process

    • Stage 2. Information Structuring (ST)

      • ST1. to remove classes unnecessary, and to delete instances with the same meaning

      • ST2. for each pair of associated classes in the reference model, the association should be instantiated

      • ST3. for each instance created in the ST2, define the set of values assigned to it.


    Requirements traceability process11

    Requirements Traceability Process

    • Stage 3. Definition of the Traceability Matrixes (TM)

      • Guideline TM1

        • For each pair of instantiated classes which are associated in a reference model, we can create a traceability matrix.

      • Guideline TM2

        • For each created matrix, we have to analyze the system artifacts which are related to the matrix and fill the association which has been instantiated in a previous stage of the process.


    Requirements traceability process12

    Requirements Traceability Process

    • Stage 3. Definition of the Traceability Matrixes (TM)

      • Applying TM1 and TM2:

        • create a traceability matrix to the instances of the <<resource>> association between REQUIREMENTS and ORGANIZATIONAL INFORMATION elements

          • <H> (High), <M> (Medium) or <L> (Low).


    Requirement management sub model1

    Requirement Management sub-model

    C O N S T R A I N T

    EXTERNAL

    0..n

    <<resource>>

    <<resource>>

    0..n

    <<satisfy>>

    1..n

    0..n

    1

    1..n

    0..n

    0..n

    ORGANIZATIONAL INFORMATION

    I N F O R M A T I O N

    0..n

    0..n

    0..n

    <<satisfy>>

    0..n

    0..n

    <<resource>>

    <<resource>>

    1

    0..n

    1..n

    SYSTEM OBJECTIVES

    <<resource>>

    0..n

    CHANGE PURPOSE

    <<resource>>

    0..n

    0..n

    0..n

    <<resource>>

    0..n

    0..n

    1

    0..n

    T A S K

    0..n

    <<resource>>

    1..n

    <<resource>>

    0..n

    0..n

    1

    0..n

    R E Q U I R E M E N T

    0..n

    0..n

    <<responsability>>

    <<responsability>>

    S T A K E H O L D E R

    0..n

    0..n


    Case study

    Case Study


    Case study1

    Case Study

    • Estimating the impact of a change

      • If some organizational information is changed, the impact in the system requirements can be analyzed.


    Conclusions

    Conclusions

    • We outline a process that can be used to extend Tropos to address requirements traceability.

    • We intend to develop a complete and usable requirement traceability process for Tropos aiming to ensure the quality improvement of both the methodology and the software developed with it.

    • Further guidelines for instantiating all the classes of the three reference models (Requirement Management and Design sub-models and Rational model) for each phase of Tropos may be required.


    Questions suggestions

    Questions/suggestions ?


  • Login