“STUDENT

MANAGEMENT
SYSTEM”
(Mobile Application)
 NATIONAL COLLEGE OF BUSSINESS ADMINISTRATION &
ECONOMICS (ECC)

Department of Computer Sciences

FINAL YEAR PROJECT WORK

This is to certify that the project entitled
STUDENTS MANAGEMENT SYSTEM
is the bonafide record of final year project work done by.

Maria Nawazish
Roll No: 152133062

Haider Ali
Roll No:152133061

Faran Shahid Baig

Roll No:152143086

Hamza Butt
Roll No:152133089

Asad Mehmood
Roll No:152133060

--------------------------- ----------------------------- ------------------------------

Supervisor Advisor Head of the Department
Mr. ALISHAN NAWAZ Mr. Asif Sabir MR. SHEHBAZ YOUNIS
 DECLARATION

We affirm that the final year project work titled “STUDENT MANAGEMENT
SYSTEM” being submitted in partial fulfillment for the award of Bachelor of
Computer Sciences is the original work carried out by us. It has not formed the part of
any other project work submitted for award of any degree or diploma, either in this or any
other University.

(Signature of the
Candidates)
Maria Nawazish
Roll No: 152133062

Haider Ali
Roll No:152133061

Faran Shahid Baig

Roll No:152143086

Hamza Butt
Roll No:152133089

Asad Mehmood
Roll No:152133060
 ACKNOWLDGEMENT
First off all we would like to thank to ALLAH, for blessing us with the knowledge to
perform with skills. And a very humble thanks to our family members to supported us
in every part of life. With their support and encouragement we are successfully
achieving our goals. We extend our sincere thanks to our friends for their constant
support throughout this project.
We express our gratitude to MR. ALISHAN NAWAZ, for having provided me the
facilities to do the project successfully.
We would like to heartfelt thanks to MR. SHAHBAZ YOUNIS (H.O.D of Computer
Sciences) for his patronage and giving us an opportunity to undertake this project.
Our sincere thanks to MR. ASIF SABIR, who has allowed us to do this project and
encouragement given to us.
We owe deep sense of gratitude to MR. SHAHBAZ YOUNIS, (H.O.D of Computer
Sciences) for appreciating our goal. We express our sincere thanks to him for his
constant encouragement.
 Table of Contents

Chapter No Contents Page No

Ch. 01 INTRODUCTION 1
1.1 Introductions 2
Ch. 02 SYSTEM ANALYSIS 3
2.1 Introduction 4
2.2 Existing System 4
2.3 Proposed System 5
2.3.1 Advantages of proposed system 5
2.4 Feasibility Study 5
2.4.1 Economically Feasibility 5
2.4.2 Technical Feasibility 6
2.4.3 Operational Feasibility 6
Ch. 03 SYSTEM REQUIREMENTS SPECIFICATION 7
3.1 Introduction 8
3.2 Purpose 8
3.3 Scope 8
3.4 Product Functions 8
3.5 Constraints 9
3.6 Assumptions and dependencies 9
3.7 External Interface Requirements 9
3.7.1 Hardware Interface 9
3.7.2 Software Interface 9
3.7.3 Memory Constraints 10
3.8 Non Function Requirements 10
3.8.1 User Friendly 10
3.8.2 Accessibility 10
3.8.3 Backup 10
3.8.4 Efficiency 11
3.8.5 Effectiveness 11
3.8.6 Extensibility 11
3.8.7 Maintainability 11
3.8.8 Modifiability 11
3.8.9 Portability 12
3.8.10 Quality 12
3.8.11 Reliability 12
3.8.12 Security 12
Ch. 04 SOFTWARE DESCRIPTION 13
4.1 Android Studio 14
4.2 Development Tools & Technology 14
4.2.1 XML 14
4.2.2 XAML 15
4.2.3 Android Language 15
4.2.3.1 JAVA Development Kit 16
4.2.3.2 Android SDK 16
4.2.4 PHP 16
4.2.5 JSON 16
4.2.6 MySQL 17
4.2.7 Wamp Sever 17
4.2.8 Android Virtual Device 17
Ch. 05 PROJECT DESCRIPTION 18
5.1 Problem Definition 19
5.2 Project Overview 19
5.3 Module Description 19
5.3.1 Administrator Module 19
5.3.2 Student Module 20
5.3.3 Faculty Module 20
Ch. 06 SYSTEM DESIGNS 21
6.1 Introduction 22
6.2 System Flow Diagram 22
6.3 Data Flow Diagram 23
6.3.1 Data Flow Diagram level 0 23
6.3.2 Data Flow Diagram level 1 23
6.3.3 Data Flow Diagram level 2 24
6.3.3.1 Admin DFD level 2 24
6.3.3.2 Faculty DFD level 2 24
6.4 Class Diagram 25
6.5 Use Case Diagram 26
6.6 Activity Diagram 27
6.6.1 Activity Diagram for Login 28
6.2.2 Activity Diagram for Admin 29
6.6.3 Activity Diagram for Teacher 30
6.6.4 Activity Diagram for Student 31
6.7 Sequence Diagram 32
6.7.1 Sequence Diagram for Login 33
6.7.2 Sequence Diagram for Teacher 34
Ch. 07 DATABASE SYSTEM 35
7.1 Introduction 36
7.2 Entity Relationship Diagram 36
7.3 Database Tables 37
7.3.1 Login Table 37
7.3.2 Faculty Table 37
7.3.3 Student Table 38
7.3.4 Section Table 38
7.3.5 Attendance Table 39
7.3.6 Quiz And Assignment Table 40
7.3.7 Final Marks Table 40
7.4 Input Design 41
7.5 Output Design 41
 Ch. 08 SYSTEM TESTING 43
