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 specialized.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 utilized this title in non-IT aspects of the business, it is an appropriate description for the 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, either by increasing earnings, reducing costs, or increasing service level towards 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 organization. They understood the application development process and frequently had programming encounter. They used textual requirements together with ANSI flowcharts, data flow 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 with regard to speed, a class of development tools known as CASE (Computer Helped Software Engineering) have been 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 lengthy learning curve, and often alienated the business community from the actual development process because of 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, designer and user. IT teams had been still perfecting their management of a central mainframe computer and suddenly had hundreds of 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 from 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 rollout yet another cumbersome application.
They began learning to do things for themselves, or employing consultants, often called Business Analysts, who report directly in their mind, to help with automation needs.This caused even more problems for IT which was suddenly asked to support software that they had not written or perhaps approved. Small independent databases were produced everywhere with sporadic, and often, unprotected 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 program development), JAD (joint program development), and OO (object oriented) equipment and methods have been developed."
For more details: IT Training
One of the ""specialties"" to arise is the Business Analyst. Although some organizations have utilized this title in non-IT aspects of the business, it is an appropriate description for the 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, either by increasing earnings, reducing costs, or increasing service level towards 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 organization. They understood the application development process and frequently had programming encounter. They used textual requirements together with ANSI flowcharts, data flow 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 with regard to speed, a class of development tools known as CASE (Computer Helped Software Engineering) have been 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 lengthy learning curve, and often alienated the business community from the actual development process because of 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, designer and user. IT teams had been still perfecting their management of a central mainframe computer and suddenly had hundreds of 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 from 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 rollout yet another cumbersome application.
They began learning to do things for themselves, or employing consultants, often called Business Analysts, who report directly in their mind, to help with automation needs.This caused even more problems for IT which was suddenly asked to support software that they had not written or perhaps approved. Small independent databases were produced everywhere with sporadic, and often, unprotected 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 program development), JAD (joint program development), and OO (object oriented) equipment and methods have been developed."
For more details: IT Training
0 comments:
Post a Comment