1 / 24

A Software Process OPL for ISO SC7 Standards

Fabiano B. Ruy Ricardo A. Falbo Monalessa P. Barcellos. A Software Process OPL for ISO SC7 Standards. Ontology & Conceptual Modeling Research Group. Federal University of Espírito Santo (Brazil). Ontologias para Engenharia de Software PPGI/UFES - October, 2014. Agenda. Introduction

Télécharger la présentation

A Software Process OPL for ISO SC7 Standards

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. Fabiano B. Ruy Ricardo A. Falbo Monalessa P. Barcellos A Software Process OPL forISO SC7 Standards Ontology & Conceptual Modeling Research Group Federal University of Espírito Santo (Brazil) Ontologias para Engenharia de Software PPGI/UFES - October, 2014

  2. Agenda • Introduction • Ontology Pattern Languages • An OPL for ISO Software Processes (ISP-OPL) • The Language • ISP-OPL Patterns • Applying ISP-OPL • Requirement Process Ontology • Final Considerations

  3. Motivation • Standards Harmonization • Many standards and models • ISO/IEC 12207, ISO/IEC 29110, ISO 9001, CMMI, MPS.BR etc. • They are developed by different organizations or groups. • They are not created under the same base of terms, concepts and semantics. • When used in combination  Interoperability problems.

  4. Motivation • ISO Study Group • Standards harmonization initiative • Proposal: Ontological Framework • DEO: Definitional Elements Ontology • CDO: Configured Definitional Ontology • SDO: Standards Domain Ontology • Is there a good solution for ontology derivation?

  5. Ontology Pattern Languages • Advantages expected of using OPLs for deriving compatible ontologies. • Modularity and Reuse • Productivity • Consistency • Interoperability (compatibility of the resulting models)

  6. ISP-OPLISO-based Software Process OPL • Characteristics • Based on the Ontological Analysis of ISO/IEC 24744(in the light of UFO) • Reusing SP-OPL and E-OPL patterns • Purpose: to propose a sound solution for the derivation of ontologies in the ISO harmonization initiative.

  7. ISP-OPLISO-based Software Process OPL • Scope • Work Units • Regarding the composition of work units and its application contexts. • Human Resources • Dealing with how people are organized in organizations and teams, involved in projects, allocated to tasks, and perform work units. • Work Products • Representing the nature and composition of work products and how they are handled in work units.

  8. ISP-OPL Patterns

  9. ISP-OPL Patterns

  10. ISP-OPL Patterns

  11. ISP-OPL Process • [language figure]

  12. Work Unit Patterns

  13. Human Resource Patterns

  14. Work Product Patterns

  15. Applying ISP-OPL • Requirements Processes • ISO/IEC 12207 – Software Life Cycle Processes • 6.4.1 - Stakeholder Requirements Definition Process • 6.4.2 - System Requirements Analysis Process • 7.1.2 - Software Requirements Analysis Process • ISO/IEC 15288 – System Life Cycle Processes • 6.4.1 - Stakeholder Requirements Definition Process • 6.4.2 - Requirements Analysis Process • ISO/IEC/IEEE 29148 – Requirements Engineering • 6.2 - Stakeholder Requirements Definition Process • 6.3 - Requirements Analysis Process

  16. Applying ISP-OPL • Scope Definition • ISO/IEC 12207 – Software Life Cycle Processes • 6.4.1 - Stakeholder Requirements Definition Process • ISO/IEC 15288 – System Life Cycle Processes • 6.4.1 - Stakeholder Requirements Definition Process • ISO/IEC/IEEE 29148 – Requirements Engineering • 6.2 - Stakeholder Requirements Definition Process • Performed Processes • Work Units • Human Resources • Work Products

  17. Applying ISP-OPL • Analyzing the Standards • Concepts Identification

  18. Applying ISP-OPL

  19. Applying ISP-OPL

  20. Applying ISP-OPL

  21. Applying ISP-OPL

  22. Applying ISP-OPL

  23. Final Considerations • Once understood, the OPL is easy to apply • The major difficulties are on understanding the standards and identifying the concepts and relations. • Enables a good productivity • The development of the resulting ontology is faster • Leads to more consistent ontologies • UFO ground, OPL built-in knowledge • Reaches interoperable ontologies • Same OPL: compatible concepts

  24. Fabiano B. Ruy (fabianoruy@inf.ufes.br) Ricardo A. Falbo (falbo@inf.ufes.br) Monalessa P. Barcellos (monalessa@inf.ufes.br) A Software Process OPL forISO SC7 Standards Ontology & Conceptual Modeling Research Group Federal University of Espírito Santo (Brazil) Ontologias para Engenharia de Software October, 2014

More Related