8.1 Introduction 44
8.1.1 Steps 44
8.2 Testing Methodologies 44
8.2.1 Unit Testing 44
8.2.2 System Testing 45
8.2.3 Performance Testing 45
8.3 Test Cases 45
8.3.1 Agent and Admin Login Form 46
8.3.2 Master Form 47
8.3.3 Report Form 48
Ch. 09 SYSTEM IMPLEMENTATION 49
9.1 Purpose 50
9.2 System Maintenance 51
Ch. 10 CONCLUSION AND FUTURE ENHANCEMENT 52
10.1 Conclusion 53
10.2 Scope for Future Development 53
Ch. 11 USER MANUALS 54
11.1 Home Screen 55
11.2 Student Portal 56
11.2.1 Student Portal -> Courses 57
11.2.2 Student Portal -> Results 58
11.2.3 Student Portal –> Setting & Logout 60
11.3 Faculty Portal 61
11.3.1 Faculty Portal -> Attendance 62
11.3.1.1 Add Attendance 62
11.3.1.2 Modify, Delete and View Attendance 63
11.3.2 Faculty Portal -> Marks 64
11.3.2.2 Add Assignment 65
11.3.3 Faculty Portal -> Setting & Logout 66
REFERENCES 67
 ABSTRACT

“Student Management System” is an application witch can be used by education

institutes to maintain the records of students and faculty members easily. Achieving
this objective is difficult using a manual system as the information is scattered, can be
redundant and collecting relevant information may be very time consuming all these
problems are solved using this project.
Faculty and students are provided with username and password, both can view their
profiles by login. And teacher can take attendance and make marks sheets through
this application.
 List of Figures

Chapter # Contents Page NO.

6.2 System Flow 27
6.3.1 Data Flow Diagram Level 0 28
6.3.2 Data Flow Diagram Level 1 28
6.3.3.1 Data Flow Diagram Level 2 Admin 29
6.3.3.2 Data Flow Diagram Level 2 Faculty 29
6.4 Class Diagram 30
6.5 Use Case Diagram 31
6.6 Activity Diagram 32
6.6.1 Login Activity 33
6.6.2 Admin Activity 34
6.6.3 Teacher Activity Diagram 35
6.6.4 Logout Activity 36
6.7 Sequence Diagram 37
6.7.1 Sequence Diagram Login 38
6.7.2 Sequence Diagram For Teacher 39
7.2 Entity Relationship Diagram 42
11.1(A) Student Login 60
11.1(B) Faculty Login 60
11.2(A) Dashboard 61
11.2(B) Navigation menu 61
11.2.1 Course Submenu 62
11.2.2(A) Results 63
11.2.2(B) Course List 63
11.2.2(C) Marks Menu 64
11.2.2(D) Marks Detail 64
11.2.3 Setting 65
11.3(A) Profile View 66
11.3(B) Menu List 66
1.3.1.1(A) Attendance Detail 67
11.3.1.1(B) Upload Attendance 67
11.3.1.2(A) Select Program 68
11.3.1.2(B) 68
11.3.2.1(A) Add Quiz 69
11.3.2.1(B) Create Quiz 69
11.3.2.2(A) Add Assignment 70
11.3.2.2(B) Create Assignments 70
11.3.3(A) Faculty Setting 71
11.3.3(B) Faculty Logouts 71
 List of Tables

Chapter # Contents Page NO.

7.3.1 Login Table 42
7.3.2 Faculty Table 42
7.3.3 Student Table 43
7.3.4 Section Table 43
7.3.5 Student Attendance Detail 44
7.3.6 Quiz Attendance 45
7.3.7 Final Marks 45
8.3.1 Admin Login Table 51
8.3.2 Master Form Table 52
8.3.3 Report Form 53
 CHAPTER 01

“INTRODUCTION”
1.1 OBJECTIVE:

“Student management system” is an online mobile application witch deals

with the maintenance of the student’s as well as faculty management details. Students
and Faculty members are provided with the unique username and passwords. Both
can get access thorough login process accordingly.
After that, it can generate the management of the student on basis of attendance,
results, reports and all disciplines by relevant teacher. Student can be view their
progress in every discipline through his/her profile.

Faculty members handle the particular Programs and Subjects responsible to make
the attendance, result etc. for all students. It calculates the attendance, results and
generates the reports on daily basis for every student.
 CHAPTER 02

“SYSTEM ANALYSIS”
2.1 INTRODUCTION
Analysis can be defined as breaking up of any whole so as to find out their
nature, function etc. It defines design as to make preliminary sketches of; to sketch a
pattern or outline for plan. To plans and carry out especially by artistic arrangement
or in a skillful wall. System analysis and design can be characterized as a set of
techniques and processes, a community of interests, a culture and an intellectual
orientation.
The various tasks in the system analysis include the following.

Understanding application.


Planning.


Scheduling.


Developing candidate solution.


Performing cost benefit analysis.


Recommending alternative solutions.



Supervising, installing and maintaining the system.

This system manages to the analysis of the report creation and develops manual entry
of the student attendance. First design the students entry form, staff allocation and
time table allocation forms. This project will help the attendance and marks sheet
system for the department to calculate percentage and reports.

2.2 EXISTING SYSTEM

The Existing system is a manual entry for the students. Here the attendance
and results will be carried out in the hand written registers. It will be a tedious job to
maintain the record for the user. The human effort is more here. The retrieval of the
information is not as easy as the records are maintained in the hand written registers.
This application requires correct feed on input into the respective field. Suppose the
wrong inputs are entered, the application resist to work. So the user finds it difficult
to use.
2.3 PROPOSED SYSTEM
To overcome the drawbacks of the existing system, the proposed system has
been evolved. This project aims to reduce the paper work and saving time to generate
accurate results from the student’s attendance. The system provides with the best user
interface. The efficient reports can be generated by using this proposed system.
2.3.1 Advantages of Proposed System


It is trouble-free to use.


