Software Product Lines
Framework Home
Introduction
Product Line Essential Activities
Product Line Practice Areas
Software Engineering
Practice Areas
Technical Management
Practice Areas
Organizational Management
Practice Areas
Frequently Asked Questions
Glossary
Bibliography

A Framework for Software Product Line Practice, Version 5.0

Table of Contents Previous Section

Bibliography

[Abowd 1996a]

Abowd, G.; Bass, L.; Clements, P.; Kazman, R.; Northrop, L.; & Zaremski, A. Recommended Best Industrial Practice for Software Architecture Evaluation (CMU/SEI-96-TR-025, ADA320786). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1996.

[Albert 2002a]

Albert, C.; Brownsword, L.; Bentley, D.; Bono, T.; Morris, E.; & Pruitt, D. Evolutionary Process for Integrating COTS-Based Systems (EPIC) Building, Fielding, and Supporting Commercial-off-the-Shelf (COTS) Based Solutions (CMU/SEI-2002-TR-005, ADA408653). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2002.

[Alexander 1979a]

Alexander, C. The Timeless Way of Building. New York, NY: Oxford University Press, 1979.

[Alhir 2002a]

Alhir, Sinan Si. "Understanding the Unified Process (UP)." Methods and Tools 10, 1 (Spring 2002): 2-17.

[America 2000a]

America, P.; Obbink, H.; van Ommering, R.; & van der Linden, F. "CoPAM: A Component-Oriented Platform Architecting Method Family for Product Family Engineering," 167-180. Software Product Lines: Proceedings of the First Software Product Line Conference (SPLC1). Denver, Colorado, August 28-31, 2000. Boston, MA: Kluwer Academic Publishers, 2000.

[Anastasopoulos 2000a]

Anastasopoulos, M. & Gacek, C. Implementing Product Line Variabilities (IESE-Report No. 089.00/E, V1.0). Kaiserslautern, Germany: Fraunhofer Institut Experimentelles Software Engineering, 2000.

[ANSI 1992a]

American National Standards Institute. Guide for the Preparation of Operational Concept Documents (ANSI/AIAA G-043-1992). Washington, DC: American National Standards Institute, 1992.

[AOSA 2007a]

Aspect-Oriented Software Association. Aspect-Oriented software Development Home Page (2007).

[Arango 1994a]

Arango, G. Ch. 2, "Domain Analysis Methods," 17-49. Software Reusability. Hemel Hempstead, England: Ellis Horwood, 1994.

[Ardis 2000a]

Ardis, M.; Dudak, P.; Dor, L.; Leu, W.; Nakatani, L.; Olsen, B.; & Pontrelli, P. "Domain Engineered Configuration Control," 479-494. Software Product Lines: Proceedings of the First Software Product Line Conference (SPLC1). Denver, Colorado, August 28-31, 2000. Boston, MA: Kluwer Academic Publishers, 2000.

[Bachmann 2000a]

Bachmann, F.; Bass, L.; Chastek, G.; Donohoe, P.; & Peruzzi, F. The Architecture Based Design Method (CMU/SEI-2000-TR-001, ADA375851). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2000.

[Bachmann 2005a]

Bachmann, F. & Clements, P. Variability in Software Product Lines (CMU/SEI-2005-TR-012, ADA450337). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2005.

[Baldwin 2002a]

Baldwin, Carliss Y. & Clark, Kim B. "The Option Value of Modularity in Design-An Example from Design Rules, Volume 1: The Power of Modularity" (May 2002).

[Basili 1984a]

Basili, V. R. & Weiss, D. "A Methodology for Collecting Valid Software Engineering Data." IEEE Transactions on Software Engineering SE-10, 6 (November 1984): 728-738.

[Bass 1997a]

Bass, L.; Clements, P.; Cohen, S.; Northrop, L.; & Withey, J. Product Line Practice Workshop Report (CMU/SEI-97-TR-003, ADA327610). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1997.

[Bass 1998a]

Bass, L.; Chastek, G.; Clements, P.; Northrop, L.; Smith, D.; & Withey, J. Second Product Line Practice Workshop Report (CMU/SEI-98-TR-015, ADA354691). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1998.

[Bass 1999a]

Bass, L.; Campbell, G.; Clements, P.; Northrop, L.; & Smith, D. Third Product Line Practice Workshop (CMU/SEI-99-TR-003, ADA361391). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1999.

[Bass 1999b]

Bass, L. & Kazman, R. Architecture-Based Development (CMU/SEI-99-TR-007, ADA366100). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1999.

[Bass 2000a]

Bass, L.; Clements, P.; Donohoe, P.; McGregor, J.; & Northrop, L. Fourth Product Line Practice Workshop Report (CMU/SEI-2000-TR-002, ADA375843). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2000.

[Bass 2003a]

Bass, L.; Clements, P.; & Kazman, R. Software Architecture in Practice, Second Edition. Reading, MA: Addison-Wesley, 2003.

[Batory 2005a]

Batory, Don. "Feature Models, Grammars, and Propositional Formulas," 7-20. Proceedings of the 9th International Software Product Line Conference (SPLC 2005) (Lecture Notes in Computer Science volume 3714). Rennes, France, September 26-29, 2005. New York, NY: Springer, 2005.

[Bayer 2000a]

