What do you propose as the best first steps to apply in pre-requirements system engineering? That is what are the steps to be taken, in your opinion, to validate system requirements? I have attached 2 of our/my published papers as an introduction to this question.
I'm not an expert, but the subject is of interest for me. Based on what the development team understands, they build a quick-n-dirty demo of the software and show it to the client. This approach is called rapid-throw-away-model approach. I cannot think any better way of
1. Engaging client
2. Get the requirements from him
An easy example is a personal webpage. The designer might spend hours asking questions, however, if he can just show the look and feel visually, the client can quickly come to the point.
Good. How would what you propose be inspected in order to assure its quality. How is the knowledge gained from either the prototype or the requirements proved to be accurate? Furthermore how can one discover the missing requirements if any derived? In general the 'client' is comprised on a wide variety of stakeholders.
But what you suggest might be quite adequate in the development of games, for example. In this case what is derived may be reasonably accurate with fewer missing necessities.
What else would you like to suggest?
David
One thing is for sure, you need an experienced systems engineer who from exp. knows what specifications went unanswered or were vague and tries to clarify them during the demonstration of the rapidly developed model. He must then re-write a user requirement statement (URS) and shared it with stakeholders. Based on the URS the project manager and systems eng need to chalk down a project charter. The charter is then signed by all the stakeholders in the project kick-off meeting. The charter paves the way for the project. Any changes required in the project would initiate a change request, which again needs to be reviewed and signed by all the stakeholders before it is initiated.
In the present days of economic difficult, the stakeholders/clients must learn to participate actively with development team they have selected, otherwise, they'd have to pay for a product that they never wanted in the first place.
Again, I'm not an expert, this is my personal opinion.
If you are interested perhaps a place to start for you would be o either go on line or get a requirements engineering book and study the Viewpoints Requirements Engineering Methodology.Let me know if you find it.
- Badges
- Science topic
- Similar topics
- Engineering
- Computer Engineering