Developing Software with Domain-Driven Model Reuse

Developing Software with Domain-Driven Model Reuse

Audris Kalnins, Tomasz Straszak, Michał Śmiałek, Elina Kalnina, Edgars Celms, Wiktor Nowakowski
ISBN13: 9781466663596|ISBN10: 1466663596|EISBN13: 9781466663602
DOI: 10.4018/978-1-4666-6359-6.ch012
Cite Chapter Cite Chapter

MLA

Kalnins, Audris, et al. "Developing Software with Domain-Driven Model Reuse." Handbook of Research on Innovations in Systems and Software Engineering, edited by Vicente García Díaz, et al., IGI Global, 2015, pp. 283-312. https://doi.org/10.4018/978-1-4666-6359-6.ch012

APA

Kalnins, A., Straszak, T., Śmiałek, M., Kalnina, E., Celms, E., & Nowakowski, W. (2015). Developing Software with Domain-Driven Model Reuse. In V. Díaz, J. Lovelle, & B. García-Bustelo (Eds.), Handbook of Research on Innovations in Systems and Software Engineering (pp. 283-312). IGI Global. https://doi.org/10.4018/978-1-4666-6359-6.ch012

Chicago

Kalnins, Audris, et al. "Developing Software with Domain-Driven Model Reuse." In Handbook of Research on Innovations in Systems and Software Engineering, edited by Vicente García Díaz, Juan Manuel Cueva Lovelle, and B. Cristina Pelayo García-Bustelo, 283-312. Hershey, PA: IGI Global, 2015. https://doi.org/10.4018/978-1-4666-6359-6.ch012

Export Reference

Mendeley
Favorite

Abstract

This chapter presents an approach to software development where model-driven development and software reuse facilities are combined in a natural way. It shows how model transformations building a Platform Independent Model (PIM) can be applied directly to the requirements specified in RSL by domain experts. Further development of the software case (PSM, code) is also supported by transformations, which in addition ensure a rich traceability within the software case. Alternatively, the PSM model and code can also be generated directly from requirements in RSL, thus providing fast development of the final code of at least a system prototype in many situations. The reuse support relies on a similarity-based comparison of requirements for software cases. If a similar part is found in an existing software case, a traceability link-based slice of the solution can be merged into the new case. The implementation of the approach is briefly sketched.

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.