Ever since organizations began to use computers to assistance their business jobs, the people who create and gaze after those ""systems"" have become more and more sophisticated and specific.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 is an appropriate description for that role that functions as the bridge between people in 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 for the customers.
History with 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 often 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 for speed, a class of development tools known 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 some methodology, involved a lengthy learning curve, and often alienated the business community from the development process due to the unfamiliar symbols utilized 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 had been still perfecting their management of the central mainframe computer and suddenly had countless independent computers to control.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 newest distributed systems technology and also the increased sophistication from the computer user prompted the amount 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 with regard to themselves, or employing consultants, often known as Business Analysts, who would report directly for them, to help with automation needs.This caused even more problems for IT which was suddenly asked to support software that they'd not written or perhaps approved.
Small independent databases were created everywhere with inconsistent, 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 as well as approaches were developed to react to the changes, RAD (rapid software development), JAD (joint software development), and OO (object oriented) resources and methods were developed."
Online and Classroom Training: IT Training
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 is an appropriate description for that role that functions as the bridge between people in 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 for the customers.
History with 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 often 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 for speed, a class of development tools known 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 some methodology, involved a lengthy learning curve, and often alienated the business community from the development process due to the unfamiliar symbols utilized 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 had been still perfecting their management of the central mainframe computer and suddenly had countless independent computers to control.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 newest distributed systems technology and also the increased sophistication from the computer user prompted the amount 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 with regard to themselves, or employing consultants, often known as Business Analysts, who would report directly for them, to help with automation needs.This caused even more problems for IT which was suddenly asked to support software that they'd not written or perhaps approved.
Small independent databases were created everywhere with inconsistent, 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 as well as approaches were developed to react to the changes, RAD (rapid software development), JAD (joint software development), and OO (object oriented) resources and methods were developed."
Online and Classroom Training: IT Training
0 comments:
Post a Comment