Monday 3 February 2014

Business Analyst Online Training and Other Online Courses


Ever since organizations began to use computers to assistance their business tasks, the people who create and observe 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 that role that functions because 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 its business operations, both by increasing earnings, reducing costs, or increasing service level towards the customers.

History from the Business Analyst Part 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 program development process and frequently had programming encounter. They used textual requirements in addition to 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 regarding speed, a class associated with development tools called CASE (Computer Helped Software Engineering) had 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 particular 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 were still perfecting their management of the central mainframe computer after which suddenly had hundreds of independent computers to handle. Client-server technologies emerged as an 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 and also the increased sophistication of the computer user prompted how many software requests to be able 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 with regard to themselves, or hiring consultants, often known as Business Analysts, who does 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'd not written or perhaps approved. Small independent databases were produced everywhere with non-consistent, 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 software development), JAD (joint software development), and OO (object oriented) equipment and methods had been developed.



No comments:

Post a Comment