Compare and contrast the role of a systems analyst, business analyst, and infrastructure analyst.
There are many differences between systems analyst, business analyst and infrastructure analyst that depend on the business or organization.
A systems analyst can see were changes need to be made, is capable of looking at a program or utility and see the code, also knows how to incorporate new data to an existing program to benefit the company and provide several advantages. The systems analyst can collect data and transform it into usable code for a new project or program.
On the other hand, a business analyst has a more complicated role since he or she acts as a link between management and IT. A business analyst may not be able to write the code to fix a problem but can at least come up with the concept of what the code is supposed to do. He or she can retrieve reports and data from IT and transform it into reports needed to develop a project or a plan.
The systems analyst may need the business analyst to determine what is needed for the code to work effectively. The business analyst needs the systems analyst to make the code work effectively. Working together, these two people can accomplish great things for the company.
At last, the infrastructure analyst in some cases serves as a supervisory role within the organization where he or she is part of and provides training to new analysts. When any technical problem presents, the infrastructure analyst must be able to provide consultation to solve the problem.
Compare and contrast phases, steps, techniques, and deliverables, and describe the phases of SDLC.
Information systems projects move through four phases and these are: planning, analysis, design and implementation.