- The Life of a System Analyst - System Requirements Gathering
The Life of a System Analyst - System Requirements Gathering
The life of a system analyst is all about making a software that is both reliable and done in time, with the budget provided, under the obstacle, risks and constraints they face throughout the life of the project. When a system analyst would like to save time, during requirements gathering, he/she must choose and follow the proper requirement gathering technique, which would help that system analyst to save time. There are several requirements gathering techniques and one very interesting technique, which can help system analyst to save time, would be to interview.
The system analyst would also have to plan their interview very careful, for each case scenario. For example, if a group is a large group of people to be interviewed, then the interviews, should be done in groups of people. By breaking the big groups into little groups, the system analyst, would be able to minimize confusion, among the stakeholders. Also, the System Analyst should have a questionnaire ready for their interviewees, in order to save time asking the question.
Another thing a system analyst should take into account during the interview is to allow the interviewees to enter in their answers to the questions on a computer or write them down on a piece of paper, in order to save time typing and gathering all this information, into one document. An important way to collect and validate requirements is to do face-to-face interviews, which is the primary source of requirements gathering. A technique that is used to conduct the interviews, should also be used, in order to fit different case scenarios and face different situations correctly. All software development projects are different and a system analyst should be prepared to face and conquer all of the obstacles a project has.
Along with the interview questionnaires, system analysts should also have a very basic understanding of the type, depth, and breadth of information, that would be involved in the systems requirements gathering. The system analyst should also know that there are other systems similar to the one, that he/she is trying to develop; therefore, the wheel should not be reinvented. By doing an observation of what is already out there in the market, a system analyst could use some, if not all of another product’s code, in order to develop their system.
Also by reviewing a company’s internal documents, which is another requirements gathering technique, can help the system analysts to save a lot of time, during their software development project requirements gathering. Reviewing internal documents can give system analysts an overview of the interworking of a company.
This information is vital, in order to properly understand, what it is that a company would need for their system development needs.
System analysts can also employ workshops, in order to quickly and effectively elicit requirements, for a complex project, which involves diverse stakeholders. In order to end up with the proper results of a workshop, the system analyst should and has to be very careful when planning and managing that workshop, because the diversity of stakeholders, can rise conflict of interested among them, which can create a lot of confusion.
Add a Comment
Hi every one, I obtained a bachelor's degree in Bioinformatics back in 2006, from Claflin University, after I received my bachelor's degree, I gained full time employment as a software engineer at a Video Relay Service company, maintaining databases and developing software for a new developed device called the VPAD.
I worked at that company for two years, then I became a web developer, and worked for a magazine for three years. After that job, I worked as a Drupal web developer, as a subcontractor for the NIH, for a year and then left the job to go back to school.
Collaboratively administrate empowered markets via plug-and-play networks. Dynamically procrastinate B2C users after installed base benefits. Dramatically visualize customer directed convergence without
Collaboratively administrate empowered markets via plug-and-play networks. Dynamically procrastinate B2C users after installed base benefits. Dramatically visualize customer directed convergence without revolutionary ROI.