Customer Support: 131 242

  • There are no items in your cart
We noticed you’re not on the correct regional site. Switch to our AMERICAS site for the best experience.
Dismiss alert

IEEE DRAFT 1074 : 0

Superseded

Superseded

A superseded Standard is one, which is fully replaced by another Standard, which is a new edition of the same Standard.

View Superseded by

DEVELOPING SOFTWARE LIFE CYCLE PROCESSES

Available format(s)

Hardcopy , PDF

Superseded date

28-07-2006

Superseded by

IEEE 1074-2006

Language(s)

English

1 OVERVIEW
  1.1 SCOPE
  1.2 PURPOSE
  1.3 PRODUCT OF STANDARD
  1.4 INTENDED AUDIENCES
      1.4.1 PROCESS ARCHITECT
      1.4.2 OTHER INTERESTED PARTIES
  1.5 CONFORMANCE
  1.6 RELATIONSHIP TO OTHER KEY STANDARDS
      1.6.1 RELATIONSHIP TO ISO 9001
      1.6.2 RELATIONSHIP TO IEEE/EIA 12207
      1.6.3 RELATIONSHIP TO SEI CMMI
      1.6.4 RELATIONSHIP TO SOFTWARE ENGINEERING STANDARDS
  1.7 RELATIONSHIP TO PROCESS IMPROVEMENT
  1.8 ORGANIZATION OF THIS DOCUMENT
      1.8.1 CLAUSES
      1.8.2 ACTIVITY GROUPING
      1.8.3 ACTIVITY SEQUENCING
2 REFERENCES
3 DEFINITIONS AND ACRONYMS
  3.1 DEFINITIONS
  3.2 ACRONYMS
4 KEY CONCEPTS
  4.1 ACTIVITIES
      4.1.1 FORMAT
      4.1.2 ENTRY AND EXIT CRITERIA
      4.1.3 REQUIRED ACTIVITIES
      4.1.4 ORGANIZATIONAL STRUCTURE
  4.2 ELEMENTS OF THE SOFTWARE PROJECT LIFE CYCLE PROCESS
      4.2.1 SOFTWARE PROJECT LIFE CYCLE MODEL
      4.2.2 SOFTWARE PROJECT LIFE CYCLE
      4.2.3 ORGANIZATIONAL PROCESS ASSETS
      4.2.4 SOFTWARE PROJECT LIFE CYCLE PROCESS
  4.3 MAPPING
      4.3.1 INSTANCE
      4.3.2 ITERATION
      4.3.3 INVOCATION
  4.4 INPUT/OUTPUT INFORMATION
      4.4.1 CONVENTIONS
      4.4.2 EXTERNAL INFORMATION
      4.4.3 GENERIC INFORMATION
      4.4.4 INFORMATION VERSUS DOCUMENTS
5 IMPLEMENTING THE STANDARD
  5.1 ESTABLISH THE REQUIREMENTS FOR A SOFTWARE PROJECT LIFE
      CYCLE PROCESS
  5.2 SELECT SOFTWARE PROJECT LIFE CYCLE MODEL
  5.3 DEVELOP SOFTWARE PROJECT LIFE CYCLE
      5.3.1 PLACE THE ACTIVITIES IN EXECUTABLE SEQUENCE
      5.3.2 DEVELOP AND JUSTIFY LIST OF ACTIVITIES NOT USED
      5.3.3 VERIFY THE MAP
  5.4 ESTABLISH SOFTWARE PROJECT LIFE CYCLE PROCESS
  5.5 VALIDATE SOFTWARE PROJECT LIFE CYCLE PROCESS
