One of the "specialties" to arise is the Business Analyst. Although some organizations have used this title in non-IT regions of the business, it is an appropriate description for your role that functions as the bridge between people running a business and IT.The use of the word "Business" is a constant reminder that any application software developed by an organization should further improve its business operations, possibly by increasing revenue, reducing costs, or increasing service level to the customers.
History from the Business Analyst Function 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 application development process and frequently had programming encounter.
They used textual requirements together with ANSI flowcharts, dataflow diagrams, data source 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 response to the demand for speed, a class associated with development tools referred to as CASE (Computer Helped 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 company community from the actual development process due to the unfamiliar symbols used 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, custom and user. IT teams have been still perfecting their management of your central mainframe computer after which suddenly had hundreds of independent computers to manage.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 brand new distributed systems technology and also the increased sophistication with the computer user prompted how many software requests in order 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 with regard to themselves, or selecting consultants, often called Business Analysts, who would report directly for 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 even approved. Small impartial databases were developed everywhere with inconsistent, and often, non-guaranteed 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 as well as approaches were developed to answer the changes, RAD (rapid application development), JAD (joint application development), and OO (object oriented) resources and methods have been developed."
Other related courses in: IT Training