It is a relatively fast approach to enter attendance


Is highly reliable, approximate result from user


Best user Interface

Efficient reports

2.4 FEASIBILITY STUDY

Feasibility analysis begins once the goals are defined. It starts by generating
broad possible solutions, which are possible to give an indication of what the new
system should look like. This is where creativity and imagination are used. Analysts
must think up new ways of doing things- generate new ideas. There is no need to go
into the detailed system operation yet. The solution should provide enough
information to make reasonable estimates about project cost and give users an
indication of how the new system will fit into the organization. It is important not to
exert considerable effort at this stage only to find out that the project is not
worthwhile or that there is a need significantly change the original goal.
Feasibility of a new system means ensuring that the new system, which we are
going to implement, is efficient and affordable. There are various types of
feasibility to be determined. They are,
2.4.1 Economically Feasibility
Development of this application is highly economically feasible. The only
thing to be done is making an environment with an effective supervision.
It is cost effective in the sense that has eliminated the paper work completely. The
system is also time effective because the calculations are automated which are made
at the end of the month or as per the user requirement.
2.4.2 Technical feasibility:
The technical requirement for the system is economic and it does not use
any other additional Hardware and software, but an android device. Technical
evaluation must also assess whether the existing systems can be upgraded to
use the new technology and whether the organization has the expertise to use it.
2.4.3 Operational Feasibility:
The system working is quite easy to use and learn due to its simple but
attractive interface. User requires no special training for operating the system.
Technical performance include issues such as determining whether the system can
provide the right information for the Department personnel student details, and
whether the system can be organized so that it always delivers this information at
the right place and on time using intranet services. Acceptance revolves around
the current system and its personnel.
 CHAPTER 03

“SYSTEM REQUIRMENTS
SPECIFICATION”
3.1 INTRODUCTION
A software requirements specification (SRS) is a description of a
software system to be developed. It lays out functional and non-functional requirements,
and may include a set of use cases that describe user interactions that the software must
provide.

This section introduces the requirement specification document for the Student
Management System. It provides the purpose and scope of the system. Any definition
and references are listed in this section as well as an overview of the remaining
requirements specification document.

3.2 PURPOSE
This SRS Document contains the complete software requirements for the Student
Management System and describes the design decisions, architectural design and the
detailed design needed to implement the system. It provides the visibility in the design
and provides information needed for software supports. It'll help you with your daily
student management routines and deliver you from your paperwork. In order to make this
possible, the system greatly decreases the amount of paperwork.

3.3 SCOPE

Student Management System is developing for general purpose and used to

replace old paper work system. SMS is to build in order to efficiently provide student
information to teachers and school administration. This increases in efficiency of result
making, provide result to parents, give feedback to student, finally, publication and email
student result. It provides a mechanism to edit the student information form which makes
the system flexible.

3.4 PRODUCT FUNCTIONS

This will allow access only to authorized users with specific roles (Faculty and
Student). Depending upon the user’s role, he/she will be able to access only specific
modules of the system.
  A login facility for enabling only authorized access to the system.
 System administrator will be able to add, modify or delete program, student,
faculty member, and login information.
 System administrator/Faculty will be able to generate reports.
3.5 CONSTRAINTS
 There will only be one administrator.
 The delete operation is available only to the administrator. To reduce the
complexity of the system, there is no check on delete operation. Hence,
administrator should be very careful before deletion of any record and he/she
will be responsible for data consistency.

3.6 ASSUMPTIONS AND DEPENDENCIES

 The login Id and password must be created by system administrator and

communicates with the concerned user confidentially to avoid unauthorized
access to the system.
 Registration process will be open only for specific duration.

3.7 EXTERNAL INTERFACE REQUIREMENTS

3.7.1 Hardware Interfaces

 Android Device with Screen resolution of at least 480 x 800 hdpi or above.
 Device should be connected with the network. It may be LAN or WAN.

3.7.2 Software Interfaces

 Android OS (ice cream sandwich or above)

 XML for designing front-end
 MS SQL for backend
 PLATEFORM : Android Language
 INTEGRATED DEVELOPMENT ENVIRONMENT (IDE): Android Studio
3.7.3 Memory Constraints

At least 512 MB RAM and 50 MB space of device storage will be required to run
the Application.

3.8 NON FUNCTIONAL REQUIREMENTS

Non-functional requirement is a requirement that specifies criteria that can be
used to judge the operation of a system, rather than specific behaviors. They are
contrasted with functional requirements that define specific behavior or functions. The
plan for implementing functional requirements is detailed in the system design. The plan
for implementing non-functional requirements is detailed in the system architecture,
because they are usually architecturally significant requirements.

3.8.1 User Friendly

User friendly means product is accessible and understandable for every user. All
things are visible and user doesn’t need to know the detailed description about each
feature. He / She just access everything in just a single moment. All the features are well
manner arrange and easily visible.

3.8.2 Accessibility

Accessibility means product should be easily accessible anywhere any place any
time, it means our website is full responsive all the time and back end works properly to
give easy access to user and administration. Also keep in mind our website is accessible
in any time of machine, either it is PCs, laptops or Mobile phones.

3.8.3 Backup

The word backup means to make the copy of original data and recovers it if their
made any misshape to our data. There are two reasons to use backup of data: The first
primary reason is to recovers data after it losses by deletion or corruption. The secondary
reason of backup is to recover data earlier time according to the user define retention
policy.
3.8.4 Efficiency

Efficiency means our product is consumed minimum resources to given the equal
load which leads to quick access and it also increase accessibility and make website user
friendly. It is better to say give minimum input and takes out maximum output. This leads
to our website more efficient.

3.8.5 Effectiveness
This feature tells about the result after it is access by any user. It should be
effective. Mean to say that resulting performance of our product should be extremely
good just as example like “GOOGLE”, it’s effective because Google resulting
performance is calculated in mili seconds. So it is effective for every user.

