Scribd
Upload
35 views

Comprog Documentation

The document outlines a student group's final project to develop a basic student management system with login, student addition, course, and score forms. It discusses why such an application is being created, the advantages, and functional and non-functional requirements including limitations in scheduling and communication capabilities. The system aims to provide a free and simple alternative to more full-featured student information systems.

Uploaded by

Kyon
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
35 views

Comprog Documentation

The document outlines a student group's final project to develop a basic student management system with login, student addition, course, and score forms. It discusses why such an application is being created, the advantages, and functional and non-functional requirements including limitations in scheduling and communication capabilities. The system aims to provide a free and simple alternative to more full-featured student information systems.

Uploaded by

Kyon
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 12

Computer Programming 2

FINAL PROJECT

Adlawan, Lourdes G.

De Guzman, Lea Marie B.

Escobido, Marc Joseph G.

Eustaquio, Romeo V. III

Montemayor, Jefferson

Santos, Mark Andrei B.

Kolehiyo ng Lungsod ng Dasmarinas

Bachelor of Science in Information System

CIS-105

Mrs. Russel Espinosa Gatdula

Ms. Kenneth Auxillos


INTRODUCTION

❑ For our group, we have chosen to do a Student Management System.

➢ A Student Management System (SIS) is another name for a Student Information System.

These technologies normally let faculty members plan their schedules and communicate

about students. This approach was created to make data tracking easier for both parents

and administrative personnel.

❑ But for now, our Student Management System will mostly focus on the login form, adding forms,

course form, and score form.

➢ Q: Can the Student Management System Faculty members organize their timetables and

interact with one another regarding their pupils?

➢ A: No. But the faculty can still monitor the added forms, course forms, and score forms.
❖ WHY ARE WE CREATING SUCH AN APPLICATION?

➢ Because the majority of Student Management Systems (SIS) charge fees. Our simple SIS

may not be as good as similar apps, but it is free in exchange for effectiveness of the usual

SIS.

➢ For a user-friendly interface and accessibility. Some people may take some time to discover

and comprehend their own SIS. Our prototype SIS, on the other hand, is known for its user-

friendly interface, which eliminates redundant functionalities that could only confuse the

end user. It is a good introduction or practice for someone who is new to Student

Management Systems.

➢ Time efficient. offers a way to take control of our daily routine and start to use our time to

our advantage, as our system is free of complicated functionalities resulting in faster

processing times and the capacity to accommodate more people.


❖ WHAT ARE THE ADVANTAGES OF THIS APPLICATION?

➢ This SIS can enhance the productivity of the school. The reason for this growth is that it

takes less time to keep records and the data is more accurate and organized. With less time,

administrators and staff can focus on the school's productivity and do their other task.

➢ It can help to keep track all the student’s records, courses and scores. SIS provides

capabilities that take care of it well as ensuring that each student's record is complete.

➢ Human labor and workload can be minimized by using a student management system. It

decreases staff workload, allowing teachers to use the SIS more effectively. As a result,

they are able to minimize teacher workload and save time that may be better spent in the

classroom.
ANALYSIS, AND REQUIREMENT SPECIFICATION

❑ Recently, great work has gone into building applications that are more adaptable and flexible.

Unfortunately, most modern apps do not provide these features since changes necessitate modifying

low-level computer code. Naturally, not all adjustments are equally challenging.

❑ If a client requests an additional dialogue box, we can (usually) do that without much effort if it's

built into the user interface.

➢ But what if, for example, a current system permits a student to choose from four course

choices for the upcoming semester, but management now wants to limit that to three? to

allow students to choose from four course options plus two alternate options in the event

that they are unable to be assigned to a primary choice?

➢ These modifications are minor from an organizational point of view, but they are

challenging and time-consuming from a software perspective. In fact, This is frequently the

case: policy guidelines change frequently, and we can't keep up with the software that

implements them.
❖ FUNCTIONAL REQUIREMENTS

➢ LOGIN FORMS: This function allows the user to enter its username and password to enter

the system.

➢ ADDING FORMS: This function allows the user to add student records in the system.

➢ COURSE FORMS: This function gives permission the user to add course forms within the

system.

➢ SCORE FORMS: This function is used to allow the user to upload or view its score forms

in the system.

❖ NON-FUNCTIONAL REQUIREMENTS

➢ SCHEDULING: The system does not have any scheduling function for the students and

faculty.

➢ COMMUNICATION: The system has no way of conveying messages within the system.

You might also like