Superior University Sialkot: Student Information System

Student Information System
Superior University Sialkot
MSC(CS) Final documentation

Computer Science & Information Technology
Final Documentation
1
Superior University Sialkot:
Program: MCS
Batch: 2016
Project Advisor: Syed Atizaz Haider
Submitted By
Sonia Nazir 004

Maryam Ismail 010
Saher Amjad 011
2
Dedicated to
Our Beloved
PARENTS AND TEACHERS
Whose prayers help us to complete this Project
Acknowledgement
We have no words to express our deepest gratitude to almighty, compassionate, and supreme
ALLAH, who enabled us to accomplish this task. We also invoke peace for Hazrat
Mohammad (PBUH), the last prophet of ALLAH; who is forever a torch of guidance for
humanity as a whole. We express our gratitude to all out teachers for their teachings that brought
us to this stage of academic zenith, but in particular, we wish to express immeasurable
gratefulness to our good-natured project supervisor Syed Atiza Haider, Lecturer of Superior
University of Sialkot.
In the last but not least, we also pay our deepest gratitude with deepest sense of respect to our
parents for their love and affection which kept us steadfast, and enabled us to attain targets and
goals of academic life. We are extremely inedited to our loving brothers, sisters, and friends for
their constant encouragement which provides us the impulsion that was necessary for attaining
initiatives.
1- Sonia Nazir
2- Maryam Ismail.
3- Sahr Amjad
Date:
August 9, 2016
3
Abstract
Now a day’s web application has made man life easy and people are performing
his/her tasks fastly and without wasting any time. Now a day’s mostly people carry
Laptop and Notepad that make life easy. Our student information system
Application will facilitate student and Teacher of the Superior University. Superior
University has no Information system implemented. Through this system anyone
can get their information own their desktop pc or laptop anywhere. As, our
application will provide users with the facility that they can get their information
(e.g. Attendance, Marks, Timetable) and teachers can upload students marks and
attendance etc. There is no existing SIS in Superior University So we decide to
develop this application for Desktop. It is designed for desktop Web base
application.
4
Contents
Acknowledgement .................................................................................................................................... 3
Abstract ..................................................................................................................................................... 4
Student Information System ..................................................................................................................... 7
Chapter 1 ....................................................................................................................................................... 8
1.1- Introduction and Background:........................................................................................................ 9
1.2- Problem Statement: ........................................................................................................................ 9
1.3- Previous Work:............................................................................................................................... 9
1.4- Objectives of the Project: ............................................................................................................... 9
1.5- Specific Project Goal:..................................................................................................................... 9
1.6- Scope the Project: ........................................................................................................................... 9
1.7- Benefits of the Project: ................................................................................................................... 9
1.8- Outputs Expected from the Project: ............................................................................................. 10
1.9- Project Description: ...................................................................................................................... 10
1.10- Functional Specification: .......................................................................................................... 10
1.11- Functional Performed: .............................................................................................................. 10
1.12- Limitation and restriction: ........................................................................................................ 10
1.13- Waterfall Method ...................................................................................................................... 10
Chapter: 2 .................................................................................................................................................... 12
2.1 Introduction: ................................................................................................................................. 13
2.2 Requirements:............................................................................................................................... 13
2.2.1 Functional Requirements: ......................................................................................................... 13
2.2.2 Non-functional Requirements: ................................................................................................. 13
2.2.3 System Requirements: .............................................................................................................. 14
Chapter: 3 .................................................................................................................................................... 15
3.1 Introduction: ................................................................................................................................... 16
3.1 Data flow diagram: ......................................................................................................................... 17
3.2 Use Case: ........................................................................................................................................ 19
3.3 Use case description:....................................................................................................................... 20
3.4 Activity diagram: ............................................................................................................................ 29
3.5 Domain Model: ............................................................................... Error! Bookmark not defined.
3.6 System Sequence diagram: ............................................................................................................. 30
3.7 Class Diagram: ................................................................................................................................ 35
Chapter: 4 .................................................................................................................................................... 36
Tools and Technology used .................................................................................................................... 37
5
4.1- Software Technologies: ................................................................................................................... 37

