Joachim Bayer
- 1.Arango, G. and Prieto-Diaz, R. (eds.) Domain Analysis Concepts and Research Directions. In Domain Analysis and Software Systems Modeling, pp. 9-31, IEEE Computer Society Press, 1991.Google Scholar
- 2.Ardis, M. and Weiss, D. Defining Families: The Commonality Analysis. Proceedings of the Nineteenth International Conference on Software Engineering, pp. 649- 650, IEEE Computer Society Press, May 1997. Google ScholarDigital Library
- 3.Basili, V., Caldiera, G., and Rombach, D. Experience Factory. Encyclopedia of Software Engineering Volume 1:469-476, Marciniak, J. ed. John Wiley & Sons, 1994.Google Scholar
- 4.Bass, L., Clements, P., and Kazman, R. Software Architecture in Practice. Addison-Wesley, 1998 Google ScholarDigital Library
- 5.Bergey, J. et. al. DoD Product Line Practice Workshop Report. Technical Report CMU/SEI-98-TR-07, Carnegie Mellon, May 1998.Google ScholarCross Ref
- 6.Foreman, J. Product Line Based Software Development- Significant Results, Future Challenges. Proceedings of the Software Technology Conference. April 1996.Google Scholar
- 7.Gomaa, H., Kerschberg, L., Sugumaran, V., Bosch, C., Tavakoli, I. and O'Hara. L. A knowledge-based software engineering environment for reusable software requirements and architectures. Automated Software Engineering, 3(3,4), pp. 285-307, August 1996.Google Scholar
- 8.Kazman, R., Abowd, L., Bass, R., and Clements, P. Scenario-Based Analysis of Software Architecture, IEEE Software, 11 / 1996. Google ScholarDigital Library
- 9.Lim, W. Reuse economics: A comparison of seventeen models and directions for future research. Proceedings of the Fourth International Conference on Software Reuse, pp. 41-50, 1996. Google ScholarDigital Library
- 10.Mollaghasemi, M. and Pet-Edwards, J. Making Multiple- Objective Decisions. IEEE Computer Society, 1997.Google Scholar
- 11.Paulk, M., Curtis, B., Chrissis, M., and Weber, C. Capability Maturity Model for Software (Version 1.1). Technical Report CMU/SEI-93-TR-024, February 1993.Google ScholarCross Ref
- 12.Potts, C., Takahashi, K., and Anton, A. Inquiry-Based Requirments Analysis. IEEE Software, pp. 21-32, March 1994 Google ScholarDigital Library
- 13.Shaw, M. and Garlan, D. Software Architecture: Perspectives on an Emerging Discipline. Prentice Hall, 1996. Google ScholarDigital Library
- 14.Software Engineering Institute, Model-Based Software Engineering. http://www.sei.cmu.edu/technology/mbse/ is.html, April 25, 1998.Google Scholar
- 15.Software Productivity Consortium Services Corporation. Reuse Adoption Guidebook, Version 02.00.05, November 1993.Google Scholar
- 16.Software Productivity Consortium. Reuse-Driven Software Processes Guidebook, Version 02.00.03. Technical Report SPC-92019-CMC, Software Productivity Consortium, November 1993.Google ScholarCross Ref
- 17.Software Technology for Adaptable Reliable Systems. Organization Domain Modeling (ODM) Guidebook, Version 2.0. Unisys STARS Technical Report STARS- VC-A025/O01/O0, Reston VA, June 1996.Google Scholar
- 18.Tracz, W. and Coglianese, L. Domain-Specific Software Architecture Engineering Process Guidelines, Technical Report ADAGE-IBM-92-02, Loral Federal Systems, 1992.Google Scholar
- 19.J. Whitey. Investment analysis of software assets for product lines. Technical Report CMU/SEI-96-TROI O, Software Engineering Institute, Carnegie Mellon University, 1996.Google Scholar
Index Terms
- PuLSE: a methodology to develop software product lines
Recommendations
The software product line architecture: An empirical investigation of key process activities
Software architecture has been a key area of concern in software industry due to its profound impact on the productivity and quality of software products. This is even more crucial in case of software product line, because it deals with the development ...
Reverse Engineering in Software Product Line - A Systematic Literature Review
CSAI '18: Proceedings of the 2018 2nd International Conference on Computer Science and Artificial IntelligenceReverse engineering is the information extraction process on system by identifying and analyzing the components that are part of that system. We analyze existing research that related with reverse engineering process on software product line. There are ...
Identifying Issues and Concerns in Software Reuse in Software Product Lines
ICSR '09: Proceedings of the 11th International Conference on Software Reuse: Formal Foundations of Reuse and Domain EngineeringOne of the reasons for introducing software product lines (SPL) is the reduction of costs through reusing common assets for different products<em>. </em> Developing assets to be reused in different products is often not easy. Increasing complexity due ...
Comments