Skip to main content

Ontology-Driven Requirements Engineering in the Responsive and Formal Design Process

  • Conference paper
  • First Online:
Systems Engineering in Context

Abstract

Requirements that are understood and shared by all stakeholders as well as system engineers are highly critical in the development of a successful system. Natural languages (NL) are essentially preferred to represent requirements to advance this shared understanding. However, natural languages are inherently imprecise and ambiguous leading to inconsistent, incomplete, and incorrect requirements. Therefore, there is a need to represent requirements formally. In this paper, the use of ontologies for knowledge representation from requirements is presented for the responsive and formal design (RFD) process. The main goals are to (1) facilitate requirements engineering, (2) serve as an intermediate representation for automatic transition to logic-based modeling, and (3) formalize the process of transformation from requirements to logic-based modeling. Therefore, requirements engineering in the RFD process will be augmented using ontologies in the domain modeling of the system to be implemented. Ontologies are utilized to capture domain requirements, and formal mechanisms are used to check for inconsistency and incompleteness at each abstraction layer in the RFD process.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Subscribe and save

Springer+ Basic
$34.99 /Month
  • Get 10 units per month
  • Download Article/Chapter or eBook
  • 1 Unit = 1 Article or 1 Chapter
  • Cancel anytime
Subscribe now

Buy Now

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 169.00
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Hardcover Book
USD 219.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Similar content being viewed by others

References

  1. Holt, J., Perry, S. A., & Brownsword, M. (2012). Model-based requirements engineering. London: IET.

    Google Scholar 

  2. Halifax, N. S. (2016). Leveraging natural language processing in requirements analysis: How to eliminate over half of all design errors before they occur. Halifax, NS: QRA Corp.

    Google Scholar 

  3. Berry, D. M., & Kamsties, E. (2004). Ambiguity in requirements specification. In Perspectives on software requirements (pp. 7–44). Berlin, Germany: Springer.

    Chapter  Google Scholar 

  4. Spivak, D. I., & Kent, R. E. (2012). Ologs: A categorical framework for knowledge representation. PLoS One, 7(1), e24274.

    Article  Google Scholar 

  5. Chenou, J., Edmonson, W. W., Esterline, A. C., & Neogi, N. A. (2014). Formal framework for ensuring consistent system and component theories in the design of small satellite systems. CSDM (Posters), CiteSeer.

    Google Scholar 

  6. Edmonson, W., Chenou, J., Neogi, N., & Herencia-Zapana, H. (2014). Small satellite systems design methodology: A formal and agile design process. In 8th Annual IEEE Systems Conference (SysCon).

    Google Scholar 

  7. Gebreyohannes, S., Edmonson, W., Chenou, J., Neogi, N., & Esterline, A. (2015). Formal requirement management for the responsive and formal design process. In 2015 IEEE International Symposium on Systems Engineering (ISSE).

    Google Scholar 

  8. Gebreyohannes, S., Edmonson, W., & Esterline, A. (2017). Formal behavioral requirements management. IEEE Systems Journal, 12(3), 3006–3017.

    Article  Google Scholar 

  9. Gebreyohannes, S., Edmonson, W., Esterline, A., Homaifar, A., & Kibret, N. (2017). Fuzzy classification context for the responsive and formal design process. In 2017 Annual IEEE International Systems Conference (SysCon).

    Google Scholar 

  10. Breitman, K. K., & Hinchey, M. G. (2008). The use of formal ontology to specify context in ubiquitous computing. In International Symposium on Leveraging Applications of Formal Methods, Verification and Validation. Springer.

    Google Scholar 

  11. Dermeval, D., Vilela, J., Bittencourt, I. I., Castro, J., Isotani, S., & Brito, P. (2014). A systematic review on the use of ontologies in requirements engineering. In 2014 Brazilian Symposium on Software Engineering (SBES).

    Google Scholar 

  12. Ruiz, F., & Hilera, J. R. (2006). Using ontologies in software engineering and technology. In Ontologies for software engineering and software technology (pp. 49–102). Berlin, Germany: Springer.

    Chapter  Google Scholar 

  13. Sadoun, D., Dubois, C., Ghamri-Doudane, Y., & Grau, B. (2014). Formal rule representation and verification from natural language requirements using an ontology. In International Workshop on Rules and Rule Markup Languages for the Semantic Web. Springer.

    Google Scholar 

  14. Sadoun, D., Dubois, C., Ghamri-Doudane, Y., & Grau, B. (2013). From natural language requirements to formal specification using an ontology. In 2013 IEEE 25th International Conference on Tools with Artificial Intelligence (ICTAI).

    Google Scholar 

  15. Gruber, T. R. (1993). A translation approach to portable ontology specifications. Knowledge Acquisition, 5(2), 199–220.

    Article  Google Scholar 

  16. Bermejo, J. (2007). A simplified guide to create an ontology.

    Google Scholar 

  17. Jones, D., Bench-Capon, T., & Visser, P. (1998). Methodologies for ontology development.

    Google Scholar 

  18. Spivak, D. I. (2014). Category theory for the sciences. Cambridge, MA: MIT Press.

    MATH  Google Scholar 

  19. Boehm, B. W. (1981). Software engineering economics. Englewood Cliffs, NJ: Prentice-Hall.

    MATH  Google Scholar 

  20. Stecklein, J. M., Dabney, J., Dick, B., Haskins, B., Lovell, R., & Moroney, G. (2004). Error cost escalation through the project life cycle. In INCOSE International Symposium (Vol. 14, pp. 1723–1737). https://doi.org/10.1002/j.2334-5837.2004.tb00608.x.

  21. Baier, C., Katoen, J.-P., & Larsen, K. G. (2008). Principles of model checking. Cambridge, MA: MIT Press.

    MATH  Google Scholar 

  22. Clarke, E. M., Grumberg, O., & Peled, D. (1999). Model checking. Cambridge, MA: MIT Press.

    Google Scholar 

  23. Clarke, E. M., & Wing, J. M. (1996). Formal methods: State of the art and future directions. ACM Computing Surveys (CSUR), 28(4), 626–643.

    Article  Google Scholar 

  24. Easterbrook, S., Lutz, R., Covington, R., Kelly, J., Ampo, Y., & Hamilton, D. (1996). Experiences using formal methods for requirements modeling.

    Google Scholar 

  25. Hall, A. (1990). Seven myths of formal methods. IEEE Software, 7(5), 11–19.

    Article  Google Scholar 

  26. Rouff, C. A., Truszkowski, W. F., Rash, J., & Hinchey, M. G. (2005). A survey of formal methods for intelligent swarms. Greenbelt, MD: NASA Goddard Space Flight Center.

    Google Scholar 

  27. Awele, E. (2018). An MBSE conceptual design phase model of a VLC system for inter-satellite communication. In 2018 Annual IEEE International Stems Conference (SysCon).

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Nadew Kibret .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2019 Springer Nature Switzerland AG

About this paper

Check for updates. Verify currency and authenticity via CrossMark

Cite this paper

Kibret, N., Edmonson, W., Gebreyohannes, S. (2019). Ontology-Driven Requirements Engineering in the Responsive and Formal Design Process. In: Adams, S., Beling, P., Lambert, J., Scherer, W., Fleming, C. (eds) Systems Engineering in Context. Springer, Cham. https://doi.org/10.1007/978-3-030-00114-8_33

Download citation

Publish with us

Policies and ethics