Chapter: 5 .................................................................................................................................................... 38
5- Screen Shots: ...................................................................................................................................... 39
Chapter: 6 .................................................................................................................................................... 57
6 Project Schedule / Milestone Chart: ............................................................................................... 58
6.1- Project Schedule / Milestone Chart: ................................................................................................ 58
6

Web based Application
7
Chapter 1
Introduction and Planning
8
1.1- Introduction and Background:
Now a day’s Web application has made man life easy and people are performing his/her
tasks fastly and without wasting any time. Now a day’s mostly people carry Laptop that make life
easy. Our Web Application will facilitate student and Teacher of the Superior University.
Superior University has no Information system implemented. Through this system anyone can get
their information own their laptop, Notepad or Pc anywhere in web browser. As, our application
will provide users with the facility that they can get their information (e.g. Attendance, Marks,
Timetable) and teachers can upload students marks and attendance etc. There is no existing SIS in
Superior University So we decide to develop this application for Browser. It is designed for Web
application.
1.2- Problem Statement:
As we know that superior university Sialkot campus is newly start so we have no student
information system to overcome this problem we develop and design Student Information
System.
1.3- Previous Work:
There is no existing information system in Superior University. As there is no previous

work on this type of project.
1.4- Objectives of the Project:
As a student it is our objective to learn the latest technologies that we are going to use, like
coding in “PHP, HTML, and CSS. To design user-friendly, Simple, and easy to use and efficient
application in given time. To Design an error free, complete and extensible Web Application.
1.5- Specific Project Goal:
As a student it is our goal to learn latest technologies and trends and to know how the
work is done professionally in the industry. The goals of the project are to design a web based
application for Browser that can provide an interactive plate form to the Teachers and students.
1.6- Scope the Project:
As Superior University is growing rapidly so this information system is available on PC

now it will be in the form of Web application. It is specific for the Browser, and has flexibility to
develop for the Web
1.7- Benefits of the Project:
 Any Registered student and teacher can use this application on their Pc, Laptop or Notepad.
9
 They can use anywhere anytime.

 Administrator can set timetable.
 Teacher can upload marks and attendance.
 Student view Profile, marks, attendance and timetable.
1.8- Outputs Expected from the Project:
Output of this project SIS web application that will provide specific the functionalities.
1.9- Project Description:

We are going to design Student Information System for browser. This is three tier
applications. The steps that will be taken in this regards that are, First design the layout using
Dream viewer, and then through MySQL connect to Database, when application will be develop
then the code compile for Website.
1.10- Functional Specification:
Following are the main Functions of the project are listed below:
This application that perform the functionality for the teacher, the teacher can upload
marks, sessional result and attendance of students, and student can access their result,
attendance, profile, time table, course history, and also can do course registration.
1.11- Functional Performed:
System is designed to perform a reliable and easy way for requisitions and see their
progress through the process and win the interests of users.
 End user login.
User enter roll no and password to login
 New window open
This window display some icons display some Information about user
 End user logout.
User logout from the application.
1.12- Limitation and restriction:

 This application works on Browser not on desktop or mobile phone.
 This application use only for Superior University accounts.
1.13- Waterfall Method

"Waterfall" (also known as the Traditional method) divides the project into well-defined
sequential stages with intermediate milestones. The final product is not delivered until all phases
are finished."Waterfall" method has many advantages, as it is the most direct way to the objective with
the shortest development time and cost possible.
10
The steps of waterfall model are:

 Requirement Definition
 System and Software Design
 Implementation
 Integration and System Testing
 Operation and Maintenance
1.13 Figure 1
11
Chapter: 2
Requirement Engineering
12
2.1 Introduction:
In this chapter, the emphasis will be to investigate different types of requirements
functional and non-functional requirements of a We Base Application. Let’s take a look of them.
2.2 Requirements:
2.2.1 Functional Requirements:
2.2.1.1- Login User:
System will give the access to use the application.
2.2.1.2- Add User:

SIS will allow the Administrator to add new user to the system’s database.
2.2.1.3-Set Timetable:
SIS will allow the Administrator to set the timetable.
2.2.1.4- Register Courses:

SIS will provide option to register courses to the user.
2.2.1.5- Upload marks:

Through this application teacher upload marks of the student.
2.2.1.6- Upload Attendance:

Through this application teacher upload attendance of the student.
2.2.1.7- View Timetable:

User of this application will view their timetable.
2.2.1.8- View Attendance:

