Conceptual Modeling for Families of Software Systems
| dc.contributor.author | Stan Jarzabek | en_US |
| dc.contributor.author | Tang Siong Tiing | en_US |
| dc.date.accessioned | 2004-10-21T14:28:52Z | en_US |
| dc.date.accessioned | 2017-01-23T07:00:34Z | |
| dc.date.available | 2004-10-21T14:28:52Z | en_US |
| dc.date.available | 2017-01-23T07:00:34Z | |
| dc.date.issued | 1994-08-01T00:00:00Z | en_US |
| dc.description.abstract | Conceptual models must be sometimes built for a family of software systems rather than for a single system. Situations when this happens include evolutionary software development, software reengineering and reuse. In all those cases a conceptual model should characterize a given application domain and all the systems in that domain, e.g., payroll. For example, in software reuse, we look for reoccurring features (or concepts) such as objects, business rules, procedures, requirement/design patterns and code modules that can be reused across payroll systems. Capturing commonalties is a primary goal of a conceptual model. But apart from commonalties, we find that there are also some variations in feature specifications from one system to another. For example, some of the employee characteristics or rules for computing employee salary may differ from one payroll system to another. The premise of work described in this paper is that conceptual models should capture both commonalties and differences across a family of similar systems. In the reuse context, if variations in feature specification are not anticipated and explicitly modeled, customization of a component for reuse will not be easy: component customization will be done in an ad hoc way and programmers will have to go through the same customization process many times. Such reuse will be expensive and resulting systems will be difficult to maintain. These problems can be avoided if we explicitly model variations in feature specification. This paper shows how such multi-version models can be created. Conceptual models are composed of frames organized in Object-Oriented way. Our domain modeling method combines independent domain analysis and reverse engineering of low level design abstractions from existing programs. | en_US |
| dc.format.extent | 55431 bytes | en_US |
| dc.format.extent | 58408 bytes | en_US |
| dc.format.mimetype | application/pdf | en_US |
| dc.format.mimetype | application/postscript | en_US |
| dc.identifier.uri | https://dl.comp.nus.edu.sg/xmlui/handle/1900.100/1372 | en_US |
| dc.language.iso | en | en_US |
| dc.relation.ispartofseries | TRB8/94 | en_US |
| dc.title | Conceptual Modeling for Families of Software Systems | en_US |
| dc.type | Technical Report | en_US |
Files
License bundle
1 - 1 of 1