3.8.6 Extensibility
Extensibility means our website has the ability to made up gradations time to
time. Because at this level things are not constant even for short time, so for small
updates our website is automated to do this job.

3.8.7 Maintainability

If the administrator or user is need to change some features, it should be easy job
for developer. Basically the maintenance means to identify correct the defects of current
work repair or replace without replace still work parts, prevent unexpected working
conditions, maximize the product life and also the reliability efficiency and safety. It also
has the ability to meet new requirements.

3.8.8 Modifiability
In above discussion, the term meet new requirements means the product is easy
modified when a user of administrator needs. This leads to save the time and cost.
3.8.9 Portability
Our website is portable means it should be easily accessible by all time of
environments, machine and search engines. Environments like Windows, Linux, Mac
OS, android and IOS etc. This makes the website more effective and efficient foe all over
the world.

3.8.10 Quality
Quality refers that our website is fully functional developed under the software
quality assurance (SQA) criteria. Quality made our product according to standard, which
is acceptable by all over the world.

3.8.11 Reliability
Reliability means there is less chance of error occur in our product. As discuss
above if the quality of our website is good then there are less chance of error to occur in
our product, and this thing made our website a effective for all users and administration.

3.8.12 Security
The term security refers to many things. The security of data lose, the security
from internal breaches, the security from hacking and un-authorized users etc. Security is
also refers save the cost and time to complete when our product is under development
process.
 CHAPTER 04

“SOFTWARE DESCRIPTION”
4.1 ANDROID STUDIO
Android Studio is the official Integrated Development Environment (IDE) for
Android app development, based on IntelliJ IDEA . On top of IntelliJ's powerful code
editor and developer tools, Android Studio offers even more features that enhance your
productivity when building Android apps, such as:

 A flexible Gradle-based build system

 A fast and feature-rich emulator

 A unified environment where you can develop for all Android devices

 Instant Run to push changes to your running app without building a new APK

 Code templates and GitHub integration to help you build common app features
and import sample code

 Extensive testing tools and frameworks

 Lint tools to catch performance, usability, version compatibility, and other

problems

 C++ and NDK support

4.2 DEVELOPMENT TOOLS AND TECHNOLOGIES

4.2.1 XML

Extensible Markup Language (XML) is used to describe data. The XML standard
is a flexible way to create information formats and electronically share structured data via
the public Internet, as well as via corporate networks.

XML code, a formal recommendation from the World Wide Web Consortium (W3C), is
similar to Hypertext Markup Language (HTML). Both XML and HTML contain markup
symbols to describe page or file contents. HTML code describes Web page content
(mainly text and graphic images) only in terms of how it is to be displayed and interacted
with.
XML data is known as self-describing or self-defining, meaning that the structure of the
data is embedded with the data, thus when the data arrives there is no need to pre-build
the structure to store the data; it is dynamically understood within the XML. The XML
format can be used by any individual or group of individuals or companies that want to
share information in a consistent way. XML is actually a simpler and easier-to-use subset
of the Standard Generalized Markup Language (SGML), which is the standard to create a
document structure.

4.2.2 XAML

XAML is a declarative markup language typically used to create an application's

user interface. It got its start in 2006 when Windows Presentation Foundation (WPF) was
introduced as part of the .NET Framework 3.0.

Positioned as the follow-up to Windows Forms, it's no wonder adoption was slow. The
typical applications you'd build with this were line-of-business versions, living inside
corporate walls. As you've probably experienced, the standard attitude in these
environments is to wait and see how a new technology will fare, rather than just jumping
right in. Next to that, the learning curve was pretty steep, which would have resulted in
higher costs. And, to be frank, WPF was plagued with performance problems.

Steadily, it got better, and when Silverlight came around things started looking brighter
for XAML. Silverlight was introduced as a cross-browser, cross-platform plugin in which
you'd use XAML to build your UI. This was also the time when Microsoft introduced its
“one technology, three screens” vision – and XAML was an unmistakable part of this.

4.2.3 Android Language

The official language for Android development is Java. Large parts of Android are
written in Java and its APIs are designed to be called primarily from Java. That said, it is
possible to develop C and C++ apps using the Android Native Development Kit (NDK),
however it isn’t something that Google promotes.
4.2.3.1 JAVA Development Kit

The Java Development Kit (JDK) is a software development environment used

for developing Java applications and applets. It includes the Java Runtime Environment
(JRE), an interpreter/loader (java), a compiler (javac), an archiver (jar), a documentation
generator (javadoc) and other tools needed in Java development.

4.2.3.2 Android SDK

It is a software development kit that enables developers to create applications for

the Android platform. The Android SDK includes sample projects with source code,
development tools, an emulator, and required libraries to build Android applications.

4.2.4 PHP

PHP is a server-side scripting language designed primarily for web

development but also used as a general-purpose programming language. Originally
created by Rasmus Lerdorf in 1994, the PHP reference implementation is now produced
by The PHP Development Team.

PHP code is usually processed by a PHP interpreter implemented as a module in the web
server or as a Common Gateway Interface (CGI) executable. The web server software
combines the results of the interpreted and executed PHP code, which may be any type of
data, including images, with the generated web page.
4.2.5 JSON

JSON stands for JavaScript Object Notation. It is an independent data exchange

format and is the best alternative for XML. Android provides four different classes to
manipulate JSONdata. These classes are JSONArray, JSONObject, JSONStringer and
JSONTokenizer.

The JSON format is often used for serializing and transmitting structured data over a
network connection. It is used primarily to transmit data between a server and web
application, serving as an alternative to XML.
4.2.6 MySQL

MySQL is an open source relational database management system (RDBMS)

based on Structured Query Language (SQL) Apache as the Web server, MySQL as the
relational database management system and PHP as the object-oriented scripting
language.