. User of this application will view their attendance.
2.2.1.9- View Marks:

. User of this application will view their marks.
2.2.2 Non-functional Requirements:

2.2.2.1- Accessibility:
Only browser users can use this application.
2.2.2.2- Availability:
Student Information System will be available to every valid and authenticated user,
according access will be provided to the valid viewer.
2.2.2.3- Maintainability:
The system will be optimized for supportability, or ease of maintenance as far as

possible. This may be achieved through the use and documentation of coding standards. The
maintainability can also be modifiable according to the need of the organization.
13
2.2.2.4- Performance:
Basically, it refers to four properties as follows:
 Response Time.
 Reliability.
 Security.
 Integrity.
2.2.2.4.1- Response Time:

Application will not take too much time to load. All the views and operations in
the application work fast.
2.2.2.4.2- Reliability:
The application should be reliable, that is it should not get failure, if it fails then it
should not take much time for the operation.
2.2.2.4.3-Security:
The system shall provide secure management. The database and application should
be secure, store and retrieval methods should be secure and authentic. It also refers to login,
logout and password requirements.
2.2.2.4.4-Integrity:
The system should tell how to support the entity constraints integrity and
referential integrity in database tables and interfaces to reduce chances of errors and redundancy.
2.2.3 System Requirements:

2.2.3.1- User’s Requirements:
The basic requirements of Superior University web application is that user must have
browser to use this application and also registered of the Superior University.
2.2.3.2- System Requirements:
2.2.3.2.1- Hardware Requirements:
Processor : Pentium iv
Ram : 256 mb
Hdd : 2 gb
Monitor : svga color
Key board : normal
Mouse : normal,
2.2.3.2.2- Software Requirements:

Operating System : Windows XP
Front End : C#, ASP.Net 2005(frame work 2.0), HTML
Back End : SQL server 2005
Web server : Apache Server
Browser : Internet Explorer or Google.
14
Chapter: 3
Analysis and Design
15
3.1 Introduction:
This chapter is all about the Use Case modeling and Software design. In this chapter,
analysis of the system is completed. So, we have to understand the current situation of the
problem domain. Now we are ready to strive for the solution of a problem domain by using
object-oriented approach.
Design is the abstraction of a solution; it is a general description of the solution to a problem

without the details. Design is view patterns seen in the analysis phase to be a pattern in a
design phase. After design phase we can reduce the time required to create the
implementation.
Following artifacts must be included in this chapter:
3.1 Context diagram.

3.2 - Data flow diagram.
3.3 Use case diagrams.
3.4 Use case description.
3.5 Activity Diagram.
3.6 Domain Model.
3.7 Sequence Diagram.
3.8 Class Diagram
16
3.1 Context Diagram:

This diagram represents what are the bounders and scope of Student Information System project. It
describes the main objective of the system and its entities involved.
Administrator
Administrator
Faculty
Student
Student information
System
Figure (3.1): the context diagram of Student information
The Administrator can be done the following:

 Admin can manage user (add faculty and student)
 Admin delete/update faculty and student.
 Add degree and batch.
 Register courses and update courses.
 Change password.
The Faculty can be done the following:

 View profile.
 View course timetable.
 Add student marks and update.
 Add student attendance and update.
The Student can be done the following:

 View profile.
 View course timetable.
 View Sessional marks
 View attendance.
17
3.1 Data flow diagram:

Level 0:
Teacher/ Student detail Detail

Student
Information My SQL
Response
Administrator Response system database
Level 1:
Student
View Attendance
View Timetable
View Sessional m
View Profile
Response
Login
Login
User Management
Administrator
Student Send Details

Add Batch/Degree
Information My SQL
Set Time Table
system Response database
Register Courses SIS
Response
Upload Sessional marks
View Timetable
Upload Attendance
View Profile
Response
Login
Teacher
18
3.2 Use Case:

Login
Logout
View Profile
View Marks
Add Degree
View Attendance Student
Add Batch
Upload Marks
Admin View Register Courses
View Time Table

Set timetable
Upload Attendance
Teacher
Add Courses
Offer courses
Course
Register Student Courses
Register Course
Register Teacher Courses
Add
Teacher Update
Delete
User Manage
Add
Student Update
Delete
Figure 3.2 Use Case 19

