ACM Home Page
Please provide us with feedback. Feedback
Software development using domain-specific software architectures: CDRl A011—a curriculum module in the SEI style
Full text PdfPdf (1.34 MB)
Source ACM SIGSOFT Software Engineering Notes archive
Volume 20 ,  Issue 5  (December 1995) table of contents
Pages: 27 - 38  
Year of Publication: 1995
ISSN:0163-5948
Authors
Richard N. Taylor  ADAGE-UCI-94-01C
Will Tracz  ADAGE-UCI-94-01C
Lou Coglianese  ADAGE-UCI-94-01C
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 10,   Downloads (12 Months): 44,   Citation Count: 2
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/217030.217034
What is a DOI?

ABSTRACT

The objective of software development using domain-specific software architectures (DSSA) is reduction in time and cost of producing specific application systems within a supported domain, along with increased product quality, improved manageability, and positioning for acquisition of future business. Key aspects of the approach include software reuse based on parameterization of generic components and interconnection of components within a canonical solution framework. Viability of the approach depends on identification and deep understanding of a selected domain of applications. The DSSA approach, to be effectively applied, requires a variety of support tools, including repository mechanisms, prototyping facilities, and analysis tools. This curriculum module describes the DSSA approach, representative examples, supporting tools, and processes.


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] M. Heidegger, Being and Time, 1.6.44.a&b, Trans. & ed. John Macquarrie & Edward Robinson, Harper & Row, San Francisco 1962, pp. 257-269.
 
3
[3] P. Feyerabend, Against Method: Outline of an Anarchistic Theory of Knowledge, Thetford Press Ltd., Thetford (GB) 1978.
 
4
[4] R. B. Heady & M. Smith, "An Empirical Study of the Topical Differences Between Total Quality Management and Quality Management," Quality Management Journal, vol. 2 no. 3 (Spring 1995), pp. 24-37.
 
5
[5] C. G. Hempel, "Deductive-Nomological vs. Statistical Explanation," Minnesota Studies in the Philosophy of Science, Vol. III, Univ. of Minn. Pr., Minneapolis 1962, pp. 98-169.
 
6
[6] M. Harwit, "An Attempt to Model the Growth of Understanding in Astronomy," Theory and Observational Limits in Cosmology, Ed. W. R. Stoeger, Specola Vaticana, Citta del Vaticano 1987, pp.89-119.
 
7
[7] R. C. Burian, "Scientific Realism and Incommensurability: Some Criticisms of Kuhn and Feyerabend," Methodology. Metaphysics, and the History of Science, Eds. R. S. Cohen & M. W. Wartofsky, D. Reidel Publishing Co., Boston 1984, pp. 1-31.
 
8
[8] M. Martin, "How to Be a Good Philosopher of Science: A Plea for Empiricism in Matters Epistemological," Methodology, Metaphysics, and the History of Science, Eds. R. S. Cohen & M. W. Wartofsky, D. Reidel Publishing Co., Boston 1984, pp. 33-42.
 
9
[9] P. Feyerabend, "How to Be a Good Empiricist: A Plea for Tolerance in Matters Epistemological," Philosophy of Science: The Delaware Seminar, Ed. B. Baumrin. Interscience, New York 1963, pp. 3-40.
 
10
[10] P. Feyerabend, "Philosophy of Science 2001." Methodology, Metaphysics, and the History of Science, Eds. R. S. Cohen & M. W. Wartofsky, D. Reidel Publishing Co., Boston 1984, pp. 137-47.
11
12
 
13
[BGW92] Bus-based Kits for Reusable Software. B.W. Beach, M.L. Griss, and K.D. Wentzel. Proceedings of ISS'92, Irvine, CA, March, 1992, pages 19-28.
14
15
16
 
17
[CGST92] An Avionics Domain-Specific Software Architecture. L. Coglianese, M. Goodwin, R. Smith, and W. Tracz. Proceedings of DARPA Software Technology Conference, April, 1992, pages 211-214.
 
18
 
19
[CT93] Architecture Based Development Guidelines for Avionics Software. Louis H. Coglianese and Will Tracz. ADAGE-IBM-92-03, version 2.1.
 
20
[Gar95] ICSE-17 Software Architecture Workshop Summary, David Garlan. Software Engineering Notes (SEN), Vol. 20, No. 3, July 1995, pages 84-89.
21
 
22
[GHJV] Design Patterns: Abstraction and Reuse of Object-Oriented Design. Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides. Addison Wesley, 1995.
 
23
 
24
[GM92] The Domain-Specific Software Architecture Program. M. Graham, and E. Mettala. Proceedings of DARPA Software Technology Conference, April, 1992, pages 204-210.
 
25
 
26
[Gui93] Domain Analysis Methods. Guillermo Arango, in Software Reusability, edited by W. Schaefer, published by Ellis Horwood, October 1993.
 
27
[Hay94] Architecture-Based Acquisition and Development of Software: Guidelines and Recommendations from the ARPA Domain-Specific Software Architecture (DSSA) Program. Dr. Frederick Hayes-Roth, Principal Investigator, Teknowledge Federal Systems. Version 1.01 February 4, 1994.
28
 
29
[McA93] DSSA-ADAGE Avionics/Architecture Knowledge Representation Language, Draft Report. David McAllester. ADAGE-MIT-93-01, September 1993.
 
30
[Par79] Designing Software for Ease of Extension and Contraction. David Lorge Parnas. IEEE Transactions on Software Engineering, Volume SE-5, Number 2, March 1979, pages 128-138.
 
31
 
32
[Prot] Prototech summary. To appear.
33
 
34
[SPC93] Overview of Megaprogramming Course. Software Productivity Consortium Services Corporation, SPC-93028- CMC, Version 01.00.02, May 1993.
35
36
 
37
[Tra93b] LILEANNA: A Parameterized Programming Language. Will Tracz. Proceedings of Second International Workshop on Software Reuse, March 1993, pages 66-78.
 
38
[TC92] DSSA Engineering Process Guidelines. Will Tracz and Lou Coglianese. ADAGE-IBM-9202, December, 1992. IBM Federal Systems Company.
 
39
[Tra94] DSSA Frequently Asked Questions. Will Tracz. Software Engineering Notes (SEN), Vol. 19, No. 2, April 1994.
40
41


Collaborative Colleagues:
Richard N. Taylor: colleagues
Will Tracz: colleagues
Lou Coglianese: colleagues