| rina wrote
Instead of a full project plan, can you give an example of one business req ( except the simple ones like sorting or filters etc)
And how you approached the requirement and what kind of questions you asked and finally the functional requirments you came up with?
This would be really useful
Thanks
|
Sure, here's an example:
Let's say that you are working with a client who wants to build an online banking system. Most project start with some sort of project charter or vision which is generally created by the client and which contains the high-level view of "why" the project has been started. Here is an oversimplified statement from a project charter:
"CyberBank was created to serve the needs of consumers who desire a web-based banking relationship. In order to accomplish its goals, CyberBank desires to build an on-line, browser-based, banking system which allows the customer to perform all their banking transactions on-line."
Now this is technically not yet a requirement since is way high-level but the reality is that everything is a requirement (a desire of the stakeholder). There many other key pieces of information included in the project charter such as who the stakeholders are and who are the ultimate approvers of the requirements and functionality of the new system.
So once the vision is established (at bit more detailed then one sentence), the business analyst proceeds to elicit the detailed requirements.
The analyst now sits down with the stakeholders identified and begins to elicit and document the requirements. In this example, starting with the one sentence in the charter the BA can start asking questions such as:
- Who are the users/customers who will be using the on-line banking system? (one of they key elements of requirements is to understand the users)
- What type of banking transactions need to be performed from the on-line banking system?
- etc.
Let's say that the stakeholders tell you that customers must be able to: transfer money and pay bills.
You hierarchical requirements might look like this:
- 1. The system shall allow the customer to transfer money between accounts.
- 2. The system shall allow the customer to pay bills.
The questions continue...
For paying bills, you could ask the stakeholders some open ended question... for example:
- Q: What bills can the customer pay? A: Any bills.
- Q: So how does the customer specify who to pay? A: They need to be able to create payees.
- Q: So how does the system know where to send the money? A: Each payee must have a bank account number specified.
- Q: So what if the customer has multiple accounts with CyberBank? A: for each bill the customer should be able to select which account (if multiple exist).
So your requirements list now looks like this:
- 1. The system shall allow the customer to transfer money between accounts.
- 2. The system shall allow the customer to pay bills.
- 2.1 The system shall allow the customer to setup payees which can receive payments
- 2.1.1 Each payee shall have a name
- 2.1.2 Each payee shall have a bank account number to route funds to
- 2.2 The system shall allow the customer to create bill payment transaction
- 2.2.1 Each bill payment transaction shall require the following data:
- 2.2.1.1 Payee
- 2.2.1.2 Dollar Amount
- 2.2.1.3 Pay-from Account
Hope this helps!
- Adrian