What is a System Analyst and why they are important in SDLC phases
Introduction
A system analyst is a person who analyzes the problems and plans solutions for them. He conducts extensive research in his effort to understand the needs of the user and then draws up a plan to implement the solution. He is the pivot around whom the project revolves. He is important at every stage of the software development life cycle (SDLC). (Shelly). The tasks that a system analyst usually performs are:
- Understand the client’s requirement.
- Identify the areas where software development is required.
- Design the system and identify the processes required to complete it.
- Create bench marks against which development process can be validated.
The Software Development Life Cycle
SDLC or the Software Development Life Cycle is a term which refers to the process of planning, creating and maintaining a system of information. The system usually involves a combination of hardware and software. (Parag C., 2008). It is the job of a systems analyst to ensure that the process of planning and implementing the information system goes smoothly. Software development is done in five phases – Planning, Analysis, Design, Implementation, and Maintenance. The role of the system analyst is not just confined to the analysis stage but spreads over the entire life cycle of development. Let us consider the role of in each of the phases of SDLC.
Planning
When the project is first conceived, the system analyst (SA) is consulted to plan the project and provide a budget estimate. In this stage, he draws up a broad plan to develop the system required by the client and identifies the information or data which is needed for the development of the system.
Analysis
This is a very important phase of SDLC. In this phase the plan drawn up by the analyst in the planning stage is, after approval from the client, broken up into smaller modules. The functional and non-functional requirements are identified. The hardware and software requirements are identified.
Design
In the design stage, the specifications are provided to the development team. Each task is carefully delegated to the person qualified to perform it. It is the responsibility of the system analyst to ensure that the tasks are fully understood and the development of the software is as per the requirements. The role of the SA in this stage is of a supervisor. He guides his team through the development process and helps them where required.
Implementation
In this phase the system analyst first tests the software modules developed. He ensures that the required hardware is available and running smoothly. After checking each module individually, he then tests the system as a whole to see that the flow of information is correct and there are no errors in the system. He may have a team who performs the testing process; however, it is the system analyst who is finally responsible for ensuring that the system is running smoothly as per requirements. He provides guidelines and bench marks for testing and checks to see if the bench marks are met.
Maintenance
After conducting several dry runs and removing any bugs in the system, the analyst then installs the system at the client’s place of work. At this stage, it is the job of the system analyst to ensure that the required hardware is available and working. The newly developed system is then installed on the hardware and again dry runs are performed using data provided by the client. Once the system is up and running, the system analyst assumes the role of a consultant who is available to fix any problems that may arise during the course of using the system.
Conclusion
Thus, we see that a system analyst plays a very important role at each stage of the software development life cycle. He is the leader whom the team members follow and look towards for guidance and assistance. It would not be wrong to say that the success of the project depends on the system analyst.
References
Shelly, Gary B., Cashman, Thomas J., & Vermaat, Misty E. Discovering Computers 2008, Complete. Boston: Thomson Course Technology. ISBN 10: 1 -4239-1205-5
Parag C. Pendharkara, Corresponding author contact information, E-mail the corresponding author, James A. Rodgerb, Girish H. Subramanian (November 2008). "Information and Software Technology". Volume 50, Issue 12 (Science Direct): Pages 1181–1188.
Useful link - http://www.slideshare.net/AniketSharma3/business-analysts-and-sdlc
