Effective Requirements Elicitation
Customer requirements are not random. But we often receive a seemingly random set of requirements, and it is our task to make sense of them - to see the "big picture". This can be achieved in many ways, of which the least painful is a structured approach, in which all the information is transformed into an MBSE model. The underlying semantic graph of the framework used for the elicitation guarantees that all information elements stored in the model are by definition strictly typed, consistent, logically connected and fully traceable. It can be easily combined to (re) produce the ideal big picture for any perspective requested by you, your team or any of your other stakeholders. It can even be presented in its original random arrangement should your customers prefer it that way. But typically you won't go back, once you've seen the value a trustworthy, well-structured, queryable and robust information base for your development projects.
Marco has had many roles in Systems Engineering: Professor at a technical university, Consultancy and Work in the development of complex systems for large scale research programmes and automotive innovation projects. He used to be a professor of SE and is now Trainer, Consultant, and Coach. Marco is an expert in model-based systems engineering and information modelling. He has developed an MBSE Architectural Framework and methodology and a keen interest in Reverse Architecting of real Systems.