Like all professions, business analysis has its golden rules – rules that are fundamental to the design of successful business systems. They might seem like common sense but it’s surprising how often we forget them and get ourselves into hot water. Here’s a short list of some of the more relevant rules for business analysts … The sooner you find a problem, the cheaper it is to fix Get the specifications right Recognise the total cost of a system Don’t…
Continue ReadingArticles
How To of Essential Modelling
04/06/2008 |
By IRM Training
Also called abstract or business modelling, essential modelling can be an extremely valuable tool for the business analyst. Instead of modelling how things are done (the current system), or how they might be done (a proposed system), we model what is done, or what might be done. For example the purpose of a Customer Service Department is to provide customers with a level of service they expect (or the company defines). Things like call centres and customer relationship management systems…
Continue ReadingAn Introduction to Technical Writing
09/03/2008 |
By IRM Training
At some time or another we all have to communicate using the written word, but all too often improving writing and communications skills are at the bottom of our “to do” list. Yet how many times has poor communications led to incorrect decisions or even downright confusion? We’re not alone either – look at this extract from public documents issued by one of the world’s leading banks: “Trade finance is designed to assist meet cash-flow shortages arising from a mismatch…
Continue ReadingUML – Business Context
08/12/2007 |
By IRM Training
“Where does UML fit?” is a common question among new (and not so new!) business analysts. We all know that the M stands for modelling but beyond this, perceptions start to differ. In its current form (V2.0) UML consists of 13 diagram types all of which provide a different view of a system. In the following extract from our Modelling Requirements with Use Case & the UML course manual we’ll take a brief look at which of the 13 diagrams…
Continue ReadingHow to use Use Cases (With Examples)
17/10/2007 |
By IRM Training
Many business analysts and business users get frustrated at the perceived lack of information in a use case diagram. “It’s all very well drawing a picture” they say but what about the details – what’s actually going on? When producing project documentation, use case diagrams are rarely used on their own. They will generally be accompanied by a textual use case and if they’re complex, may also have a supporting activity diagram to show what’s going on “inside” the use…
Continue ReadingStakeholder Communications – Pictures not Words
25/07/2007 |
By IRM Training
Many people on our Business Analysis workshop ask why we use dataflow diagrams (DFDs). Why not Use Case…or even BPMN? After all DFDs have been around for 20 years, surely the world has moved on? Well, has it? The primary purpose of a business analyst is to communicate – to stakeholders and to solution providers – and when it comes to communication we all know that pictures (diagrams) are much more effective and less ambiguous than words. Remember the phrase “A…
Continue ReadingCreative Thinking Techniques
11/05/2007 |
By IRM Training
This extract from IRM’s training material looks at how systematic, creative thinking techniques can be used to design practical solutions to business problems. Successful designs don’t just happen. Whilst we can sometimes get ‘flashes of brilliance’, successful designs are more likely to occur as part of a systematic process. Great things are not done by impulse, but by a series of small things brought together. Vincent Van Gogh (1853-1890) Read full paper: Creative Thinking Techniques If you liked…
Continue ReadingProblem Analysis Techniques
05/03/2007 |
By IRM Training
This extract from IRM’s training material looks at how a structured approach to defining and analysing problems can be used as the basis for designing better solutions. Part 1 of this paper looks at problem definition. Part 2 introduces the reader to analytical techniques for determining the root cause of a problem. Read the full paper here: Problem Analysis Techniques (PDF Download)
Learn more problem solving skills on our 2-day course
Learn MoreBusiness Analyst Skills
03/12/2006 |
By IRM Training
With plenty of talk in the industry about the growing importance of the business analyst, it’s worth taking a step back and understanding exactly what the analyst does. Most employers hire a BA to do three things: Engage with clients, stakeholders, project sponsors Analyse problems and create solutions Document solutions as a specification Let’s have a look at what’s involved in each step and what business analyst skills are required… 1. Engage with Clients Before a client bares their soul…
Continue ReadingA Manager’s Guide to User Acceptance Testing
20/06/2005 |
By IRM Training
For most businesses and organisations, if IT stops, the business stops. Whenever a company turns on a new production line, opens a new retail store, launches a new product or provides a new service, there is invariably a new or modified IT system behind it. Going live is the culmination of time, effort, resources and finance. A problem-free IT system is the “acid test” of significant, often crucial investment. Whilst the technical testing of IT systems is a highly professional…
Continue Reading