References IEEE PUBLICATIONS

(1)

References

IEEE PUBLICATIONS

[1] IEEEIANSI. IEEE Guide to Software Configuration Management. ANSI/IEEE Std 1042-1987, IEEE Press, New York, NY, 1987.

[2] IEEE Standard Glossary of Software Engineering Terminology, IEEE Std 610.12-1990 (Sep 28), Reaffirmed Sep 2002, IEEE Press, New York, NY, 2002.

[3] IEEE Standard for Software Quality Assurance Plans, IEEE Std 730-2002 (Sep), IEEE Press, New York, NY, 2002.

[4] IEEE Standard for Software Configuration Management Plans, IEEE Std 828-1998 (Jun 25), IEEE Press, New York, NY, 1998.

[5] IEEE Standard for Software Test Documentation, IEEE Std 829-1998 (Sep 16), IEEE Press, New York, NY, 1998.

[6] IEEE Recommended Practice for Software Requirements Specifications, IEEE Std 830-1998(Jun 25), IEEE Press, New York, NY, 1998.

[7] IEEE Standard Dictionary of Measures to Produce Reliable Software, IEEE Std 982.1-1988(Jun 9), IEEE Press, New York, NY, 1988.

[8] An American National Standard-IEEE Standard for Software Unit Testing, ANSI/IEEE Std 1008-1987(R1993), Reaffirmed Dec. 2002, IEEE Press, New York, NY, 2002.

[9] IEEE Standard for Software Verification and Validation, IEEE Std 1012-1998 (Mar 9), IEEE Press, New York, NY, 1998.

[10] Supplement to IEEE Standard for Software Verification and Validation: Content Map to IEEEIEIA 12207.1-1996, IEEE Std 1012a-1998 (Sep 16), IEEE Press, New York, NY, 1998.

[11] IEEE Recommended Practice for Software Design Descriptions, IEEE Std 1016-1998 (Sep 23), IEEE Press, New York, NY, 1998.

[12] IEEE Standard for Software Reviews, IEEE Std 1028-1997 (Mar 4), Reaffirmed Sep 2002, IEEE Press, New York, NY, 2002.

[13] IEEE Standard Classification for Software Anomalies, IEEE Std 1044-1993 (Dec 2), Reaffirmed Sep 2002, IEEE Press, New York, NY, 2002.

[14] IEEE Standard for Software Productivity Metrics, IEEE Std 1045-1992 (Sep 17), Reaffirmed Dec 2002, IEEE Press, New York, NY, 2002.

[15] IEEE Standard for Software Project Management Plans, IEEE Std 1058-1998 (Dec 8), IEEE Press, New York, NY, 1998.

(2)

402 References

[16] IEEE Standard for a Software Quality Metrics Methodology, IEEE Std 1061-1998 (Dec 8), IEEE Press, New York, NY, 1998.

[17] IEEE Recommended Practice for Software Acquisition, IEEE Std 1062-1998 Edition (Dec 2), Reaffirmed Sep 2002, IEEE Press, New York, NY, 2002.

[18] IEEE Standard for Software User Documentation, IEEE Std 1063-2001 (Dec 5), IEEE Press, New York, NY, 2001.

[19] IEEE Standard for Developing Software Life Cycle Processes, IEEE Std 1074-1997 (Dec 9), IEEE Press, New York, NY, 1997.

[20] IEEE Standard Reference Model for Computing System Tool Interconnections, IEEE Std 1175-1991 (Dec 5), IEEE Press, New York, NY, 1991.

[21] IEEE Guide for CA Software Engineering Tool Interconnections-Classification and Description, IEEE Std 1175.1-2002 (Nov. 11), IEEE Press, New York, NY, 2002. [22] IEEE Standard for Software Maintenance, IEEE Std 1219-1998 (Jun 25), IEEE Press,

New York, NY, 1998.

[23] IEEE Standard for the Application and Management of the Systems Engineering Process, IEEE Std 1220-1998 (Dec 8), IEEE Press, New York, NY, 1998.

[24] IEEE Standard for Software Safety Plans, IEEE Std 1228-1994 (Mar 17), Reaffirmed Dec 2002, IEEE Press, New York, NY, 2002.

[25] IEEE Guide for Developing System Requirements Specifications, IEEE Std 1233, 1998 Edition (Apr 17), Reaffirmed Sep 2002, IEEE Press, New York, NY, 2002. [26] IEEE Standard for Functional Modeling Language-Syntax and Semantics for

IDEFO, IEEE Std 1320.1-1998 (Jun 25), IEEE Press, New York, NY, 1998.

