Project Fose1

Download as pdf or txt
Download as pdf or txt
You are on page 1of 11

Fundamentals of

Software Engineering

Submitted To: Ms. Shagun Jain

Submitted By:
Name: Himanshu Yadav
Roll No. : 23/SE/74
EXPERIMENT 1
OBJECTIVES

Identify the Student information system (SIS).

INTRODUCTION

We are going to identify the requirements for the Student Information System
(SIS).

What Is A Student Information System (SIS)?


A Student Information System, or SIS, is a web-based platform that helps schools
and colleges take student data online for easier management and better clarity.
That's at its most basic.

The SIS system is able to collect school-wide data online so that it can be easily
accessed by teachers, parents, students, and administrators. That includes
personal student information, grades, records of tests, attendance, appraisal
performance, and plenty more.

Essentially, a SIS allows the school to make data points for lots of areas in one
place so that it's easy to keep track of progress and performance.

Hardware Requirements

In addressing the hardware requirements for an Student Information System (SIS),


a robust infrastructure is paramount. The core components, discussed below
form the foundation for efficient data handling. These are as follows:-

Database Server:
 A reliable database server with scalable architecture and data integrity is
recommended for hosting SIS database.
 The server should have sufficient storage space for the store billing and sales
database.
 Regular automatic backups, efficient indexing, and security measures for
protection.
Network Infrastructure:
 A stable highspeed network for payments or to access the sore database with
secure network protocols for data transmission.

Backup System:
 Quick recovery protocols address potential disruptions, contributing to
uninterrupted operations involve predefined procedures and strategies to swiftly
restore the SIS system to full functionality in the event of a disruption or failure.

Objectives of Student Information Systems

The Student Information System is a resource that offers a self-service solution


for students to get their administrative tasks done in one place. Equally, it is can
support faculty and staff by helping to simplify and integrate work processes.

The ability to standardize data formats between divisions means a more unified
and clear data readout at a glance, ultimately saving time. Data integrity, privacy,
and security can all be protected in an open-access environment.

When it comes to student records, an SIS offers high efficiency as all data is
automatically organized and stored for easy access whenever it is needed.

Features of a Student Information System (SIS)


Information storage is what an SIS does at its most basic. That means records
consolidated all in one place for students, teachers, and parents to access.
Reports can be created on anything, from how many students are local to what
GPA is in any given class.

Administration for students is made easier with a Student Information System.


Monitoring student progress and updating profiles often happens in real time.
Bringing together otherwise siloed departments is a special feature of the SIS that
is able to place information, data, and resources in a universally accessible place.
This allows for open communication across an institution.

As all this data storage and handling is cloud-based, so it is super secure. Setup is
often easier, access is wider, technical support is immediate, and adaptations to
changes is more easily possible.

Billing and payments can also be taken care of by the system. Parents or students
can be invoiced, payments can be made, and the school can see and control it all
from one place.
EXPERIMENT 2

OBJECTIVE
Develop a data flow diagram model (level-0, level-1 DFD) of the System
Information System.
INTRODUCTION
DFD stands for Data Flow Diagram, which is a graphical representation of how
data flows within a system. It's commonly used in system analysis and design to
illustrate the now of information between various processes, data stores, and
external entities.
• Level 0 DFD: The highest-level DFD that represents the entire system as a single
process and shows the interactions between the system and external entities.
•Level 1 DFD: A more detailed DFD that breaks down the processes from the Level
0 DFD into subprocesses, providing a more in-depth view of the system's
functionality.
Experiment-3
Aim: Data dictionary for the Student Information System

Student Table:

Student_ID: Primary Key, unique identifier for each student.


First_Name: First name of the student.
Last_Name: Last name of the student.
DOB: Date of birth of the student.
Major: Field of study or major of the student.
Course Table:

Course_ID: Primary Key, unique identifier for each course.


Title: Title or name of the course.
Instructor_ID: Foreign Key, references the instructor teaching the
course.
Instructor Table:

Instructor_ID: Primary Key, unique identifier for each instructor.


Name: Name of the instructor.
Contact_Info: Contact information of the instructor (email, phone, etc.).
Enrollment Table:
Enrollment_ID: Primary Key, unique identifier for each enrollment
record.
Student_ID: Foreign Key, references the student enrolled in the course.
Course_ID: Foreign Key, references the course in which the student is
enrolled.
Grade: Grade received by the student in the course.

This data dictionary outlines the tables in the Student Information


System and the attributes (fields) within each table, along with their
respective data types and descriptions. Depending on the specific
requirements of the system, additional attributes or tables may be
necessary.
Experiment-4

Aim:Design entity relationship diagram for student


information system.
Experiment-5
Aim -Software Requirements Specification (SRS) for Student
Information System

1. Introduction
1.1 Purpose
The purpose of this document is to outline the functional and non-functional requirements for the
development of a Student Information System (SIS). The SIS will provide a comprehensive platform for
managing student data, including enrollment, grades, attendance, and personal information.

1.2 Scope
The SIS will be used by educational institutions such as schools, colleges, and universities to streamline
administrative tasks related to student management. It will provide administrators, teachers, and
students with a user-friendly interface to access and manage relevant information.

2. Overall Description
2.1 Product Perspective
The SIS will be a standalone system, interacting with existing databases for student records and courses
where necessary. It will integrate with authentication systems to ensure secure access for users.

2.2 User Classes and Characteristics


• Administrators: Responsible for managing student records, generating reports, and overseeing
system configuration.

• Teachers: Can access student information for their respective classes, enter grades, and track
attendance.

• Students: Access their own academic records, course schedules, and personal details.

2.3 Operating Environment


The SIS will be web-based and compatible with modern web browsers such as Chrome, Firefox, and
Safari. It will be hosted on a secure server with appropriate backup and security measures in place.

3. Functional Requirements
3.1 User Authentication
1. Users must authenticate themselves with a username and password.

2. Administrators have additional privileges to manage user accounts.

3.2 Student Management


1. Add, edit, and delete student profiles.

2. Record student enrollment information including courses and academic programs.

3.3 Course Management


1. Add, edit, and delete course information including course codes, titles, and descriptions.

2. Assign teachers to courses and manage course schedules.

3.4 Attendance Tracking


1. Record student attendance for each class session.

2. Generate attendance reports for individual students and classes.

3.5 Grade Management


1. Enter and update student grades for assignments, exams, and other assessments.

2. Calculate overall course grades based on weighted components.

4. Non-functional Requirements
4.1 Performance
The system must be responsive and able to handle concurrent user interactions without significant delay.

4.2 Security
User data must be encrypted during transmission and storage. Access control mechanisms must be in
place to restrict unauthorized access to sensitive information.

4.3 Usability
The interface must be intuitive and easy to navigate, with clear instructions provided for each
functionality.

You might also like