References

12.1 Systems Engineering (1994). The Journal of the National Council on Systems Engineering (NCOSE) 1(1), Sunnyvale, CA. (Note: NCOSE has changed its name to INCOSE, 2033 Sixth Ave. #804, Seattle, WA 98121-2546.)

12.2 ''Systems Engineering in the Global Market Place'' (1995). NCOSE 5th Annual International Symposium, St. Louis, July 22-26.

12.3 Eisner, H., J. Marciniak, and R. McMillan (1991). ''Computer-Aided System of Systems (S2) Engineering.'' IEEE International Conference on Systems, Man, and Cybernetics, Charlottesville, VA., October 13-16.

12.4 Eisner, H., R. McMillan, J. Marciniak, and W. Pragluski (1993). ''RCASSE: Rapid Computer-Aided System of Systems (S2) Engineering.'' NCOSE 3rd Annual International Symposium, Arlington, VA, July 26-28.

12.5 Kuhn, D., and S. Garcia (1994). ''Developing a Capability Maturity Model for Systems Engineering.'' Best Presentations of the NCOSE 4th Annual International Symposium, San Jose, CA, August 10-12.

12.6 Garcia, S. (1994). SE-CMM Model Description, Release 2.04, SEI-94-HB-4. Pittsburgh, PA: Software Engineering Institute, Carnegie-Mellon University.

12.7 Pierson, H. (1995). ''Comparison of NCOSE Interim Model & SE-CMM,'' Virginia Center of Excellence for Software Reuse and Technology Transfer, April 11. Presented as part of NCOSE Notes from the Network 3(4).

12.8 Systems Engineering Capability Model (SECM), EIA/IS 731, (1998). Washington, DC: Electronic Industries Association, Engineering Department.

12.9 L. Ibrahim, et al., (1997). The Federal Aviation Administration (FAA) Integrated Capability Maturity Mode (iCMM)l, Version 1.0, Washington, DC: Federal Aviation Administration, November.

12.10 Software Engineering Institute, Carnegie-Mellon University, Website: www. sei.cmu.edu

12.11 Rechtin, E. (1991). Systems Architecting. Englewood Cliffs, NJ: Prentice Hall.

12.12 Rechtin, E., and M. Maier (1997). The Art of Systems Architecting. Boca Raton, FL: CRC Press.

12.13 Rechtin, E. (1994). ''Foundations of Systems Architecting,'' Systems Engineering 1(1): 35-42.

12.14 Rechtin, E. (1994). ''The Systems Architect: Specialty, Role and Responsibility.'' Best Presentations of the NCOSE 4th Annual International Symposium, San Jose, CA., August 10-12.

12.15 First Annual Workshop on Engineering of Systems in the 21st Century: Facing the Challenge, Focus Group Reports (1994). Sponsored by the Office of Naval Research and Naval Surface Warfare Center, Department of the Navy, Fredericksburg, VA, June 28-30.

12.16 C4ISR Architecture Framework, Version 2.0 (1997). Washington, DC: U.S. Department of Defense, Pentagon, December 18; see also Website: www.c3i.osd.mil

12.17 C4ISR Architecure Working Group (AWG) (1998). Final Report. Washington, DC: U.S. Department of Defense, Pentagon, April 14; see also Website: www. c3i.osd.mil

12.18 Public Policies & Priorities: 1995-1996 (1995). Washington, DC: American Association of Engineering Societies.

12.19 Statement of the AAES on The Role of the Engineer in Sustainable Development: Sustainable Technologies and Processes (1995). Washington, DC: American Society of Engineering Societies.

12.20 Sage, A. (1992). Systems Engineering. New York: John Wiley.

12.21 Sage, A. (1992). Systems Management for Information Technology and Software Engineering. New York: John Wiley.

12.22 Armstrong, J., and A. Sage (1995). An Introduction to Systems Engineering. New York: John Wiley.

12.23 Sage, A., and W. Rouse (1999). Handbook of Systems Engineering and Management, New York; John Wiley.

12.24 Sage, A. (1994). ''The Many Faces of Systems Engineering,'' Systems Engineering 1(1): 43-60.

12.25 Cochran, M., et al. (1995). A Tailorable Process for Systems Engineering, Software Productivity Consortium Report SPC-94095-CMC. Herndon, VA: Software Productivity Consortium.

12.26 Eisner, H. (1988). Computer-Aided .Systems Engineering. Englewood Cliffs, NJ: Prentice Hall.

12.27 Conference on Tools & Methods for Business Engineering, (1995). Sponsored by Enterprise Reengineering (7777 Lesburg Pike, Falls Church, VA), Arlington, VA, May 16-17.

12.28 Center of Excellence in Computer-Aided Systems Engineering (CECASE), J. Holtzman, Director, Lawrence, KS.

12.29 Lamonica, F. (1994). ''Rome Laboratory System Engineering Research and Development Program,'' CrossTalk (April): 4-7.

12.30 Federal Computer Week (1995). July 3; and Washington Technology.

12.31 Secretary of Defense Memorandum on Military Specifications and Standards (1994). Washington, DC: U.S. Department of Defense.

12.32 Acquisition Reform: DOD Begins Program to Reform .Specifications and .Standards (1994). Report to Congressional Committees, GAO/NSIAD-95-14. Washington, DC: U.S. General Accounting Office.

12.33 Blueprint for Change: Report of the DoD Process Action Team on Specifications and Standards (1994). Washington, DC: Office of the Under Secretary of Defense. Reprinted by the U.S. Department of Commerce, National Technical Information Service, AD-A278-102.

12.34 Joint Logistics Commanders Guidance for Use of Evolutionary Strategy to Acquire Weapon Systems (1995). Fort Belvoir, VA: Defense Systems Management College Press.

12.35 The Defense Acquisition System, DoD Directive 5000.1 (2000); Operation of the Defense Acquisition System, DoD Directive 5000.2 (2000); Mandatory Procedures for Major Defense Acquisition Programs (MDAPS) and Major Automated Information Systems (MAIS) Acquisition Program, DoD Directive 5000.2-R (2000). Washington, DC: U.S. Department of Defense.

12.36 Gansler, J. (2000). The Road Ahead. Washington, DC: Department of Defense, Office of the Under Secretary of Defense for Acquisition and Technology, June.

12.37 Sage, A., and C. Lynch (1998). ''Systems Integration and Architecting,'' Systems Engineering 1. (3).

12.38 The National Software Council, John J. Marciniak, President. Kaman Sciences Corporation, Alexandria, VA [(703) 329-7368].

12.39 Report of the Defense Science Board Task Force on Acquiring Defense Software Commercially (1994). Washington, DC: Office of the Under Secretary of Defense for Acquisition and Technology.

12.40 Report of the Defense Science Board (DSB) Task Force on Defense Software (2000). Washington, DC: Office of the Under Secretary of Defense for Acquisition and Technology, November.

12.41 The Standish Group. CHAOS Report; see also Website: standishgroup.com, 1999.

12.42 Druyun, D. (1994). ''Software Reuse Incentive Policy,'' CrossTalk (January): 5. (Druyun was the Deputy Assistant Secretary of the Air Force (Acquisition) at the time.)

12.43 Levine, T. (1994). ''Report of the Working Group on Reuse Education,'' CrossTalk (December): 21-25.

12.44 Davis, T. (1994). ''The Reuse Capability Model,'' CrossTalk (March): 5-9.

12.45 Hills, F. (1994). ''Study Points Way to More Effective Software Reuse,'' CrossTalk (May): 23-24.

12.46 Sodhi, J., and M. Smith (1994). ''Marching Toward a Software Reuse Future,'' CrossTalk (September): 20-24.

12.47 ''Commerce Department Announces 41 Awards for Advanced R&D in Four Key Technologies,'' (1994) U.S. Department of Commerce News (October): 1-2.

12.48 Eisner, H. (1995). ''Reengineering the Software Acquisition Process Using Developer Off-the-Shelf Systems (DOTSS),'' 1995 IEEE International Conference on Systems, Man and Cybernetics, Vancouver, BC, October 22-25.

12.49 Sorensen, R. (1995). ''A Comparison of Software Development Methodologies,'' CrossTalk (January): 12-17.

12.50 Boehm, B., and W. Scacchi (1995). Simulation and Modeling for Software Acquisition (SAMSA). Los Angeles: University of Southern California, ATRIUM Laboratory, Information and Operations Management Department, School of Business Administration.

12.51 Guidelines for Successful Acquisition and Management of Software-Intensive Systems (GSAM), Vol. 1—Version 3.0 (2000), Department of the Air Force, Software Technology Support Center, May; see also Website: web2. deskbook.osd.mil

12.52 Tomlin, B. (1991). ''Integrated Computer-Aided Software Engineering.'' Software Technology Support Center Conference, April 16, Hill AFB, Ogden, UT.

12.53 Paige, E. (1995). ''DOD Commitment to I-CASE,'' CrossTalk (May): 6.

12.54 Kogut, P., and P. Clements (1994). ''The Software Architecture Renaissance,'' CrossTalk (November): 20-23.

12.55 Defense Information Systems Agency (DISA) (1994). Department of Defense Technical Architecture Framework for Information Management, volume 1, Overview, Version 2.0. Washington, DC: Department of Defense (June 30).

12.56 Draft Recommended Practice for Architectural Description, IEEE 1471 (1999). New York: Institute for Electrical and Electronics Engineers (IEEE), December.

12.57 Sittenhauer, C., M. Olsem, and J. Balaban (1995). ''Software Reengineering at the STSC,'' CrossTalk (January): 6-8.

12.58 Urban, J., H. Joo, and Y. Wu (1995). ''Software Reverse Engineering and Reengineering.'' Report prepared for Rome Laboratory, RL/COEE, Griffis AFB, New York.

12.59 Chikofsky, E., and J. Cross (1990). ''Reverse Engineering and Design Recovery: A Taxonomy,'' IEEE Software 7(1).

12.60 Frazer, A. (1992). ''Reverse Engineering: Hype, Hope or Here?,'' in P. A. V. Hall, ed., Software Reuse and Reverse Engineering in Practice. London: Chapman & Hall.

12.61 Lewis, T., et al. (1995). ''Where Is Software Headed?'' Computer 28 (August): 20-32.

12.62 Marciniak, J., ed. (1994). Encyclopedia of Software Engineering. New York: John Wiley.

12.63 Senge, P. (1990). The Fifth Discipline. New York: Doubleday.

12.64 Berk, K., D. Barrow and T. Steadman (1992). ''Project Management Tools Report.'' Ogden, UT: Software Technology Support Center, Hill AFB.

12.65 Practical Software Measurement (PSM); see Website: www.psmsc.com, 1998.

12.66 Significant Changes Underway in DoD's Earned Value Management Process (1997), Washington, DC: GAO/NSIAD - 97 - 108, U.S. Government Accounting Office (GAO), May.

Project Management Made Easy

Project Management Made Easy

What you need to know about… Project Management Made Easy! Project management consists of more than just a large building project and can encompass small projects as well. No matter what the size of your project, you need to have some sort of project management. How you manage your project has everything to do with its outcome.

Get My Free Ebook


Post a comment