[27] IEEE Standard for Conceptual Modeling Language Syntax and Semantics for IDEFIX 97 (IDEF object), IEEE Std 1320.2-1998 (Jun 25), IEEE Press, New York, NY, 1998. IEEE Guide for Information Technology-System Definition-Concept of Operations (ConOps) Document, IEEE Std 1362-1998 (Mar 19), IEEE Press, New York, NY, 1998.

[28] IEEE Standard for Information Technology-System Definition-Concept of Opera-tions (ConOps) Decument, IEEE Std 1362-1998 (Mar 19), IEEE Press, New York, NY, 1998. IEEE Standard for Information Technology-Software Reuse-Data Mod-el for Reuse Library Interoperability: Basic Interoperability Data ModMod-el (BIDM), IEEE Std 1420.1-1995 (Dec 12), Reaffirmed Jun 2002, IEEE Press, New York, NY, 2002.

[29] Supplement to IEEE Standard for Information Technology-Software Reuse-Data Model for Reuse Library Interoperability: Asset Certification Framework, IEEE Std 1420.1a-1996 (Dec 10), Reaffirmed Jun 2002, IEEE Press, New York, NY, 2002. [30] IEEE Trial-Use Supplement to IEEE Standard for Information Technology-Software

Reuse-Data Model for Reuse Library Interoperability: Intellectual Property Rights Framework, IEEE Std 1420.1b-1999 (lun 26), Reaffirmed Jun 2002, IEEE Press, New York, NY, 2002.

[31] IEEE Standard-Adoption of International Standard ISO/IEC 14102: 1995-lnforma-tion Technology-Guideline for the Evalua1995-lnforma-tion and Selec1995-lnforma-tion of CASoftware Engi-neering tools, IEEE Std 1462-1998 (Mar 19), IEEE Press, New York, NY, 1998. [32] IEEE Standard-Adoption of International Standard ISO/IEC 12119:

1994(£)--ln-formation Technology-Software Packages-Quality Requirements and Testing, IEEE Std 1465-1998 (Jun 25), IEEE Press, New York, NY, 1998.

(3)

[33] IEEE Recommended Practice for Architectural Description of Software Intensive Sys-tems, IEEE Std 1471-2000 (Sep 21), IEEE Press, New York, NY, 2000.

[34] IEEE Guide-Adoption of PMI Standard-A Guide to the Project Management Body of Knowledge, IEEE Std 1490-2003 (Dec 10), Replaces 1490-1998 (Jun 25), IEEE Press, New York, NY, 2003.

[35] EIAlIEEE Interim Standard for Information Technology-Software Life Cycle Processes-Software Development: Acquirer-Supplier Agreement, IEEE Std 1498-1995 (Sep 21), IEEE Press, New York, NY, 1498-1995.

[36] IEEE Standard for Information Technology-Software Life Cycle Processes-Reuse Processes, IEEE Std 1517-1999 (Jun 26), IEEE Press, New York, NY, 1999. [37] IEEE Standard for Software Life Cycle Processes-Risk Management, IEEE Std

1540-2001 (Mar 17), IEEE Press, New York, NY, 200 I.

[38] IEEE Recommended Practice for Internet Practices-Web Page Engineering-In-tranet/Extranet Applications, IEEE Std 2001-2002 (Jan 21, 2003), IEEE Press, New York, NY, 2003.

[39] Industry Implementation of International Standard ISO/IEC 12207:1995 Standard for Information Technology-Software Life Cycle Processes-Software Life Cycle Processes, IEEE/EIA 12207.0/.1/.2-1996 (Mar), IEEE Press, New York, NY, 1996. [40] IEEE, IEEE Standards Collection, Software Engineering, 1994 Edition, IEEE Press,

New York, NY, 1994.

[41] IEEE, IEEE Software Engineering Standards Collection, IEEE Press, New York, NY, 2003.

[42] IEEE, Software and Systems Engineering Standards Committee Charter Statement, http://standards.computer.org/S2ESC/S2ESC_pols/S2ESC _Charter.htm, 2003. [43] S2ESC Guide for Working Groups, http://standards.computer.org/S2ESC/S2ESC_

wgresources/S2ESC-WG-Guide-2003-07 -14.doc, 2003.

[44] IEEE, Guide to the Software Engineering Body of Knowledge (SWEBOK), Trial Ver-sion, IEEE Press, New York, NY, 2001.

[45] McConnell, S., "The Art, Science, and Engineering of Software Development,IEEE

Software Best Practices, Vol. 15 No.1, 1998.

ISO PUBLICATIONS

[46] International Standard 9000, Quality Management Systems-Fundamentals and Vo-cabulary, ISO 9000:2000(E), 2000, Switzerland.

[47] International Standard 9001, Quality Management Systems-Requirements, ISO 9001:2000(E), 2000, Switzerland.

[48] International Standard 90003, Software and System Engineering-Guidelines for the Application of ISO 900 I:2000 to Computer Software, ISO/IECF 90003:2003(E), 2003, Switzerland.

