Building an Ontological Model for Software Requirements Engineering

Building an Ontological Model for Software Requirements Engineering

Joselice Ferreira Lima, Bruno Paula Garcia, Gustavo Miranda Caran
ISBN13: 9781466636644|ISBN10: 1466636645|EISBN13: 9781466636651
DOI: 10.4018/978-1-4666-3664-4.ch003
Cite Chapter Cite Chapter

MLA

Lima, Joselice Ferreira, et al. "Building an Ontological Model for Software Requirements Engineering." Sociotechnical Enterprise Information Systems Design and Integration, edited by Maria Manuela Cruz-Cunha, et al., IGI Global, 2013, pp. 37-55. https://doi.org/10.4018/978-1-4666-3664-4.ch003

APA

Lima, J. F., Garcia, B. P., & Caran, G. M. (2013). Building an Ontological Model for Software Requirements Engineering. In M. Cruz-Cunha, J. Varajão, & A. Trigo (Eds.), Sociotechnical Enterprise Information Systems Design and Integration (pp. 37-55). IGI Global. https://doi.org/10.4018/978-1-4666-3664-4.ch003

Chicago

Lima, Joselice Ferreira, Bruno Paula Garcia, and Gustavo Miranda Caran. "Building an Ontological Model for Software Requirements Engineering." In Sociotechnical Enterprise Information Systems Design and Integration, edited by Maria Manuela Cruz-Cunha, João Varajão, and Antonio Trigo, 37-55. Hershey, PA: IGI Global, 2013. https://doi.org/10.4018/978-1-4666-3664-4.ch003

Export Reference

Mendeley
Favorite

Abstract

This chapter is a work about the development of a model for the engineering requirement based on ontology. The development patterns are not used efficiently, especially for non-observance of the principles of requirements engineering. The overall objective of the chapter is to propose the use of an ontology based on the artifacts of software requirements engineering and can be used on any project developed in any organization. The method uses experimental procedures, which are held in experiments with real situations in a project in progress at a reputable company in the development of hardware, but that currently covers its business in the software services industry. As a result, there is an improved understanding of software requirements, as well as its trace within the scope of the project, i.e., one can easily traverse the model and identify all the artifacts impacted by the change.

Request Access

You do not own this content. Please login to recommend this title to your institution's librarian or purchase it from the IGI Global bookstore.