Requirement gathering for a student information system
Requirement gathering is the core of software. Software can only be termed as a quality product if it adheres to the requirements. However, we no longer follow the traditional methods of acquiring requirements. A proper procedure needs to be followed. For example, if a student information system is being designed a complete procedure has to be conducted for acquiring the requirements. The analysts have an active role in this process and they are responsible for passing on the information to the developers in the most comprehensive possible manner.
Holding sessions with the client – student information system
The basic step is that meetings need to be conducted with the client. The meeting should have a participant from the development team usually the team lead attends such meetings. The QA Lead also needs to be present at the meeting. Moreover, the participation of the analysis team is mandatory because they will be the ones documenting the details. Now the presence of the representative from each of the team is important so that they can contribute their point of view. Now the analysis team should have done their homework and should be ready with their set of questions as well. Moreover, the client should deliver their requirements. Now when the client is delivering the requirements and the Development team feels that there are some issues in incorporating certain requirements this aspect should be communicated to the client at that point. One of the members of the analysis team should minute the points so that while developing the functional specifications for the student information system so that none of the details should be missed out. Now even the functional specification involves many versions till the client and the company preparing the software agrees on the requirements.
Adhering to the requirements in mandatory – student information system
Now when the developer is preparing the student information system he has no room for creativity because his client would be evaluating the student information system on his own requirements. Let us say that the client demanded the inclusion of a certain field on the user interface of the student information system. Now if that field is missing this can affect the client’s work and may set a negative impression on him regarding the developer. The developer should make an effort that minimum amendments are required related to his work.
It would not be wrong to state that the success of development of the student information system is primarily dependent on the requirement analysis. If this phase goes well half the work of the student information system is done. I personally do not agree to the idea of having amendments in the middle of the development process. This can be avoided if there is an agreement between the company and the client that once the project is under the development major requirement changes would not be entertained. This clause of the agreement can save everyone from a significant amount of trouble and help deliver the student information system in a timely manner. The testing team should also make sure that the student information system strictly adheres to all the requirements mentioned in the functional specification. This way it would be easier to acquire the desired results and the output can be assumed to be of a more professional level.
Read More Information about student information system, student information systems, information system, information systems, information systems managers
Title: Requirement gathering for a student information system
Reviewed by Mohamed Mahmoud on Nov 18
Summary: Requirement gathering for a student information system
Description: Now when the developer is preparing the student information system he has no room for creativity because his client would be evaluating the student