Briefing Study: Requirements Analysis and Specification (slide 22)
Summary of what's been covered in this briefing study
If you've worked through this briefing study you should have a good feel for the benefits of and the need for:
- a structured
..set of techniques for use during the stages of requirements analysis and specification in both feasibility and full studies.
You'll be familiar with the three data-centric views of a business system:
And you'll have understood that the breadth and depth to which you use the techniques varies from project to project. Art not science!
You'll have read examples of:
- how and when the techniques are used
- how they cross validate each other
You'll have seen:
- how they are a good way of doing your investigation
- that their products form a structured central holding place for your analysis work at each step of the way
- how they start off skeletal..
- ..and are then fleshed out and firmed up as you and the users progress
If you're like me when I first started to be introduced to these techniques, you'll have lots of unanswered questions and you'll be wondering where to go next. If so, move on to the next slide.
Good Practice tip
Always use plain English when you speak and write. Even emails and texts. This helps to make sure that as much as possible of what you're trying to get across actually does, and in a way that's not open to interpretation.
- Ambiguity is not the friend of the Business Analyst!
- Avoid jargon where possible in what you write. If you can't, include a definition of the terms at the end or in the appendix
- Build a project glossary and make it available to the project team. Keep updating it as you come across more terms
Remember that body language is a hugely important part of communication. Learn about it and:
- say the same thing with it as you're saying with your mouth
- listen with it when your ears are hearing what someone else is saying - then resolve any discrepancies!