This paper discusses the need to consider solution space objects as we model the problem space and develop our requirements models. Several major efforts are currently underway to develop domain and information engineering methodologies which used different representations to model the problem space.
Most of these methods are being developed independent of one another. As a result, the impact of one on the other is not being addressed. In addition, their is a movement afoot to standardize data and exploit the use of reusable software assets. However, problem space modeling methods specifically avoid being constrained by such solution space objects.
The author proposes a three step process for resolving the problem. First, a high level domain and data model is developed independent of solution space constrains for a product-line. Next, the resulting models are used to evaluate tradeoffs as product or project-related functional, performance, interface and quality requirements are developed at a more detailed level. Finally, solution space objects are considered as design requirements as the requirements unfold and are specified. The overall method fuses or integrates several methods into one single overall solution approach. It makes sure solution space objects are considered as problem space specifications are formulated at the individual project or product level.
To be successful, the process proposed must represent its underlying models using a consistent representation. In addition, the criteria and rules which govern the acceptability of the interim products that result at each step of the process need to be made explicit along with the major tradeoffs that need to be considered. Finally, the methodology must be adapted to be compatible with an object, functional or hybrid model and the translation from one to another.
Keywords: modeling, methodology integration, methodology fusion,
standard data, reusable software assets, domain engineering, information
engineering
Workshop Goals: Broaden viewpoints, stimulate discussion and generate a
few good ideas on how to deal with the challenge.
Working Groups: Domain analysis/engineering; Reuse and OO methods, Method
fusion/integration