The Department of Defense (DoD) Information Enterprise (IE) is an organizing construct that consists of DoD information assets, processes, activities, and resources required to achieve an information advantage and share information across the DoD. The construct is envisioned to help the DoD move to trusted network-centric operations through the acquisition of services and systems that […]
Lessons Learned are those experiences in the past that can be used in the future to prevent mistakes or perform a task or job better. A lesson is not learned until it is put into practice or until behavior changes. The DoD has a few sources of lessons learned for Software that can be
Software Source Selection Consideration for Computer Systems & Software (CS&S) tasks includes: Creating CS&S Request for Proposal (RFP) content Accomplishing Software Proposal Evaluation It’s should be the objective to select developers with sound approaches; applicable domain experience in the development of software-intensive systems; proven program management, systems engineering, and software engineering processes; and
A Software Specification Review (SSR) is conducted for each Computer Software Configuration Item (CSCI) after the System Functional Review (SFR), but prior to the initiation of preliminary design for the individual CSCI. The SSR is part of the overall systems engineering process of allocating and formally defining requirements and must occur after the system/subsystem level
The Software Development Process is the structured approach to developing software for a system or project. There are a number of approaches (see Software Development Approaches) that can be used to include waterfall, spiral and incremental development. These different approaches will focus the testing effort at different points in the development process. However, each is
The software development process often results in software size growth due to additional decomposed and derived requirements at the lower system tiers. A typical challenge for embedded systems is that software size often grows under the radar, unconstrained, unmanaged, and unattended. In order to combat this situation, consider establishing a software size control program.
Software Risk Estimation is one of the most significant risks faced by any weapon system program. The ability to properly estimate software size, effort, and schedule is crucial and must be addressed by every Program Manager (PM). Visit: Software Estimation Process Consideration Visit: Estimating Reuse Feasibility The following factors contribute to software estimation risk: Ability
Software Size Estimating is an important activity in software engineering that is used to estimate the size of an application or component in order to be able to implement other program management activities such as cost estimation or schedule progress. The software engineer is responsible for generating independent estimates of the software size throughout the
Software is addressed in the Request for Proposal (RFP) in order to solicit proposals that provide the information to support an effective Government evaluation and identification of strengths, deficiencies, uncertainties, weaknesses, and risks related to software. The sections is an RFP that should address software include: [1] Statement of Objectives (SOO) Statement of Work (SOW)
The Software Resources Data Report (SRDR) collects software metrics data to supplement actual Contractor Cost Data Reporting (CCDR) cost data to provide a better understanding and improved estimating of software-intensive programs. Cost and Software Data Reporting (CSDR) System The Cost and Software Data Reporting (CSDR) system is the primary means that DoD uses to collect
