| Here we present a simplified Project
Manager’s view of what system engineering and requirements management may
be all about.
|Project Management Triangle
Project Managers understand the CTR triangle. The aim in every new
project is to do things better, faster and cheaper. In other words,
to do things in the right way.
|Systems Engineering 'Pyramid'
For complex and multi-disciplinary projects, teams of design and construct
engineers, project managers, business analysts and commercial controllers
are involved to deliver what the Customer/Client needs. The increasing
dynamics and interaction between people as system developers as well
as people as end-users of the engineering product (project) necessitates
a focus on ‘what is the right thing to do?’
The Q for Quality is the more complex element that needs to be at
the top of tetrahedron with the CTR base. Quality is defined as meeting
the Customer’s requirements. System engineering is the process of managing
stakeholders' requirements throughout the whole project life-cycle. It is
- Creating a shared vision of what the customer future business needs
are and what (technical and people/process management) opportunities
exist to address them in a cost-effective way;
- Giving visibility to the requirements among all the project teams
from inception to decommissioning;
- A top-down flowdown of requirements into logically-split and manageable
chunks, while making sure that interface issues are identified and would
not fall by the wayside;
- Providing traceability between requirements (what the Customer wants),
design (how we can satisfy the Customer needs), production (how to make
sure the integrated product works as intended) and delivery (when is
the project/product accepted by the Client to be complete and finished).
- Integrated design and production, also referred to as Concurrent Engineering
– Making sure that the design takes on-board all the …abilities factors,
e.g. operability, maintainability, constructability, dependability.