Will Tracz
Abstract
A Domain-Specific Software Architecture (DSSA) has been defined as:• "an assemblage of software components, specialized for a particular type of task (domain), generalized for effective use across that domain, composed in a standardized structure (topology) effective for building successful applications" [Hay94] or, alternately• "a context for patterns of problem elements, solution elements, and situations that define mappings between them [Hid90].The following small example illustrates these definitions as well as provides the reader with some insight into the types of processes and tools needed to support the creation and use of a DSSA.
- [Bat94] D. Batory. A Software Generator for Flavored Type Expressions. Technical Report ADAGE-UT-94-02, University of Texas at Austin, February 1994.Google Scholar
- [CS93] L. Coglianese and R. Szymanski. DSSA-ADAGE: An Environment for Architecture-based Avionics Development. In Proceedings of AGARD'93, May 1993.Google Scholar
- [CT92] L. Coglianese and W. Tracz. Architecture-Based Development Process Guidelines for Avionics Software. Technical Report ADAGE-IBM-92-02, IBM Federal Systems Company, December 1992.Google Scholar
- [GHJV94] E. Gamma, R. Helm, R. Johnson, and J. Vlissides. Design Patterns - Microarchitectures for Reusable Object - Oriented Software. Addison-Wesley, 1994.Google Scholar
- [GS93] D. Garlan and M. Shaw. An Introduction to Software Architectures. Advances in Software Engineering and Knowledge Engineering, I:41-49, 1993.Google Scholar
- [Hay94] Architecture-Based Acquisition and Development of Software Guidelines and Recommendations from the ARPA Domain-Specific Software Architecture (DSSA) Program. Technical report, Teknowledge Federal Systems, October 1994.Google Scholar
- [Hid90] Proceedings of the Workshop on Domain-Specific Software Architectures. Technical Report CMU/SEI-88-TR-30, Software Engineering Institute, Hidden Valley, PA, July 9-12 1990.Google Scholar
- [HRT94] R. Hayes-Roth and W. Tracz. DSSA Tool Requirements for Key Process Functions. Technical Report ADAGE-IBM-93-13B, Loral Federal Systems - Owego, October 1994. Version 3.0.Google Scholar
- [Jon86] T.C. Jones. Programming Productivity. McGraw-Hill Book Company, New York, 1986.Google Scholar
- [KCH+90] 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.Google ScholarCross Ref
- [LAK+95] D.C. Luckham, L.M. Augustin, J.K. Kenney, J. Vera, D. Bryan, and W. Mann. Specification and Analysis of System Architecture Using Rapide. IEEE Transactions on Software Engineering, TBD 1995. Google ScholarDigital Library
- [PD91] R. Prieto-Díaz. Reuse Library Process Model. Technical Report AD-B157091, IBM CDRL 03041-002, STARS, July 1991.Google Scholar
- [RBP+91] J. Rumbaugh, M. Blaha, W. Premerlani, F. Eddy, and W. Lorensen. Object-Oriented Modeling and Design. Prentice-Hall, Inc., Englewood Cliffs, NJ, 1991. Google ScholarDigital Library
- [Sch90] W.L. Scherlis. DARPA Software Technology Plan. In Proceedings of ISTO Software Technology Community Meeting, June 27-29 1990.Google Scholar
- [SG95] M. Shaw and D. Garlan. Software Architecture - Perspectives on an Emerging Discipline. Prentice Hall, 1995. Google ScholarDigital Library
- [TC92] W. Tracz and L. Coglianese. DSSA Engineering Process Guidelines. Technical Report ADAGE-IBM-92-02A, IBM Federal Systems Company, December 1992.Google Scholar
- [TPD+94] A. Terry, G. Papanogopoulos, M. Devito, N. Coleman, and L. Erman. An Annotated Repository Schema. Version 4.0. Technical report, Teknowledge Federal Systems, 1994.Google Scholar
- [Tra87] W. Tracz. Software Reuse: Motivators and Inhibitors. In Proceedings of COMPCON87, February 1987.Google Scholar
- [Tra93a] W. Tracz. LILEANNA: A Parameterized Programming Language. In Proceedings of Second International Workshop on Software Reuse, pages 66-78, March 1993.Google Scholar
- [Tra93b] W. Tracz. Parameterized Programming in LILEANNA. In Proceedings of ACM Symposium on Applied Computing SAC'93, pages 77-86, February 1993. Google ScholarDigital Library
- [TSC94] W. Tracz, S. Shafer, and L. Coglianese. DSSA-ADAGE Design Records. Technical Report ADAGE-IBM-93-05A, Loral Federal Systems Company, July 1994. Version 1.1.Google Scholar
- [Wen94] K. Wentzel. Software Reuse, Facts and Myths. In Proceedings of 16th Annual International Conference on Software Engineering, pages 267-273, May 16-21 1994. Google ScholarDigital Library
Index Terms
- DSSA (Domain-Specific Software Architecture): pedagogical example
Recommendations
Domain-specific software architecture (DSSA) frequently asked questions (FAQ)
The Advanced Research Projects Agency's Domain-Specific Software Architecture (DSSA) Project has been the focal point of much interest in the software engineering community. This paper provides a list of "Frequently Asked Questions" (FAQ)1. For a more ...
Designing Domain-Specific Software Architecture (DSSA): Towards a New Approach
WICSA '07: Proceedings of the Sixth Working IEEE/IFIP Conference on Software ArchitectureSince the first works involving software reuse, domain engineering is considered a key process to develop reusable and flexible software. However, the results have shown that there is still much to do before the vision of domain engineering is ...
Domain-Specific Software Component Models
CBSE '09: Proceedings of the 12th International Symposium on Component-Based Software EngineeringWe believe that for developing applications in a specific domain, the best kind of software component model to use is a domain-specific one. We also believe that current component models intended for specific domains are actually not domain-specific. In ...
Comments