Requirements Engineering

Is user story mapping nothing more than good old business process analysis? Yes and no, says Dr. Andrea Herrmann and explains the differences.

Requirements Engineering nach IREB umfasst ein breites Spektrum an Aufgaben, die Sie mit objectiF RM bewältigen. Um die Anforderungen weiterzugeben, können Sie die Jira-Schnittstelle einsetzen.

Establishing baselines is an important task for requirements engineering. Why is that, and how do you establish baselines?

Rainer Wendt describes the new structures for agile principles of agile business anaysis with the concept of planning horizons.

Observation techniques like field observation, apprenticing and contextual inquiry are good development techniques in requirements engineering. What are some tips?

How does the role of agile coaches in businesses look today? And what would organizations be missing is they went without agile coaches?

Why do you want to specify products when you could just develop them? Seven reasons to renounce documentation.

A structured exchange of requirements among companies are not easy to arrange. The ReqIF standard in the OMG can help.

What should you pay attention to when developing usability requirements? What role does human performance capacities and perception play?

An interview with Rainer Wendt, president of the IIBA Germany Chapter, about becoming a business analyst and business analysis in the IIBA Germany chapter.

Solution Evaluation is the assessment of existing or new solutions before or after a business goes into operation. Read more about Solution Evaluation.

Find out how to develop systematic risk identifcation mechanisms in your projects so that you can manage and minize the risks you face regularly. 

Using a system footprint to visualize your system requirements and allow everyone on your team to stay informed of the big picture. 

Are there sustainable business models able to prove that the Internet of Things is not just a concept but an economically feasible trend?

Run-of-the-mill is a term that describes something that is of average quality, something that is mean, or cookie-cutter. But is it always a bad thing?

When eliciting requirements it is paramount to keep an eye on the context and on the background on which persons are creating requirements.

If you are busying yourself with stakeholders and their goals, a goal diagram might be an effective and easy way for you to visualize interdependencies.

How do you want to deliver good results if you do not know the goals of your stakeholders? Read what happens when you ignore stakeholders and their wishes.