Towards a Functional Size Measure for Object-Oriented Systems from Requirements Specifications
QSIC '04 Proceedings of the Quality Software, Fourth International Conference
Evaluating requirements modeling methods based on user perceptions: A family of experiments
Information Sciences: an International Journal
| Hi-index | 0.00 |
Many different attempts have been made out over the last three decades to tackle the problems in software engineering that directly or indirectly lead to the symptoms of software crisis. These attempts have mostly focused on different specific fields, such as improved programming languages, improved modeling techniques, introduction of analysis and design methods, formal specifications, CASE tools, etc. In spite of the various attempts to develop high quality software systems, a difficult task still remains to be able to provide a solution to this classical problem: how to go from the problem space (user requirements) to the solution space (design and implementation) with sound methodological guidance. This PhD thesis is developed in the context of OO-Method (an object-oriented method for conceptual modeling and code generation) providing an approach to undertake this problem by extending the OO-Method Conceptual Model with a Requirements Model. The two cornerstones of this approach are the Requirements Model, which provides mechanisms to identify and specify functional user requirements at different abstraction levels, and the Requirements Analysis Process, which establishes conceptual links between the requirements and the structure and behavior of an OO-Method Conceptual Schema. These provide a smooth transition from a requirements specification to a conceptual schema in a traceable way. An industrial Requirements Specification Environment is being developed as a supporting tool. The integration of this tool with the automatic Conceptual Model Execution Environment provided by the OO-Method Case Tool (OlivaNova Model Execution Software®) will bring an achievable dream closer to reality, that is, to be able to go from requirements to code.