• Save
Me2011 Presentation by Loniewski
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share
Uploaded on

Incorporating Model-Driven Techniques into Requirements Engineering for the Service-Oriented development Process

Incorporating Model-Driven Techniques into Requirements Engineering for the Service-Oriented development Process

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
669
On Slideshare
669
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • 1) 2) 3) As requirements in the SOA-based systems development are frequently described in the industry as a natural language specifications, which is the case of the case study European Project, it has also served as the motivation for this work
  • A systematic review involves several stages and activities. In this work, we followed the approach proposed by Kitchenham for a systematic literature review. In the Planning the review step : the need for the review is identified, the research questions are specified, and the review protocol is defined. Conducting the review : the primary studies are selected, the quality assessment used to include studies is defined, the data extraction and monitoring is performed, and the obtained data is synthesized. Reporting the review : the dissemination mechanisms are specified, and the review report is presented.
  • A systematic review involves several stages and activities. In this work, we followed the approach proposed by Kitchenham for a systematic literature review. In the Planning the review step : the need for the review is identified, the research questions are specified, and the review protocol is defined. Conducting the review : the primary studies are selected, the quality assessment used to include studies is defined, the data extraction and monitoring is performed, and the obtained data is synthesized. Reporting the review : the dissemination mechanisms are specified, and the review report is presented.
  • A systematic review involves several stages and activities. In this work, we followed the approach proposed by Kitchenham for a systematic literature review. In the Planning the review step : the need for the review is identified, the research questions are specified, and the review protocol is defined. Conducting the review : the primary studies are selected, the quality assessment used to include studies is defined, the data extraction and monitoring is performed, and the obtained data is synthesized. Reporting the review : the dissemination mechanisms are specified, and the review report is presented.
  • A systematic review involves several stages and activities. In this work, we followed the approach proposed by Kitchenham for a systematic literature review. In the Planning the review step : the need for the review is identified, the research questions are specified, and the review protocol is defined. Conducting the review : the primary studies are selected, the quality assessment used to include studies is defined, the data extraction and monitoring is performed, and the obtained data is synthesized. Reporting the review : the dissemination mechanisms are specified, and the review report is presented.
  • A systematic review involves several stages and activities. In this work, we followed the approach proposed by Kitchenham for a systematic literature review. In the Planning the review step : the need for the review is identified, the research questions are specified, and the review protocol is defined. Conducting the review : the primary studies are selected, the quality assessment used to include studies is defined, the data extraction and monitoring is performed, and the obtained data is synthesized. Reporting the review : the dissemination mechanisms are specified, and the review report is presented.
  • A systematic review involves several stages and activities. In this work, we followed the approach proposed by Kitchenham for a systematic literature review. In the Planning the review step : the need for the review is identified, the research questions are specified, and the review protocol is defined. Conducting the review : the primary studies are selected, the quality assessment used to include studies is defined, the data extraction and monitoring is performed, and the obtained data is synthesized. Reporting the review : the dissemination mechanisms are specified, and the review report is presented.
  • A systematic review involves several stages and activities. In this work, we followed the approach proposed by Kitchenham for a systematic literature review. In the Planning the review step : the need for the review is identified, the research questions are specified, and the review protocol is defined. Conducting the review : the primary studies are selected, the quality assessment used to include studies is defined, the data extraction and monitoring is performed, and the obtained data is synthesized. Reporting the review : the dissemination mechanisms are specified, and the review report is presented.
  • A systematic review involves several stages and activities. In this work, we followed the approach proposed by Kitchenham for a systematic literature review. In the Planning the review step : the need for the review is identified, the research questions are specified, and the review protocol is defined. Conducting the review : the primary studies are selected, the quality assessment used to include studies is defined, the data extraction and monitoring is performed, and the obtained data is synthesized. Reporting the review : the dissemination mechanisms are specified, and the review report is presented.

