Differences

This shows you the differences between two versions of the page.

--- en:safeav:softsys:softmgmt [2025/04/24 15:04] – created pczekalski
+++ en:safeav:softsys:softmgmt [2025/10/17 12:22] (current) – agrisnik
@@ Line 1: / Line 1: @@
 ====== Software Lifecycle and Configuration Management ======
 {{:en:iot-open:czapka_b.png?50| Bachelors (1st level) classification icon }}
+====== Software Lifecycle and Typical Lifecycle Models ======
+The software lifecycle defines the complete process by which software is conceived, developed, deployed, maintained, and eventually retired. In the context of modern engineering — particularly for complex systems such as autonomous platforms, embedded systems, or enterprise solutions — understanding the lifecycle is essential to ensure quality, reliability, and maintainability. The lifecycle acts as a roadmap that guides project teams through stages of development and management. Each stage defines specific deliverables, milestones, and feedback loops, ensuring that the software evolves in a controlled, traceable, and predictable way ((Sommerville, I. (2016). Software Engineering (10th ed.). Pearson)).
+=== Definition ===
+“The software lifecycle refers to a structured sequence of processes and activities required to develop, maintain, and retire a software system.” — ((Pressman, R. S., & Maxim, B. R. (2020). Software Engineering: A Practitioner’s Approach (9th ed.). McGraw-Hill)) In other words, the lifecycle describes how a software product transitions from idea to obsolescence — incorporating all the engineering, management, and maintenance steps along the way. The lifecycle ensures:
+  * **Consistency:** A common framework for teams and stakeholders.
+  * **Quality assurance:** Enables verification and validation at each stage.
+  * **Traceability:** Establishes clear relationships between requirements, design, code, and tests.
+  * **Risk management:** Provides checkpoints to detect and correct issues early.
+  * **Scalability:** Supports integration of multiple teams, technologies, and versions.
+In regulated domains like aerospace, automotive, and medical devices, adherence to a defined lifecycle is also a legal requirement for certification and compliance (e.g., ISO/IEC 12207, DO-178C, ISO 26262).
+The main lifecycle models, Configuration management and configuration management tools are discussed in the following chapters:
+<WRAP excludefrompdf>
+      * [[en:safeav:softsys:lifecycles]]
+      * [[en:safeav:softsys:configuration]]
+      * [[en:safeav:softsys:configurationtools]]
+</WRAP>

en/safeav/softsys/softmgmt.1745507043.txt.gz · Last modified: 2025/04/24 15:04 by pczekalski