Impact of software architecture reuse on development processes and standards

Journal of Systems and Software

Volumn 50, Issue 3, 2000, Pages 221-236

  Cioch, Frank A ^a   Brabbs, John M ^b   Sieh, Larry ^b  

^a Oakland University   (United States)

^b US Army Tank Automotive Command   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

COMPUTER ARCHITECTURE; COMPUTER SIMULATION; COMPUTER SOFTWARE SELECTION AND EVALUATION; LEGACY SYSTEMS; REQUIREMENTS ENGINEERING; SOFTWARE ENGINEERING; STANDARDS; TECHNOLOGY TRANSFER; USER INTERFACES;

USER-CENTERED ANALYSIS; WORK FLOW MODELING;

COMPUTER SOFTWARE REUSABILITY;

EID: 0033879243     PISSN: 01641212     EISSN: None     Source Type: Journal    
DOI: 10.1016/S0164-1212(99)00099-0     Document Type: Article

References (30)

1. Andriole, S.J., 1989. Storyboard Prototyping: A New Approach to User Requirements Analysis. QED Information Sciences.
2. Beyer H., Holtzblatt K. Apprenticing with the customer. Commun. ACM. 38(5):1995;45-52.
3. Boehm B. A spiral model of software development and enhancement. Computer. 21(5):1988;61-72.
4. Carroll J.M. Making use a design representation. Commun. ACM. 37(12):1994;29-35.
5. Cioch, F.A., 1996. Task-oriented information sharing among software developers. In: Proc. 14th Pacific Northwest Software Quality Conf., pp. 40-54.
6. Cioch, F.A., Brabbs, J., Kanter, S., 1994. Using the spiral model to assess, select and integrate software development tools. In: Proc. Third Symposium on Assessment of Quality Software Development Tools. IEEE, pp. 14-28.
7. Cioch, F.A., Palazzolo, M., Lohrer, S., 1996. A documentation suite for maintenance programmers. In: Proc. Int. Conf. on Software Maintenance. IEEE, pp. 286-295. This paper won the Conference Best Paper Award, sponsored by the J. Software Maintenance.
8. Connor D.R., Patterson R.W. Building commitment to organizational change. Training and Development J. 36(4):1982;18-30.
9. Corbitt G.F., Norman R. Implementation: the operational feasibility perspective. J. Systems Management. 40(5):1989;32-33.
10. Davis A. Operational prototyping: a new development approach. IEEE Software. 9(5):1992;70-78.
11. DMSO, 1989. web page: http://hla.dmso.mil.
12. Fischer G. Cognitive view of reuse and redesign. IEEE Software. 11(5):1987;60-72.
13. Fowler, P.J., Maher Jr., J.H., 1992. Foundations for Systematic Software Technology Transition. 1992 SEI Technical Review. Software Engineering Institute, Carnegie-Mellon University.
14. Garlan D., Allen R., Ockerbloom J. Architectural mismatch: why reuse is so hard. IEEE Software. 12(6):1995;17-26.
15. Gillies, A.C., Smith, P., 1994. Managing Software Engineering: CASE Studies and Solutions. Chapman & Hall, London, Ch. 7.
16. Holtzblatt K., Beyer H. Making customer-centered design work for teams. Commun. ACM. 36(10):1993;93-103.
17. Humphrey, W.S., 1989. CASE Planning and the Software Process. Software Engineering Institute Technical Report. CMU/SEI-89-TR-26, ESD-TR-89-34.
18. Jacobson I., Christerson M., Jonsson P., Overgaard G. Object-Oriented Software Engineering. 1992;Addison-Wesley, Reading, MA.
19. Jacobson I., Griss N.G., Jonsson P. Making the reuse business work. Computer. 30(10):1997;36-42.
20. Leonard-Barton D. Implementation as mutual adaptation of technology and organization. Research Policy. 17(5):1988;251-267.
21. Lohrer, S., Cioch, F.A., 1998. Using layered API's to reduce HLA transition costs. In: 1998 Spring Simulation Interoperability Workshop Proc. Simulation Interoperability Standards Organization.
22. Luqi, Royce W. Status report: computer-aided prototyping. IEEE Software. 9(6):1992;77-81.
23. Mili H., Mili F., Mili A. Reusing software: issues and research directions. IEEE Trans. Software Eng. 21(6):1995;528-561.
24. Schmidt D.C. Systems programming with C++ wrappers. C++ Report. 4(8):1992;50-54.
25. Schmidt D.C. An object-oriented interface to IPC services. C++ Report. 4(9):1992;48-54.
26. Schmidt D.C. Encapsulating operating system IPCs. C++ Report. 5(2):1993;43-50.
27. Schmidt D.C., Fayad M.E. Lessons learned building reusable OO frameworks for distributed software. Commun. ACM. 40(10):1997;85-87.
28. Sparks S., Benner K., Faris C. Managing object-oriented framework reuse. Computer. 29(9):1996;52-61.
29. Topper A. Evaluating CASE tools: guidelines for comparison. American Programmer. 4(7):1991;12-20.
30. Tracz W. DSSA (Domain-Specific Software Architecture) pedagogical example. ACM Sigsoft Software Engineering Notes. 20(3):1995;49-62.