|
ABSTRACT
One of the dilemmas that has prevented software developers from resuing software is the lack of software artifacts to use or the existence of artifacts that are difficult to integrate. Domain-Specific Software Architectures (DSSAs) have been proposed[4] in order to address these issues. A DSAA not only provides a framework for reusable software components to fit into, but captures the design rationale and provides for a degree of adaptability. This paper1 presents an outline for a Domain-Specifid Software Architecture engineering process.
REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
| |
1
|
|
| |
2
|
[2] K.C. Kang, S.G. Cohen, J.A. Hess, W.E. Novak, and A.S. Peterson. Feature-Oriented Domain Analysis (FODA) Feasibility Study. Technical Report CMU/SEI-90-TR-21, Software Engineering Institute, November 1990.
|
| |
3
|
[3] K.J. Lee and et al. An ood paradigm for flight simulators, 2nd edition. Technical Report CMU/SEI- 88-TR-30, Software Engineering Institute, 1988.
|
| |
4
|
[4] E.G. Mettala. Domain Specific Software Architectures, June 1990. Presentation at ISTO Software Technology Community Meeting.
|
| |
5
|
[5] R. Prieto-Diaz. Domain Analysis for Reusability. In Proceedings of COMPSAC'87, pages 23-29, 1987.
|
| |
6
|
[6] R. Prieto-Diaz. Reuse Library Process Model. Technical Report AD-B157091, IBM CDRL 03041- 002, STARS, July 1991.
|
 |
7
|
|
| |
8
|
[8] W. Tracz and L. Coglianese. Domain Engineering Process Guidelines. Technical Report ADAGE-IBM-92-02, IBM Federal Sector Division, March 1992.
|
| |
9
|
[9] W.J. Tracz. Software Reuse Maxims. ACM Software Engineering Notes, 13(4):28-31, October 1988.
|
| |
10
|
[10] P.S. Young and R.N. Taylor. Teamware: Process Programming Support for Managers and Teams, July 1992.
|
|