ANNEX A Software Project Life Cycle Activities
      A.1 Project Management Activity Groups
          A.1.1 Project Initiation Activities
                A.1.1.1 Develop Software Project Life Cycle
                        Process (Required)
                A.1.1.2 Perform Estimations (Required)
                A.1.1.3 Allocate Project Resources (Required)
                A.1.1.4 Define Metrics (Required)
                A.1.1.5 Determine Security Objectives (Required)
          A.1.2 Project Planning Activities
                A.1.2.1 Plan Evaluations (Required)
                A.1.2.2 Plan Configuration Management (Required)
                A.1.2.3 Plan System Transition
                A.1.2.4 Plan Installation
                A.1.2.5 Plan Documentation (Required)
                A.1.2.6 Plan Training
                A.1.2.7 Plan Project Management (Required)
                A.1.2.8 Plan Integration
                A.1.2.9 Plan Release Management
          A.1.3 Project Monitoring and Control Activities
                A.1.3.1 Manage Risks (Required)
                A.1.3.2 Manage the Project (Required)
                A.1.3.3 Identify SPLCP Improvement Needs (Required)
                A.1.3.4 Retain Records (Required)
                A.1.3.5 Collect and Analyze Metric Data (Required)
                A.1.3.6 Close Project (Required)
      A.2 Pre-Development Activity Groups
          A.2.1 Concept Exploration Activities
                A.2.1.1 Identify Ideas or Needs (Required)
                A.2.1.2 Formulate Potential Approaches (Required)
                A.2.1.3 Conduct Feasibility Studies (Required)
                A.2.1.4 Refine and Finalize the Idea or Need
                        (Required)
          A.2.2 System Allocation Activities
                A.2.2.1 Analyze System Functions
                A.2.2.2 Develop System Architecture
                A.2.2.3 Allocate System Requirements
          A.2.3 Software Importation Activities
                A.2.3.1 Identify Imported Software Requirements
                A.2.3.2 Evaluate Software Import Sources
                A.2.3.3 Define Software Import Method
                A.2.3.4 Import Software
      A.3 Development Activity Groups
          A.3.1 Software Requirements Activities
                A.3.1.1 Define and Develop Software Requirements
                A.3.1.2 Define Interface Requirements
                A.3.1.3 Prioritize and Integrate Software
                        Requirements
          A.3.2 Design Activities
                A.3.2.1 Perform Architectural Design
                A.3.2.2 Design Database
                A.3.2.3 Design Interfaces
                A.3.2.4 Perform Detailed Design
          A.3.3 Implementation Activities
                A.3.3.1 Create Executable Code
                A.3.3.2 Create Operating Documentation
                A.3.3.3 Perform Integration
                A.3.3.4 Manage Software Releases
      A.4 Post - Development Activity Groups
          A.4.1 Installation Activities
                A.4.1.1 Distribute Software
                A.4.1.2 Install Software
                A.4.1.3 Accept Software in Operational Environment
          A.4.2 Operation and Support Activities
                A.4.2.1 Operate the System
                A.4.2.2 Provide Technical Assistance and Consulting
                A.4.2.3 Maintain Support Request Log
          A.4.3 Maintenance Activities
                A.4.3.1 Identify Software Improvement Needs
                A.4.3.2 Implement Problem Reporting Method
                A.4.3.3 Reapply SPLCP
          A.4.4 Retirement Activities
                A.4.4.1 Notify User
                A.4.4.2 Conduct Parallel Operations
                A.4.4.3 Retire System
      A.5 Support Activity Groups
          A.5.1 Evaluation Activities
                A.5.1.1 Conduct Reviews (Required)
                A.5.1.2 Create Traceability Matrix
                A.5.1.3 Conduct Audits
                A.5.1.4 Develop Test Procedures
                A.5.1.5 Create Test Data
                A.5.1.6 Execute Tests
                A.5.1.7 Report Evaluation Results (Required)
                A.5.1.8 Confirm Security Accreditation (Required)
          A.5.2 Software Configuration Management Activities
                A.5.2.1 Develop Configuration Identification
                        (Required)
                A.5.2.2 Perform Configuration Control (Required)
                A.5.2.3 Perform Status Accounting (Required)
          A.5.3 Documentation Development Activities
                A.5.3.1 Implement Documentation (Required)
                A.5.3.2 Produce and Distribute Documentation
                        (Required)
          A.5.4 Training Activities
                A.5.4.1 Develop Training Materials
                A.5.4.2 Validate the Training Program
          A.5.4.3 Implement the Training Program
ANNEX B Glossary
ANNEX C Mapping Example
ANNEX D Information Mapping Template
ANNEX E Sample Software Project Life Cycle Models
ANNEX F Bibliography

Presents a process for creating a software project life cycle process (SPLCP). It is primarily directed at the Process Architect for a given software project. It is the function of the Process Architect to develop the SPLCP.

DocumentType
Draft
Pages
108
PublisherName
Institute of Electrical & Electronics Engineers
Status
Superseded
SupersededBy

IEEE 1058-1998 IEEE Standard for Software Project Management Plans
ISO/IEC 15408-2:2008 Information technology — Security techniques — Evaluation criteria for IT security — Part 2: Security functional components
IEEE 730-2014 IEEE Standard for Software Quality Assurance Processes
IEEE 1008-1987 IEEE Standard for Software Unit Testing
IEEE 828-2012 IEEE Standard for Configuration Management in Systems and Software Engineering
IEEE 1540-2001 IEEE Standard for Software Life Cycle Processes - Risk Management
IEEE 830-1998 IEEE Recommended Practice for Software Requirements Specifications
ISO/IEC 15408-3:2008 Information technology — Security techniques — Evaluation criteria for IT security — Part 3: Security assurance components
IEEE 1233-1998 IEEE Guide for Developing System Requirements Specifications
IEEE 1062-1998 IEEE Recommended Practice for Software Acquisition, 1998 Edition
IEEE 1490:2011 IEEE GUIDE - ADOPTION OF THE PROJECT MANAGEMENT INSTITUTE STANDARD - A GUIDE TO THE PROJECT MANAGEMENT BODY OF KNOWLEDGE
IEEE 12207.0-1996 IEEE/EIA Standard - Industry Implementation of International Standard ISO/IEC 12207:1995 (ISO/IEC 12207) Standard for Information Technology -- Software Life Cycle Processes
IEEE 1220-2005 IEEE Standard for Application and Management of the Systems Engineering Process
ISO 9001:2015 Quality management systems — Requirements
IEEE 1012-2012 IEEE Standard for System and Software Verification and Validation
IEEE 1063-2001 IEEE Standard for Software User Documentation
AS 3563.1-1991 Software quality management systems - Requirements
ISO/IEC 15408-1:2009 Information technology — Security techniques — Evaluation criteria for IT security — Part 1: Introduction and general model
IEEE 1219-1998 IEEE Standard for Software Maintenance
IEEE 829-2008 IEEE Standard for Software and System Test Documentation
ISO/IEC 15939:2007 Systems and software engineering Measurement process

Access your standards online with a subscription

Features

  • Simple online access to standards, technical information and regulations.

  • Critical updates of standards and customisable alerts and notifications.

  • Multi-user online standards collection: secure, flexible and cost effective.

Need help?
Call us on 131 242, then click here to start a Screen Sharing session
so we can help right away! Learn more