Organization domain modeling (ODM): formalizing the core domain modeling life cycle
SSR '95 Proceedings of the 1995 Symposium on Software reusability
Software reuse: architecture, process and organization for business success
Software reuse: architecture, process and organization for business success
Requirements engineering: a roadmap
Proceedings of the Conference on The Future of Software Engineering
Formal specification: a roadmap
Proceedings of the Conference on The Future of Software Engineering
FORM: A feature-oriented reuse method with domain-specific reference architectures
Annals of Software Engineering
Integrating Feature Modeling with the RSEB
ICSR '98 Proceedings of the 5th International Conference on Software Reuse
Building Solutions with Microsoft Commerce Server 2002
Building Solutions with Microsoft Commerce Server 2002
Software Reuse Research: Status and Future
IEEE Transactions on Software Engineering
An Approach to Constructing Feature Models Based on Requirements Clustering
RE '05 Proceedings of the 13th IEEE International Conference on Requirements Engineering
Model Checking RAISE Applicative Specifications
SEFM '07 Proceedings of the Fifth IEEE International Conference on Software Engineering and Formal Methods
A Feature Model of E-Government Systems Integrated with Formal Specifications
ITNG '08 Proceedings of the Fifth International Conference on Information Technology: New Generations
From Feature Models to Business Processes
SCC '08 Proceedings of the 2008 IEEE International Conference on Services Computing - Volume 2
A Use Case Based Approach to Feature Models' Construction
RE '09 Proceedings of the 2009 17th IEEE International Requirements Engineering Conference, RE
| Hi-index | 0.00 |
The use of formal methods should help to achieve a high degree of confidence that a system will conform to its specification, enhancing in consequence software quality and reliability. However, a general acceptance of formal methods among software engineers is still some way off because formal methods are usually only accessible to specialists and they do not have developed in depth strategies for the first stages of development. This is also valid to Domain Analysis, because its first stage is to capture the knowledge of a particular domain, making necessary to have a model comprehensible by software engineers and domain experts. In order to address this problem and take advantage of formal methods, we suggest integrating the phase reusable Domain Analysis into the RAISE Method, combining Domain Analysis notions with a formal language in the early steps of software development process. In this paper, we present a set of heuristics to fruitfully use knowledge represented in a Domain Analysis model to derive a formal specification in the RAISE Specification Language.