The SQL part of “MySQL” stands for “Structured Query Language”. SQL is the most
common standardized language used to access databases. Depending on your
programming environment, you might enter SQL directly (for example, to generate
reports), embed SQL statements into code written in another language, or use a language-
specific API that hides the SQL syntax.

4.2.7 Wamp Server

WampServer is a Windows web development environment. It allows you to

create web applications with Apache2, PHP and a MySQL database. It also comes with
PHPMyAdmin and SQLite Manager to easily manage your
databases. WampServer installs automatically (installer), and its usage is very intuitive.

4.2.8 Android Virtual Device

An Android Virtual Device (AVD) is an emulator configuration that allows

developers to test the application by simulating the real device capabilities. We can
configure the AVD by specifying the hardware and software options. AVD manager
enables an easy way of creating and managing the AVD with its graphical interface.
 CHAPTER 05

“PROJECT DESCRIPTION”
5.1 PROBLEM DEFINITION
This system developed will reduce the manual work and avoid redundant data.
By maintaining the attendance and marks sheets manually, then efficient reports
cannot be generated. The system can generate efficient daily and weekly, consolidate
reports. As the attendances are maintained in registers it has been a tough task for
admin and staff to maintain for long time. Instead the software can keep long and
retrieve the information when needed.
5.2 PROJECT OVERVIEW

Attendance Management System basically has two main modules for proper
functioning


Admin module is has rights for creating any new entry of faculty and student

details.

User has rights of making daily attendance, marks sheets, generating report.
Attendance report can be taken by given details of student details, date and

class.
5.3 MODULE DESCRIPTION
The system should be designed in such a way that only authorized people
should be allowed to access some particular modules. The records should be modified
by only administrators and no one else. The user should always be in control of the
application and not the vice versa.
The user interface should be consistent so that the user can handle the application
with ease and speed. The application should be visually, conceptually clear.
5.3.1 Administrator Module
 Student Details:
In this module deals with the allocation of roll no and personal details for new
batch or student. It will generate of personal details of student and academic
details of the students with the photos.
 Staff Details:
It helps to allot the subject and the subject code to the particular staffs.
It provides the facility to have a user name and password to the staffs.
5.3.2 Student Module
 Login: to allow the entry of only authorized users through valid login Id and
password.
 Dashboard: to view student personal and institution details.
 Courses: to view related courses, class time table.
 Results: to view results and reports of attendance and marks.
 Setting: to change the login password.
 Logout: to logout from account.
5.3.3 Faculty Module
 Login: to allow the entry of only authorized users through valid login Id and
password.
 Profile: to view personal details.
 Attendance: to maintain student’s attendance.
 Marks: to maintain students marks.
 Marks Report: to generate the marks reports and award lists.
 Setting: to change the login password.
 Logout: to logout from account.
 CHAPTER 06

“SYSTEM DESIGNS”
6.1 INTRODUCTION
A model is a description from which detail has been removed in a systematic
manner and for a particular purpose. A simplification of reality intended to promote
understanding. Models are the most important engineering tool, they allow us to
understand and analyses large and complex problems.

6.2 SYSTEM FLOW DIAGRAM

Figure: 6.2 System Flow Diagram

6.3 Data Flow Diagram

6.3.1 DFD level 0

Figure: 6.3.1 DFD level 0

6.3.2 DFD level 1

Figure: 6.3.2 DFD level 1

6.3.3 DFD level 2

6.3.3.1 Admin

Figure: 6.3.3.1 DFD level 2 Admin

6.3.3.2 Faculty

Figure: 6.3.3.2 DFD level 2 Faculty

6.4 CLASS DIAGRAM

Figure: 6.4 Class Diagram

6.5 USE CASE DIAGRAM FOR (SMS)

Figure: 6.5 Use Case Diagram

6.6 ACTIVITY DIAGRAM

Figure: 6.6 Activity Diagram

6.6.1 Activity Diagram for Login

Figure: 6.6.1 Login Activity

6.6.2 Activity Diagram for Admin

Figure: 6.6.2 Admin activity diagram

6.6.3 Activity Diagram of Teacher

Figure: 6.6.3 Teacher Activity Diagram

6.6.4 Activity Diagram for Student

Figure: 6.6.4 Logout Activity

6.7 SEQUENCE DIAGRAM OF (SMS)

Figure # 6.7: Sequence Diagram for (SMS)

6.7.1 Sequence Diagram for Login

Figure: 6.7.1: Sequence Diagram for Login

6.7.2 Sequence Diagram for Teacher

Figure: 6.7.2 Sequence Diagram for Teacher

 CHAPTER 07

“DATABASE DESIGNS”
7.1 INTRODUCTION
Database design is the process of producing a detailed data model of database.
This data model contains all the needed logical and physical design choices and physical
storage parameters needed to generate a design in a data definition language, which can
then be used to create a database.

7.2 ENTITY RELATIONSHIP DIAGRAM

An entity-relationship diagram (ERD) is a graphical representation of an
information system that shows the relationship between people, objects, places, concepts
or events within this system.

Figure: 7.2 ERD

7.3 DATABASE TABLES
7.3.1 Login Table

 To create a login details for the table.

FIELDS DATATYPE CONTRAINTS DESCRIPTION

Stored number
Tablename varchar(20) Primarykey of
tables from login

Table: 7.3.1 Login

7.3.2 FACULTY TABLE

 To create username and password for the staff details.

FIELDS DATATYPE CONTRAINTS DESCRIPTION

Define separate
Id varchar(20) Primarykey
teacher code id
name varchar(20) NotNull Define teacher name
Define unique teacher
Email varchar(20) NotNull
email
Teacher login
Pwd varchar(20) NotNull
password
Designation varchar(20) NotNull Teacher Designation
Define teacher
qualification varchar(20) NotNull
qualification
Define teacher
Dep_from varchar(20) NotNull
department
img varchar(20) NotNull Teacher picture

