The system engineering is a rigorous and multidisciplinary method, which has for objective to create and achieve something (a product, a service, a system) which responds efficiently to needs of “everyone” all along it’s “throughout its life cycle”. It’s a method that includes 18 concepts, modeling languages, a specific approach and tools. It’s carried out from the needs and the requirements of the customer. A system done thanks to system engineering is formed of integrated elements so that they provide, by their interactions, services corresponding to the mission.
Field of application in companies:
The deployment of System Engineering is a change process, a mean to achieve corporate strategic objectives. Initiatives of System Engineering were initially implemented to develop large technology systems and complex products. They have proved applicable, both in more traditional industrial and engineering applications, than in the tertiary sector where they provide a rigorous approach to the engineering of complex organizations and their information systems.
The different concepts:
Concept 1: a system is an abstraction, a pure view of the mind to perceive and better understand what’s around us. If a problem generates needs so to all solutions of the problem, we must have an answer brought by the system.
Concept 2: a system is defined by concept of Purpose, Mission and Objectives. In fact, purpose justifies the existence of the system (allows to…), mission expresses the main functions of the system and finally, objectives are evaluations of the missions fulfilled the system. We haven’t not confused constraint and objectives. In fact, a constraint is imposed while an objective it’s a goal to be achieved.
Concept 3: any system has a life cycle from the editor of need to withdrawal of system services. The steps of this life cycle are defined by milestones. At each milestone, we need to define who needs it, who is concerned and who is involved. This brings us to the next concept.
Concept 4: the system is about people and organizations at each step of the life cycle. These people and these organizations express their needs, we call them stakeholders.
Concept 5: the system to be realized is part of an over-system. However, you have to be careful because the purpose of our system can be linked to the mission of over-system and his objectives can be declined from those of over-system.
Our system is relative to a subsystem but also with compared to subsystems. We model this by hierarchical diagrams.
Concept 6: the Interfaced Systems are systems belonging to the over-system and who interact with our system.
Concept 7: among the Interfaced Systems, there are Enabling Systems. Those are systems that allow our system to exist or to be kept in operational operation. For example, the maintenance system, the production system…
Concept 8: the system exchanges services with Interfaced Systems to succeed in his mission. At each service corresponds to a function, a flow (data flow or energy flow), a physical links which transfers these flows and finally interfaces.
Concept 9: the system will evolve in operational contexts that can be different at each stage of the life cycle. We model it with context diagram which represents the different flows and Interfaced Systems.
Concept 10: at every moment, the system is in an operational mode. The system evolves from one mode to another through transitions. We model it with mode diagram.
Concept 11: at each mode, the behavior of the system is described by operational scenarios.
Concept 12: the system is a solution to a problem. So we must define this problem with the needs and the requirements. (Refer to the article on the requirements).
Concept 13: the system is part of over-system; he concerns people and organizations (stakeholders), he requires services provided by other systems (Enabling Systems), he interacts with Interfaced Systems and finally he is decomposable into subsystems or components.
Concept 14: the system is characterized by architectures in order to control its complexity by breaking it down into functions. There are two types of architectures: functional architectures and organic architectures. (Refer to the article on the architectures).
Concept 15: there are also context architectures gathering all the information collected by the other concepts.
Concept 16: functional architecture (Refer to the article).
Concept 17: organic architecture (Refer to the article).
Concept 18: the last concept is : a system is driving or must drive.
and now on to the next subject. [ https://mkxprojet.wixsite.com/website/post/cea-partnership-and-rica-presentation ]
Comments