Project Fose1
Project Fose1
Project Fose1
Software Engineering
Submitted By:
Name: Himanshu Yadav
Roll No. : 23/SE/74
EXPERIMENT 1
OBJECTIVES
INTRODUCTION
We are going to identify the requirements for the Student Information System
(SIS).
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
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.
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.
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:
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.
• 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.
3. Functional Requirements
3.1 User Authentication
1. Users must authenticate themselves with a username and password.
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.