カテゴリー 全て - requirements - management - testing - design

によって Mark Philbrick 12年前.

360

Software Guidebook

The text outlines a comprehensive approach to software development and project management. It emphasizes the importance of understanding and discussing system requirements, dedicating significant attention to the Software Development Life Cycle (

Software Guidebook

Guidebook

Appendix

Templates
Acronyms

Training

Support Activities

HQ/Division
Source Selection
TSN
Post Award
Preaward
SCAMPI

Re-planning

Report

Analyze

SDLC

Test Phase
System Integration testing
CSCI Testing
CSC Integration and testing
Coding and CSU testing
Detail Design
Preliminary Design
Software Requirements Anaysis

Discuss system requirements

Core Processes
Phase independent Core Processes

DCMA support activities

Tools
Risk Management
Reviews and Audits
CM
SQA

Strategy

Develop/document Surveillance strategy
Template

Impacts of no resources to current workload

Review Supplier Planning docs

See 1. Software Program Management Oversight

Outgoing LOD
Flowdown DCMA requirements (as applicable)
DCMA Software FTE Analysis
DCMA Requirements
Informal requests

Conversation

Emails

Phone calls

Capture in PC later (depends on scope)

ALPC
Incoming LOD
QALI/LOI
MOA
Contract review

Data rights

SPDP material

FAR clauses

GFE/GFM

MS

Overview

John Eget has agreed to do all of this.

Maintenance of Guidebook
Core process
Concept
purpose
PBM
Take Action / Documentation - Core
How to use guidebook
Flow
Purpose of Guidebook