Requirements Engineering

Perhaps you know the following situation.
Your customer has a certain conception of the product that they order from you. You also have a clear conception of the product you will realise due to discussions with your customer.
But what part do the future users play?
And are there maybe other interest groups?

Source: www.enabled.com.au/page.cfm/Profile/News/?context=1052&contentid=3510&method=display#bmk_3510

We offer support in such a scenario as explained above within the area Requirements Engineering. As impartial partners without any vested interest in the project result we bring onboard as many interest groups as possible from the start of the project, the so-called stakeholders (e.g. customers, final users, the "affected"). With the help of professional methods ALL involved parties find a common solution and therefore have almost the same appreciation of the future product. The comparatively small investment at the beginning of the project saves you the majority of the typical running changes during the project, which would have a far larger effect on time frameworks and budget of the project.

As a further consequence, this common understanding must also be documented in an appropriate way. Again, our experience can help: We can fall back on proven tools and methods for the production and administration of the requirements.

Finally the acquired requirements must still be validated in order to arrive at a consolidated version of the requirements, which corresponds to the common understanding. We can offer various methods e.g. peer reviews, moderated inspection meetings and the like as support with regard to this.

Now we have created a starting point for further activities. However, the work is still not done.

Further project steps include paying attention to the requirements and coordinating the resulting direction of the project. We are always available to offer you help and advice.

http://www.smart-systems.at/products/products_software_re_en.html