[49] International Standard 9004, Quality Management Systems-Guidelines for Perfor-mance Improvements, ISO 9004:2000(E), 2000, Switzerland.

[50] ISO 9000 Introduction and Support Package Module: Guidance on ISO 9001:2000 Subclause 1.2 "Application," 524R4; ISO/TC 176/SC 2, 2004, London.

(4)

404 References

Guidance on the Documentation Requirements of ISO 9001:2000, 525R, ISO/TC

176/SC 2, 2001, London.

[52] ISO 9000 Introduction and Support Package Module: Guidance on ISO 9001:2000 Guidance on the Terminology Used in ISO 9001:2000 and ISO 9004:2000, 526R, ISO/TC 176/SC 2, 2001.

[53] ISO 9000 Introduction and Support Package Module: Guidance on ISO 9001:2000 Guidance on the Concept and Use of the Process Approach for Management Systems, 544R2, ISO/TC 176/SC 2, London, 2004.

[54] ISO 9000 Introduction and Support Package Module: Guidance on ISO 9001:2000 Guidance on Outsourced Processes, 630R2, ISO/TC 176/SC2, London, 2003. [55] ISO/IEC 15504 International Standard for Software Process Assessment, ISO/IEC TR

15504, Switzerland, 2003/2005.

[56] ISO 19011 Guidelines for Quality and Environmental Management Systems Monitor-ing, BS EN ISO 19011:2002, London, 2002.

[57] Information technology-Software Functional Size Measurement-Definition of Concepts, ISO/IEC JTCl/SC7, ISO/IEC 14143.1:1999, Canada, 1998. [58] Systems Engineering-System Life Cycle Processes, ISO/IEC JTCl/SC7, ISO/IEC

15288:2002, Canada, 2002.

[59] Information Technology-Software Engineering-Software Measurement Process, ISO/IEC JTCl/SC7, ISO/IEC 15939:2001, Canada, 2001.

OTHER REFERENCES

[60] Arthur, L., Software Evolution: The Software Maintenance Challenge, Wiley, 1988. [61] Babich, W., Software Configuration Management, Addison-Wesley, 1986.

[62] Victor R. Basili, et aI., "A Reference Architecture for the Component Factory," ACM

Trans. Software Eng. and Methodology, Vol 1., No.1, Jan. 1992, pp. 53-80.

[63] Bersoff, E., Henderson, V., and Siegel, S., Software Configuration Management: A

Tutorial,IEEE Computer Society Press, 1980, pp. 24-32.

[64] Bounds, N. M. and Dart S. A., Configuration Management (CM) Plans: The

Begin-ning to Your CM Solution, Software Engineering Institute, Carnegie Mellon Universi-ty, 1993.

[65] Bredemeyer Consulting, The Architecture Discipline-Software Architecting Success

Factors and Pitfalls,http://www.bredemeyer.comlCSFs_pitfalls.htm. 2004.

[66] Carr, M. et aI., Taxonomy-Based Risk Identification, Software Engineering Institute, Carnegie Mellon University, Technical Report, CMU/SEI-93- TR-006, 1993. [67] Croll, P., "Eight Steps to Success in CMMI-Compliant Process Engineering,

Strate-gies and Supporting Technology," in Third Annual CMMJ® Technology Conference and Users Group, 2003.

[68] Croll, P., "How to Use Standards as Best Practice Information Aids for CMMI-Com-pliant Process Engineering," in 14th Annual DoD Software Technology Conference, 2002.

[69] Croll, P. and Land, S. K., "S2ESC: Setting Standards for Three Decades," IEEE

Com-puter Magazine,January 2005.

(5)

[71] U.S. Department of Defense, Software Transition Plan, Data Item Description DI-IPSC-81429.

[72] U.S. Department of Energy Quality Managers Software Quality Assurance Subcom-mittee, "Software Risk Management, A Practical Guide," SQAS21.01.00-1999, 2000.

[73] Department of Justice Systems Development Life Cycle Guidance, Interface Control Document Template, Appendix C-17; http://www.usdoj.gov/jmd/irm/lifecycle/table. htm.

[74] Dunn, R. H. and Ullman, R. S.,TQM for Computer Software, 2nd edition,

McGraw-Hill, 1994.

[75] Ford, G. and Gibbs, N., "A Mature Profession of Software Engineering," Software Engineering Institute, Carnegie Mellon University, Technical Report, CMU/SEI-96-TR-004, 1996.

[76] Freedman, D. P. and Weinberg, G. M.,Handbook of Walkthroughs, Inspections, and

Technical Reviews, Evaluating Programs, Projects, and Products,3rd edition, Dorset House, 1990.

