Ever since organizations began to use computers to assistance their business jobs, the people who create and maintain those “”systems”” have become a growing number of sophisticated and particular .This specialization is necessary because as computer systems become more and more complex, no one person can know how to do everything.
One of the “specialties” to arise is the Business Analyst. Although some organizations have used this title in non-IT aspects of the business, it really is an appropriate description for your role that functions since the bridge between people in operation and IT.The use of the word “Business” is a constant reminder that any application software developed by an organization should further improve it’s business operations, possibly by increasing income, reducing costs, or increasing service level to the customers.
History from the Business Analyst Role In the 1980s when the software development life cycle was well accepted as a necessary step, people doing this work typically came from a technical background and were working in the IT business. They understood the software development process and sometimes had programming experience. They used textual requirements along with ANSI flowcharts, data-flow diagrams, database diagrams, and prototypes.The biggest complaint about software development was the length of time required to develop a system that didn’t always meet the business needs. Business people had become accustomed to sophisticated software and wanted it better and faster.
In reaction to the demand with regard to speed, a class associated with development tools referred to as CASE (Computer Assisted Software Engineering) were invented.These tools were designed to capture requirements and use them to manage a software development project from beginning to end. They required a strict adherence to a methodology, involved a long learning curve, and often alienated the business community from the development process due to the unfamiliar symbols found in the diagrams.As it teams struggled to learn to use CASE tools, PCs (personal computers) began to appear in large numbers on desktops around the organization. Suddenly anyone could be a computer programmer, designer and user. IT teams have been still perfecting their management of your central mainframe computer and suddenly had countless independent computers to handle.Client-server technologies emerged as and advanced alternative to the traditional “”green screen, “” keyboard-based software.
The impact on the software development process was devastating. Methodologies and classic approaches to development had to be revised to support the new distributed systems technology as well as the increased sophistication of the computer user prompted the number of software requests to skyrocket.Many business areas got tired of waiting for a large, slow moving IT department to roll-out yet another cumbersome application. They began learning to do things for themselves, or hiring consultants, often called Business Analysts, who does report directly to them, to help together with automation needs.This caused even more problems for IT which was suddenly asked to support software that they had not written or approved. Small impartial databases were created everywhere with non-consistent, and often, unguaranteed data.
During this time, the internal Business Analyst role was minimized and as a result many systems did not solve the right business problem causing an increase in maintenance expenses and rework.
New methodologies and approaches were developed to respond to the changes, RAD (rapid application development), JAD (joint application development), and OO (object oriented) tools and methods had been developed.”