Table: 7.3.2 Faculty Table

7.3.3 Student Table

FIELDS DATATYPE CONSTRAINTS DESCRIPTION

Describe unique
Id Varchar(20) Primarykey
student id
Define the name of
Name Varchar(20) NotNull
student
Father name of
F_name Varchar(20) NotNull
student
Student section id
Section_id Varchar(20) NotNull
(FK)
Define degree
Session Varchar(20) NotNull
duration
Degree Varchar(20) NotNull Type of degree
Pwd Varchar(20) NotNull Login password
Blood groop of
Blood_groop Varchar(20) NotNull
student
Img Varchar(20) NotNull Student picture
Student semester id
Semester_id Varchar(20) NotNull
(FK)
Teacher of
Tod_id Varchar(20) NotNull
departments

Table: 7.3.3 Student table

7.3.4 Section Table
 To create section details for particular class.

FIELDS DATATYPE CONSTRAINTS DESCRIPTION

Id Varchar(15) Primarykey Define section id
Name Varchar(15) NotNull Section name
Course_id Varchar(15) NotNull Course id (FK)
Total student Varchar(15) NotNull Total number of
students

Table: 7.3.4 Section Table

7.3.5 Attendance table:

 To create attendance details for particular class and lecture.

FIELDS DATATYPE CONSTRAINTS DESCRIPTION

Id Varcahar(20) primarykey Define id

Date Date NotNull Date

Student_id Varcahar(20) NotNull Define student id

Define present
P_a Varcahar(20) NotNull and absent
attendance
Section_id Varcahar(20) NotNull Section id

Teacher_id Varcahar(20) NotNull Define teacher id

Lecture_id Varcahar(20) NotNull Lecture id

Course_id Varcahar(20) NotNull Course id

Define topic
Topic_name Varcahar(20) NotNull
name
Class_type Varcahar(20) NotNull Class type

Remarks Varcahar(20) NotNull Define Remarks

Teacher of
Tod_id Varcahar(20) NotNull
department id
Time of
Created_at Number NotNull
attendance
Semester_id Varcahar(20) NotNull Semester id

Table: 7.3.5 Student Attendance table

7.3.6 Quiz and Assignment Table

FIELDS DATATYPE CONSTRAINTS DESCRIPTION

Define unique quiz
Id Varcahar(20) Primarykey
or assignment id
Define quiz or
Title Varcahar(20) NotNull
assignment title
Type of
Type Varcahar(20) NotNull
quiz/assignment
Define course
Course_id Varcahar(20) NotNull related to
assignment/quiz
Define relevant
Teacher_id Varcahar(20) NotNull
teacher
Section_id Varcahar(20) NotNull Relevant section
Define the dual or
Dual_degree Varcahar(20) NotNull
single degree
Define total marks
Total_marks Varcahar(20) NotNull
of assignment/quiz

Table: 7.3.6 Quiz and Assignment Table

7.3.7 Final Marks Table

FIELDS DATATYPE CONSTRAINTS DESCRIPTION

Define unique quiz
Id Varcahar(20) Primarykey
or assignment id
Define teacher to
Teacher_id Varcahar(20) NotNull
relevant course
Define course related
Course_id Varcahar(20) NotNull
to final marks report
Define semester for
Semester_id Varcahar(20) NotNull
marks
Define the specific
Student_id Varcahar(20) NotNull
student
Define total marks of
Total_marks Varcahar(20) NotNull
individual student

Table: 7.3.7 Final Marks Table

7.4 INPUT DESIGN
Input design is part of overall system design that requires special attention
designing input data is to make the data entered easy and free from errors. The input
forms are designed using the controls available in PHP. Validation is made for each and
every data that is entered. Help information is provided for the users during when the
customer feels difficult.
Input design is the process of converting the user originated inputs to a computer based
format. A system user interacting through a workstation must be able to tell the system
whether to accept the input to produce reports. The collection of input data is considered
to be most expensive part of the system design. Since the input has to be planned in such
a manner so as to get relevant information, extreme care is taken to obtain pertinent
information
This project first will entered to the input of allocation forms it will be created on student
details form and subject entry form. It will help to calculate subject wise attendance
system and marks sheet. Next one if u wants any verification on your data’s also
available in details show forms.
7.5 OUTPUT DESIGN
Output design this application “Student management system” generally refers to
the results and information that are generated by the system for many end-users; output is
the main reason for developing the system and the basis on which they evaluate the
usefulness of the application.
The output is designed in such a way that it is attractive, convenient and informative.
Forms are designed with various features, which make the console output more pleasing.
As the outputs are the most important sources of information to the users, better design
should improve the system’s relationships with us and also will help in decision making.
Form design elaborates the way output is presented and the layout available for capturing
information.
One of the most important factors of the system is the output it produces. This system
refers to the results and information generated. Basically the output from a computer
system is used to communicate the result of processing to the user.
Student management system to show the report subject wise attendance maintaining
by staffs. Also generates the marks sheet in respect of all sessional, quiz and
assignment marks. Takes a whole report obtains on an administrator privileges only.
This forms will show weekly report and consolidate report generated date, batch, and
class wise to our end user. We want to change our report to convert Excel format .if
you want change any modification.
 CHAPTER 08

“SYSTEM TESTING”
8.1 INTRODUCTION
Once source code has been generated, software must be tested to uncover (and
correct) as many errors are possible before delivery. Our goal is to design a series of test
cases that have a high likelihood of finding errors. To uncover the errors software
techniques are used. These techniques provide systematic guidance for designing test that
 Exercise the internal logic of software components, and
 Exercise the input and output domains of the program to uncover errors
8.1.1 Steps: Software is tested from two different perspectives:
 Internal program logic is exercised using ―White box test case design technique.
 Software requirements are exercised using ―block box test case design