Bayer, J.; Muthig, D.; & Widen, T. "Customizable Domain Analysis," 178-194. Proceedings of the First International Symposium on Generative and Component-Based Software Engineering (GCSE '99). Erfurt, Germany, September 28-30, 1999. New York, NY: Springer, 2000.

[Bean 2000a]

Bean, J. "Use XML Even As It Changes." Enterprise Development 2, 2 (February 2000): 44-50.

[Beck 1994a]

Beck, K. & Johnson, R. "Patterns Generate Architectures," 139-149. Proceedings of the Eighth European Conference on Object-Oriented Programming (ECOOP '94). Bologna, Italy, July 4-8, 1994. New York, NY: Springer-Verlag, 1994.

[Beck 1999a]

Beck, K. Extreme Programming Explained. Reading, MA: Addison-Wesley, 1999.

[Beck 2002a]

Beck, K. Test-Driven Development: By Example. Boston, MA: Addison-Wesley, 2002.

[Beizer 1990a]

Beizer, B. Software Testing Techniques. Boston, MA: International Thompson Computer Press, 1990.

[Berczuk 2003a]

Berczuk, Steve. Software Configuration Management Patterns. Boston, MA: Addison-Wesley, 2003.

[Bergey 1998a]

Bergey, J.; Clements, P.; Cohen, S.; Donohoe, P.; Jones, L.; Krut, B.; Northrop, L.; Tilley, S.; Smith, D.; & Withey, J. DoD Product Line Practice Workshop Report (CMU/SEI-98-TR-007, ADA346252). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1998.

[Bergey 1999a]

Bergey, J.; Smith, D.; Weiderman, N.; & Woods, S. Options Analysis for Reengineering (OAR): Issues and Conceptual Approach (CMU/SEI-99-TN-014, ADA370600). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1999.

[Bergey 1999b]

Bergey, J.; Fisher, M.; & Jones, L. The DoD Acquisition Environment and Software Product Lines (CMU/SEI-99-TN-004, ADA244787). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1999.

[Bergey 2001a]

Bergey, J.; O'Brien, L.; & Smith, D. Options Analysis for Reengineering (OAR): A Method for Mining Legacy Assets (CMU/SEI-2001-TN-013, ADA395201). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2001.

[Bergey 2002a]

Bergey, J.; O'Brien, L.; & Smith, D. "Using the Options Analysis for Reengineering (OAR) Method for Mining Components for a Product Line," 316-327. Software Product Lines: Proceedings of the Second Software Product Line Conference (SPLC2). San Diego, CA, August 19-22, 2002. Berlin, Germany: Springer, 2002.

[Bergey 2003a]

Bergey, J.; O'Brien, L.; & Smith, D. Application of Options Analysis for Reengineering in a Lead System Integrator Environment (CMU/SEI-2003-TN-009). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2003.

[Bergey 2004a]

Bergey, J.; Campbell, G.; Cohen, S.; Fisher, M.; Gallagher, B.; Jones, L.; Northrop, L.; & Soule, A. Software Product Line Acquisition: A Companion to a Framework for Software Product Line Practice, Version 3.0. (2004).

[Bergey 2006a]

Bergey, John & Cohen, Sholom. Product Line Acquisition in a DoD Organization-Guidance for Decision Makers (CMU/SEI-2006-TN-020, ADA447911). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2006.

[Birk 2003a]

Birk, A.; Heller, G.; John, I.; Joos, S.; Muller, K.; Schmid, K.; & von der Massen, T. Report of the GI Work Group "Requirements Engineering for Product Lines" (IESE-Report No. 121.03/E, V1.0). Kaiserslautern, Germany: Fraunhofer Institut Experimentelles Software Engineering, 2003.

[Boeckle 2002a]

Boeckle, G.; Munoz, J.; Knauber, P.; Krueger, C.; Leite, J.; van der Linden, F.; Northrop, L.; Stark, M.; & Weiss, D. "Adopting and Institutionalizing a Product Line Culture,"49-59. Software Product Lines: Proceedings of the Second Software Product Line Conference (SPLC2). San Diego, CA, August 19-22, 2002. Berlin, Germany: Springer, 2002.

[Boehm 1981a]

Boehm, B. Software Engineering Economics. Englewood Cliffs, NJ: Prentice-Hall, 1981.

[Boehm 1988a]

Boehm, B. W. "A Spiral Model of Software Development and Enhancement." Computer 21, 5 (May 1988): 61-72.

[Boehm 1989a]

Boehm, B. IEEE Tutorial on Software Risk Management. Piscataway, NJ: IEEE Computer Society Press, 1989.

[Boehm 2000a]

Boehm, B. "…And Very Few Lead Bullets, Either" [CD-ROM]. Proceedings of Impacts 2000: The 15th Annual Software Engineering Symposium. Washington, DC, September 18-21, 2000. Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2000.

[Boehm 2004a]

Boehm, Barry; Brown, A. Winsor; Madachy, Ray; & Yang, Ye. "A Software Product Line Life Cycle Cost Estimation Model," 156-164. Proceedings of the International Symposium on Empirical Software Engineering (ISESE 2004). Redondo Beach, CA, August 19-20, 2004. Los Alamitos, CA: IEEE Computer Society, 2004.

[Boehm 2004b]

Boehm, B. & Turner, R. Balancing Agility and Discipline: A Guide for the Perplexed. Reading, MA: Addison-Wesley, 2004.

[Booch 1994a]

Booch, G. Object-Oriented Analysis and Design with Applications. Reading, MA: Addison-Wesley, 1994.

[Bosch 2000a]

Bosch, J. Design and Use of Software Architectures: Adopting and Evolving a Product-Line Approach. Reading, MA: Addison-Wesley, 2000.

[Bosch 2000b]

Bosch, J. "Organizing for Software Product Lines," 117-134. Proceedings of the 3rd International Workshop on Software Architectures for Product Families (IWSAPF-3). Las Palmas de Gran Canaria, Spain, March 15-17, 2000. Berlin, Germany: Springer, 2000.

[Bosch 2002a]

Bosch, J. "Maturity and Evolution in Software Product Lines: Approaches, Artifacts, and Organization," 257-271. Software Product Lines: Proceedings of the Second Software Product Line Conference (SPLC2). San Diego, CA, August 19-22, 2002. Berlin, Germany: Springer, 2002.

[Brassard 2001a]

Brassard, M. & Ritter, D. Sailing Through Six Sigma. Marietta, GA: Brassard & Ritter, 2001.

[Brooks 1987a]

Brooks, F. "No Silver Bullet: Essence and Accidents of Software Engineering." Computer 20, 4 (April 1987): 10-19.

[Brown 1994a]

Brown, A. W.; Carney, D. J.; Morris, E. J.; Smith, D. B.; & Zarrella, P. F. Principles of Case Tool Integration. Oxford, U.K.: Oxford University Press, 1994.

[Brown 1994b]

Brown, A. W. "Why Evaluating CASE Environments is Different from Evaluating CASE Tools," 4-13. Proceedings of the Third Symposium on Assessment of Quality Software Development Tools. Washington, DC, June 7-9, 1994. Los Alamitos, CA: IEEE Computer Society Press, 1994.

[Brown 1996a]

Brown, A. & Wallnau, K. "A Framework for Evaluating Software Technology." IEEE Software 13, 5 (September 1996): 39-49.

[Brown 1998a]

Brown, A. W. & Wallnau, K. C. "The Current State of CBSE." IEEE Software 15, 5 (September/October 1998): 37-46.

[Brownsword 1996a]

Brownsword, L. & Clements, P. A Case Study in Successful Product Line Development (CMU/SEI-96-TR-016, ADA315802). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1996.

[Bruckhaus 1996a]

Bruckhaus, T.; Madhavji, N. H.; Janssen, I.; & Henshaw, J. "The Impact of Tools on Software Productivity." IEEE Software 13, 5 (September 1996): 29-38.

[Budgen 2003a]

Budgen, David & Thomson, Mitchell. "CASE Tool Evaluation: Experiences from an Empirical Study." The Journal of Systems and Software 67, 2 (2003): 55-75.

[Burrows 2005a]

Burrows, Clive & Wesley, Ian. Ovum Evaluates: Configuration Management. London, UK: Ovum, Ltd., 2005.

[Buschmann 1996a]

Buschmann, F.; Meunier, R.; Rohnert, H.; Sommerlad, P.; & Stal, M. Pattern-Oriented Software Architecture: A System of Patterns. New York, NY: John Wiley & Sons, 1996.

[Cagan 1992a]

Cagan, M. & Wright, A. Requirements for a Modern Software Configuration Management System. Irvine, CA: Continuous Software Corporation, currently Telelogic, Inc., 1992.

[CARDS 1994a]

Comprehensive Approach to Reusable Defense Software (CARDS). Training Plan (STARS-VC-B003/001/00). Reston, VA: Unisys Corporation, 1994.

[Carney 1997a]

Carney, D. Assembling Large Systems from COTS Components: Opportunities, Cautions, and Complexities. SEI Monographs on the Use of Commercial Software in Government Systems. Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1997.

[Carney 1998a]

Carney, D.; Brownsword, L.; & Oberndorf, T. "The Opportunities and Complexities of Applying Commercial Off-the-Shelf Components." Crosstalk 11, 4 (April 1998): 4-6.

[Carney 1998b]

Carney, D. "Evaluation of COTS Products: Some Thoughts on the Process" [online]. SEI Interactive 1, 2 (September 1998).

[Carney 1998c]

Carney, D. "COTS Evaluation in the Real World" [online]. SEI Interactive 1, 3 (December 1998).

[Charan 1999a]

Charan, R. & Colvin, G. "Why CEOs Fail." Fortune 139, 12 (June 21, 1999): 68-78.

[Charette 1989a]

Charette, R. Software Engineering Risk Analysis and Management. New York, NY: McGraw-Hill, 1989.

[Chastek 2001a]

Chastek, G.; Donohoe, P.; Kang, K.; & Thiel, S. Product Line Analysis: A Practical Introduction (CMU/SEI-2001-TR-001, ADA396137). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2001.

[Chastek 2002a]

Chastek, G., ed. Software Product Lines: Proceedings of the Second Software Product Line Conference (SPLC2). San Diego, CA, August 19-22, 2002. Berlin, Germany: Springer, 2002.

[Chastek 2002b]

Chastek, G. & McGregor, J. Guidelines for Developing a Product Line Production Plan (CMU/SEI-2002-TR-006, ADA407772). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2002.

[Chastek 2002c]

Chastek, Gary; Donohoe, Patrick; & McGregor, John D. Product Line Production Planning for the Home Integration System Example (CMU/SEI-2002-TN-029, ADA405846). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2002.

[Chastek 2003a]

Chastek, Gary & Donohoe, Patrick. Product Line Analysis for Practitioners (CMU/SEI-2003-TR-008). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2003.

[Chastek 2004a]

Chastek, Gary; Donohoe, Patrick; & McGregor, John D. A Study of Product Production in Software Product Lines (CMU/SEI-2004-TN-012), Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University.

[Christensen 1997a]

Christensen, Clayton M. The Innovator's Dilemma: When New Technologies Cause Great Firms to Fail. Boston, MA: Harvard Business School Press, 1997.

[Clemen 1991a]

Clemen, R. T. Making Hard Decisions: An Introduction to Decision Analysis. Boston, MA: PWS-Kent Publishing Co., 1991.

[Clements 1998a]

Clements, P.; Bass, L.; Chastek, G.; Northrop, L.; Smith, D.; & Withey, J. Second Product Line Practice Workshop Report (CMU/SEI-98-TR-015, ADA354691). Colorado Springs, CO, November 1997. Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1998.

[Clements 1998b]

Clements, P. & Weiderman, N. Report on the Second International Workshop on Development and Evolution of Software Architectures for Product Families (CMU/SEI-98-SR-003, ADA346343). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1998.

[Clements 2000a]

Clements, P. Active Reviews for Intermediate Designs (CMU/SEI-2000-TN-009, ADA383775). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2000.

[Clements 2001a]

Clements, P.; Kazman, R.; & Klein, M. Evaluating Software Architectures: Methods and Case Studies. Boston, MA: Addison-Wesley, 2001.

[Clements 2002a]

Clements, P.; Bachmann, F.; Bass, L.; Garlan, D.; Ivers, J.; Little, R.; Nord, R.; & Stafford, J. Documenting Software Architectures: Views and Beyond. Reading, MA: Addison-Wesley, 2002.

[Clements 2002b]

Clements, P. & Krueger, C. Two-part Point/Counterpoint column: "Being Proactive Pays Off" and "Eliminating the Adoption Barrier." IEEE Software 19, 4 (July/August 2002): 28-31.

[Clements 2002c]

Clements, P. & Northrop, L. Software Product Lines: Practices and Patterns. Boston, MA: Addison-Wesley, 2002.

[Clements 2005a]

Clements, Paul C.; McGregor, John D.; & Cohen, Sholom G. The Structured Intuitive Model for Product Line Economics (SIMPLE) (CMU/SEI-2005-TR-003). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2005.

[Clements 2005b]

Clements, P.; Jones, L.; McGregor, J.; & Northrop, L. "Project Management in a Software Product Line Organization." IEEE Software 22, 5 (September/October 2005): 54-62.

[Clemons 1997a]

Clemons, Eric K. & Hitt, Lorin M. Strategic Sourcing for Services: Assessing the Balance Between Outsourcing and Insourcing. http://opim.wharton.upenn.edu/~clemons/files/outsourcing_v4_2.pdf (June 1997).

[Cohen 1991a]

Cohen, S. G.; Stanley Jr., J. L.; Peterson, A. S.; & Krut Jr., R. W. Application of Feature-Oriented Domain Analysis to the Army Movement Control Domain and Appendices A-I (CMU/SEI-91-TR-028, ADA256590). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1991.

[Cohen 1996a]

Cohen, S.; Friedman, S.; Martin, L.; Royer, T.; Solderitsch, N.; & Webster, R. Concept of Operations for the ESC Product Line Approach (CMU/SEI-96-TR-018, ADA313952). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1996.

[Cohen 1998a]

Cohen, S. & Northrop, L. "Object-Oriented Technology and Domain Analysis," 86-93. Proceedings of the Fifth International Conference on Software Reuse. Victoria, B.C., June 2-5, 1998. Los Alamitos, CA: IEEE Computer Society Press, 1998.

[Cohen 1999a]

Cohen, S. Guidelines for Developing a Product Line Concept of Operations (CMU/SEI-99-TR-008, ADA367714). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1999.

[Cohen 2001a]

Cohen, S. Case Study: Building and Communicating a Business Case for a DoD Product Line (CMU/SEI-2001-TN-020, ADA395155). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2001.

[Cohen 2003a]

Cohen, S. Predicting When Product Line Investment Pays (CMU/SEI-2003-TN-017, ADA418466). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2003.

[Coplien 1998a]

Coplien, J.; Hoffman, D.; & Weiss, D. "Commonality and Variability in Software Engineering." IEEE Software 15, 6 (November/December 1998): 37-45.

[Crosby 1979a]

Crosby, P. B. Quality Is Free. New York, NY: McGraw-Hill, 1979.

[Crossroads 2006a]

CM Crossroads. CM Crossroads Home Page. http://www.cmcrossroads.com/ (2007).

[Cruikshank 1998a]

Cruikshank, J. L. & Sicilia, D. B. The Engine That Could: 75 Years of Value-Driven Change at Cummins Engine Company. Boston, MA: Harvard Business School Press, 1998.

[Curtis 1992a]

Curtis, B.; Kellner, M.; & Over, J. "Process Modeling." Communications of the ACM 35, 9 (September 1992): 75-90.

[Cusumano 1991a]

Cusumano, M. A. Japan's Software Factories. New York, NY: Oxford University Press, 1991.

[Czarnecki 2005a]

Czarnecki. K. "Overview of Generative Software Development," 326-341. Unconventional Programming Paradigms (UPP) 2004 (Lecture Notes in Computer Science volume 3566). Le Mont Saint Michel, France, September 15-17, 2004. Berlin, Germany: Springer-Verlag, 2005.

[Dabrowski 1993a]

Dabrowski, C. & Katz, S. A Context Analysis of the Network Management Domain (NISTIR 5309). Gaithersburg, MD: National Institute of Standards and Technology, 1993.

[Dabrowski 1994a]

Dabrowski, C. & Watkins, J. A Domain Analysis of the Alarm Surveillance Domain V1.0 (NISTIR 5494). Gaithersburg, MD: National Institute of Standards and Technology, 1994.

[Dager 2000a]

Dager, J. "Cummins's Experience in Developing a Software Product Line Architecture for Real-Time Embedded Diesel Engine Controls," 23-45. Software Product Lines: Proceedings of the First Software Product Line Conference (SPLC1). Denver, Colorado, August 28-31, 2000. Boston, MA: Kluwer Academic Publishers, 2000.

[Dart 1991a]

Dart, S. "Concepts in Configuration Management Systems," 1-18. Proceedings of the Third International Conference on Software Configuration Management. Trondheim, Norway, June 12-14, 1991. New York, NY: Association for Computing Machinery Press, 1991.

[Davis 1990a]

Davis, A. M. Software Requirements: Analysis and Specification. Englewood Cliffs, NJ: Prentice-Hall, 1990.

[DeBaud 1999a]

DeBaud, J. & Schmid, K. "A Systematic Approach to Derive the Scope of Software Product Lines," 34-43. Proceedings of the 21st International Conference on Software Engineering (ICSE). Los Angeles, CA, May 16-22, 1999. Los Alamitos, CA: IEEE Computer Society, 1999.

[Del Rosso 2006a]

Del Rosso, C. "Continuous Evolution Through Software Architecture Evaluation: A Case Study." Journal of Software Maintenance and Evolution Research and Practice 18, 5 (September/October 2006): 351-383.

[Deming 1986a]

Deming, W. E. Out of the Crisis. Cambridge, MA: MIT Center for Advanced Engineering, 1986.

[Deschamps 1995a]

Deschamps, J. & Nayak, P. R. Product Juggernauts. Watertown, MA: Harvard Business School Press, 1995.

[DFARS 1998a]

U.S. Department of the Navy. The Defense Federal Acquisition Regulation Supplement (DFARS) (1998).

[Diaz 2005a]

Díaz, Oscar; Trujillo, Salvador; & Anfurrutia, Felipe I. "Supporting Production Strategies as Refinements of the Production Process," 210-221. Proceedings of the 9th International Software Product Lines Conference (SPLC 2005). Rennes, France, September 26-29, 2005. New York, NY: Springer, 2005.

[DISA 1993a]

Defense Information Systems Agency Center for Information Management (DISA/CIM) Software Reuse Program. Domain Analysis and Design Process, V1. Arlington, VA: Defense Information Systems Agency Center for Information Management, 1993.

[DISA 1995a]

Defense Information Systems Agency. US Army Space and Strategic Defense Command, Software Reuse Business Model. Washington, DC: The Department of Defense, 1995.

[Donohoe 2000a]

Donohoe, P., ed. Software Product Lines: Proceedings of the First Software Product Line Conference (SPLC1). Denver, Colorado, August 28-31, 2000. Boston, MA: Kluwer Academic Publishers, 2000.

[Dorfman 1997a]

Dorfman, M. & Thayer, R. H. Software Requirements Engineering. Los Alamitos, CA: IEEE Computer Society Press, 1997.

[Dorofee 1994a]

Dorofee, A.; Walker, J.; Gluch, D.; Higuera, R.; Murphy, R.; Walker, J.; & Williams, R. Team Risk Management Guidebook. Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1994.

[Dorofee 1996a]

Dorofee, A.; Walker, J.; Alberts, C.; Higuera, R.; Murphy, R.; & Williams, R. Continuous Risk Management Guidebook. Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1996.

[Dumaine 1989a]

Dumaine, B. "How Managers Can Succeed by Speed." Fortune 119, 4 (February 1989): 54.

[Ecklund 1996a]

Ecklund, Jr., E.; Delcambre, L.; & Freiling, M. "Change Cases: Use Cases That Identify Future Requirements," 342-358. Conference Proceedings of the OOPSLA 96. San Jose, CA, October 6-10, 1996. San Jose, CA: ACM Press, 1996.

[Eisner 1994a]

Eisner, H. "Systems Engineering Sciences," 1312-1322. Encyclopedia of Software Engineering, Volume 2. New York, NY: John Wiley & Sons, 1994.

[Estublier 2005a]

Estublier, Jacky; Leblang, David; van der Hoek, Andre; Conradi, Reidar; Clemm, Geoffrey; Tichy, Walter; & Wiborg-Weber, Darcy. "Impact of Software Engineering Research on the Practice of Software Configuration Management." ACM Transactions on Software Engineering and Methodology 14, 4 (October 2005): 383-430.

[Etzioni 1964a]

Etzioni, A. Modern Organizations. Englewood Cliffs, NJ: Prentice-Hall, 1964.

[FAA 1995a]

Federal Aviation Administration (FAA) Office of Information Technology Integrated Product Team for Information Technology Services. Ch. 6, "The Business Case." Business Process Improvement (Reengineering) Handbook of Standards and Guidelines. Washington, DC: Federal Aviation Administration, 1995.

[Fairley 1994a]

Fairley, R. "Risk Management for Software Projects." IEEE Software 2, 3 (May 1994): 57-67.

[FAR 2005a]

U.S. Federal Regulation Acquisition Agency. Federal Acquisition Regulation. http://www.arnet.gov/far/index.html (2005).

[Faulk 1997a]

Faulk, S. R. "Software Requirements: A Tutorial," 128-149. Software Requirements Engineering. Los Alamitos, CA: IEEE Computer Society Press, 1997.

[Faulk 2000a]

Faulk, S.; Harmon, R.; & Raffo, D. "Value-Based Software Engineering (VBSE): A Value-Driven Approach to Product-Line Engineering," 205-224. Software Product Lines: Proceedings of the First Software Product Line Conference (SPLC1). Denver, Colorado, August 28-31, 2000. Boston, MA: Kluwer Academic Publishers, 2000.

[Favre 2003a]

Favre, Jean-Marie; Estublier, Jacky; & Sanlaville, Remy. "Tool Adoption Issues in a Very Large Software Company," 81-89. ACSE 2003: Third International Workshop on Adoption-Centric Software Engineering (CMU/SEI-2003-SR-004, ADA416604). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2003.

[Finkelstein 1994a]

Finkelstein, A.; Kramer, J.; & Nuseibeh, B. Software Process Modeling and Technology. New York, NY: John Wiley & Sons, 1994.

[Finnegan 1997a]

Finnegan, P.; Holt, R.; Kalas, I.; Kerr, S.; Kontogiannis, K.; Muller, H.; Mylopolous, J.; Perelgut, S.; Stanley, M.; & Wong, K. "The Software Bookshelf." IBM Systems Journal 36, 4 (November 1997): 564-593.

[Fowler 1999a]

Fowler, P.; Middlecoat, B.; & Yo, S. Lessons Learned Collaborating on a Process for SPI at Xerox (CMU/SEI-99-TR-006, ADA373332). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1999.

[Fraunhofer 2006a]

Fraunhofer Institut Experimentelles Software Engineering (IESE). Product Line Architectures. http://www.iese.fraunhofer.de/fhg/Images/CC_PLA_Flyer_e_2006_03_tcm168-62107.pdf (2006).

[Fritsch 2004a]

Fritsch, C. & Hahn, R. "Product Line Potential Analysis," 228-237. Proceedings of the Third Software Product Lines Conference (SPLC 2004) (Lecture Notes in Computer Science volume 3154). Boston, MA, August 30-September 2, 2004. New York, NY: Springer, 2004.

[FSF 2007a]

The Free Software Foundation. The Free Software Foundation Home Page. http://www.fsf.org/ (2007).

[Gaffney 1992a]

Gaffney, J. E. & Cruickshank, R. D. "A General Economics Model of Software Reuse," 327-337. Proceedings of the 14th International Conference on Software Engineering (ICSE). Melbourne, Australia, May 11-15, 1992. New York, NY: ACM, 1992.

[Gallagher 1997a]

Gallagher, B. P.; Alberts, C. J.; & Barbour R. E. Software Acquisition Risk Management Key Process Area (KPA)—A Guidebook V1.0 (CMU/SEI-97-HB-002, ADA328098). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1997.

[Gallagher 1999a]

Gallagher, B. P. Software Acquisition Risk Management Key Process Area (KPA)—A Guidebook Version 1.02 (CMU/SEI-99-HB-001, ADA370385). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1999.

[Gamma 1995a]

Gamma, E.; Helms, R.; Johnson, R.; & Vlissides, J. Design Patterns: Elements of Reusable Object-Oriented Software. Reading, MA: Addison-Wesley, 1995.

[Ganesan 2005a]

Ganesan, D. & Knodel, J. "Identifying Domain-Specific Reusable Components from Existing OO Systems to Support Product Line Migration," 27-36. R2PL 2005-Proceedings of the First International Workshop on Reengineering Towards Product Lines (CMU/SEI-2006-SR-002, ADA448167). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2005.

[Ganesan 2006a]

Ganesan, D.; Muthig, D.; & Yoshimura, K. "Predicting Return-on-Investment for Product Line Generations," 13-22. Proceedings of the 10th International Software Product Lines Conference (SPLC 2006). Baltimore, MD, August 21-24, 2006. Los Alamitos, CA: IEEE Computer Society, 2006.

[Garlan 1995a]

Garlan, D.; Allen, R.; & Ockerbloom, J. "Architectural Mismatch: Why Reuse Is So Hard." IEEE Software 12, 6 (November 1995): 17-26.

[Gelenbe 1999a]

Gelenbe, E, ed. System Performance Evaluation: Methodologies and Applications. Boca Raton, FL: CRC Press, 1999.

[Geppert 2003a]

Geppert, B. & Weiss, D. "Goal-Oriented Assessment of Product-Line Domains," 180-188. Proceedings of the Ninth International Software Metrics Symposium (METRICS'03). Sydney, Australia, September 3-5, 2003. Los Alamitos, CA: IEEE Computer Society, 2003.

[Glass 1998a]

Glass, R. L. Software Runaways: Lessons Learned from Massive Software Project Failures. Upper Saddle River, NJ: Prentice-Hall, 1998.

[Gleick 1987a]

Gleick, J. Chaos: Making a New Science. New York, NY: Penguin Books, 1987.

[Goldberg 1995a]

Goldberg, A. & Rubin, K. S. Succeeding with Objects: Decision Frameworks for Project Management. Reading, MA: Addison-Wesley, 1995.

[Grady 1992a]

Grady, R. B. Practical Software Metrics for Project Management and Process Improvement. Englewood Cliffs, NJ: Prentice-Hall, 1992.

[Grady 1997a]

Grady, R. B. Successful Software Process Improvement. Englewood Cliffs, NJ: Prentice-Hall, 1997.

[Graham 1998a]

Graham, I. Requirements Engineering and Rapid Development: An Object-Oriented Approach. Essex, England: Addison-Wesley, 1998.

[Griss 1994a]

Griss, M. Software Reuse: Objects and Frameworks Are Not Enough (HPL-95-03). Palo Alto, CA: Hewlett-Packard, 1994.
http://www.hpl.hp.com/techreports/95/HPL-95-03.html

[Griss 1998a]

Griss, M. L.; Favaro, J.; & d'Alessandro, M. "Integrating Feature Modeling with the RSEB," 76-85. Proceedings of the Fifth International Conference on Software Reuse. Victoria, B.C., June 2-5, 1998. Los Alamitos, CA: IEEE Computer Society Press, 1998.

[Hammond 1999a]

Hammond, J. S.; Keeney, R. L.; & Raiffa, H. Smart Choices: A Practical Guide to Making Better Decisions. Boston, MA: Harvard Business School Press, 1999.

[Harel 1998a]

Harel, D. & Politi, M. Modeling Reactive Systems with Statecharts: The STATEMATE Approach. Reading, MA: Addison-Wesley, 1998.

[Hofmeister 2000a]

Hofmeister, N. S. Applied Software Architecture. Reading, MA: Addison-Wesley, 2000.

[Hollander 1999a]

Hollander, C. R. & Ohlinger, J. "CCT: A Component-Based Product Line Architecture for Satellite-Based Command and Control Systems," 201-206. Proceedings of the Workshop on Object Technology for Product-Line Architectures. Lisbon, Portugal, June 15, 1999. Bilbao, Spain: European Software Institute, 1999.

[Hotz 2006a]

Hotz, L.; Wolter K.; Krebs, T.; Deelstra, S.; Sinnema, M.; Nijhuis, J.; & MacGregor, J. Configuration in Industrial Product Families - The ConIPF Methodology. Amsterdam, The Netherlands: IOS Press, 2006.

[Huang 2003a]

Y. Huang, I. J. Taylor, D. W. Walker, and R. Davies, "Wrapping Legacy Codes for Grid-Based Applications," 139-145. Proceedings of the 17th International Parallel and Distributed Processing Symposium (Workshop on Java for HPC). Nice, France, April 22-26, 2003. Los Alamitos, CA: IEEE Computer Society, 2003.

[Huff 1996a]

Huff, K. E. "Effect of Product Lines on Current Process Technology," 5-7. Proceedings of the 10th International Software Process Workshop. Dijon, France, June 17-19, 1996. Los Alamitos, CA: IEEE Computer Society, 1996.

[Humphrey 1992a]

Humphrey, W. & Feiler, P. Software Process Development and Enactment: Concepts and Definitions (CMU/SEI-92-TR-004, ADA258465). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1992.

[Humphrey 1995a]

Humphrey, W. A Discipline for Software Engineering. Reading, MA: Addison-Wesley, 1995. (See page 4 for a definition of software process and pages 441-459 for information on process definition.)

[Humphrey 2000a]

Humphrey, W. "Justifying a Process Improvement Proposal." news@SEI interactive 3, 1 (March 2000).

[IEEE 1987a]

Institute of Electrical and Electronics Engineers. IEEE Guide to Software Configuration Management (IEEE Std 1042-1987). New York, NY: Institute of Electrical and Electronics Engineers, 1987.

[IEEE 1990a]

Institute of Electrical and Electronic Engineers. IEEE Standard Glossary of Software Engineering Terminology (IEEE Std 610.12-1990). New York, NY: Institute of Electrical and Electronics Engineers, 1990.

[IEEE 1996a]

Institute of Electrical and Electronics Engineers. IEEE Recommended Practice for the Adoption of Computer-Aided Software Engineering (CASE) Tools (IEEE Std 1348-1995). New York, NY: Institute of Electrical and Electronics Engineers, 1996.

[IEEE 1998a]

Institute of Electrical and Electronics Engineers. Information Technology–Guideline for the Evaluation and Selection of CASE Tools (IEEE Std 1462-1998). New York, NY: Institute of Electrical and Electronics Engineers, 1998.

[IEEE 1998b]

Institute of Electrical and Electronics Engineers. IEEE Guide for Information Technology–Systems Definition–Concept of Operations (CONOPS) Document(IEEE Std 1362-1998). New York, NY: Institute of Electrical and Electronics Engineers, 1998.

[IEEE 2000a]

Institute of Electrical and Electronics Engineers. Recommended Practice for Architectural Description of Software-Intensive Systems (IEEE Std 1471-2000). New York, NY: Institute of Electrical and Electronics Engineers, 2000.

[IEEE 2005a]

Institute of Electrical and Electronics Engineers. IEEE Standard for Software Configuration Management Plans (IEEE Std 828-2005). New York, NY: Institute of Electrical and Electronics Engineers, 2005.

[ISO 1995a]

International Organization for Standardization. Information Technology—Guideline for the Evaluation and Selection of CASE Tools [ISO/IEC 14102:1995(E)]. Geneva, Switzerland: International Organization for Standardization, 1995.

[ISO 1995b]

International Organization for Standardization & International Electrotechnical Commission. Quality Management—Guidelines for Configuration Management [ISO 10007:1995 (E)]. Geneva, Switzerland: International Organization for Standardization/ International Electrotechnical Commission, 1995.

[ISO 2007a]

International Organization for Standardization. International Organization for Standardization Home Page. http://www.iso.org/iso/en/ISOOnline.frontpage (2007).

[Jackson 2000a]

Jackson, M. Problem Frames and Methods: Structuring and Analyzing Software Development Problems. New York, NY: Addison-Wesley, 2000.

[Jacobson 1997a]

Jacobson, I.; Griss, M.; & Jonsson, P. Software Reuse: Architecture, Process, and Organization for Business Success. Reading, MA: Addison-Wesley Longman, 1997.

[Jandourek 1996a]

Jandourek, E. "A Model for Platform Development." Hewlett-Packard Journal 47, 4 (August 1996): 56-71.

[Jansen 2004a]

Jansen, Anton & Bosch, Jan. "Evaluation of Tool Support for Architectural Evolution," 375-378. Proceedings of the 19th IEEE International Conference on Automated Software Engineering (ASE '04). Linz, Austria, September 20-24, 2004. Los Alamitos, CA: IEEE Computer Society Press, 2004.

[John 2006a]

John, I.; Knodel, J.; Lehner, T.; & Muthig, D. "A Practical Guide to Product Line Scoping." Software Product Lines: Proceedings of the 10th International Software Product Line Conference (SPLC 2006). Baltimore, Maryland, August 21-24, 2006. Los Alamitos, CA: IEEE Computer Society, 2006.

[Jones 1996a]

Jones, L. & Northrop, L. "The Establishing Phase: Planning for Successful Improvement." Software Process: Improvement and Practice 2, 1 (March 1996): 51-53.

[Jones 1996b]

Jones, L.; Kasunic, M.; & Ginn, M. "Managing Technology Change: Implementing the SEI's IDEAL Model in a Less Than Ideal World," Track 5 [CD-ROM]. Proceedings of the Eighth Software Technology Conference. Salt Lake City, UT, April 21-26, 1996. Hill AFB, UT: Software Technology Support Center, in cooperation with Utah State University, Continuing Education, 1996.

[Jones 1999a]

Jones, L. & Northrop, L. "Software Process Improvement Planning," 1-24. Proceedings of the European Software Engineering Process Group Conference. Amsterdam, Netherlands, June 7-10, 1999. UK: European Software Process Improvement Foundation, 1999.

[Jones 2002a]

Jones, L. & Soule, A. Software Process Improvement and Product Line Practice: CMMI and the Framework for Software Product Line Practice (CMU/SEI-2002-TN-012, ADA403868). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2002.

[Jones 2004a]

Jones, Lawrence G. Software Process Improvement and Product Line Practice: Building on Your Process Improvement Infrastructure (CMU/SEI-2004-TN-044, ADA431119). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2004.

[Jones 2005a]

Jones, L. & Northrop, L. Software Product Line Adoption in a CMMI Environment (CMU/SEI-2005-TN-028, ADA441309). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2005.

[Kang 1990a]

Kang, K.; Cohen, S.; Hess, J.; Novak, W.; & Peterson, A. Feature-Oriented Domain Analysis (FODA) Feasibility Study (CMU/SEI-90-TR-021, ADA235785). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1990.

[Kang 1998a]

Kang, K.; Kim, S.; Lee, J.; Shin, E.; & Huh, M. "FORM: A Feature-Oriented Reuse Method with Domain-Specific Reference Architectures." Annals of Software Engineering 5, 5 (September 1998): 143-168.

[Kang 2002a]

Kang, K.; Lee, J.; & Donohoe, P. "Feature-Oriented Product Line Engineering." IEEE Software 19, 4 (July/August 2002): 58-65.

[Karlsson 1995a]

Karlsson, E., ed. Software Reuse: A Holistic Approach. Chichester, England: John Wiley & Sons, 1995.

[Kasse 2002a]

Kasse, T. Action Focused Assessment for Software Process Improvement. Norwood, MA: Artech House, 2002.

[Kazman 1998a]

Kazman, R.; Klein, M.; Barbacci, M.; Lipson, H.; Longstaff, T.; & Carrière, S. J. "The Architecture Tradeoff Analysis Method," 68-78. Proceedings of the ICECCS. Monterey, CA, August 10-14, 1998. Los Alamitos, CA: IEEE Computer Society Press, 1998.

[Kazman 1999a]

Kazman, R.; Barbacci, M.; Klein, M.; Carrière, S. J.; & Woods, S. G. "Experience with Performing Architecture Tradeoff Analysis," 54-63. Proceedings of the 21st International Conference on Software Engineering (ICSE). Los Angeles, CA, May 16-20, 1999. New York, NY: ACM, 1999.

[Kazman 2000a]

Kazman, R.; Klein, M.; & Clements, P. ATAM: Method for Architecture Evaluation (CMU/SEI-2000-TR-004, ADA382629). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2000.

[Kazman 2002a]

Kazman, R.; O'Brien, L.; & Verhoef, C. Architecture Reconstruction Guidelines, Third Edition (CMU/SEI-2002-TR-034, ADA412306). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2003.

[Kenwood 2001a]

Kenwood, Carolyn A. A Business Case Study of Open Source Software. http://www.mitre.org/work/tech_papers/tech_papers_01/kenwood_software/index.html (2001).

[Keuffel 1999a]

Keuffel, W. "Planning for and Mitigating Risk." Software Development 7, 9 (September 1999): S1-S5.

[Kirkpatrick 1992a]

Kirkpatrick, R. J.; Walker, J. A.; & Firth, R. "Software Development Risk Management: An SEI Appraisal," 1-28. Software Engineering Institute Technical Review '92 (CMU/SEI-92-REV). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1992.

[Klein 1999a]

Klein, M.; Kazman, R.; Bass, L.; Carriere, J., Barbacci, M.; & Lipson, H. "Attribute-Based Architecture Styles," 225-243. Proceedings of the First Working IFIP Conference on Software Architecture (WICSA1). San Antonio, TX, February 22-24, 1999. Boston, MA: Kluwer Academic Publishers, 1999.

[Knauber 2000a]

Knauber, P.; Muthig, D.; Schmid, K.; & Widen, T. "Applying Product Line Concepts in Small and Medium-Sized Companies." IEEE Software 17, 5 (September/October 2000): 88-95.

[Knodel 2005a]

Knodel, J. & Muthig, D. "Analyzing the Produce Line Adequacy of Existing Components", 37-45. R2PL 2005-Proceedings of the First International Workshop on Reengineering Towards Product Lines (CMU/SEI-2006-SR-002, ADA448167). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2005.

[Kotonya 1996a]

Kotonya, G. & Sommerville, I. "Requirements Engineering with Viewpoints," 150-163. Software Requirements Engineering, Second Edition. Los Alamitos, CA: IEEE Computer Society Press, 1996.

[Krasner 1988a]

Krasner, G. E. & Pope, S. T. "A Cookbook for Using the Model-View-Controller User Interface Paradigm in Smalltalk-80." Journal of Object-Oriented Programming 1, 3 (August/September 1988): 26-49.

[Kruchten 1998a]

Kruchten, P. The Rational Unified Process: An Introduction. Reading, MA: Addison-Wesley, 1998.

[Kruchten 2004a]

Kruchten, Philipe. The Rational Unified Process: An Introduction, Third Edition. Boston, MA: Addison-Wesley, 2004.

[Krueger 2001a]

Krueger, C. "Easing the Transition to Software Mass Customization," 282-293. Proceedings of the 4th International Workshop on Software Product Family Engineering. Bilbao, Spain, October 3-5, 2001. New York, NY: Springer, 2001.

[Krueger 2002a]

Krueger, Charles W. "Variation Management for Software Production Lines," 37-48. Software Product Lines: Proceedings of the Second Software Product Line Conference (SPLC2). San Diego, CA, August 19-22, 2002. Berlin, Germany: Springer, 2002.

[Krut 96]

Krut, R. & Zalman, N. Domain Analysis Workshop Report for the Automated Prompt and Response System Domain (CMU/SEI-96-SR-001, ADA311456). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1996.

[Kuusela 2000a]

Kuusela, J. & Savolainen, J. "Requirements Engineering for Product Families," 61-69. Proceedings of the 22nd International Conference on Software Engineering (ICSE). Limerick, Ireland, June 4-11, 2000. New York, NY: ACM, 2000.

[Lee 2000a]

Lee, K.; Kang, K.; Koh, E.; Chae, W.; Kim, B.; & Choi, B. "Domain-Oriented Engineering of Elevator Control Software," 3-22. Software Product Lines: Proceedings of the First Software Product Line Conference (SPLC1). Denver, Colorado, August 28-31, 2000. Boston, MA: Kluwer Academic Publishers, 2000.

[Leon 2005a]

Leon, Alexis. Software Configuration Management Handbook, Second Edition. Norwood, MA: Artech House, Inc., 2005.

[Lim 1998a]

Lim, W. C. Managing Software Reuse: A Comprehensive Guide to Strategically Reengineering the Organization for Reusable Components. Upper Saddle River, NJ: Prentice-Hall PTR, 1998.

[Lewis 2005a]

Lewis, G.; Morris, E.; O'Brien, L.; Smith, D.; & Wrage, L. SMART: The Service-Oriented Migration and Reuse Technique (CMU/SEI-2005-TN-029, ADA441900). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2005.

[Livesey 1997a]

Livesey, D. & Guinane, T. Developing Object-Oriented Software: An Experience-Based Approach. Upper Saddle River, NJ: Prentice-Hall, 1997.

[Loveland-Link 1999a]

Loveland-Link, J.; Barbour, R.; Krum, A.; & Neitzel, A. Rollout and Installation of Risk Management at the IMINT Directorate, National Reconnaissance Office (CMU/SEI-99-TR-009, ADA375848). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1999.

[Low 1999a]

Low, G. & Leenanuraksa, V. "Software Quality and CASE Tools," 142-150. Proceedings of the Ninth International Workshop on Software Technology and Engineering Practice (STEP '99). Pittsburgh, PA, August 30-September 2, 1999. Los Alamitos, CA: IEEE Computer Society Press, 1999.

[Lundell 2004a]

Lundell, Björn & Lings, Brian. "Changing Perceptions of CASE Technology." The Journal of Systems and Software 72, 2 (2004): 271-280.

[Maccari 2000a]

Maccari, Alessandro & Riva, Claudio. "Empirical Evaluation of CASE Tools Usage at Nokia." Empirical Software Engineering 5, 3 (November 2000): 287-299.

[Maccari 2002a]

Maccari, Alessandro; Riva, Claudio; & Maccari, Francesco. "On CASE Tool Usage at Nokia," 59-68. Proceedings of the 17th IEEE International Conference on Automated Software Engineering (ASE '02). Edinburgh, UK, September 23-27, 2002. Washington, DC: IEEE Computer Society Press, 2002.

[Marttiin 1998a]

Marttiin, P. & Koskinen, M. Similarities And Differences of Method Engineering and Process Engineering Approaches. http://citeseer.ist.psu.edu/marttiin98similarities.html (1998).

[McAndrews 1993a]

McAndrews, D. R. Establishing a Software Measurement Process (CMU/SEI-93-TR-016, ADA267896). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1993.

[McDonald 1995a]

McDonald, M. & Dunbar, I. Market Segmentation: A Step-by-Step Approach to Creating Profitable Market Segments. Basingstoke, England: Macmillan Business, 1995.

[McFeeley 1996a]

McFeeley, R. IDEAL: A User's Guide for Software Process Improvement (CMU/SEI-96-HB-001, ADA305472). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1996.

[McGregor 1999a]

McGregor, J. D. "Validating Domain Models." Journal of Object-Oriented Programming 12, 4 (July/August 1999): 12-17.

[McGregor 2001a]

McGregor, J. D. Testing a Software Product Line (CMU/SEI-2001-TR-022, ADA401736). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2001.

[McGregor 2002a]

McGregor, J. D. "Building Reusable Test Assets for a Product Line," 345-6. Proceedings of the 7th International ICSR Conference. Austin, TX, April 15-19, 2002. Berlin, Germany: Springer, 2002.

[McGregor 2005a]

McGregor, J. D. Arcade Game Maker Pedagogical Product Line: Concept of Operations, Version 2.0. (2005).

[McGregor 2005b]

McGregor, J. Preparing for Automated Derivation of Products in a Software Product Line (CMU/SEI-2005-TR-017, ADA448223). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2005.

[Meyer 1997a]

Meyer, M. H. & Lehnerd, A. P. The Power of Product Platforms: Building Value and Cost Leadership. New York, NY: The Free Press, 1997.

[Microsoft 2007a]

Microsoft Corporation. Microsoft Home Page. http://www.microsoft.com/en/us/default.aspx (2007).

[Mockus 1999a]

Mockus, A. & Siy, H. "Measuring Domain Engineering Effects on Software Change Cost," 304-311. Proceedings of Metrics 99: Sixth International Symposium on Software Metrics. Boca Raton, FL, November 4-6, 1999. New York, NY: IEEE Computer Society Press, 1999.

[Moore 1991a]

Moore, G. A. Crossing the Chasm, Marketing and Selling Technology Products to Mainstream Customers. New York, NY: Harper Business Publishing, 1991.

[Morris 1993a]

Morris, C. & Ferguson, C. "How Architecture Wins Technology Wars." Harvard Business Review 71, 2 (March-April 1993): 86-96.

[Moszkowski 1986a]

Moszkowski, B. Executing Temporal Logic Programs. New York, NY: Cambridge University Press, 1986.

[Muller 1988a]

Muller, H. & Klashinsky, K. "Rigi-A System for Programming-in-the Large," 80-86. Proceedings of the 10th International Conference on Software Engineering (ICSE). Raffles City, Singapore, April 11-15, 1988. New York, NY: IEEE Computer Society Press, April 1988.

[Muller 2000a]

Muller, H.; Jahnke, J.; Smith, D.; Storey, M.; Tilley, S.; & Wong, K. "Reverse Engineering: A Roadmap," 47-60. The Future of Software Engineering. Proceedings of the 22nd International Conference on Software Engineering. Limerick, Ireland, June 4-11, 2000. New York, NY: ACM, 2000.

[Muller 2003a]

Muller, H.; Weber, A.; & Wong, K. "Leveraging Cognitive Support and Modern Platforms for Adoption-Centric Reverse Engineering (ACRE)," 30-35. Third International Workshop on Adoption-Centric Software Engineering (CMU/SEI-2003-SR-004). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2003.

[Musa 1999a]

Musa, J. Software Reliability Engineering. New York, NY: McGraw-Hill, 1999.

[Newell 1972a]

Newell, A. & Simon, H. A. Human Problem Solving. Englewood Cliffs, NJ: Prentice-Hall, 1972.

[Northrop 2004a]

Northrop, Linda. Software Product Line Adoption Roadmap (CMU/SEI-2004-TR-022, ADA431117). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2004.

[O'Brien 2001a]

O'Brien, L. & Stoermer, C. "MAP-Mining Architectures for Product Line Evaluations," 35-44. Proceedings of the Third Working IEEE/IFIP Conference on Software Architecture (WICSA1). Amsterdam, Netherlands, August 28-31, 2001. Los Alamitos, CA: IEEE Computer Society, 2001.

[O'Brien 2002a]

O'Brien, L.; Stoermer, C.; & Verhoef, C. Software Architecture Reconstruction: Practice Needs and Current Approaches (CMU/SEI-2002-TR-024, ADA407795). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2002.

[O'Brien 2003a]

O'Brien, L. & Stoermer, C. Architecture Reconstruction Case Study (CMU/SEI-2003-TN-008, ADA413856). Pittsburgh, PA: Engineering Institute, Carnegie Mellon University, 2003.

[O'Brien 2005a]

O'Brien, L.; Bass, L.; & Merson, P. Quality Attributes and Service-Oriented Architectures (CMU/SEI-2005-TN-014, ADA441830). Pittsburgh, PA: Engineering Institute, Carnegie Mellon University, 2005.

[Oberndorf 1998a]

Oberndorf, P. COTS and Open Systems. SEI Monographs on the Use of Commercial Software in Government Systems. Pittsburgh, PA: Software Engineering, Carnegie Mellon University, 1998.

[Ohlinger 2000a]

Ohlinger, J. CCT Lessons Learned: What We Did, Why We Did It, and What We Would Do Differently.
http://sunset.usc.edu/GSAW/GSAW2000/pdf/Ohlinger.pdf (2000).

[OMG 1996a]

Object Management Group. The Common Object Request Broker: Architecture and Specification, Revision 2.0 (97-02-25). Needham, MA: Object Management Group, Inc., 1996.

[OMG 2005a]

Object Management Group. Software Process Engineering Metamodel Version 1.1.
http://www.omg.org/technology/documents/formal/spem.htm (January 2005).

[OMG 2007a]

Object Management Group. UML Resource Page.
http://www.uml.org (2007).

[OSI 2007a]

The Open Source Initiative. Open Source Home Page.
http://www.opensource.org/ (2007).

[Ossher 2000a]

Ossher, Harold; Harrison, William; & Tarr, Perri. "Software Engineering Tools and Environments: A Roadmap," 261-277. Proceedings of the Conference on the Future of Software Engineering. Limerick, Ireland, June 4-11, 2000. New York, NY: ACM, 2000.

[Osterweil 1987a]

Osterweil, L. "Software Processes Are Software Too," 2-13. Proceedings of the 9th International Conference on Software Engineering (ICSE). Monterey, CA, March 30-April 2, 1987. New York, NY: IEEE Computer Society Press, 1987.

[Park 1996a]

Park, R. E.; Goethert, W. B.; & Florac, W. A. Goal-Driven Software Measurement—A Guidebook (CMU/SEI-96-HB-002, ADA313946). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1996.

[Parnas 1972a]

Parnas, D. "Information Distribution Aspects of Design Methodology," 339-344. Proceedings of the 1971 IFIP Congress. Ljubljana, Yugoslavia, August 23-28, 1971. Amsterdam, Netherlands: North-Holland Publishing Company, 1972.

[Parnas 2001a]

Parnas, D. & Weiss, D. "Active Design Reviews: Principles and Practices," 132-136. Weiss, D. & Hoffman, D., eds. Software Fundamentals: Collected Papers by David L. Parnas. Reading, MA: Addison-Wesley, 2001.

[Paulk 1993a]

Paulk, M.; Weber, C. V.; Garcia, S. M; Chrissis, M.; & Bush, M. Key Practices of the Capability Maturity Model, Version 1.1 (CMU/SEI-93-TR-025, ADA263432). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1993.

[Paulk 1995a]

Paulk, M. C.; Weber, C. V.; Curtis, B.; & Chrissis, M. B. The Capability Maturity Model: Guidelines for Improving the Software Process. Reading, MA: Addison-Wesley, 1995.

[Peterson 1991a]

Peterson, A. S. & Cohen, S. G. A Context Analysis of the Movement Control Domain for the Army Tactical Command and Control System (ATCCS) (CMU/SEI-91-SR-003, ADA248117). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1991.

[Porter 1980a]

Porter, M. Competitive Strategy. New York, NY: The Free Press, 1980.

[Poulin 1997a]

Poulin, J. S. Measuring Software Reuse: Principles, Practices, and Economic Models. Reading, MA: Addison-Wesley, 1997.

[Poulin 1997b]

Poulin, J. S. "The Economics of Software Product Lines." International Journal of Applied Software Technology 3, 1 (March 1997): 20-34.

[Powell 1996a]

Powell, A.; Vickers, A.; Williams, E.; & Cooke, B. Ch. 11, "A Practical Strategy for the Evaluation of Software Tools," 165-185. Method Engineering: Principles of Method Construction and Tool Support–Proceedings of the IFIP TC8, WG8.1/8.2 Working Conference on Method Engineering. Atlanta, GA, August 26-28, 1996. London, UK: Chapman & Hall, 1996.

[Prahalad 1990a]

Prahalad, C. & Hamel, G. "The Core Competency of the Corporation." Harvard Business Review 68, 3 (May-June 1990): 79-92.

[Pressman 1998a]

Pressman, R. Software Engineering: A Practitioner's Approach, Fifth Edition. New York, NY: McGraw-Hill Book Company, 1998.

[Prieto-Diaz 1991a]

Prieto-Diaz, R. & Arango, G. Domain Analysis and Software Systems Modeling. Los Alamitos, CA: IEEE Computer Society Press, 1991.

[Pronk 2000a]

Pronk, B. J. "An Interface-Based Platform Approach," 331-352. Software Product Lines: Proceedings of the First Software Product Line Conference (SPLC1). Denver, Colorado, August 28-31, 2000. Boston, MA: Kluwer Academic Publishers, 2000.

[Radice 1994a]

Radice, R. & Garcia, S. "Tutorial 4: Upgraded Integrated Process/TQM Tools: An Integrated Approach to Software Process Improvement," The Sixth Annual Software Technology Conference Papers [CD-ROM]. Salt Lake City, Utah, April 11-14, 1994. Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1994.

[Ramesh 1997a]

Ramesh, B.; Stubbs, C.; Powers, T.; & Edwards, M. "Requirements Traceability: Theory and Practice." Annals of Software Engineering 3, 3 (September 1997): 397-415.

[Reifer 1997a]

Reifer, D. J. Practical Software Reuse: Strategies for Introducing Reuse Concepts in Your Organization. New York, NY: John Wiley & Sons, 1997.

[Robertson 1998a]

Robertson, D. & Ulrich, K. "Planning for Product Platforms." Sloan Management Review 39, 4 (Summer 1998): 19-31.

[Rolland 1997a]

Rolland, C. A Primer For Method Engineering.
http://citeseer.ist.psu.edu/cache/papers/cs/29244/
ftp:zSzzSzsunsite.informatik.rwth-aachen.dezSzpubzSzCREWSzSzCREWS-97-06.pdf/
rolland97primer.pdf (1997).

[Ryans 2000a]

Ryans, A.; More, R.; Barclay, D.; & Deutscher, T. Winning Market Leadership: Strategic Market Planning for Technology-Driven Businesses. New York, NY: John Wiley & Sons, 2000.

[Schmid 2000a]

Schmid, Klaus. "Scoping Software Product Lines," 513-532. Proceedings of the First Software Product Line Conference (SPLC1). Denver, Colorado, August 28-31, 2000. Boston, MA: Kluwer Academic Publishers, 2000.

[Schmid 2001a]

Schmid, Klaus; Thiel, Steffen; Bosch, Jan; Johnsson, Susanne; Jaring, Michel; Thomé, Bernhard; & Trosch, Siegfried. Scoping.
http://www.esi.es/esaps/public-pdf/CWD124-08-06-01.pdf (June 8, 2001).

[Schmid 2005a]

Schmid, K.; Krennrich, K.; & Eisenbarth, M. Requirements Management for Product Lines: A Prototype (IESE-Report 061.05/E).
http://publica.fraunhofer.de/eprints/N-31550.pdf (2005).

[Schmid 2006a]

Schmid, K.; Krennrich, K.; & Eisenbarth, M. "Requirements Management for Product Lines: Extending Professional Tools," 113-122. Proceedings of the Tenth International Software Product Line Conference (SPLC 06). Baltimore, Maryland, August 21-34, 2006. Los Alamitos, CA: IEEE Computer Society, 2006.

[Schmidt 2000a]

Schmidt, Douglas; Stal, Michael; Rohnert, Hans; & Buschmann, Frank. Pattern-Oriented Software Architecture, Volume 2, Patterns for Concurrent and Networked Objects. New York, NY: Wiley, September 2000.
http://www.wiley.com/WileyCDA/WileyTitle/productCd-0471606952.html

[Schmidt 2003a]

Schmidt, M. J. What's a Business Case? And Other Frequently Asked Questions.
http://www.solutionmatrix.com/downloads/Whats_a_Business_Case.pdf (2003).

[Schnell 1996a]

Schnell, K.; Zalman, N.; & Bhatt, A. Transitioning Domain Analysis: An Industry Experience (CMU/SEI-96-TR-009, ADA310918). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1996.

[Schwaber 2005a]

Schwaber, Carey with the assistance of Barnett, Liz; Friedlander, David; & Hogan, Lindsey. The Expanding Purview of Software Configuration Management. Cambridge, MA: Forrester Research, Inc.

http://www.forrester.com/Research/Document/Excerpt/0,7211,36337,00.html (2005).

[Seacord 2001a]

Seacord, R.; Comella-Dorda, S.; Lewis, G.; Place, P.; & Plakosh, D. Legacy System Modernization Strategies (CMU/SEI-2001-TR-025, ADA396051). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2001.

[Seacord 2003a]

Seacord R., Plakosh D., Lewis G. A. Modernizing Legacy Systems: Software Technologies, Engineering Processes, and Business Practices. Boston, MA: Addison-Wesley, 2003 (ISBN 0-321-11884-7).

[SEI 1995a]

Software Engineering Institute. The Capability Maturity Model: Guidelines for Improving the Software Process. Reading, MA: Addison-Wesley, 1995.

[SEI 2000a]

Software Engineering Institute. Capability Maturity Model Integration, Version 1.1 CMMI for Systems Engineering and Software Engineering (CMMI-SE/SW, V1.1) (CMU/SEI-2000-TR-018, ADA388775). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2000.

[SEI 2006a]

Software Engineering Institute. CMMI® for Development, Version 1.2 CMMI-DEV, V1.2 (CMU/SEI-2006-TR-008, ADA455858). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2006.

[SEI 2007a]

Software Engineering Institute. Attribute-Driven Design Method (2007).

[SEI 2007b]

Software Engineering Institute. Software Architecture for Software-Intensive Systems (2007).

[SEI 2007c]

Software Engineering Institute. COTS-Based Systems (CBS) Initiative (2007).

[SEI 2007d]

Software Engineering Institute. Product Line Analysis (2007).

[SEI 2007e]

Software Engineering Institute. Product Line Technical Probe (2007).

[SEI 2007f]

Software Engineering Institute. Reengineering (2007).

[SEI 2007g]

Software Engineering Institute. Quality Attribute Workshops (2007).

[SEI 2007h]

Software Engineering Institute. Economics of Software Product Lines (2007).

[SEI 2007i]

Software Engineering Institute. Software and Systems Process Improvement Networks (SPINs) (2007).

[Shaw 1996a]

Shaw, M. & Garlan, D. Software Architecture: Perspectives on an Emerging Discipline. Englewood Cliffs, NJ: Prentice-Hall, 1996.

[Shaw 2000a]

Shaw, J. Control Channel Toolkit: Open Architecture-Based Product Line Development
http://sunset.usc.edu/GSAW/GSAW2000/pdf/shaw.pdf (2000).

[Sheard 1997a]

Sheard, S. "The Frameworks Quagmire." Crosstalk 10, 9.
http://www.stsc.hill.af.mil/crosstalk/frames.asp?uri=1997/09/frameworks.asp (September 1997).

[Shehata 2002a]

Shehata, M.; Eberlein, A.; & Hoover, J. Requirements Reuse and Feature Interaction Management.
http://www2.enel.ucalgary.ca/People/eberlein/publications/FI_ICSSEA2002.pdf (2002).

[Six Sigma 2007a]

iSixSigma. Six Sigma Home Page.
http://www.isixsigma.com/ (2007).

[Smith 1990a]

Smith, C. Performance Engineering of Software Systems. Reading, MA: Addison-Wesley, 1990.

[Smith 2001a]

Smith, C. & Williams, L. Software Performance Engineering for Object-Oriented Systems. Reading, MA: Addison-Wesley, 2001.

[Smith 2002a]

Smith, D.; O'Brien, L.; & Bergey, J. "Using the Options Analysis for Reengineering (OAR) Method for Mining Components for a Product Line," 316-327. Software Product Lines: Proceedings of the Second Software Product Line Conference (SPLC2). San Diego, CA, August 19-22, 2002. Berlin, Germany: Springer, 2002.

[Sneed 2001a]

Sneed, H. M. "Recycling Software Components Extracted From Legacy Programs," 43-51. Proceedings of the 4th International Workshop on Principles of Software Evolution. Vienna, Austria, September 10-11, 2001. New York, NY: ACM Press, 2001.

[Sommerville 1997a]

Sommerville, I. & Sawyer, P. Requirements Engineering: A Good Practice Guide. New York, NY: John Wiley & Sons, 1997.

[Soni 1995a]

Soni, D.; Nord, R. R.; & Hofmeister, C. "Software Architecture in Industrial Applications," 196-207. Proceedings of the 17th International Conference on Software Engineering (ICSE). Seattle, Washington, April 23-30, 1995. New York, NY: Association for Computing Machinery Press, 1995.

[SPC 1993a]

Software Productivity Consortium. Reuse Adoption Guidebook (SPC-92051-CMC, Version 02.00.05). Herndon, VA: Software Productivity Consortium, 1993.

[SPC 1993b]

Software Productivity Consortium. Reuse-Driven Software Processes Guidebook (SPC-92019-CMC, Version 02.00.03). Herndon, VA: Software Productivity Consortium, 1993.

[SPLiT 2004a]

International Workshop on Software Product Line Testing. SPLiT Proceedings and Presentations.
http://www.biglever.com/split2004/presentations.html (2004).

[SPLiT 2005a]

Second International Workshop on Software Product Line Testing. SPLiT Proceedings and Presentations.
http://www.biglever.com/split2005/presentations.html (2005).

[STARS 1996a]

Software Technology for Adaptable Reliable Systems (STARS). Organization Domain Modeling (ODM) Guidebook Version 2.0 (STARS-VC-A025/001/00). Manassas, VA: Lockheed Martin Tactical Defense Systems, 1996.

[Sun 2007a]

Sun Microsystems, Inc. Sun Microsystems Home Page.
http://www.sun.com/ (2007).

[Svahnberg 2000a]

Svahnberg, M. & Bosch, J. "Issues Concerning Variability in Software Product Lines," 50-60. Proceedings of the Third International Workshop on Software Architectures for Product Families. Las Palmas de Gran Canaria, Spain, March 15-17, 2000. Berlin, Germany: Springer, 2000.

[Szyperski 2002a]

Szyperski, C. Component Software: Beyond Object-Oriented Programming, 2nd ed.. Boston, MA: Addison-Wesley, 2002.

[Thiel 2000a]

Thiel, S. & Peruzzi, F. "Starting a Product Line Approach for an Envisioned Market: Research and Experience in an Industrial Environment," 495-512. Software Product Lines: Proceedings of the First Software Product Line Conference (SPLC1). Denver, Colorado, August 28-31, 2000. Boston, MA: Kluwer Academic Publishers, 2000.

[Tichy 1989a]

Ticky, N. & Charan, R. "Speed, Simplicity, Self-Confidence: An Interview with Jack Welch." Harvard Business Review 67, 5 (September-October 1989): 112-120.

[Tilley 1997a]

Tilley, S. R. Discovering DISCOVER (CMU/SEI-97-TR-012, ADA331014). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1997.

[Tilley 1998a]

Tilley, S. R. A Reverse-Engineering Environment Framework (CMU/SEI-98-TR-005, ADA343688). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1998.

[Toft 2000a]

Toft, P.; Coleman, D.; & Ohta, J. "A Cooperative Model for Cross-Divisional Product Development for a Software Product Line," 111-132. Software Product Lines: Proceedings of the First Software Product Line Conference (SPLC1). Denver, Colorado, August 28-31, 2000. Boston, MA: Kluwer Academic Publishers, 2000.

[Tolvanen 2005a]

Tolvanen, Juha-Pekka & Kelly, Steven. "Defining Domain-Specific Modeling Languages to Automate Product Derivation: Collected Experiences," 198-209. Proceedings of the Ninth International Software Produce Lines Conference (SPLC 2005). Rennes, France, September 26-29, 2005. New York, NY: Springer, 2005.

[Tompkins 2004a]

Tompkins, J. 40 Risks to Establishing an Outsourcing Relationship.
http://www.tompkinsinc.com/operations/info/40_Outsourcing_Risks.pdf (2004).

[Tracz 1995a]

Tracz, W. Confessions of a Used Program Salesman: Institutionalizing Software Reuse. New York, NY: Addison-Wesley, 1995.

[Tracz 1988a]

Tracz, W. "RMISE Workshop on Software Reuse Meeting Summary," 41-53. Software Reuse: Emerging Technology. Washington, DC: Computer Society Press, 1988.

[TreeAge 1999a]

TreeAge Software, Inc. DATA Interactive White Paper.
http://server.treeage.com/objdocs/start/whitepaper.php3 (1999).

[Ulrich 2002a]

Ulrich, W. M. Legacy Systems: Transformation Strategies. Upper Saddle River, NJ: Prentice Hall, 2002 (ISBN 0-13-044927-X).

[Van Zyl 2000a]

Van Zyl, J. & Walker, A. J. "Strategic Product Development: A Strategic Approach to Taking Software Products to Market Successfully," 86-111. Software Product Lines: Proceedings of the First Software Product Line Conference (SPLC1). Denver, Colorado, August 28-31, 2000. Boston, MA: Kluwer Academic Publishers, 2000.

[Vollman 1994a]

Vollman, T. "Standards Support for Software Tool Quality Assessment," 29-39. Proceedings of the Third Symposium on Assessment of Quality Software Development Tools. Washington, DC, June 7-9, 1994. Los Alamitos, CA: IEEE Computer Society Press, 1994.

[Vu 2000a]

Vu, J. "Findings of the Managing Software Innovation and Technology Change Workshop: Managing Technology Transfer" [CD-ROM]. Proceedings of the Software Engineering Process Group (SEPG) 2000. Seattle, WA, March 20-23, 2000. Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2000.

[Wallnau 1997a]

Wallnau, K.; Weiderman, N.; & Northrop, L. Distributed Object Technology with CORBA and Java: Key Concepts and Implications (CMU/SEI-97-TR-004, ADA327035). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1997.

[Wallnau 2002a]

Wallanu, Kurt; Hissam, Scott A.; & Seacord, Robert C. Building Systems from Commercial Components. Upper Saddle River, NJ: Addison-Wesley, 2002.

[Walrad 2002a]

Walrad, Chuck & Strom, Darrel. "The Importance of Branching Models in SCM." IEEE Computer 35, 9 (September 2002): 31-38.

[Wappler 2000a]

Wappler, T. "Remember the Basics: Key Success Factors for Launching and Institutionalizing a Software Product Line," 73-84. Software Product Lines: Proceedings of the First Software Product Line Conference (SPLC1). Denver, Colorado, August 28-31, 2000. Boston, MA: Kluwer Academic Publishers, 2000.

[Wartik 1992a]

Wartik, S. & Prieto-Diaz, R. "Criteria for Comparing Reuse-Oriented Domain Analysis Approaches." International Journal of Software Engineering and Knowledge Engineering 2, 3 (September 1992): 403-431.

[Weiderman 1997a]

Weiderman, N.; Northrop, L.; Smith, D.; Tilley, S.; & Wallnau, K. Implications of Distributed Object Technology for Reengineering (CMU/SEI-97-TR-005, ADA326945). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1997.

[Weiss 1999a]

Weiss, D. M. & Lai, C. T. R. Software Product-Line Engineering: A Family-Based Software Development Process. Reading, MA: Addison-Wesley, 1999.

[Westfechtel 2003a]

Westfechtel, Bernhard & Conradi, Reidar. "Software Architecture and Software Configuration Management," 24-39. Proceedings of the ICSE Workshops SCM 2001 and SCM 2003: Selected Papers. van der Hoek, A. & Westfechtel, B., eds. Lecture Notes in Computer Science Volume 2649. Berlin, Germany: Springer-Verlag, 2003.

[Wheeler 2005a]

Wheeler, David A. Why Open Source Software/Free Software (OSS/FS, FLOSS, or FOSS)? Look at the Numbers!
http://www.dwheeler.com/oss_fs_why.html (2005).

[Wijnstra 2000a]

Wijnstra J. "Supporting Diversity with Component Frameworks as Architectural Elements," 50-59. Proceedings of the 22nd International Conference on Software Engineering (ICSE). Limerick, Ireland, June 4-11, 2000. New York, NY: ACM, 2000.

[Wikipedia 2007a]

Wikipedia. Agile Software Development.
http://en.wikipedia.org/wiki/Agile_software_development (2007).

[Williams 1999a]

Williams, R.; Pandelios, G.; & Behrens, S. Software Risk Evaluation (SRE) Method Description (Version 2.0) & SRE Team Members Notebook (Version 2.0) (CMU/SEI-99-TR-029, ADA001008). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1999.

[Wingerd 2005a]

Wingerd, Laura & Seiwald, Christopher. High-Level Best Practices in Software Configuration Management.
http://www.perforce.com/perforce/bestpractices.html (2005).

[Withey 1996a]

Withey, J. Investment Analysis of Software Assets for Product Lines (CMU/SEI-96-TR-010, ADA315653). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1996.

[Woods 1999a]

Woods, S. G.; Carriere, S. J.; & Kazman, R. "A Semantic Foundation for Architectural Reengineering," 391-398. Proceedings of the ICSM99. Oxford, UK, August 30 - September 3, 1999. Oxford, UK: Oxford Press, 1999.

[Yacoub 2000a]

Yacoub, S.; Mili, A.; Kaveri, C.; & Dehlin, M. "A Hierarchy of COTS Certification Criteria," 397-412. Software Product Lines: Proceedings of the First Software Product Line Conference (SPLC1). Denver, Colorado, August 28-31, 2000. Boston, MA: Kluwer Academic Publishers, 2000.

[Zahran 1998a]

Zahran, Sami. Software Process Improvement : Practical Guidelines for Business Success. Reading, MA: Addison-Wesley, 1998 (ISBN 0-201-17782-X).

[Zhang 2005a]

Zhang, Weishan & Jarzabek, Stan. "Reuse Without Compromising Performance: Industrial Experience from RPG Software Product Line for Mobile Devices," 57-69. Proceedings of Software Product Lines: Ninth International Conference. Rennes, France, September 26-29, 2005. New York, NY: Springer, 2005.

[Zhao 1999a]

Zhao, J. "Bibliography on Software Architecture Analysis." Software Engineering Notes 24, 3 (May 1999): 61-62.

[Zona 1999a]

Zona Research, Inc. Enterprise JavaBeans Technology, a Business Benefits Analysis. (1999).
http://java.sun.com/products/ejb/pdf/zona.pdf

[Zubrow 2003a]

Zubrow, Dave & Chastek, Gary. Measures for Software Product Lines (CMU/SEI-2003-TN-031). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2003.

Table of Contents Previous Section