3.3 Use case description:
3.3.1- Administrator:
3.3.1.1- Use case-Login:
Title Login
Scope System under design
Level Main function
Primary Actor Administrator
Stakeholders and Administrator: 1. Manages accounts.
Interest 2. Set timetable.
3. Register Courses
Teachers: Wants to access the system login to see their timetable
and to update marks and attendance.
Students: Wants to access the system login to see their Profile
timetable, marks and attendance.
Preconditions User should have valid account information to login
Post conditions User was logged into the system successfully
Main success scenario User System
1. User enters id 1. System verifies and validates
and password. the user and redirect user to its
assigned page according to role
from which user belong.
Special requirement Id and Password

Frequency of Limited
occurrence
3.3.1.2. Use case-Logout:
Title Logout
Level Main function
Stakeholders and Administrator: 1. Manages accounts
Interest 2. Set timetable
3. Register Courses
Students: Wants to access the system login to see their Profile,
20
Preconditions User click on logout button.

Post conditions User log out from the system successfully.
Main success User System
scenario 1. User was logged into 1. System display logout button
the system.
2. User selects the option
and logout from their
account.
Special requirement
occurrence
3.3.1.3. Use case-User management:
Title User Management

Level Sub function
3. Register Courses
Students: Wants to access the system login to see their Profile,
Preconditions All the operations performed manually.
Administrator has to login his or her account.
System should be in running state.
Post conditions User must be logged into main page.
Two fields appear Student and Teacher.
scenario 1. User selects the” User 2. System displays two options
management option “ Student and Teacher.
from the main page.
Special requirement Nil

occurrence
3.3.1.3.1.Use case-Teacher management:
Title Teacher Management
Level Sub function
21

3. Register Courses
Students: Wants to access the system login to see their timetable
Preconditions User must be on main page to select the Teacher option.
Post conditions User can operate different functions like add, delete and update.

scenario 1. User click on “User 1. System displays options
management”. Student and Teacher.
2. User click on 2. System displays different
“Teacher” option. options add delete and update.

occurrence
3.3.1.3.2.Use case-Student management:
Title Student Management

Level Sub function
Administrator: 1. Manages accounts
2. Register Courses
3. Set timetable
Stakeholders and
Interest
Students: Wants to access the system login to see their timetable
Preconditions User must be on main page to select the Student option.
User can operate different functions like add, delete and update.
Post conditions
User System
1. User click on “User 1. System displays options Student
management”. and Teacher.
Main success scenario
2. User click on “Student” 2. System displays different options
option. add delete and update against
the Student option.
22

occurrence
3.3.1.3.2.1. Use case-User management Add:
Title Add
Level Sub function
Interest 2. Add teacher info into database.

User must be clicked on “Add” option.
Post conditions The “add” option must be visible.
User must be clicked on “Add” option.
scenario 1. User click on “User 1. System displays options Student
management”. and Teacher .
“Teacher” option. options add, delete and
3. User click on “add” update.
option. 3. System then adds the new info.

occurrence
3.3.1.2. 2.Use case-User management Delete:
Title Delete
Level Sub function
Interest 2. Delete teacher info.
Post conditions The “delete” option must be visible.
User must be clicked on “Delete” option.
23

“Teacher” option. options add delete and
3. User click on “Delete” update.
option. 3. System then deletes specific
info.
occurrence
3.3.1.2.3. Use case-User management Update:
Title Update
Level Sub function
Teachers: Received updated info.

Post conditions The “Update” option must be visible,
User must click on “Update” option.

2. User click on 2. System displays different options
“Teacher” option. add delete and update.
3. User click on “Update” 3. System then updates the specific
option. info.

occurrence
3.3.1.4.Use case-Set timetable:
Title Set timetable

Level Main function
Stakeholders and Administrator: Set timetable.
24
Interest Teachers: View their timetable

