Requirement Engineering

Static or Dynamic requirements Introduction

Scope creep is not something to be feared — it is something to be removed from the equation. Fortunately, the process by which you can be confident of avoiding scope creep also enables you to provide a top-quality service for the client in terms of assessing their needs and providing a solution that should deliver to a more than satisfactory standard.

Every project manager knows that you need the right information to make your project a success. Vital information such as a projects requirements, client’s expectations and assumptions and understanding the risks are all a key part of the planning process.

Non-Functional Requirement (NFR) specifies the quality attribute of a software system.

A user story is a tool in Agile software development used to capture a description of a software feature from a user's perspective. The user story describes the type of user, what they want and why. A user story helps to create a simplified description of a requirement.

Set-based design is different than a traditional 'point-based' approach. A point-based design approach commits to a set of requirements and a single design strategy too early in the 'cone of uncertainty'. It often leads to incorrect assumptions and late discoveries that require significant rework.

Project statistics state that most project rework/failure is due to incomplete/improper/unclear requirements, hence the role the Business Analyst becomes even more critical as they shoulder a huge responsibility of eliciting and collaborating with the stakeholders to obtain clear, concise and complete requirements.

The elicitation and collaboration knowledge area focuses on drawing forth or receiving information from stakeholders and other sources by directly interacting with stakeholders, researching topics, experimenting or simply being handed information.