Estimating Systems Engineering Reuse

Systems engineering reuse is the utilization of previously developed systems engineering products or artifacts such as architectures, requirements, and test plans across different projects. Such reuse is intended as a means of reducing development cost, project schedule, or performance risk, by avoiding the repetition of some systems engineering activities. Although projects involving systems engineering reuse are becoming more frequent, models or tools for estimating the cost, benefit, and overall impact on a project as a result of reusing products or artifacts have not yet been adequately developed. This paper provides an overview of systems engineering reuse and recent developments with the Constructive Systems Engineering Cost Model (COSYSMO) to estimate the effect of reuse on systems engineering effort. The overview of systems engineering reuse includes a review of how reuse is handled in other domains and results from an industry survey. The recent developments in COSYSMO presents on-going research in the creation of a reuse extension for the model such as the identification of categories of systems engineering reuse, reuse extensions for the size drivers in the model, and a revised set of cost drivers.

[1]  Martin Loomes,et al.  Re-engineering for reuse: a paradigm for evolving complex reuse artefacts , 1998, Proceedings. The Twenty-Second Annual International Computer Software and Applications Conference (Compsac '98) (Cat. No.98CB 36241).

[2]  John A. McDermid,et al.  Ten steps towards systematic requirements reuse , 2008, Requirements Engineering.

[3]  Charles W. Krueger,et al.  Software reuse , 1992, CSUR.

[4]  Richard Selby,et al.  Software Reuse in Large-Scale Systems , 2005 .

[5]  Sadahiro Isoda,et al.  Software reuse in Japan , 1996, Inf. Softw. Technol..

[6]  Wayne C. Lim Managing Software Reuse , 2004 .

[7]  Wing Lam,et al.  A Pragmatic Approach to Reuse Introduction in an Industrial Setting , 1996 .

[8]  Will Tracz Confessions of a used program salesman , 1995 .

[9]  Edward Wiles,et al.  Economic models of software reuse: A survey, comparison and partial validation , 1999 .

[10]  D. D. Judicibus Reuse: a Cultural Change , 1996 .

[11]  R.T. Stephens Measuring enterprise reuse in large corporate environment , 2004, Thirty-Sixth Southeastern Symposium on System Theory, 2004. Proceedings of the.

[12]  Christopher J. Fox,et al.  Sixteen questions about software reuse , 1995, CACM.

[13]  Victor R. Basili,et al.  Support for comprehensive reuse , 1991, Softw. Eng. J..

[14]  David Garlan,et al.  Architectural Mismatch: Why Reuse Is So Hard , 1995, IEEE Softw..

[15]  Robert L. Glass,et al.  Reuse: What's Wrong with This Picture? , 1998, IEEE Softw..

[16]  Ricardo Valerdi,et al.  Extensions of COSYSMO to Represent Reuse , 2006 .

[17]  Rubén Prieto-Diaz Reuse as a New Paradigm for Software Development , 1996 .

[18]  Gan Wang,et al.  COSYSMO reuse extension , 2008 .

[19]  Marilee J. Wheaton,et al.  ANSI/EIA 632 as a standardized WBS for COSYSMO , 2005 .

[20]  Jeffrey S. Poulin,et al.  Determining the value of a corporate reuse program , 1993, [1993] Proceedings First International Software Metrics Symposium.

[21]  Suzanne Robertson,et al.  Reuse Lifecycle: Essentials and Implementations , 1996 .

[22]  Marilee J. Wheaton,et al.  Lessons Learned From Industrial Validation of COSYSMO , 2007 .

[23]  A. Terry Bahill,et al.  When can we safely reuse systems, upgrade systems, or use COTS components? , 2000 .

[24]  Michelle T. Beckert Organizational characteristics for successful product line engineering , 2000 .

[25]  Wayne C. Lim,et al.  Reuse economics: a comparison of seventeen models and directions for future research , 1996, Proceedings of Fourth IEEE International Conference on Software Reuse.

[26]  Melody M. Moore,et al.  Software Reuse: Silver Bullet? , 2001, IEEE Software.

[27]  Will Tracz,et al.  Confessions of a used-program salesman: lessons learned , 1995, SSR '95.

[28]  Jacob L. Cybulski,et al.  Reuse of early life-;cycle artifacts: workproducts, methods and tools , 1998, Ann. Softw. Eng..

[29]  Barry W. Boehm,et al.  Managing Software Productivity and Reuse , 1999, Computer.

[30]  Gan Wang,et al.  Reuse in Systems Engineering , 2010, IEEE Systems Journal.

[31]  Anthony Finkelstein,et al.  Re-use of formatted requirements specifications , 1988, Softw. Eng. J..

[32]  Shari Lawrence Pfleeger,et al.  Economics of reuse: issues and alternatives , 1990 .

[33]  Ricardo Valerdi,et al.  Considerations for successful reuse in systems engineering , 2008 .

[34]  David Probert,et al.  Engineering reuse: a framework for improving performance , 2000, Proceedings of the 2000 IEEE International Conference on Management of Innovation and Technology. ICMIT 2000. 'Management in the 21st Century' (Cat. No.00EX457).

[35]  T. P. Wright,et al.  Factors affecting the cost of airplanes , 1936 .

[36]  Ann Majchrzak,et al.  Enabling knowledge creation in far-flung teams: Best practices for IT support and knowledge sharing , 2004, IEEE Engineering Management Review.

[37]  Hoyt Lougee Reuse and DO-178B Certified Software: Beginning With Reuse Basics , 2004 .

[38]  Ricardo Valerdi,et al.  THE CONSTRUCTIVE SYSTEMS ENGINEERING COST MODEL (COSYSMO) , 2005 .

[39]  Will Tracz,et al.  Software reuse myths , 1988, SOEN.

[40]  Victor R. Basili,et al.  Defining factors, goals and criteria for reusable component evaluation , 1996, CASCON.

[41]  Anthony Finkelsteiin,et al.  Re-use of formatted requirements specifications , 1988 .

[42]  Lynne P. Cooper,et al.  Learning from Project Experiences Using a Legacy-Based Approach , 2005, Proceedings of the 38th Annual Hawaii International Conference on System Sciences.

[43]  Donald J. Reifer,et al.  Practical software reuse , 1997 .

[44]  Gabriel Szulanski,et al.  Getting it right the second time. , 2002, Harvard business review.

[45]  Scott O. Lilienfeld,et al.  What's wrong with this picture? , 2001, Scientific American.

[46]  Sarah A. Sheard,et al.  TWELVE SYSTEMS ENGINEERING ROLES , 1996 .

[47]  Rubén Prieto-Díaz,et al.  Status report: software reusability , 1993, IEEE Software.