How do you make Systems Engineering more user-friendly?

A significant challenge in creating effective systems is that people from different engineering fields might not always comprehend each other due to their diverse engineering backgrounds. For instance, I faced difficulties understanding various aspects of pressure and fluid mechanics while working on an advanced dialysis system, coming from an electronics background. This was due to the system's electrochemical nature. What greatly assisted me was when a colleague used visuals like pictures, diagrams, and symbols to illustrate how the system is structured, its functions, and the interactions between its components. It's crucial to establish a shared, clear, and consistent way of communication throughout the system development process.

First and foremost SE is about getting things properly joined up and getting the problem in hand defined properly before diving off into solution mode. Everyone wins when this starts to happen because more things get done right first time, less effort gets wasted and teams start working together in a truly collaborative way. This can all be achieved without forcing people into tooling decisions upfront, that is the icing on the cake, get the key ingredients for success sorted first.

Clarity on definition, specification and use of terminology with a view to reduce or eliminate ambiguity is key. Keeping a simple and concise nomenclature and glossary of terms whilst building on known concepts is key to allow effective interaction with other disciplines of engineering.

Systems are only meaningful if the system delivers value to the end-user. To this, clarity on system purpose, intention and user needs needs can allow even complex systems basis of design to be traced back to the value to the user and user interaction requirements.

To enhance user-friendliness in software engineering (SE), adopt a method that puts the user's needs, likes, and feedback first. Keep the user involved in every SE stage. My team and I encountered a similar situation where we had to reconsider our design. While working on a medical device used by older or ill patients who had limited wrist strength due to treatment, we faced an issue. The treatment prep required users to change the inlet tubing, which involved lifting a lid with force, inserting a tube, and sealing the lid – all with limited strength. Realizing this was too demanding for patients already dealing with their health, we completely revamped the inlet system. This could've been prevented with an initial user-focused approach.

To enhance user-friendliness in software engineering, consider employing agile techniques that promote flexibility, adaptability, and teamwork throughout the process. When all the teams are aware of the progress and hurdles in the development process it always translates to a faster delivery in the long run.

This thinking approach prevents limited viewpoints, makes complicated things simpler, and improves the system's overall effectiveness. When you see the system's creation as a complete thing, involving various engineering fields, it becomes easier to find and fix mistakes. Knowing where to search and understanding the entire process helps. A skilled systems engineer should be familiar with tasks like designing, writing, and conducting tests – all essential steps.

Based on what I've learned, systems engineering is a tight-knit and highly cooperative area. Experienced people in this field are usually eager to help if you just reach out. I was lucky to have fantastic mentors who patiently guided me through the essentials when I started my job. As time went on and I gained experience, I was excited to pass on my knowledge and help others who approached me with inquiries.

Maybe read a book on system safety and system assurance to understand how to develop life cycle requirements based upon risk, which are stakeholders needs?