Industry best practices for the software development life cycle
Subtitle: final report
By: by Ray Babcock, Gary Harkin, and Hunter Lloyd; for the  Montana Department of Transportation
Contributors: Harkin, Gary; Lloyd, Hunter; Montana. Dept. of Transportation; United States. Federal Highway Administration; Montana State University (Bozeman, Mont.)
Publisher: Montana Dept. of Transportation
Published: 2007
Place of publication: [Helena, Mont.]
Language: eng
Format: [electronic resource] ;
Number of pages: 152
Subjects: Data processing; Software architecture; Computer network architectures; Computer operating systems; UML (Computer science); Computer programs; Best practices; Project management; Software
Description: In the area of software development, there are many different views of what constitutes a best practice.  The goal of this project was to identify a set of industry best practice techniques that fit the needs of MDT, and provide a consistent and robust process for software development.  The researchers believe that the Unified Software Development Process represents the closest methodology to an industry standard for software development.  The Project Management Professional certification of the Project Management Institute represents best practice in project management.  The researchers have suggested the Unified Modeling Language as a representational method for developing software designs.  Practical suggestions for the elicitation of software requirements are provided.  The complete set of MDT forms was converted to an XML utility system to allow for easy changes and configurations.
Notes: "November 2007"- cover date.

Includes bibliographical references (p. 45-46).

Final report ; 5/2005-11/2006.

Sponsored by the Montana Dept. of Transportation, Research Programs 8117-25

Mode of access:  World Wide Web, PDF reader.
Table of contents: label: 1
title: Introduction; label: 1.1
title: Report Organization; label: 2
title: The Software Development Life Cycle
pagenum: 4; label: 2.1
title: Planning
pagenum: 4; label: 2.2
title: System Analysis
pagenum: 5; label: 2.3
title: System Design; label: 2.4
title: Technical Design
pagenum: 6; label: 2.5
title: Development
pagenum: 6; label: 2.6
title: Implementation
pagenum: 6; label: 2.7
title: Conclusion; label: 3
title: Requirements Development
pagenum: 8; label: 3.1
title: Introduction
pagenum: 8; label: 3.2
title: Requirements Elicitation
pagenum: 9; label: 3.3
title: Using Features
pagenum: 9; label: 3.4
title: Interviewing
pagenum: 10; label: 3.5
title: Context Free Questions
pagenum: 10; label: 3.6
title: Requirements Workshop
pagenum: 11; label: 3.7
title: Brainstorming and Idea Redirection
pagenum: 13; label: 3.8
title: Storyboarding
pagenum: 14; label: 3.9
title: Stakeholders
pagenum: 15; label: 3.10
title: Use Cases
pagenum: 16; label: 3.11
title: "Mary Had a Little Lamb" Heuristic
pagenum: 16; label: 4
title: Project Management
pagenum: 18; label: 4.1
title: Scope Management
pagenum: 18; label: 4.2
title: Time Management
pagenum: 19; label: 4.3
title: Cost Management
pagenum: 19; label: 4.4
title: Quality Management
pagenum: 20; label: 4.5
title: Risk Management
pagenum: 20; label: 5
title: Process Measurement
pagenum: 22; label: 5.1
title: Objectives
pagenum: 23; label: 5.2
title: Metrics
pagenum: 23; label: 5.3
title: Collection and Presentation
pagenum: 26; label: 5.4
title: Privacy
pagenum: 26; label: 5.5
title: Possible Metrics
pagenum: 27; label: 6
title: Software Design
pagenum: 29; label: 6.1
title: Planning Phase
pagenum: 29; label: 6.2
title: System Analysis Phase
pagenum: 30; label: 6.3
title: System Design Phase
pagenum: 30; label: 6.4
title: Technical Design Phase
pagenum: 32; label: 6.5
title: Development Phase
pagenum: 37; label: 6.6
title: Implementation Phase
pagenum: 39; label: 6.7
title: Conclusion Phase
pagenum: 40; label: 6.8
title: Risk and Agile Development
pagenum: 40; label: 7
title: User Interface Development
pagenum: 41; label: 8
title: Software Development
pagenum: 42; label: 8.1
title: Code Walkthroughs
pagenum: 42; label: 8.2
title: Programming Pairs
pagenum: 42; label: 9
title: Documentation
pagenum: 43; label: 10
title: Training Plan and Training
pagenum: 44; label: 11
title: References
pagenum: 45; label: Appendix A
title: UML Example
pagenum: 47; label: Appendix B
title: SDLC Roles
pagenum: 74; label: Appendix C
title: The SDLC Outline
pagenum: 76; label: Appendix D
title: SDLC Form List
pagenum: 93; label: Appendix E
title: SDLC Forms
pagenum: 94