Requirement Tracking Management System

Abstract

The Software Requirements are description of features and functionalities of the target system. Requirements can express the expectation of the users from the software product. Requirements are definitely from client’s point of view. The process of collecting requirements from client is called Requirement Engineering. Requirement analysis is an utmost process for the success of a software project. This is a process where requirements are being documented, actionable, measurable, testable, traceable, helps to identify business opportunities. Basically, requirement analysis involves all the tasks that are being conducted to identify the needs of different clients. Versioning of requirements is an important part of requirement engineering. Requirement’s version is a process to record the changes of requirements and label the history with a version number, it is able to help the user to track the change of a requirements. From here he can compare the current requirements with newer requirements. In our country, most of the software firms use Microsoft word files to document or to keep track on the requirements. Sometimes they use handwritten papers also. This is not safe as well. The files can be missed or lost any time and this way is not helpful for comparison between older and newer requirements for version control. Version control is a system that records changes to a file or set of files over time so that we can recall the specific version later if we need. It enables multiple people to simultaneously work on a single project. Version control is important for code, files and assets that multiple team members will collaborate on. This will help a firm to keep track of changes, and keep every team member working off the latest version. So, according to these functionalities, we are proposing a management system that can work on requirement and requirement tracking.