How to use Systems & Requirements Engineering to help with complex and simple engineering problems in everyday life and not just in computer programming.
What techniques can be integrated into the analysis in the problem domain that can help to obtain the outline of the problem and indicate possible technical solutions?
Any contribution is always welcome!
As per my understanding of your question. There are many AI and statistical algorithms that can be used to solve the real life applications:
Marketing,
superstore management system
Internal management system of a company
Banking systems
etc.
Hello Filipe Wiltgen ,
I was once involved with an effort to develop NII (Non-Intrusive Inspection) systems for the screening of cargo containers at ports of entry. Our group of companies was a contractor to the US goverment in this effort, and we had a chief systems engineer, whose job was to interface with customer.
It did not go well, the customer did not know and/or understand the systems engineering jargon, and the chief systems engineer would not or could not make himself understood; he was eventually removed from the project. This was an inter-organizational failure, but there were also intra-organizational failures.
NII system had been developed for about twenty years before our particular project started, and some of it had been tested and deployed at ports of entry. But neither the contractor nor the customer deeply immersed themselves in the history of these earlier efforts. Thus, they were unaware of problems with and successes of the testing that had been done previously. Instead of learning from history, both the contractor and the customer thought that they could do their testing better than those who had come before them. Additionally, both the contractor and the custimer thought that they understood the workings and restrictions of the end users at the ports of entry - they did not.
Regards,
Tom Cuff
Dear Thomas Cuff ,
This case that he told is precisely the great difficulty of the insertion of science in industry. Believing in experience of other researchers and walking path, without having to build new paths not "paved", which almost always leads to failure.
Here in Brazil I participated in a similar customs governmental project to analyze container ships via x-ray with AI. However, there was nothing and we rolled up our sleeves and did research, development and installation since 2008.
As you had the background it would have been even easier to install and use, if those involved had understood problem (problem domain).
The Systems & Requirements Engineering team, always has an arduous task to match the needs of project, with the wishes of stakeholders.
I tend to joke that it's like teaching kindergarten kids to use quantum physics! Kkkkkk!
It is not easy!
I am sad that you have not been successful with this project.
Thank you for sharing your description and showing us how we should always look at past, so as not to make same mistakes in the future!
Thank you very much for your invaluable contribution to this debate.
Best Regards,
Wiltgen
Dear Zahoor Ahmed ,
It is not about AI, but how to deal with problem domain in Systems & Requirements Engineering in real and non-computational problems.
Most people think that Systems & Requirements Engineering is for computer engineering, this is far from true.
AI is a mathematical way of simulating knowledge in a computational algorithm, here is the knowledge of a problem translated into requirements that may or may not become a technical solution, and of any nature, and in any type of system, including AI if so where appropriate. However, it goes much deeper than that.
The discussion is about understanding and analyzing the problem and not the solution. In other words, it is left side of the V model and not right.
Thank you very much for your contribution.
Regards,
Prof. Wiltgen
In fact, this is a multifarious issue that encompasses a number of aspects for engineering design and development.
It includes:
- comprehending stakeholder requirements (functional, performance, operational, usability, design constraints, costs, etc.) and peculiarities and translating them into system concept and architecture development
- conceptualization of the requirements
- development process design
- validation and traceability of the development stages and outcomes
...
- Badges
- Science topic
- Similar topics
- Engineering