SPCB System Project: Development, Implementation, and Analysis

This document presents a project proposal for the development of a student enrollment system for the SPCB institute. It begins with a justification for the system's necessity, highlighting the challenges of manual data handling and the benefits of automation, including improved data integrity, time savings, and enhanced efficiency for both staff and students. The project outlines the business case, detailing the benefits such as streamlined processes, reduced errors, and improved security. The project scope defines the system's purpose of providing a single platform for student enrollment and other tasks. The document includes a schedule analysis, use case diagrams, sequence diagrams, data flow diagrams, entity-relationship diagrams, and screen interfaces to illustrate the system's design and functionality. The analysis covers cost-benefit aspects and identifies the system's ability to improve accuracy, offer better analysis, and maintain data security and privacy.

Justification why system needs to be developed
In today’s world, everyone has to keep up with the different technologies and their advancements. The
SPCB is an institute that has to deal with loads of data related to various courses and programs offered
by the institute. Along with this the student data flowing in and out of the system is very enormous to
handle by manual handling Each semester of a year the data is constantly increasing which arises a
question of maintenance of data integrity and consistency in the system. The system gives an efficient
way of storing, managing and processing all the information required to be stored in the system. The
system makes use of normalization concepts in database designing that reduces redundancy of data in
the system. This will save a lot of time for the staff members of the institute as well as for the student s
as everything will be automated in the system.
Description of business case and about business benefits
Business case of any project describes various aspect of the proposed project. These aspects can be
costs, benefits, solution, timeline, challenge are analysed in order to understand what problem the
system is really beneficial for. Business case for the new proposed SPCB system deals with efficient
handling of all the use cases that happen during student enrolment in various programs every year. The
current situation of the institute deals with these use cases manually which increases high risk of
erroneous tasks. There are various tasks that are performed by the system that needs high care and
attention like setting student’s marks and grades or generation of report.
The business benefits that SPCB institute will get on the implementation of the proposed system are –
 Processes becomes time saving for all stakeholders (Students and administrative staff members)
 Saves man hours for end users
 Students may enrol at the ease of any location and does not require to wait in long queues.
 Sequence of dealing with enrolment during peak time of semester is dealt orderly.
 Less chaos and more managed tasks
 System is more reliable
 Security and privacy of student’s data is maintained.
 Increased accuracy in enrolment process.
 Offers better analysis.
Project scope
The purpose of the project is to provide a single platform to the students as well as the institute’s staff
members where they can perform the student enrolment and other tasks more efficiently and
accurately. The project reduces the tedious task of data management in the SPCB institute and also
maintains data privacy, security, integrity, consistency and reduces possibility of erroneous data in the
system. The system allows only authorized users to utilize the system’s functionality and access
information stored in the system. Thus, maintaining security of data and privacy of student’s data in the
system.

The cost benefit analysis of the system calculates the total cost going in and out of the organization to
determine the likeliness of the organization achieving its goal. The system proposed is one time
investment that will save cost of x- man’s hour, saves cost of reports and analysis, saves in-house
programming costs, improves control and reduces training required to be given to staff members
Schedule analysis of the project will determine how the project will be managed and developed with
timeline. The project is scheduled to gather all the resources required in one day and implementation is
scheduled to be completed in 15 days. After implementation of project, the testing and delivery of the
developed project is scheduled to take 5 days each. Hence, the whole working project will be developed
in total of 26 days of time.
Use case Diagram
Use case diagram of a system is used to represent the system’s interaction with its surrounding outer
environment. The actors in use case diagram are referred to persons or stakeholder that interacts with
the system in order to utilize the system’s functioning. The following is use case diagram for given SPCB
scenario which has two actors or user roles, namely, student and admin. Each of these user role with
have limited functionalities that can be accessed as depicted by the diagram below.

Sequence Diagram
Sequence diagram is a diagram which shows the sequence of activities that will occur in the system for a
particular use case. The following sequence diagram shows for enrolment of student into a program.

Data flow diagram and Context diagram
Data flow diagram of system is a diagram that depicts the flow of data in and out of the system. The
following is zero level DFD for SPCB system designed.
Context diagram of the SPCB system with one process exploded is shown in the following diagram. For
this, the one process chosen is program management process of SPCB system.

Entity relationship diagram
Entity relationship diagram of a system shows what entities exist in the system and how those entities
are related with one another. The ER diagram for SPCB system in Crow’s foot notation is shown below –

As we can see in the above diagram, there are five entities in our database, namely, student, course,
program, program_course and student_course.
Three screen interfaces
The following are three required user screens –
1. Main menu
There are two main menus according to two user roles in our system. The following is the main menu
screen for admin.
The following is the main menu screen for student.

2. Input Screen
The following is the input screen for adding new students usecase.
3. Report
The following is the student report generated by the system.