# Information Systems Development Lifecycle: Key Standards and Models
The development lifecycle of information systems defines the sequence of stages from initial idea to decommissioning. It's a structured process that impacts development efficiency. For IT professionals, understanding lifecycle standards is critical for selecting the right approach based on the project.
The ISO/IEC 12207 standard describes software lifecycle processes without prescribing a rigid model. Processes are divided into:
- Primary: acquisition, supply, development, operation, maintenance.
- Supporting: project management, risk management, quality management, configuration management, verification, validation.
- Organizational: lifecycle management, infrastructure management, project portfolio management, HR, knowledge management, process improvement.
Advantages: clear separation of customer and supplier roles, ideal for audits. Disadvantages: bureaucracy, overly cumbersome. The ISO/IEC 15288 standard for systems engineering is built on it, covering software, hardware, and processes.
GOST 34.601-90: Sequence of Stages
GOST 34 governs the creation of automated systems, including information systems as integrated hardware-software solutions. The model includes 9 stages:
- Requirements formation for automated systems (survey, terms of reference).
- Concept development (R&D, variant selection).
- Technical specification.
- Preliminary design.
- Technical design.
- Working documentation.
- Commissioning (startup, testing).
- Maintenance.
- Completion of work.
Advantages: high manageability, legal precision for critical systems. Disadvantages: low flexibility, long cycles, incompatibility with Agile without adaptation. In practice, GOST 34 is used as a foundation, with iterations applied within stages.
Waterfall Model
A linear model with sequential execution of phases: requirements, design, implementation, verification, maintenance. Transition to the next phase only after completing the previous one.
Suitable for projects with fixed requirements: government contracts, security, aviation. Advantages: simple planning, budget control, clear roles. Disadvantages: inflexibility, risks from errors in requirements, late delivery of the product.
The model evolved from MIL-STD-498 and is used in hybrids with Agile within phases.
RUP: Iterative Framework
Rational Unified Process (RUP) is an adaptable framework with two dimensions:
- Phases: Inception, Elaboration, Construction, Transition.
- Disciplines: business modeling, requirements, analysis/design, implementation, testing, deployment.
Key practices:
- Iterative development focused on risks.
- Requirements and change management.
- Component-based architecture.
- Visual modeling (UML).
- Continuous quality control.
Iterations (2–6 weeks) produce increments. Advantages: balance of discipline and flexibility. Disadvantages: complexity for small projects, requires experience. It evolved into OpenUP and Agile Unified Process.
Agile Methodologies
Agile is a family of iterative approaches based on the Agile Manifesto. Principles:
- Working software as the primary measure of progress.
- Welcome changing requirements.
- Frequent deliveries (2 weeks to 2 months).
- Face-to-face conversation.
- Motivated teams.
Frameworks include:
- Organization: backlog, meetings, retrospectives.
- Requirements: prioritization, feedback.
- Engineering: CI/CD, TDD, refactoring.
- Estimation: story points.
Advantages: flexibility, early value delivery, team motivation. Disadvantages: risk of chaos without discipline.
Key Takeaways
- ISO/IEC 12207 defines processes for any model, ideal for contracts.
- GOST 34 ensures sequencing for automated systems, relevant in Russia for large projects.
- Waterfall for predictable tasks, often hybridized with Agile.
- RUP balances iterations and structure via UML and risk management.
- Agile dominates product development, focusing on value.
Model selection depends on context: criticality, scale, requirements volatility. Knowledge of standards enables process adaptation to the project.
— Editorial Team
No comments yet.