[77] Gremba, J. and Myers, C., "The IDEAL Model: A Practical Guide for Improvement,"

Bridge,Issue 3, Software Engineering Institute, Carnegie Mellon University, 1997.

[78] Hass, A. M. J.,Configuration Management Principles and Practice,Addison-Wesley,

2003.

[79] Jalote P.,An Integrated Approach to Software Engineering, 2nd edition,

Springer-Verlag, 1997.

[80] Kasunic, M., "An Integrated View of Process and Measurement," Software Engineer-ing Institute, Carnegie Mellon University, Presentation, http://www.sei.cmu.edu/ sema/pdf/integrated-view-process.pdf, 2004.

[81] Land, S. K., "1st User's of Software Engineering Standards Survey," IEEE Software and Systems Engineering Standards Committee (S2ESC), 1997.

[82] Land S. K., "2nd User's of Software Engineering Standards Survey," IEEE Software and Systems Engineering Standards Committee (S2ESC), 1999.

[83] Land, S. K., "IEEE Standards User's Survey Results," inISESS '97Conference

Pro-ceedings,IEEE Press, 1997.

[84] Land, S. K., "Second IEEE Standards User's Survey Results," inISESS '99

Confer-ence Proceedings, IEEE Press, 1999.

[85] Land, S. K.,Jumpstart CM!vf®ICMMJ® Software Process Improvement Using IEEE

Software Engineering Standards,John Wiley, 2004.

[86] McConnell, S.,Professional Software Development,Addison-Wesley, 2004.

[87] McFeeley, B.,IDEAL: A User's Guide to Software Process Improvement, Software

Engineering Institute, Carnegie Mellon University, Handbook, CMU/SEI-96-HB-001, 1996.

[88] Moore, 1., "Increasing the Functionality of Metrics through Standardization," in Con-ference on Developing Strategic liT Metrics, 1998.

[89] Moore, 1.,Road Map to Software Engineering-A Standards Based Guide, Wiley,

2005.

[90] Phifer, E.,DAR Basics: Applying Decision Analysis and Resolution in the Real World,

Software Engineering Institute, Carnegie Mellon University, SEPG Presentation, http:// www.sei.cmu.edu/cmmi/presentations/sepg04.presentations/dar.pdf, USA, 2004.

(6)

406 References

[91] Pressman, R., Software Engineering, McGraw-Hill, 1987.

[92] Royce, W., "CMM® vs. CMMI, From Conventional to Modem Software Manage-ment," The Rational Edge, 2002.

[93] Schach, S. R., Classical and Object-Oriented Software Engineering, 3rd Edition, Ir-win, 1993.

[94] SEI, The Capability Maturity Model: Guidelines for Improving the Software Process, v.1.1, Software Engineering Institute, Carnegie Mellon University, 1997.

[95] SEI, A Framework for Software Product Line Practice, V 4.2, Software Engineering Institute, Carnegie Mellon University, Web Report, http://www.sei.cmu.edu/plp/ framework.html#outline, 2004.

[96] SEI, Capability Maturity Model Integration (CMMI) for Software Engineering, v.I. 1 Staged Representation, Software Engineering Institute, Carnegie Mellon University, Technical Report, CMU/SEI-2002-TR-029, 2002.

[97] SEI, Integrated Product Development (IPD)-CMM®, Software Engineering Institute, Carnegie Mellon University, Model Draft, 1997.

[98] SEI, Organizational Process Improvement Checklist Using IDEALsM , Software Engi-neering Insititute, Carnegie Mellon University, Presentation, www.sei.cmu.edu/ideal/ ideal.present.

[99] USAF Software Technology Support Center (STSC), CMM-SE/SW Vl.lto SW-CMM®

Vl.l Mapping, 2002.

[100] Veenendall, E. V., Ammerlaan, R., Hendriks, R., van Gensewinkel, V., Swinkels, R., and van der Zwan, M., "Dutch Encouragement; Test Standards we Use in Our Pro-jects," Professional Tester, Number 16, October 2003.

[101] Westfall, L. L., "Seven Steps to Designing a Software Metric," BenchmarkQA, Whitepaper, 2002.

[102] Whitgift, D., Methods and Tools for Software Configuration Management, Wiley, 1991.

[103] Wiegers, K. E., Creating A Software Engineering Culture, Dorset House Publishing, 1996.

[104] Williams and Wegerson, Evolving the SEPG to a CMMI World, http://www.sei.cmu. edu/cmmi/presentations/sepg03.presentations/williams-wegerson.pdf, 2002.

[105] Zubrow, D., Hayes, W., Siegel,1.,and Goldenson, D., Maturity Questionnaire, Spe-cial Report, CMU/SEI-94-SR-7, Software Engineering Institute, Carnegie Mellon University,1994.