techniques.
In both cases, the intent is to find the maximum number of errors with the
Minimum amount of effort and time.
8.2 TESTING METHODOLOGIES
A strategy for software testing must accommodate low-level tests that are
necessary to verify that a small source code segment has been correctly implemented
as well as high-level tests that validate major system functions against customer
requirements. A strategy must provide guidance for the practitioner and a set of
milestones for the manager. Because the steps of the test strategy occur at a time
when deadline pressure begins to rise, progress must be measurable and problems
must surface as early as possible. Following testing techniques are well known and
the same strategy is adopted during this project testing.
8.2.1 Unit testing
Unit testing focuses verification effort on the smallest unit of software
design-the software component or module. The unit test is white-box oriented. The
unit testing implemented in every module of student attendance management System.
by giving correct manual input to the system ,the data are stored in database and
retrieved. If you want required modules to access input or get the output from the End
user. Any error will accrued the time will provide handler to show what type of error
will be accrued.
8.2.2 System testing
System testing is actually a series of different tests whose primary purpose is
to fully exercise the computer-based system. Below we have described the two types
of testing which have been taken for this project. it is to check all modules worked on
input basis .if you want change any values or inputs will change all information. So
specifies input is must.
8.2.4 Performance Testing
Performance testing is designed to test the run-time performance of software
within the context of an integrated system. Performance testing occurs throughout all
steps in the testing process. Even at the unit level, the performance of an individual
module may be assessed as white-box tests are conducted.
This project reduce attendance table, codes. It will generate report fast no have extra time
or waiting of results .entered correct data will show result few millisecond. Just use only
low memory of our system. Automatically does not getting access to any other software.
Get user permission and access to other applications.

8.3 TEST CASES

Test case is an object for execution for other modules in the architecture does
not represent any interaction by itself. A test case is a set of sequential steps to
execute a test operating on a set of predefined inputs to produce certain expected
outputs. There are two types of test cases:-manual and automated. A manual test case
is executed manually while an automated test case is executed using automation.
In system testing, test data should cover the possible values of each parameter based
on the requirements. Since testing every value is impractical, a few values should be
chosen from each equivalence class. An equivalence class is a set of values that
should all be treated the same.
Ideally, test cases that check error conditions are written separately from the
functional test cases and should have steps to verify the error messages and logs.
Realistically, if functional test cases are not yet written, it is ok for testers to check for
error conditions when performing normal functional test cases. It should be clear
which test data, if any is expected to trigger errors.
TEST CASE
8.3.1 Agent and admin login form
Sr# Test case Test case Test case Step Expected Actual Test
id name Decision result Result Case
Status
pass/fail
1 Login Validate
To verify Enter the Login Login Pass
admin login that login login successful Successful
name on name and or an error
Login password message
Page and click “In valid
submit login or
button password”
must be
displayed
2 Login Validate To verify Enter the Login Login Pass
Staff login that login login successful Successful
name on name and or an error
Login password message
Page and click “In valid
submit login or
button password”
must be
displayed
3 Password Validate To verify Enter An error An error fail
password That password message Message
Password and login “password “password
on login name invalid” invalid”
Page Click must be must be
submit displayed Displayed
button

Table: 8.3.1 Admin login table

8.3.2 Master form

Sr # Test Test Test Step Expected result Actual

Test
case Case case Result
case
id name Decision
status
pass/fail
1 To Nothing An error message Pass
Validate
allocate entered student name not
Create allocation
separate and click equal to null must Inserted
student form
roll no submit be displayed successful
details
for the button
students
2 Validate Nothing An error message Pass
To
allocation entered staff details
allocate
form and click Password, username
separate
Create submit not equal to null Inserted
subject
staff button must be displayed successful
username
details
password
for the
staffs
3 Validate To Nothing An error message Pass
allocate Verify entered not click not
Create
period that data and click allocation subject Inserted
time
form Stored submit table not equal to successful
table
On button null must be
database displayed
4 View Check fail
To An error
details of
verify message
all data An error message
that data return
generated return null will be
stored null will
displayed
on be
database displayed

Table: 8.3.2 Master Form Table

8.3.3 Report form

Sr # Test case Test case Test case Step Expected Actual Test
id name Decision result Result case
status
pass/fail
1 Weekly Validate To select Nothing An error Retrieved Pass
report class that source entered message Data
attendance And and on not successful
form destination click selected
submit
button
2 Consolidate Validate To select Nothing An error Retrieved Pass
report class that depart entered message Data
attendance on and and on not successful
form Time click selected
submit
button

Table: 8.3.3 Report Form Table

 CHAPTER 09

“SYSTEM IMPLEMENTATION”
9.1 PURPOSE
System implementation is the important stage of project when the theoretical
design is tuned into practical system. The main stages in the implementation are as
follows:
 Planning
 Training
 System testing and
 Changeover Planning

Planning is the first task in the system implementation. At the time of implementation
of any system people from different departments and system analysis involve. They
are confirmed to practical problem of controlling various activities of people outside
their own data processing departments.
The line managers controlled through an implementation coordinating committee.
The committee considers ideas, problems and complaints of user department, it must
also consider:
 The implication of system environment
 Self-selection and allocation for implementation tasks
 Consultation with unions and resources available
 Standby facilities and channels of communication
