Overview of Requirement Elicitation and Collaboration

Requirement Elicitation is also popularly known as Requirement Gathering. The difference between two terms Elicitation and Gathering is that Elicitation implies the collection process involves many difficulties, while Gathering does not (so from my point of view, Elicitation is a bit more accurate!). Moreover, Elicitation requires the interaction between BA and stakeholders, or Communication in… Continue reading Overview of Requirement Elicitation and Collaboration

Model Requirement – Good User Story

In the previous post, we are already familiar with User Story – what it is, how it is created, and so on. However, it’s still a very long way until a good User Story is reached. Recall that both User Stories and Use Cases are requirement representatives. Also, recollect that to ensure requirement is stated… Continue reading Model Requirement – Good User Story

Model Requirement – User Stories

To recall from the previous post Model Requirement – Use Case, while Use Case is typically used in Waterfall project with predictive requirement approach, User Story normally exists in Agile projects with adaptive requirement approach. As a matter of fact, it’s not necessary for an Agile project to use User Story as representation of requirement… Continue reading Model Requirement – User Stories

Model Requirement – Sitemap

This week, let’s be familiar with Sitemap – another type of Stakeholder Requirement. Different from all previous types (Entity Relationship Diagram, Workflow, State Transition Diagram, Permission Matrix, Use Case Diagram), this Sitemap is not very popularly known or is underestimated. It might be the reason of its absence in many functional specification. The first question… Continue reading Model Requirement – Sitemap

Model Requirement – Use Case Diagram

This week, let’s continue with another type of Stakeholder requirement – Use Case diagram. In previous posts, Use Case diagram is introduced as to depict which actor can perform which actions (or so-call use cases) and the relationships between those actions. According to UML standard notion of Use Case diagram, the best way to think of… Continue reading Model Requirement – Use Case Diagram

Model Requirement – State Transition Diagram

This week, let’s get to know the next type of Stakeholder requirement – State Transition diagram. Recall from previous posts, State Transition diagram shows change in all possible states of an entity. It belongs to Data and Information modelling category, and is drawn using State Modelling technique. Following UML standard, State Transition diagram is also known… Continue reading Model Requirement – State Transition Diagram

Model Requirement – Workflow Diagram

This week, let’s get familiar with another type of Stakeholder Requirement – Work flow Diagram. It’s a sequence flow of work such as review or approval process. Recall that the technique we will use to draw a Work flow is Process Modelling. According to BABOK version 3, there are many types of Process Models and… Continue reading Model Requirement – Workflow Diagram