Requirements Management White Papers

“Method H” ™ is a new and simple technique for business analysis. Business Analysts can use it to improve communication with users and get requirements in a clear, comprehensive format.

This white paper describes what data normalisation is all about and why users need to understand the subject. It also covers how to create a logical data model.

When it comes to requirement gathering for development of software system, a lot of software writers and analysts follow the age-old processes wherein the needs of the customers are given priority. TOPE is based on the fact that needs arise because of problems. This process tips conventional approaches upside down.

Business driven IT is the goal of most organisations. The implementation is often more difficult than expected. This white paper covers a number of examples explaining how it can be achieved.

Although requirements may be thoroughly documented, sometimes the solution is not considered a success. The product delivered at the end may not result in the solution the customer has in mind. Find out how to manage both requirements and stakeholders.

Keeping track of changing requirements is often forgotten. It is only when something goes wrong and the wrong specs are used that traceability becomes an issue. Learn how to manage requirements and why it is important to have traceability.

Ever wondered what business process modeling was all about, and how it fitted with IT development? Read this article for an overview of the subject including some examples.

JAD or any other Workshop approach will function far more smoothly if there is a facilitator. This paper outlines what the facilitator should contribute.