Overview
In this activity, the project software manager, assisted by the software engineering process group (SEPG), establishes a software engineering environment consisting of facilities, equipment, and tools to support the software project.
Roles and Responsibilities
The project software manager and software engineering staff manager (if assigned) establishes the software engineering environment to meet the needs of the software project within cost, schedule, and performance constraints.
The system administrator installs the software engineering environment.
The project manager approves the acquisition of new hardware and software.
The SEPG may be consulted for information on new tools and technologies.
Controls
Budget available for purchasing new hardware and software.
Software project scope identifying the products that must be developed and the software project schedule.
Inputs
Commercial tool information to be evaluated.
Risk management tracking information to be acquired.
Procedures
1) Based upon the software products to be developed (as identified in the work breakdown structure (WBS)) and the software schedule, the project software manager and software engineering manager determine the appropriate software engineering environment and risk management tracking mechanism to be used. The project software manager should consult Appendix D - Tools of this Guidebook and the SEPG to determine what tools are currently available for use within the organization.
2) If the tools available within the organization are unsuitable for the project, the project software manager and software engineering manager should, with the help of the SEPG, determine what commercial tools are available and evaluate them (see activity 4.1.3 Determine Improvement Goals And Potential Changes). The project software manager also may consult [LHB 5300.4, pp. 5-1 to 5-6], Software Technology Support Center reports, and Internet news groups for more information on commercially available tools. The project software manager consults with the project manager, as well as the SEPG, to determine the available budget for acquiring new hardware and software, and updates the WBS (see activity 1.1.1.1.2 Develop Work Breakdown Structure) and software project cost estimates accordingly (see activity 1.1.1.1.4 Perform Cost Estimates).
3) When acquiring new hardware and software, the project software manager should consider the need to purchase hardware spares, and the correct number of licenses, as well as budgeting for future maintenance. The system administrators who are responsible for installing the new hardware and software should be notified of the expected arrival date for installation planning purposes.
4) The project software manager documents the selected software engineering environment in the Software Engineering Environment section of the Software Development Plan (SDP) (see Appendix E). An example of a software engineering environment is described in Figure 1.1.1.2.2-1.
Figure 1.1.1.2.2-1 Example of Software Engineering Environment
Vendor
Product
Version Number
CSCI
Microsoft DOS 6.2 Flight, Ground Support Microsoft Windows 3.11 Flight, Ground Support Microsoft Windows NT 3.51 Flight, Ground Support Microsoft Word 6.0 Flight, Ground Support Microsoft Powerpoint 4.0 Flight, Ground Support Microsoft Access 2.0 Flight, Ground Support Microsoft Excel 5.0 Flight, Ground Support Microsoft Project 4.0 Flight, Ground Support Intersolv PVCSÔ 5.2 Flight, Ground Support Mix Power C 2.12 Ground Support Mark V Object Maker 3.4 Flight Alsys Ada Compiler 5.12 Flight Hardware commercial-off-the-shelf (COTS) platform - Gateway 2000 PC (Intel 486-based)
5) The system administrator(s) installs and checks out the acquired software and/or hardware.
Outputs
The software engineering environment acquired and installed for use during the project.
The description of the software engineering environment documented in the Software Engineering Environment section of the SDP.