Understanding the issue

There are several methods for identifying issues with an existing system. It is crucial to recognise these issues since they need to be solved for the system to be successfully created and developed. These methods consist of:

Surveying or interviewing present information system users

It is possible to obtain in-depth, individualised information on faults with the present system through an interview or survey. The present users will be able to provide the interviewer with the essential information because they are most likely the system's creators and have the best knowledge of the system's functionality. Students can do the survey or interviews using Google Docs or forms in a convenient way possible for them.

Analysing the Current System by Establishing

A context diagram must be used to diagrammatically depict the current system's functioning

How it functions: A surveyor can use this to ascertain how the system is supposed to function and then contrast that with how it actually performs. This will show how well the system is functioning. Surveys, observations, and interviews may all be used to gain knowledge of how the system should function.

What it does- through this, it is possible to observe what the system is meant to do. The major objective of the system is the end achievement, thus they must reach it in order to be deemed successful. Surveys, observations, and interviews can all be used to understand what the system accomplishes.

Who uses it? By identifying the system's users, we can get a sense of who the system works best for and how successful it is overall. Surveys, interviews, and observations can be used to ascertain this.

Report on Requirements

The objective of a requirements report is to describe the system's needs in detail so that it is clear how and why the system should be created. The requirements report provides a broad overview of all the data related to the justification for the system's development. The report will describe the new system's goals and objectives in comparison to those of the previous system or a period when there was no system in place. Additionally, the report will explain how the new system will aid the organisation that has put it into practice.

The requirements report template is provided below and you can use this template or create your own report depending on your requirements. An example and two versions of templates are provided at the end of the document.

The first version of the template consists of the subheadings of the requirements report and the second one is the easier version with further explanation of the requirements report.

The checklist for the first phase is given below.