Students: View their timetable
Preconditions 1. Administrator must login.
2. Set the timetable against
(degree,batch ,semester,course_code, course_title, room#, teacher)
Post conditions Timetable has been set.
1. User was logged into 1. System display set timetable
the system. option.
2. User select the option
and set the timetable.

occurrence
3.3.2- Teachers:
3.3.2.1.Use case-upload marks:
Title Upload marks

Level Sub function
Primary Actor Teachers
Stakeholders and Teachers: Upload marks.
Interest Students: View their uploaded marks.
Preconditions 1. Teachers must login.
2. Upload the marks against
(degree,batch,semester, student id,course_code,course_title,)
Post conditions Marks has been uploaded.
1. User was logged into 1. System display marks upload
the system. option.
and uploaded the
marks.

occurrence
25
3.3.2.2.Use case-upload attendance:
Title Upload attendance

Level Sub function
Primary Actor Teachers
Stakeholders and
Interest Teachers: Upload attendance.
Students: View their uploaded attendance.
Preconditions 1. Teachers must login.

2. Upload the attendance against
(degree,batch ,semester, student id, course_code, course_title,)
Post conditions Attendance has been uploaded.
1. User was logged into 1. System display attendance
the system. uploads option.
and uploaded the
attendance.

occurrence
3.3.2.3.Use case- view timetable:
Title Teacher view timetable

Level Main function
Primary Actor Teacher
Teacher: Wants to access the system login to see their timetable.
Preconditions
1. Teacher has to login his or her account.
2. Click on view timetable from their account .
Post conditions System display their timetable.

scenario 1. User was logged into 1. System display view
the system. timetable option.
26

and view the
timetable.

occurrence
3.3.3-Students
3.3.4.1.Use case- Student view marks:
Title Student view marks

Level Main function
Primary Actor Student
Teachers: Wants to access the system login
and to upload marks .
Students: Wants to access the system login to see their
to uploaded marks.
Preconditions 1. Student has to login his or her account.
2. Click on view marks from their account .
Post conditions System display their marks.

1. User was logged into 1. System display view marks option.
the system.
and view the marks.

occurrence
3.3.3.2.Use case-Student view attendance:
Title Student view attendance

Level Main function
27

Teachers: Wants to access the system login
and to upload attendance .
to uploaded attendance.
Preconditions
1. Student has to login his or her account.
2. Click on view attendance from their account .
Post conditions System display their attendance.

1. User was logged 1. System display view attendance
into the system. option.
2. User select the
option and view
the attendance.
occurrence
3.3.3.3.Use case-Student view timetable:
Title Student view timetable

Level Main function
timetable.
Preconditions
1. Student has to login his or her account.
2. Click on view timetable from their account .
Post conditions System display their timetable.

1. User was logged 1. System display view timetable
into the system. option.
2. User select the
option and view
the timetable.
Occurrence
28
3.4 Activity diagram:
User management
Admin
Process
Add Degree & Batch
Set Timetable
Logout
Register Courses
Login
View Profile
Process
View Timetable
Yes Teacher
Upload Attendance
Logout
No
Upload Marks
Login Error
View Profile
Show Result
View Timetable
Student
View Attendance
Logout
View Marks
29
3.6 System Sequence diagram:

3.5.1-Login sequence diagram:
Interface Database
User
Open Login Panel
Enter(Id,Password)
Check Validate
Matched Validate
Access to main panel
Failure Not Validate
Not Matched
Show Error Message
Figure 3.5.1 Login sequence diagram
3.6.2-Administrator set timetable:
Interface Database
Administrator
Open time_table panel
Enter(course_code,course_title,section,teacher,room_#)
Query
set time table Accept Detail
Show time table
Figure 3.6.2-Administrator set timetable

30
3.6.3-Administrator add teacher:
Interface Database
Administrator
Open teacher management
Add teacher_Detail
Query
Save Record Accept Detail
Show teacher_record saved
Failure Record already eixts
Detect error
Show error message
Figure 3.6.3-Administrator add teacher
3.6.4-Administrator update teacher:
Interface Database
Administrator
Open teacher management
Update teacher_Detail
Query
Show teacher_updated record saved
Detect error
Show error message
Figure 3.6.4- Administrator update teacher
31
3.6.5-Administrator add student:
Interface Database
Administrator
Open student management
Add student_Detail
Query
Show student_record saved
Detect error
Show error message
Figure 3.6.5-Administrator add student

3.6.6-Administrator delete student:
Interface Database
Administrator
Delete student_Detail
Query
Delete Record Accept Detail
Show student_record deleted
Failure Record not found
Detect error
Show error message
Figure3.6.6-Administrator delete student
32
3.6.7-Administrator update student:
Interface Database
Administrator
Update student_Detail
Query
Update Record Accept Detail
Show student_updated record
Failure Record not found
Detect error
Show error message
Figure 3.6.7-Administrator update student
3.6.8-Teacher uploads marks:
Interface Database
Teacher
Open marks panel
Enter(marks)
Query
Upload marks Accept Detail
Show marks uploaded
Figure 3.6.8-Teacher uploads marks
33
3.6.9-Teacher uploads attendance:
Interface Database
Teacher
Open attendence panel
Enter(Attendence)
Query
Upload Attendence Accept Detail
Show Attendence Uploaded
Figure 3.6.9-Teacher uploads attendance
3.6.10-Student view marks:
Interface Database
Student
Open student panel
select sessional marks panel
Query
dispaly marks Accept Detail
View marks
Figure 3.6.10-Student view marks
34
3.6.11-Student view attendance:
Interface Database
Student
Open student panel
select attendence panel
Query
dispaly attendence Accept Detail
View attendence
Figure 3.6.11-Student view attendance
3.7- Class Diagram:
Administrator
1 -A_id : string
-A_fname : string
-A_lname : string
1
-A_password : string
+A_settimetable() : void
+A_usermanagement() : void
+A_viewattendence() : void
* *
+A_viewtimetable() : void
+A_viewmarks() : void
Student +A_login() : void Teacher
+A_logout() : void
-s_id : string -T_id
-s_fname : string -T_fname : string
-s_lname : string 1 -T_lname : string
-s_password : string -T_password : string
+s_login() : void +T_login() : void
+s_logout() : void +T_logout() : void
+s_viewmarks() : void +T_viewtimetable() : void
+s_viewattendence() : void 1 +T_uploadmarks() : void
+s_viewtimetable() : void +T_uploadattendence() : void
A_usermanagement
1
-s_id : string
-T_id : string
+Student management() : void 1
+Techer mamagement() : void
* *
Student management Teacher management

-s_id : string -T_id : string
+s_add() : void +T_add() : void
+s_delete() : void +T_delete() : void
+s_update() : void +T_update() : void
Figure3.5 Class Diagram

35
Chapter: 4
Tools and Technology
36
Tools and Technology used

4.1- Software Technologies:
4.1.1- Dreamweaver
4.1.2- Php
4.1.3- HTML
4.1.4- My SQL Server
4.1.5- CSS
4.1.6- Window XP
4.1.7- Web Browser.
37
Chapter: 5
Screen Shots
38
5- Screen Shots:
5.1- Login Screen:
Figure: 5.1 Login Screen
1. Login User
2. User has Cancel option
39
5.2 Administrator
5.2.1 Administrator Home
Figure 5.2.1Administrator Home
1. Admin can Manage User.

2. Admin can add degree and batch.
3. Administrator set timetable and save it.
4. Select the Course register and assign it.
5. Admin have option to change the password.
40
5.2.2- Change Password
Figure 5.2.2Change Password
1- Edit password in the change password page.

2- Save the edited pass word.
41
5.2.3- Select User
Figure 5.2.3 Select User
1. Select faculty or Student option for registration

2. Go to home page.
3. Go to set Timetable
4. Go to register courses
5. Go to user management.
6. Go to add batch.
42
5.2.4 Student Form
Figure 5.2.4 Student Form
1. Fill the form to register the Student

2. Go to home page.
6. Go to add batch.
43
5.2.5 Faculty form
Figure 5.2.5 Faculty form
1. Fill the form to register the Student.

2. Go to home page.
6. Go to add batch.
44
5.2.6 Register Courses
Figure 5.2.6 Register Courses
1. Check the Courses and register.

2. Go to Home page
6. Go to add batch
45
5.3. Teacher
5.3.1 Teacher Home
Figure 5.3.1 Teacher Home
1. Teacher can see profile.

2. Teacher see timetable.
3. Teacher can upload student’s attendance.
4. Teacher can upload student’s marks.
5. Teacher have option to change the password
46
5.3.2 Teacher Course For Timetable
Figure 5.3.2 Teacher Course For Timetable
1. Select Course view the Timetable

2. Go to Home page
3. Go to Upload Attendance page
4. Go to Upload Marks page
47
5.3.3View Timetable
Figure 5.3.3 View Timetable
1. View the Timetable

2. Go to Home page
48
5.3.4 Select Courses Upload Marks
Figure 5.3.4Select Courses Upload Marks
1. Select the subject for uploading Marks and Attendance

2. Go to Home page
3. Go to upload Attendance page.
4. Go to upload marks page.
49
5.3.5- Upload Marks
Figure 5.3.5Upload Marks
1. Enter the marks against the roll no.

2. Go to Home.
3. Go to Timetable.
4. Go to Attendance.
5. Go to upload marks.
50
5.3.6 UploadAttendance
Figure 5.3.6 Upload Attendance
1. Check roll no for upload Attendance.

2. Go to Home page
51
5.4. Student
5.4.1 Student Home
Figure 5.4.1Student Home
1. Student can view profile

2. Go to Timetable page
3. Go to Attendance page
4. Go to Sessional Marks
5. Go to Change password page
52
5.4.2 Select Course View Timetable
Figure5.4.2 Select Course View Timetable
1. Select the Subject Code view the Timetable

2. Go to Home page
53
5.4.3 View Timetable
Figure 5.4.3View Timetable
1. View the Timetable

2. Go to Home page
54
5.4.4 View Attendance
Figure 5.4.4View Attendance
1. View the Attendance

2. Go to Home page
55
5.4.5 View Marks
Figure 5.4.5 View Marks
1. View the Result

2. Go to Home page
56
Chapter: 6
Project Schedule
57
6 Project Schedule / Milestone Chart:

6.1.1 Key Milestones and Deliverables:
Key Milestones and Deliverables:
No Elapsed time
. from start (in
Milestone Deliverables
months) of the
project
1. 1st Month Layout design Final Designing Documents
2. 3rd Month Design Specifications Final Design Document
3. 5th Months Development Application
4. 6th Months Testing Beta Release
5. 7th Months Final product and User Manual Final product and User Manual
6.1- Project Schedule / Milestone Chart:
This Project schedule which is made using MS-Project with all tasks, deliverables,
milestones, cost estimates, clearly indicated.
58

Superior University Sialkot: Student Information System

Uploaded by

Copyright:

Available Formats

Superior University Sialkot: Student Information System

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Superior University Sialkot: Student Information System

Uploaded by

Copyright:

Available Formats

Student Information System

Superior University Sialkot

MSC(CS) Final documentation

Superior University Sialkot:

Project Advisor: Syed Atizaz Haider

Sonia Nazir 004

Whose prayers help us to complete this Project

4.1- Software Technologies: ................................................................................................................... 37

Student Information System

Introduction and Planning

1.1- Introduction and Background:

1.2- Problem Statement:

1.3- Previous Work:

There is no existing information system in Superior University. As there is no previous

1.4- Objectives of the Project:

1.5- Specific Project Goal:

1.6- Scope the Project:

As Superior University is growing rapidly so this information system is available on PC

1.7- Benefits of the Project:

 They can use anywhere anytime.

1.8- Outputs Expected from the Project:

1.9- Project Description:

1.10- Functional Specification:

1.11- Functional Performed:

1.12- Limitation and restriction:

1.13- Waterfall Method

The steps of waterfall model are:

2.2.1.2- Add User:

2.2.1.4- Register Courses:

2.2.1.5- Upload marks:

2.2.1.6- Upload Attendance:

2.2.1.7- View Timetable:

2.2.1.8- View Attendance:

2.2.1.9- View Marks:

2.2.2 Non-functional Requirements:

The system will be optimized for supportability, or ease of maintenance as far as

2.2.2.4.1- Response Time:

2.2.3 System Requirements:

2.2.3.2.2- Software Requirements:

Analysis and Design

Design is the abstraction of a solution; it is a general description of the solution to a problem

Following artifacts must be included in this chapter:

3.1 Context diagram.

3.1 Context Diagram:

Figure (3.1): the context diagram of Student information

The Administrator can be done the following:

The Faculty can be done the following:

The Student can be done the following:

3.1 Data flow diagram:

Teacher/ Student detail Detail

Student Send Details

3.2 Use Case:

Admin View Register Courses

View Time Table

Figure 3.2 Use Case 19

3.3 Use case description:

Special requirement Id and Password

3.3.1.2. Use case-Logout: