Systems engineering is:
"Big Picture thinking, and the application of Common Sense to projects;”
“a structured and auditable approach to identifying requirements, managing interfaces and controlling risks throughout the project lifecycle.”
“Build the right system; build the system right”.Systems engineering considers the whole problem, the whole system, and the whole system lifecycle from concept to disposal, “from lust to dust”
The V lifecycle model shows the logical relationship between the different systems engineering activities or ‘processes’.
Understanding the Problem
Understand and write down the benefit to be achieved by the system, and how the system will be used. Identify the key measures of operational effectiveness (MOEs), and work out how much improvement you expect from the new system. Identify the stakeholders and agree the system boundary.
Think! How will the environment change betweennow and when the system is ready? And how will the environment and end users respond to the new system?
Investigate alternative solutions
Consider, model and evaluate both novel solutions and improvements to existing ones. Work out how you will choose between the alternatives; and record your decision process and rationale in case things change later and you need to back-track. Define a system architecture that encompasses all elements of the solution.
Prepare the test and support systems
Prepare the test, training and support capabilitiesin parallel with the “operational system”. Makesure they are all compatible and ready when theyare needed to test, commission, deploy and use the system.
Agree and manage the requirements
Requirements form the basis for contracts and acceptance. Starting from the desired effect of the new system, balance requirements with budget and technical feasibility. Identify and consult relevant stakeholders. Identify and manage assumptions. Assess impact of proposed changesand trade-offs. And test the system against its requirements.
Agree and manage the interfaces
Manage interfaces to make sure the parts of the solution combine with each other and the operational environment to create an effective whole – and to allow teams to work in parallel confident that all the pieces they are developing will fit together and work together. Identify who is responsible for and involved in each interface.
Track progress against a plan
As well as the traditional project management measures of cost, schedule and resources, it is important to track skills, decisions and technical performance. Adapt to changes and be prepared to backtrack on decisions. Failure to agree requirements or interfaces may be symptoms of deeper problems.
Systems Engineering does:
- - cope with complexity. The benefits of systems engineering include not being caught out by omissions and invalid assumptions, managing real world changing issues, and producing the most efficient, economic and robust solutions to the need being addressed.
By using the Systems Engineering approach, project costs and timescales are managed and controlled more effectively by having greater control and awareness of the project requirements, interfaces and issues and the consequences of any changes.”
Systems engineers work with programme managers to achieve system and project success. Research indicates that effective use of systems engineering can save 10-20% of the project budget.
It is not hard to know when system engineering fails, because when something important goes wrong it usually makes the news fast. People get killed, buildings fall down, companies go bust, the law becomes involved.
But when system engineering goes right, no-one notices - which is just how it should be. The computer works when you switch it on, trains run on time, your flight lands on time and no one gets mad.
The International Council on Systems Engineering (INCOSE) defines systems engineering as “an interdisciplinary approach and means to enable the realisation of successful systems. - -”
UK members were asked what this definition means to them. This leaflet collates the best of these answers into an explanation of the what and why of systems engineering.
Systems Engineering IntegratesTechnical Effort
Across the Development Project :
> Functional Disciplines
> Technology Domains
> Specialty Concerns
This leaflet is intended to help the “intelligent layperson” to understand what systems engineering is and how it could help them and their business.
Half of all project failures could be prevented by more effective systems engineering
More than one in three of all projects will fail. More than two-thirds will not achieve all their aims. Failure is usually obvious only when the project is overdue and the budget has been spent. But decisions and plans made earlier in the project can alter your risk, sometimes dramatically.
Leaflet prepared and published by the UK Chapter of the International Council on Systems Engineering.
With contributions from:
- Timothy Cusk - Network Rail;
- Mark Lewis – Scott Wilson;
- Steve Fielding - Metronet Rail SSL Ltd;
- Jim Brunton – Managed - Complexity;
- Colin Brain – SE Validation;
...and the “Z1 project team”; Ayman El-Fatatry, Ken Astley (SEIC) Samantha Brown (BAE SYSTEMS); Les Oliver (EADS Astrium), Paul Davies and Hillary Sillitto, (Thales); Hazel Woodcock, (Telelogic); and review comments from other UK Chapter Members
All quieries should be addressed to the series editor Hazel Woodcock