Domain-Driven Reuse of Software Design Models

Domain-Driven Reuse of Software Design Models

Audris Kalnins, Michal Smialek, Elina Kalnina, Edgars Celms, Wiktor Nowakowski, Tomasz Straszak
ISBN13: 9781616928742|ISBN10: 1616928743|EISBN13: 9781616928766
DOI: 10.4018/978-1-61692-874-2.ch009
Cite Chapter Cite Chapter

MLA

Kalnins, Audris, et al. "Domain-Driven Reuse of Software Design Models." Model-Driven Domain Analysis and Software Development: Architectures and Functions, edited by Janis Osis and Erika Asnina, IGI Global, 2011, pp. 177-200. https://doi.org/10.4018/978-1-61692-874-2.ch009

APA

Kalnins, A., Smialek, M., Kalnina, E., Celms, E., Nowakowski, W., & Straszak, T. (2011). Domain-Driven Reuse of Software Design Models. In J. Osis & E. Asnina (Eds.), Model-Driven Domain Analysis and Software Development: Architectures and Functions (pp. 177-200). IGI Global. https://doi.org/10.4018/978-1-61692-874-2.ch009

Chicago

Kalnins, Audris, et al. "Domain-Driven Reuse of Software Design Models." In Model-Driven Domain Analysis and Software Development: Architectures and Functions, edited by Janis Osis and Erika Asnina, 177-200. Hershey, PA: IGI Global, 2011. https://doi.org/10.4018/978-1-61692-874-2.ch009

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. The basis for all of this is a semiformal requirements language RSL. The requirements in RSL consist of use cases refined by scenarios in a simple controlled natural language and the domain vocabulary containing the domain concepts. The chapter 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. 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.