ECBA Business Certification – Separating Analysis from Layout
Looking at what Business objectives you are attempting to satisfy before leaping to the technology lets you use the technology wisely, manage scope and reduce prices, producing systems that work for your customers. It is easy to Concentrate on the technical features of any project and lose sight of the reason for its presence. Every job is different to solve a problem. Either what you have does not work well enough and needs improving, or you will need to invent something entirely new. After all, When it air not broke, do not fix it.
Too often the Pressures of deadlines and budgets direct us to skip the important process of analyzing business requirements, and we jump straight into the tech. But how often do we find that the machine does not do precisely what is required. Users are obliged to use workarounds, reducing a few of the advantages we were supposed to supply which also affects our credibility.
The classic waterfall lifecycle
There are many Variations on the ecba certification System Development Life Cycle (SDLC) and the following might not be precisely the terminology that your methodology uses. The output from each Stage is the input to another. Or to put it a bit more elegantly, you cannot make a silk purse from a sow’s ear. You cannot implement a excellent operational system with no good analyzed system, you cannot build a fantastic system without great technical specifications and you cannot design a good system without a fantastic business specification.
Make Sure that talented Folks are used early in your job, to make certain you could attain a fantastic output in the end. Do not fool yourself into believing you are doing anyone any favors by bypassing company analysis and moving directly to style, or by combining both. If the deadline is tight, then negotiate a phased implementation. If the budget is tight, then remove some functionality.
Many surveys, Including the work of Boehm, have shown consistently that the increase in cost of fixing errors increases exponentially the later that fix occurs in the SDLC.
Would Shakespeare have Been a much better writer if he had a word processor?
Any instrument will consider what you tell it. There are some terrific tools around which can take the dumb hack work out of your job so you can focus on doing what you do best. But do not feel that in the event that you have got the best tool possible your systems are the greatest possible. If you do not believe me, grab your favorite word processor and write a sonnet that people will be delighted to estimate 400 years from now.
Separate business Analysis from specialized design
Business analysis is About believing what your answer needs to do, while design is all about how to make it happen with all the technology available. Bearing this in mind will make it much easier to avoid blending both of these phases. What and How. This can enable you to build stronger systems. What your business Does not change as much as it gets done. Technology changes more quickly than business requirements. Companies restructure. However, what they do has not changed, just which person does it. Business analysis gives a logical view of procedure and data needs and is not bound by physical execution.