Systems and software lifecycle engineering SLEN
(unchanged)
Establishing and deploying an environment for developing, continually improving and securely operating software and systems products and services.
Guidance notes
(modified)
This skill involves establishing and evolving the working practices and supporting environment used to develop and operate software and systems across their entire lifecycle. It is commonly associated with terms such as DevOps, DevSecOps, site reliability engineering and developer productivity engineering.
It focuses on integrating technical practices, collaborative methods, automation and lifecycle processes. It is distinct from the development, integration, testing, deployment and operational activities performed using these practices and environments. Lifecycle practices and environments are developed and evolved collaboratively with the practitioners and teams that use them.
Activities include, but are not limited to:
- establishing secure, reliable software lifecycle practices
- developing a supporting framework of methods, tools, processes, procedures and skilled personnel
- deploying and evolving this environment with teams responsible for developing and operating software and systems
- building repeatable, reliable capabilities through trial, feedback, learning and continual evolution
- adapting practices to specific products and services
- defining, controlling and improving lifecycle processes
- incorporating risk management, quality, security, privacy and safety
- maximising automation
- establishing architecture and design principles to support lifecycle processes
- focusing on mission, value and customer needs
- cultivating a culture of collaboration, learning, adaptation and resilience
- integrating industry frameworks to guide improvements.
Understanding the responsibility levels of this skill
Where lower levels are not defined...
- Specific tasks and responsibilities are not defined because the skill requires a higher level of autonomy, influence, and complexity in decision-making than is typically expected at these levels. You can use the essence statements to understand the generic responsibilities associated with these levels.
Where higher levels are not defined...
- Responsibilities and accountabilities are not defined because these higher levels involve strategic leadership and broader organisational influence that goes beyond the scope of this specific skill. See the essence statements.
Developing skills and demonstrating responsibilities related to this skill
The defined levels show the incremental progression in skills and responsibilities.
Where lower levels are not defined...
You can develop your knowledge and support others who do have responsibility in this area by:
- Learning key concepts and principles related to this skill and its impact on your role
- Performing related skills (see the related SFIA skills)
- Supporting others who are performing higher level tasks and activities
Where higher levels are not defined...
- You can progress by developing related skills which are better suited to higher levels of organisational leadership.
Click to learn why SFIA skills are not defined at all 7 levels.
Show/hide extra descriptions and levels.
Level 1
Level 2
Systems and software lifecycle engineering: Level 3
(unchanged)
Provides support for implementing systems and software lifecycle practices by applying established methods and procedures.
Supports automation and continuous integration processes under direction.
Monitors and reports on the effectiveness of lifecycle management activities.
Contributes to the documentation and maintenance of lifecycle tools and practices.
Systems and software lifecycle engineering: Level 4
(unchanged)
Elicits requirements for systems and software lifecycle working practices and automation.
Prepares design options for the working environment of methods, procedures, techniques, tools and people.
Selects systems and software lifecycle working practices for software components and micro-services.
Deploys automation to achieve well-engineered and secure outcomes.
Systems and software lifecycle engineering: Level 5
(modified)
Leads the collaborative selection, adoption and adaptation of systems and software lifecycle working practices with the teams that use them.
Plans and coordinates deployment of the engineering environments and supporting capabilities for systems and software lifecycle working practices.
Guides teams in applying and improving lifecycle practices.
Identifies opportunities to extend or adapt lifecycle practices and supporting capabilities to new products, services or domains.
Systems and software lifecycle engineering: Level 6
(unchanged)
Obtains organisational commitment to strategies to deliver systems and software lifecycle working practices to achieve business objectives.
Works with others to integrate organisational policies, standards and techniques across the full software and systems lifecycle.
Develops and deploys the working environment supporting systems and software lifecycle practices for strategic, large and complex products and services.
Leads activities to manage risks associated with systems and software lifecycle working practices. Plans and manages the evaluation or assessment of systems and software lifecycle working practices
Systems and software lifecycle engineering: Level 7
(unchanged)
Represents and leads systems and software lifecycle working practices at the highest level in the organisation.
Identifies opportunities for innovation in systems and software lifecycle working practices to achieve organisational goals and objectives.
Leads the essential cultural and environmental changes and communicates the benefits to all stakeholders.
Oversees the quality of the work performed and delivers measurable business benefits.