IEEE HomeSearch IEEE ShopWeb Account Contact IEEE IEEE
MembershipPublicationsServicesStandardsConferencesCareers/Jobs
IEEE-SA IEEE-SA Member Area Search our standards database for Abstract, Sponsor, Status, Contact,Ordering and Historical information. IEEE-SA Standards Association
Products & ServicesIEEE-SA MembershipStandards DevelopmentNews & InformationnavFillerHOMEHOME Icon

IEEE Std 1220-1994 IEEE Trial-Use Standard for Application and Management of the Systems Engineering Process -Description

Abstract: The interdisciplinary tasks that are required throughout a system's life cycle to transform customer needs, requirements, and constraints into a system solution are defined. This standard applies to a performing activity within an enterprise that is responsible for developing a product design and establishing the life cycle infrastructure needed to provide for life cycle sustainment. It specifies the requirements for the systems engineering process and its application throughout the product life cycle. The requirements of this standard are applicable to new products as well as incremental enhancements to existing products.

Keywords: enterprise, Systems Engineering Detailed Schedule (SEDS), Systems Engineering Management Plan (SEMP), Systems Engineering Master Schedule (SEMS), systems engineering process

Content +

  • 1. Overview
    • 1.1 Scope
    • 1.2 Purpose
    • 1.3 Understanding this standard
    • 1.4 Organization of this standard
  • 1. References
  • 3. Definitions and acronyms
    • 3.1 Definitions
    • 3.2 Acronyms
  • 4. General requirements
    • 4.1 Systems engineering process
    • 4.2 Policies and procedures for systems engineering
    • 4.3 Planning the technical effort
      • 4.3.1 Systems Engineering Management Plan (SEMP)
      • 4.3.2 Systems Engineering Master Schedule (SEMS)
      • 4.3.3 Systems Engineering Detailed Schedule (SEDS)
      • 4.3.4 Technical plans
    • 4.4 Evolutionary development strategies
    • 4.5 Modeling and prototyping
    • 4.6 Integrated database
    • 4.7 Product and process data package
      • 4.7.1 Hardware
      • 4.7.2 Software
      • 4.7.3 Life cycle processes
    • 4.8 Specification tree
    • 4.9 Drawing tree
    • 4.10 System Breakdown Structure (SBS)
    • 4.11 Integration of the systems engineering effort
      • 4.11.1 Concurrent engineering
      • 4.11.2 Integrated teams
    • 4.12 Technical reviews
    • 4.13 Quality management
    • 4.14 Continuing product and process improvement
      • 4.14.1 Re-engineering
      • 4.14.2 Self assessment
      • 4.14.3 Lessons learned
  • 5. Application of systems engineering throughout the system life cycle
    • 5.1 System definition stage
      • 5.1.1 System definition
      • 5.1.2 Specifications
      • 5.1.3 Configuration baselines
      • 5.1.4 Technical reviews
    • 5.2 Preliminary design stage
      • 5.2.1 Preliminary subsystem definition
      • 5.2.2 Subsystem specifications
      • 5.2.3 Configuration baselines
      • 5.2.4 Technical reviews
    • 5.3 Detailed design stage
      • 5.3.1 Detailed subsystem definition
      • 5.3.2 Specifications
      • 5.3.3 Configuration baselines
      • 5.3.4 Technical reviews
    • 5.4 Fabrication, Assembly, Integration, and Test (FAIT) stage
      • 5.4.1 System integration and test
      • 5.4.2 Analyze, fix, and retest
      • 5.4.3 Project and technical plans
      • 5.4.4 Specifications
      • 5.4.5 Configuration baselines
      • 5.4.6 Technical reviews
    • 5.5 Production and customer support stages
      • 5.5.1 System products
      • 5.5.2 Technical reviews
      • 5.5.3 Customer support
      • 5.5.4 System evolution
    • 5.6 Simultaneous engineering of products and services of life cycle processes
      • 5.6.1 Life cycle process product and service development
      • 5.6.2 Specifications
      • 5.6.3 Baselines
  • 6. The systems engineering process
    • 6.1 Requirements analysis
      • 6.1.1 Customer expectations
      • 6.1.2 Project and enterprise constraints
      • 6.1.3 External constraints
      • 6.1.4 Operational scenarios
      • 6.1.5 Measures of effectiveness (MOE)
      • 6.1.6 System boundaries
      • 6.1.7 Interfaces
      • 6.1.8 Utilization environments
      • 6.1.9 Life cycle process concepts
      • 6.1.10 Functional requirements
      • 6.1.11 Performance requirements
      • 6.1.12 Modes of operation
      • 6.1.13 Technical performance measures
      • 6.1.14 Physical characteristics
      • 6.1.15 Human factors
      • 6.1.16 Requirements baseline
    • 6.2 Requirements validation
      • 6.2.1 Customer expectations
      • 6.2.2 Enterprise and project constraints
      • 6.2.3 External constraints
      • 6.2.4 Variances and conflicts
      • 6.2.5 Validated requirements baseline
    • 6.3 Functional analysis
      • 6.3.1 Functional decomposition
      • 6.3.2 Functional behaviors
      • 6.3.3 Subfunction states and modes
      • 6.3.4 Functional time line
      • 6.3.5 Data and control flows
      • 6.3.6 Functional failure modes and effects
      • 6.3.7 Hazard monitoring functions
      • 6.3.8 Functional architecture
    • 6.4 Functional verification
      • 6.4.1 Verification procedures
      • 6.4.2 Verification evaluation
      • 6.4.3 Variances and conflicts
      • 6.4.4 Verified functional architecture
    • 6.5 Synthesis
      • 6.5.1 Group and allocate functions
      • 6.5.2 Physical solution alternatives
      • 6.5.3 Safety and environmental hazards
      • 6.5.4 Life cycle quality factors
      • 6.5.5 Technology requirements
      • 6.5.6 Physical and performance characteristics
      • 6.5.7 Physical interfaces
      • 6.5.8 Standardization opportunities
      • 6.5.9 Off-the-shelf availability
      • 6.5.10 Make or buy alternatives
      • 6.5.11 Models and prototypes
      • 6.5.12 Failure modes, effects, and criticality.
      • 6.5.13 Testability needs
      • 6.5.14 Design capacity to evolve
      • 6.5.15 Design
      • 6.5.16 Evolutionary development
      • 6.5.17 Drawings and schematics
      • 6.5.18 Physical architecture
    • 6.6 Physical verification
      • 6.6.1 Verification approach
      • 6.6.2 Verification evaluation
      • 6.6.3 Variances and conflicts
      • 6.6.4 Verified physical architecture
      • 6.6.5 Verified life cycle process physical architectures
      • 6.6.6 Verified system architecture
      • 6.6.7 Establish specifications and configuration baselines
      • 6.6.8 Develop system breakdown structure
    • 6.7 Systems analysis
      • 6.7.1 Requirement conflicts
      • 6.7.2 Functional alternatives
      • 6.7.3 Solution alternatives
      • 6.7.4 Risk factors (identify)
      • 6.7.5 Trade study scope
      • 6.7.6 Trade study
      • 6.7.7 Risk handling option
      • 6.7.8 Alternative recommendation
      • 6.7.9 Trade-offs and impacts
      • 6.7.10 Solution effectiveness assessment
    • 6.8 Control
      • 6.8.1 Design capture
      • 6.8.2 Technical management
      • 6.8.3 Systems analysis and test data
      • 6.8.4 Requirement and design changes
      • 6.8.5 Progress against project plans
      • 6.8.6 Progress against technical plans
      • 6.8.7 Product and process metrics
      • 6.8.8 Specifications and configuration baselines
      • 6.8.9 Requirements views and architectures
      • 6.8.10 Project plans
      • 6.8.11 Technical plans
      • 6.8.12 Integrated database.
    • A.1 The systems engineering process
    • A.2 Systems engineering internal to an enterprise
      • A.2.1 Market opportunity
      • A.2.2 New technological advances
      • A.2.3 Project environment
      • A.2.4 Enterprise environment
      • A.2.5 External environment
      • A.2.6 Products
    • A.3 The systems engineering problem and solution space
    • B.1 Systems Engineering Management Plan (SEMP) template
    • B.2 SEMP structure

links: [Standard Status] - [Purchase] - [PDF*] - [Software Engineering Collection - Description]

available for Standards Online Software Engineering Collection subscribers only

spacer

Copyright ©2004 IEEE-SA
Contact IEEE-SA
(m.v.rodriguez@ieee.org)
URL: http://standards.ieee.org/reading/ieee/std_public/description/se/1220-1994_desc.html

spacer