• 33    System purpose
• 33.1    Introduction
• 33.2    Why do this?
• 33.3    Different kinds of projects
• 33.4    Investigating purpose
• 33.5    Competition
• 33.6    Defining scope
• 33.7    Artifacts
• 33.8    Validating purpose
• 33.9    Review milestone
• 33.10    Change of purpose
• 33.11    Using purpose
• 34    System concept
• 34.1    Introduction
• 34.2    Why build a concept?
• 34.3    What a concept is and is not
• 34.4    Developing the concept
• 34.5    Artifacts
• 34.6    Feedback to system purpose
• 34.7    Validating concept
• 34.8    Reviews and approval
• 34.9    Changing the concept
• 34.10    Using the concept
• 35    Proposals
• 35.1    Introduction
• 35.2    What is a proposal?
• 35.3    Work flow for a project with a proposal
• 35.4    Artifacts summary
• 36    Specifications
• 36.1    Purpose
• 36.2    Theory of specification
• 36.3    Specifications and systems
• 36.4    Example
• 36.5    Kinds of specifications
• 36.6    Using specifications in a system
• 36.7    Using specifications for a component
• 36.8    Specification artifacts
• 37    Requirements
• 37.1    What are requirements?
• 37.2    A single requirement
• 37.3    Multiple requirements
• 37.4    Organizing requirements
• 37.5    Writing good requirements
• 37.6    Requirement derivation
• 37.7    Advanced requirements
• 37.8    Analyzing requirements
• 37.9    Validating requirements
• 37.10    Verification
• 37.11    Limitations of requirements
• 37.12    Working with requirements
• 37.13    Tools
• 38    Models
• 39    Interface definitions

The first part of the life cycle: purpose, concept, and specification.