Student management system will implement student details, staff handles subject
details, separate login details, marks tables detail. It will used to entered subject wise
attendance. This application elaborate attendance table generate weekly, consolidate
report provide to the End user. Mostly this application will calculate date wise
attendance .To select starting date to end date generate reports at the time of
activities.
9.2 SYSTEM MAINTENANCE
Software maintenance is far more than finding mistakes. Provision must be
made for environment changes, which may affect either the computer, or other parts
of the computer based systems. Such activity is normally called maintenance. It
includes both the improvement of the system functions and the corrections of faults,
which arise during the operation of a new system.
It may involve the continuing involvement of a large proportion of computer
department recourses. The main task may be to adapt existing systems in a changing
environment.
Back up for the entire database files are taken and stored in storage devices like flash
drives, pen drives and disks so that it is possible to restore the system at the earliest. If
there is a breakdown or collapse, then the system gives provision to restore database
files. Storing data in a separate secondary device leads to an effective and efficient
maintains of the system. The nominated person has sufficient knowledge of the
organization’s computer passed based system to be able to judge the relevance of
each proposed change.
 CHAPTER 10

“CONCLUSION AND FUTURE

ENHANCEMENT”
10.1 CONCLUSION
To conclude, Project Data Grid works like a component which can access all
the databases and picks up different functions. It overcomes the many limitations
incorporated in the Student management system according to attendance and results.
 Easy implementation Environment
 Generate report Flexibly

10.2 SCOPE FOR FUTURE DEVELOPMENT

The project has a very vast scope in future. The project can be implemented
on intranet in future. Project can be updated in near future as and when requirement
for the same arises, as it is very flexible in terms of expansion. With the proposed
software of database Space Manager ready and fully functional the client is now able
to manage and hence run the entire work in a much better, accurate and error free
manner. The following are the future scope for the project.
 Discontinue of particular student eliminate potential attendance.
 Bar code Reader based attendance system.
 Individual Attendance system with photo using Student login.
 CHAPTER 11
“USER MANUALS”
11.1 HOME SCREEN
Home screen contains on two tabs, one for the student portal witch is default screen,
and the second one is for faculty portal. Both tabs have different pages with control. Student
portal is for student login. And faculty portal tab is for faculty login page.

Figure: 11.1 (A) Student Login Figure: 11.1 (B) Faculty Login
11.2 STUDENT PORTAL
Student Portal basically contains on several screens, default screen is to profile view
or dashboard. Student Portal also have a left navigation bar, which is contains on a menu and
submenu lists.

Figure: 11.2 (A) Dashboard Figure: 11.2 (B) Navigation Menu

11.2.1 Student Portal -> Courses
Courses menu depends on three submenus which are followings:
 Summary
 Class
 Marks

Figure: 11.2.1 Course Submenu

11.2.2 Student Portal -> Results
In this menu a student can be view his/her results in all respects such as attendances and
marks details.
First of all student will be touch/click on result there will be appear a course list. Select any
course to view results related that course. After that there will appear another screen with the
menu. Select any one of these to get results about this. See the following figures for this
process.

` Figure: 11.2.2 (A) Results Figure: 11.2.2 (B) Courses List

Student Portal -> Results

Figure: 11.2.2 (C) Marks menu Figure: 11.2.2 (D) Marks Details
11.2.3 Student Portal -> Setting & Logout
In student portal there is a setting menu, with the help of this module student will be
able to change his/her password. Student also can be recover password in the case of forgot
password.
And last one is logout button, student can logout from his/her profile with the help of this
button.

Figure: 11.2.3 Setting

11.3 FACULTY PORTAL
After login in from Faculty Portal, it also contains on several screens, default screen is for
teacher profile view. Faculty Portal also have a left navigation bar, which is contains on a
menu and submenu lists.

Figure: 11.3 (A) Profile View Figure: 11.3 (B) Menu List
11.3.1 Faculty Portal -> Attendance
Attendance button has it’s submenu related to attendance, which are following:
 Add Attendance
 Modify Attendance
 Delete Attendance
 View Attendance
11.3.1.1 Add Attendance
Add attendance proceed as following:

Figure: 11.3.1.1 (A) Att. Detail Figure: 11.3.1.1 (B) Upload Attendance
11.3.1.2 Modify, Delete and View Attendance
To modify, delete and view attendance first of all we should select the class or
topic to view relevant attendance list after that we can perform modify and delete
attendance.

11.3.1.2 (A) Select program 11.3.1.2 (B)

11.3.2 Faculty Portal -> Marks
Marks module in faculty portal has following sub menus:
 Add Quiz
 Add Assignment
 Add Session
 Add Final
11.3.2.1 Add Quiz
Add quiz have following procedure:

Figure: 11.3.2.1 (A) Add Quiz Figure: 11.3.2.1 (B) Create Quiz
11.3.2.2 Add Assignment
Add assignment procedure.

Figure: 11.3.2.2 (A) Add Assign Figure: 11.3.2.2 (B) Create Assign
11.3.3 Faculty Portal -> Setting & Logout
Same like Student Portal Procedure.

Figure: 11.3.3 (A) Faculty Setting Figure: 11.3.3 (B) Faculty logout
 REFERENCES

PROJECTS REFERENCES
1. http://s3.amazonaws.com/academia.edu.documents/44976688/sratp.rtf?AWS
AccessKeyId=AKIAIWOWYYGZ2Y53UL3A&Expires=1501777151&Sign
ature=62viIXv%2BLBhYxUgWN%2BqYP3AK664%3D&response-
content-
disposition=attachment%3B%20filename%3DSOFTWARE_REQUIREME
NTS_SPECIFICATION_SRS.doc
2. http://s3.amazonaws.com/academia.edu.documents/34275294/student-
attendance-management-
system.pdf?AWSAccessKeyId=AKIAIWOWYYGZ2Y53UL3A&Expires=1
496487435&Signature=LhbDQoKYd5JjzKJmzdwf7CwMBD4%3D&respon
se-content-
disposition=attachment%3B%20filename%3DSTUDENTS_ATTENDANC
E_MANAGEMENT_SYSTEM_MI.pdf

WEBSITES
1. https://developer.android.com/training/index.html
2. https://www.tutorialspoint.com/android/
3. https://www.w3schools.com/php/
4. https://www.tutorialspoint.com/sql/
5. https://www.smartdraw.com/uml-diagram/