Transcript

  • 1. 13 th International Conference on Model Driven Engineering Languages and Systems - MODELS 2010 3rd-8th October, 2010 - Oslo (Norway) Incorporating Model-Driven Techniques in to Requirements Engineering for the Service-Oriented Development Process Grzegorz Loniewski , Ausias Armesto and Emilio Insfran ISSI Research Group . Departamento de Sistemas Informáticos y Computación (DSIC) Universi t a t Politécnica de Valencia , Spain {gloniewski, einsfran}@dsic.upv.es, aarmesto@indra.es
  • 2. Outline
    • Motivation
    • Introduction
    • Methodology
    • Case Study
    • Conclusions
  • 3. Outline
    • Motivation
    • Introduction
    • Methodology
    • Case Study
    • Conclusions
  • 4. Motivation
    • Model- D riven D evelopment (MDD) emphasizes the use of
      • models at a higher abstraction level
      • automation via model execution , model transformation or code generation
    • RE is hardly included in the mainstream of MDD approaches
      • managed, documented, and easily understandable requirements have a great impact on final product quality
      • methodologies, tools, … in the MDD processes mainly starts at the PIM level and CIM2PIM transformations are rarely used
    • Loniewski, G., Insfran, E., Abrahao, S.: A S ystematic R eview of the U se of R equirements E ngineering T echniques in M odel- D riven D evelopment. In: MODELS 2010 , LNCS, vol. 6395, pp. 213–227
    • SOAs are recently applied to a great extent in the industry, where requirements are frequently in the form of text (NL, SNL or templates) which is difficult to automatically transform (case study)
    Motivation Introduction Methodology Case Study Conclusions
  • 5. Outline
    • Motivation
    • Introduction
    • Methodology
    • Case Study
    • Conclusions
  • 6. Objectives : Propose a methodology for model-driven requirements engineering approach to be applied in the architecture-centric service-oriented systems development Motivation Introduction Methodology Case Study Conclusions Introduction I MODELS 2010 - A Systematic Review of the Use of Requirements Engineering Techniques in Model-Driven Development MODELS 2010 - A Systematic Review of the Use of Requirements Engineering Techniques in Model-Driven Development
    • Partial objectives to reach the goal:
      • Systematic literature review : RE in MDD ( methodologies, methods, techniques )
      • Methodologies studied:
        • Rational Unified Process (RUP): the most successful known methodology, extensible, with emphasis on requirements artifacts
        • OpenUP and OpenUP/MDD: architecture centric OpenUP/MDD: support only for PIM2PSM transformations
        • Agile Unified Process (AUP): model-based approach no clear use of a models, development process mailny manual
      • Technological solutions: Service-oriented approaches
        • SOMA, SOUP, SoaML: service modeling approaches, with emphasis on manual service identification and specification
        • Minevra, SOA-MDK: model-based paradigms to service-oriented development, unclear nature of the MDA principles application
  • 7. Introduction II Motivation Introduction Methodology Case Study Conclusions
    • Approach architecture: bases on the Model Driven Architecture (MDA) abstraction levels
    • Approach foundation: Rational Unified Process (RUP) as a base methodology
    • Methodology implementation: Rational Method Composer (RMC)
      • RUP implemented as a plugin library
    • Process Engineering: Unified Method Architecture (UMA) extension mechanisms for defining:
      • method content
      • processes
    We use Method Engineering to define the approximation of the Model-Driven Requirements Engineering approach by combining:
  • 8. Outline
    • Motivation
    • Introduction
    • Methodology
    • Case Study
    • Conclusions
  • 9. Methodology In terms of MDA framework abstraction levels Motivation Introduction Methodology Case Study Conclusions Classic MDA framework cycle RUP extension for MDRE framework cycle
  • 10. Methodology RUP Extension
    • RUP
      • Requirements discipline replaced with Model-Driven Requirements
      • Environment discipline as a means to adapt the methodology to particular MDD process
    extension Motivation Introduction Methodology Case Study Conclusions
  • 11. Methodology Model-Driven Requirements discipline I Model-Driven Requirements workflow Motivation Introduction Methodology Case Study Conclusions
  • 12. Methodology Model-Driven Requirements discipline II Motivation Introduction Methodology Case Study Conclusions Model Analyst Transformations Specifier Identify the System Architecture Define Meta-Models Define Transformations Plan Transformations Develop RM Run Transformations Software Architecture Document (SAD) Transformation Rules Catalog (TRC) Transformation Iteration Plan (TIP) Requirements Model (RM) Generated Analysis Model (GAM) Vision Software Architecture Document (SAD) Transformation Rules Catalog (TRC) Requirements Artifacts , SAD RM, TRC, TIP
  • 13. Outline
    • Motivation
    • Introduction
    • Methodology
    • Case Study
    • Conclusions
  • 14. Case Study Context Motivation Introduction Methodology Case Study Conclusions
    • European Project MPOWER (founded by the European Union under 6th Framework Programme)
    • Main objectives:
      • Implementing a middle-ware platform of services for empowering cognitive disabled and elderly
      • Quick and easy development of health-care services
    • Project of 3 years duration has been successfully finished and currently is being used in a Smart-Residence in Poland
    • Realization assumptions:
          • The use of open standards and implementation tools
          • The use of Service-Oriented Architecture (SOA)
          • Implementation of home-care proof-of-concept application
    • MPOWER approach is based on MDSD principles, however applied only to PIM and PSM
  • 15. Scenario 1 (Requirement 1) : Lately Annie has experienced problems with managing her everyday living due to early dementia, and she finds this very frustrating and the rest of her family does not feel comfortable with the situation. She forgets to take her medication, appointments, get anxious when is alone. For Annie and her family it is vital to create an environment where Annie is able to cope with her daily activities and where the family does not need to be afraid of her. Transformation Rules Catalog PIM (BPMN) PIM (Service Model) CIM Case Study Example of use: SOA for Health-care Motivation Introduction Methodology Case Study Conclusions
  • 16. Case Study Summary Motivation Introduction Methodology Case Study Conclusions CIM PIM PSM
  • 17. Outline
    • Motivation
    • Introduction
    • Methodology
    • Case Study
    • Conclusions
  • 18. Conclusions
      • Defined : A methodology for software development that incorporates a RE model-driven approach
      • Adapted : This methodology was adapted to fit the particular needs of SOA-based systems development
      • Validated : A comparative case study based on a real health-care project
      • Problems :
        • The limitation related to the use of business modeling discipline artifacts in the requirement s elicitation phase
        • Creating a well-defined and consistent Requirements Model (CIM-level) is the main challenge in this approach
    Motivation Introduction Methodology Case Study Conclusions
  • 19. Conclusions Further and ongoing work Motivation Introduction Methodology Case Study Conclusions
      • We are currently working on an agile version of this approach based on the OpenUP methodology;
      • We are currently working on redefinition of presented here approach in terms of artifact-oriented metamodel in collaboration with Technical University of Munich;
      • We plan to provide a tool support with which to easily create artifacts demanded for the model-driven development process (document templates, wizards);
      • We plan to investigate on the usability of this approach in real projects of SOA-based systems development, approach validation;
  • 20. Incorporating Model-Driven Techniques in to Requirements Engineering for the Service-Oriented Development Process Grzegorz Loniewski , Ausias Armesto and Emilio Insfran Thanks for your attention!
  • 21. Background II
    • Model-based methodologies
      • Rational Unified Process (RUP) – the most successful software engineering methodology; provides use-case driven, architecture oriented and iterative process of quality software development
      • Agile Unified Process (AUP) – is a simplified version of the RUP which applies agile techniques to Agile Model-Driven Development (AMDD), change management, and Test-Driven Development (TDD);
      • OpenUp – is another very simplified RUP version intended for small teams and which defines the minimal set of roles, tasks and artifacts;
        • OpenUP/MDD – OpenUP plug-in - is consistent with the MDA, but focuses only on the transformations from the PIM to PSM level
    Motivation Objective Background OpenUP/MDRE SOA 4 Healthcare Conclusions
  • 22. Background III
    • Methodologies for SOA-based systems
      • Service Oriented Modeling and Architecture (SOMA) – to analyze business domains decomposing them into: business processes, sub-processes, use cases;
      • Service Oriented Unified Process (SOUP) – lightweight instance of RUP with SOA specific deliverables for business services and for business processes models and rules; it is rather model-based than model-driven;
    • Requirements Engineering in the health-care
      • Most approaches focus only on the requirements elicitation techniques
      • Natural language and structured natural language are the main means to describe user scenarios (healthcare primary requirements artifacts)
      • Very important element of the healthcare RE is specifying consistent requirements which: come from different distributed sources, describe many complex stakeholders needs and domain concepts, such as: clinical knowledge, data to be stored, care conditions, care relationships
    Motivation Objective Background OpenUP/MDRE SOA 4 Healthcare Conclusions
  • 23. SOA for Healthcare Proposed Development process Motivation Objective Background OpenUP/MDRE SOA 4 Healthcare Conclusions
  • 24. Discussion (1/2) Motivation Research Method Results Discussion Validation Conclusions
      • The results indicate that there is an important interest for RE techniques in MDD, however,
          • models and model transformations are not as frequently used as expected in the requirements phase
          • not only models are used to specify requirements
          • requirements specs are hardly ever included in the mainstream of the automated model transformations
    PIM  PSM CIM/NL  PIM PSM  CM
  • 25. Discussion (2/2)
      • In addition, we have identified several research gaps:
          • Lack of a efforts to integrate RE solutions into MDD process
            • RE not as target or just documentation but as driver
          • Lack of more validations for RE proposals
            • well-defined case studies, experiments
            • well-documented solutions
          • Joint efforts with industry
          • Traceability (forward/backward) not as an option
    Motivation Research Method Results Discussion Validation Conclusions
  • 26. Methodology Model-Driven Requirements discipline I
      • Defines 2 additional roles :
          • Model Analyst
          • Transformation Specifier
      • Defines 17 new or redefined tasks related to requirements: capturing, modeling, and transformation
      • Defines 7 new work products as a principal artifacts of the discipline:
          • Model Dependencies Specification
          • Requirements Model
          • Generated Analysis Model
          • Transformation Rules Catalog
          • Transformation Iteration Plan
          • Model Validation Plan
          • Model Validation Record
    Motivation Introduction Methodology Case Study Conclusions