Reflections Assignment

Model-Based Systems Engineering
After reading chapter 13 “Model-Based Systems Engineering (MBSE)”, I gained the
knowledge of the main idea was to transform the systems engineering approach from
“document-centric” to “model-centric.” Hence, the systems engineer would develop models of
the system instead of documents. MBSE can help to capture all the information from the
different phases and share that information with the designers and other stakeholders. Modern
MBSE tools provide the means for this sharing, as long as the tool is easy for everyone to use.
Model-Based systems engineering (MBSE) provides several advantages over document-based
engineering, including Optimized communication and sharing of information, Simpler change
management, Increased traceability and improved efficiency, productivity and quality. I haven't
utilized the Model-Based Systems Engineering (MBSE) topic in the actual world, therefore it is
new to me. I'm interested in learning more about this subject, particularly how model-based
systems engineering (MBSE) operates and examples of its use in system design and operation.

Lean, Iterative and Agile methods applied to Systems Engineering
The most interesting learning in this chapter was the evolution of life cycle models from
with traditional methods Waterfall life cycle to Agile including Lean life cycle to work more
efficiently and provide better outcomes more quickly and reliably. In Waterfall / Traditional Life
Cycle development, the systems are considered fully specifiable and predictable and can be
built through extensive planning. In contrast, in agile development, the systems have high-
quality, adaptive software that can be continuously developed and improved in small teams,
with rapid testing and feedback. The control mechanisms for the traditional methods are
process centered, while agile control is performed by people The communication for a
traditional approach is formal versus informal for the agile method. The customer is important
in identifying and validating requirements for the traditional approach but considered critical in
the agile method Agile development is a team-based approach that emphasizes rapid
deployment of a functional application with a focus on customer satisfaction. There are7 main
Agile methodologies: 1-Scrum,2- Lean (including Kanban) ,3- Extreme Programming (XP), 4Crystal,5- Dynamic systems development method (DSDM),6- Feature-driven development
(FDD),7- Rapid application development (RAD)
Scrum: A framework can address complex adaptive problems to deliver high-quality
products, quickly with highest value .Lean (including Kanban): A methodology focused on
reducing waste and improving the productivity and speed of processes and projects. The Lean
tools include Value Stream Mapping, Value analysis, Waste analysis, Why-why diagram, 5S and
visual management ,Kaizen ,Flow, Pull, and Kanban ,Mistake proofing ,Standard work and
Systems . Extreme Programming (XP): An agile software development framework applying
engineering practices for software development. Crystal: An agile software development
approach focusing mainly on people and their interactions, rather than processes and tools.
Dynamic systems development method (DSDM): An agile project delivery framework that is
both iterative and incremental, incorporating agile methods and principles including continuous
customer involvement. Feature-driven development (FDD): An agile software development
methodology focusing on product features. Rapid application development (RAD): An agile
software development methodology that focuses on rapid prototype releases and iterations.
In this chapter, I would want to understand more specifics about Agile methodologies
and Lean with examples. One of the methods I've used in the actual world of business is 5S. The
5S method was used to decrease waste in the office and workshop at my former job in the auto
industry. We established 5S teams for each area and documented the implementation
methods. We also have a regular auditing schedule to ensure the system is functioning
effectively.

People skills, teamwork, communication, culture and change management applied to systems
engineering
The most fascinating lesson from this chapter was the significance of change
management as a teamwork skill in systems engineering. The engineering practice is dynamic in
nature, increasing in complexity, enhancing in Connectivity, and growing in need for
convergence among disciplines. Given the shift in the nature of problems and solutions, there is
an opportunity within Systems Engineering for transforming into a Trans disciplinary discipline
Change management draws on theories from many disciplines, including culture ,psychology,
behavioral science, engineering, and systems thinking. A central idea of all change management
theories is that no change ever happens in isolation. The most critical first step of any change
program is for top management to define the purpose of the program, develop the vision, the
systems engineering program vision and develop the core values of the systems engineering
organization. The modeling vision should be aligned with the culture. The core values of the
modeling organization can be compared to the core values of the company to assess how well
they are aligned. The organization must develop the life cycle methodology for modeling and
systems engineering that they will follow to plan and develop the models. Beyond the technical
abilities of systems engineering, it is crucial for the systems engineer to develop vital people,
communication, facilitation, and leadership skills in order to succeed. Since teams of
professionals are needed to design and develop systems, relationship-building and people
abilities including Teamwork and teambuilding skills are among the most crucial.
I would like to learn in this chapter how evaluate the change Progress and Analyze
Results successfully. In my previous job in car manufacture as environmental engineering,
People skills, teamwork, communication, culture and change management one of the most
topics to establish, implement, maintain and improve an environmental management system.
For reaching to those goals we establish procedure for skills, responsibility and communication.
We created different teams for each part of Environmental Management System. In
Environmental Management System, we had to ensure that our objectives were designed to
meet cultural and societal situations.