THESIS

DIGITAL SCHOOL DIARY
Session (2019-2023)
Program
Bachelor of Studies in Software Engineering
Submitted By:
Muhammad Javid 52325-F18
Muhammad Hussain 52325-F18
Muhammad Ibrahim Malik 52325-F18
Supervised By:
Mr. Faisal Bahadur
Assistant Professor, I.T Department
HAZARA UNIVERSITY, MANSEHRA

FINAL APPROVAL
This is to certify, that we have read the project report titled “Digital School Diary”
submitted by the students of BSSE 7th Semester.
Roll No: Students Name:

Muhammad Javid 52325-F18
Muhammad Hussain 52325-F18
Muhammad Ibrahim Malik 52325-F18
It is our judgement, that this project report is of sufficient standard to warrant its
acceptance by Department of CS & IT, Hazara University, Mansehra.
COMMITTEE
1. External Examiner _________________________
2. Internal Examiner _________________________
3. Supervisor _________________________
4. Head of Department _________________________

DECLARATION
We declare that this thesis is an original report of our research, has been written by
us and has not been submitted for any previous degree. This experimental work is
almost entirely our own work; the collaborative contributions have been indicated
clearly band acknowledged.
iii
DEDICATED
To
Our Beloved Parents, family, and also our best

friends Who remained there side by side with us
and make our little world complete
May Allah bless them with a very happy, successful and a

healthy life! (AAMEEN)
iv
ACKNOWLEDGEMENT
With the great name of Allah, the most gracious and merciful, who gifted us blessings,
strength and powers, without which we could not complete this project. Before we get
into thick of the things we would like to add a few heart felt words for the people who
were part of this project in numerous ways. People who gave unending support right from
the stage project idea were conceived. In particular we are extremely indebted our
respectable teacher and supervisor Mr. Faisal Bahadur of this project, and also we are
thankful to our class fellows and juniors for their support. Vivacious and exuberant
approach always put us on right track. We are extremely thankful to our beloved Parents
and family whose prayers and continuous encouragement made the successful completion
of this project possible. Thanks.
Muhammad Javid
Muhammad Hussain
Muhammad Ibrahim Malik
v
PROJECT BRIEF
Project Title: Digital School Diary
Developed By: Muhammad Javid

Muhammad Hussain
Muhammad Ibrahim Malik
Supervised By: Mr. Faisal Bahadur
Operating System: Microsoft Window 10
Tools Used: Andriod Studio, Java, XML, SQLite
System Used: Core i5, 3rd Gen, 4GB ram and 64bit O-S
vi
TABLE OF CONTENTS
CHAPTER 1 INTRODUCTION
1. Introduction................................................................................................................1
1.2 Introduction of the Tools used in the Project...........................................................1
1.2.2 XAMPP:................................................................................................................2
1.2.3 PHP:......................................................................................................................3
1.3 Scope of the Project.................................................................................................3
1.4 Feasibility of the Project..........................................................................................3
1.4.1 Economical Feasibility......................................................................................3
1.5 Introduction of Report..............................................................................................4
CHAPTER 2 PRESENT SYSTEM
2. Present System...........................................................................................................6
2.2 Data flow Diagrams.................................................................................................6
2.3 Flow Chart of Present System..................................................................................8
2.4 Why we need new system (Drawback or Limitations of the Present system)?.......8
2.5 What are available solutions for the Present issue...................................................9
2.6 Justification of the proposed system........................................................................9
CHAPTER 3 DESIGN OF PROPOSED SYSTEM
3. Design of Proposed System..............................................................................11
3.1 Introduction of Proposed System...........................................................................11
3.2 Flow Chart of the proposed system........................................................................11
3.3 Entities involved in the proposed system...............................................................12
3.3.1 User:....................................................................................................................12
3.3.2 Admin:.................................................................................................................12
vii
3.4 System Diagram of the Proposed System..............................................................13
3.5 Data base design.....................................................................................................14
3.5.1 Normalization......................................................................................................14
3.5.2 Denormalization..................................................................................................14
3.8 Algorithm of a system............................................................................................17
3.9 Justification of the proposed system......................................................................18
CHAPTER 4 TESTING
4.1 Testing Introduction...............................................................................................20
4.2 Purpose of Testing..................................................................................................20
4.3. Test Cases..............................................................................................................20
4.4. Conclusions...........................................................................................................23
CHAPTER 5 RESULTS/SCREENSHOTS
5 Results and Screenshots....................................................................................26
CHAPTER 6 REFERENCES
viii
LIST OF FIGURES
Figure 2.1 Level 0 Data flow Diagram................................................................................6
Figure 2.4 Flow chart of present system..............................................................................8
Figure 3.1 Flow chart of the Proposed System..................................................................11
Figure 3.2 System Diagram of the Proposed System.........................................................13
Figure 3.3 Entity Relationship Diagram............................................................................16
Figure 3.4 UML Sequence Diagram..................................................................................17
IX
CHAPTER 1
INTRODUCTION
1. Introduction
1.1 Introduction to the Project and its Background
This project is about Digital School Diary, which is an advanced mobile application for
school to make better communication between student/parents and teacher. With this app
parents can always remain up-to date with their child's notices and circulars, Homework,
Class Diary, Attendance, Fee, etc. School Diary upgrade institution with the paper less
mode of Teacher & Parents, and doing Communication with the help of this Android app.
1.2 Introduction of the Tools used in the Project
The tools use in the project are the following.
1.2.1 Android Studio:
Android Studio is the official Integrated Development Environment (IDE) for Android
app development. Based on the powerful code editor and developer tools from IntelliJ
IDEA . 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
 Apply Changes to push code and resource changes to your running app without
restarting your app
 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
 Built-in support for Google Cloud Platform, making it easy to integrate Google
Cloud Messaging and App Engine
ACC ONLINE RANKING AND PREDICTION SYSTEM 1

1.2.2 Java:
Java is a widely-used programming language for coding web applications. It has been a
popular choice among developers for over two decades, with millions of Java applications
in use today. Java is a multi-platform, object-oriented, and network-centric language that
can be used as a platform in itself. It is a fast, secure, reliable programming language for
coding everything from mobile apps and enterprise software to big data applications and
server-side technologies.

1.2.3 XML:
XML (Extensible Markup Language) is a markup language similar to HTML, but without
predefined tags to use. Instead, you define your own tags designed specifically for your
needs. This is a powerful way to store data in a format that can be stored, searched, and
shared. Most importantly, since the fundamental format of XML is standardized, if you
share or transmit XML across systems or platforms, either locally or over the internet, the
recipient can still parse the data due to the standardized XML syntax.
There are many languages based on XML, including XHTML, MathML, SVG, RSS,

and RDF.
1.2.4 SQLite:
SQLite is a C-language library that implements a small, fast, self-contained, high-

reliability, full-featured, SQL database engine. SQLite is the most used database engine in
the world. SQLite is built into all mobile phones and most computers and comes bundled
inside countless other applications that people use every day.
The SQLite file format is stable, cross-platform, and backwards compatible and the
developers pledge to keep it that way through the year 2050. SQLite database files are
commonly used as containers to transfer rich content between systems and as a long-term
archival format for data . There are over 1 trillion. SQLite databases in active use. SQLite
source code is in the public-domain and is free to everyone to use for any purpose.
1.3 Scope of the Project
The basic scope of my project to make better communication between student/parents and
teacher. With this app parents can always remain up-to date with their child's notices and
circulars, Homework, Class Diary, Attendance, Fee, etc. School Diary upgrade institution
with the paper less mode of Teacher & Parents, and doing Communication with the help
of this Android app.
1.4 Feasibility of the Project
1.4.1 Economical Feasibility

1.4.1.1 Software cost:
As I mentioned above that my tool is android studio and it is completed free of cost and if
upload it on Google Playstore for a local use then approximately $25(Rs.6265) are
required.
1.4.1.2 Transportation cost:
Does not use any hardware in my project.
1.4.1.3 Hardware cost:
Does not use any hardware in my project
1.4.2 Technical Feasibility:
As we know project only has software not hardware based so there is not technical
feasibility yet because it has no any connection between software and hardware.

1.5 Introduction of Report
Chapter 1 First chapter will provide a brief introduction of the project such as
background, problem statement, scope, tools and feasibility of the
Developing project.
Chapter 2 This chapter will covers why we need a new system if the existing system
occurs. What are the limitations of the existing system due to which we
come in need of new system? The available solutions to design and
develop new system and justification of the proposed system.
Chapter 3 This chapter will give a clear view of the proposed system. The aims and
objectives of proposed system. Moreover, it we define how sequences of
activities and data flow in a process and who is responsible for these
activities. Moreover the main modules and software requirements of
proposed system.
Chapter 4 Discuss the methods used for testing your system. The testing mainly
consists of the black-box and white-box testing. Also, here the
performance of the software is also tested.
Chapter 5 In this chapter the end results are shown which are given by the system. It
mainly consists of screen snips and figures.
Chapter 6 This chapter is composed of training manual that is intended to assist users
in using a particular product, service, or application. It's usually written by
a technician, product developer.

CHAPTER 2
PRESENT SYSTEM
2. Present System
2.1 Elaborate a scenario for present system
Some potential problems with hand-written student school diaries include:
Illegibility: Some students may have poor handwriting, making it difficult for teachers to
read their entries.
Inconsistency: Hand-written diaries may have inconsistent formatting, making it difficult

for teachers to quickly find information.
Error-prone: Hand-written entries are more prone to errors, such as mistakes in spelling
or grammar.
Time-consuming: Teachers may spend more time grading and providing feedback on
hand- written diaries, as they need to read through each entry and make corrections.
Loss or Damaged: Students may lose or damage their diaries which may cause loss of
important information.
Inefficient record-keeping: Hand-written diaries may make it difficult for teachers to

keep track of student progress over time, as they are not easily searchable or sort-able.
Digital solutions like e-diaries, learning management systems have been gaining
popularity to overcome these problems.
2.2 Data flow Diagrams
A data flow diagram (DFD) is a graphical or visual representation using a standardized

set of symbols and notations to describe a business's operations through data movement.
They are often elements of a formal methodology such as Structured Systems Analysis
and Design Method (SSADM). Superficially, DFDs can resemble flow charts or Unified
Modeling Language (UML), but they are not meant to represent details of software logic.
DFDs make it easy to depict the business requirements of applications by representing the
sequence of process steps and flow of information using a graphical representation
or visual representation rather than a textual description. When used through an entire
development process, they first document the results of business analysis. Then, they
refine the representation to show how information moves through, and is changed by,
application flows. Both automated and manual processes are represented.

LEVEL 0 DFD
Figure 2.1 Level 0 Data flow Diagram
LEVEL 1 DFD

LEVEL 2 DFD
2.3 Flow Chart of Present System

Figure 2.4 Flow chart of present system
2.4 Why we need new system (Drawback or Limitations of the Present

system)?
Some potential problems with hand-written student school diaries include:
Illegibility: Some students may have poor handwriting, making it difficult for teachers to
read their entries.
Inconsistency: Hand-written diaries may have inconsistent formatting, making it difficult

for teachers to quickly find information.
Error-prone: Hand-written entries are more prone to errors, such as mistakes in spelling
or grammar.
Time-consuming: Teachers may spend more time grading and providing feedback on
hand- written diaries, as they need to read through each entry and make corrections.
Loss or Damaged: Students may lose or damage their diaries which may cause loss of
important information.
Inefficient record-keeping: Hand-written diaries may make it difficult for teachers to

keep track of student progress over time, as they are not easily searchable or sort-able.
Digital solutions like e-diaries, learning management systems have been gaining
popularity to overcome these problems.
2.5 What are available solutions for the Present issue
As well as the solution is concerned Such a system is required where all manual functions
like attendance on registers, slips of tution fees, Result cards are completely transform
into Online like Android Application where two panels one for Teacher and Other for
Student-Parents having features like Daily base Diary, Timetables, Invoices, Daily
Attendance, Chat between Parents and Teacher And Results.
2.6 Justification of the proposed system
Our Proposed system be like a Android Application which has two panels one for
Teacher and Other for Student-Parents having features like Daily base Diary,

Timetables, Invoices, Daily Attendance, Chat between Parents and Teacher And
Results.

CHAPTER 3
DESIGN OF PROPOSED SYSTEM

3. Design of Proposed System
3.1 Introduction of Proposed System
As we start from a zero level, we need team’s data and make it organize. As I personally
observed their data is still manual also their daily tournament data is still on paper so, its a
forward step to make street talent on social media. In the result public can watch their
regional teams performance, scores, ranking even live prediction between the playing
teams.Our purposes to on-air our street talent to public and in the result public can
support them and bring them to international stadium. One another thing that my project
has an Automatic feature to calculating online ranks as well as prediction.
3.2 Flow Chart of the proposed system
Figure 3.1 Flow chart of the Proposed System
13
ACC ONLINE RANKING AND PREDICTION SYSTEM
3.3 Entities involved in the proposed system
Following are the main entities which are involved in the purpose system.
3.3.1 Teacher:
Figure 3.2 Teacher
3.3.2 Student:
Figure 3.3 Student
14
3.4 System Diagram of the Proposed System
Figure 3.4 System Diagram of the Proposed System

(Teacher side)
15
Figure 3.5 System Diagram of the Proposed System
(Student side)
16
3.5 Data base design
Database Design is a collection of processes that facilitate the designing, development,

implementation and maintenance of enterprise data management systems. Properly
designed database is easy to maintain, improves data consistency and are cost effective in
terms of disk storage space. The database designer decides how the data elements
correlate and what data must be stored. The main objectives of database design in DBMS
are to produce logical and physical designs models of the proposed database system. The
logical model concentrates on the data requirements and the data to be stored independent
of physical considerations.
3.5.1 Normalization
Normalization is a database design technique that reduces data redundancy and eliminates
undesirable characteristics like Insertion, Update and Deletion Anomalies.
Normalization rules divides larger tables into smaller tables and links them using
relationships. The purpose of Normalization in SQL is to eliminate redundant (repetitive)
data and ensure data is stored logically.
The inventor of the relational model Edgar Codd proposed the theory of normalization of
data with the introduction of the First Normal Form, and he continued to extend theory
with Second and Third Normal Form. Later he joined Raymond F. Boyce to develop the
theory of Boyce-Codd Normal Form.
3.5.2 Denormalization
Denormalization is a database optimization technique in which we add redundant data to

one or more tables. This can help us avoid costly joins in a relational database. Note that
denormalization does not mean not doing normalization. It is an optimization technique
that is applied after doing normalization.
In a traditional normalized database, we store data in separate logical tables and attempt
to minimize redundant data. We may strive to have only one copy of each piece of data in
database.
For example, in a normalized database, we might have a Courses table and a teachers
table. Each entry in Courses would store the teacher ID for a Course but not the teacher
17
Name. When we need to retrieve a list of all Courses with the Teacher’s name, we would
do a join between these two tables.
In some ways, this is great; if a teacher changes his or her name, we only have to update
the name in one place.
The drawback is that if tables are large, we may spend an unnecessarily long-time doing
joins on tables.
Deormalization, then, strikes a different compromise. Under denormalization, we decide

that we’re okay with some redundancy and some extra effort to update the database in
order to get the efficiency advantages of fewer joins.
The major Aims for database design are:
 To represent the data and relationships between data required by major applications
areas and user groups.
 To provide a data model that support any transactions required on data.
 To specify a design that will achieve the stated performance requirements for the
system such as response time.
Unfortunately these aims are not always easy to achieve and sometimes require comprises
to made,particular to achieve acceptable system performance. The two main approaches
to the design of a database system are referred to as the top down and bottom up
approaches.
In our project, we have used the top down approach.
The Top down database design approach is composed of two major two phases:
i) Logical database design
ii) Physical database design
18
3.6 Entity Relationship Diagram
Figure 3.6 Entity Relationship Diagram
19
3.7 UML Sequence Diagram
Figure 3.4 UML Sequence Diagram
3.9 Justification of the proposed system
20
Our Proposed system be like a Android Application which has two panels one for
Teacher and Other for Student-Parents having features like Daily base Diary,
Timetables, Invoices, Daily Attendance, Chat between Parents and Teacher And
Results.
21
CHAPTER 4
TESTING
4.1 Testing Introduction
After the development of any application, the major tasks are testing the application to
remove errors and deficiencies and then implementation of application with simple and
easy user interface so that anyone can use it with ease.
4.2 Purpose of Testing
Testing is any activity aimed at evaluating a function or capability of a product or

application and determining that it meets its required results. Testing is the process of
executing a program or application with the intent of finding errors. The focus of our test
strategy was primarily functional and end-to-end testing due to the limited development
time frame. The benefits of testing include preventing bugs, reducing development costs
and improving performance.
4.3. Test Cases
Test Scenarios
4.3.1 Teacher sign up test case
ID Test Test Case Pre- Steps Post- Expected Actual Test

Case Description Conditions Conditions Results Results Case
Name Status
01 Teacher Teacher Teacher must 1-If A report is After Teacher Pass

sign up should be be choose teachers generated Login then
Can
enter their “Teacher’’ completed confirming next page
now put
name,user Profile when their sign teacher sign up is arising
students
open the up then and login status where total
Name,p#no,
Related
application. open their is updated. 6 features
Address,and
side. like Info.
same
attendance,
2-If
passwords
teacher H-work,
in both
doesn’t marks,
boxes.
sign up, it
Invoices,
cant be
Chat, and
login.
Timetable.
23
4.3.2 Student sign up test case
ID Test Test Case Pre-Conditions Steps Post-Conditions Expected Actual Test

Case Description Results Results Case
Name Status
02 Student Student Student must 2-If A report is After Student Pass

should be be choose Student generated Login then
signup Can now
enter their “Student’’ confirming next page
completed check
name,user Profile when student sign up is arising
their sign
their
open the and login status where total
Name, up then
marks,
application. is updated. 6 features
father open their
like attendance,
name, roll side.
attendance, Invoices,
no,p#no,
2-If
H-work, Timetable,
Address,and Student
marks,
same doesn’t Hwork,
passwords sign up, it Invoices,
Results etc
in both cant be
Chat, and
boxes. login.
Timetable.
4.3.3 Add home work test case
ID Test Test Case Pre- Steps Post- Expected Actual Test

Case Description Conditions Conditions Results Results Case
Name Status
03 Add Teacher Teacher must 1- First Home work Home Home Pass
should add has teacher side should uploaded for work work
Home
subject access. be login students. shown on shown to
work
name, topic into students all
name, teacher side. students
description side. which
and date of 2- Then have
assign & click on applicatio
24
submission “ADD n and sign
Home up
Work’’ completed.
Icon.
4.3.4 Mark Attendance test case
I Test Case Test Case Pre- Steps Post- Expected Actual Test
D Name Descriptio Conditions Conditions Results Results Case
n Statu
s
0 Mark Teacher Teacher must 1-First Attendance Attendanc Attendanc Pass

4 Attendanc should has teacher should be were uploaded e e
e Mark side access. login into for students.
Shown to Shown to
attendanc teacher side.
all all
e on right Then click students. students
date and on
which
must click “Attendance have
on “OK” ” applicatio
button. n and sign
up
completed
.
4.3.5 Uploaded Students Result test case
ID Test Case Test Case Pre- Steps Post- Expected Actual Test
Name Descriptio Conditions Conditions Results Results Case
n Statu
s
0 Student Teacher Teacher must 1-First Results were Results + .Results + Pass
5 s should has teacher should uploaded to Grade + Grade +
mark be login Percentag Percentage
Result
25
students side access. into students side. e Shown to
marks. teacher all
shown to
side. students
all
Then students. which
click on have
applicatio
“Results
n and sign
”
up
completed
4.3.6 Add Invoices test case
I Test Test Case Pre- Steps Post- Expecte Actual Test

D Case Descriptio Conditions Conditions d Results Results Case
Name n Status
06 Add Teacher Teacher must 1-First Invoices are Invoices Invoices Pass
Invoice should has teacher side should be uploaded. are Shown to
s upload access. login into shown to all
students fair teacher students students
invoices. side. in their which
related have
Then
accounts. applicatio
click on
n and sign
“Student
up
s
completed
Invoice”
4.4. Conclusions
The Internet has become a major resource in every field, thus in this project has also
used internet to make it functional. To implement this as a android application we used
Java as the Technology. Java has several advantages such as enhanced performance,
scalability, built- in security and simplicity. To build any android application using
Java we need a programming language such as JAVA, XML and so on. JAVA was the
26
language used to build this application. Java uses SQLite server to interact with the
database as it provides in-memory caching that eliminates the need to contact the
database server frequently and it can easily deploy and maintain an application. SQLite
was used as back-end database since it is one of the most popular open source
databases, and it provides fast data access, easy installation and simplicity.
A good android application design must be accompanied with user-friendly

application logic. It should be convenient for the user to view the contents of their
application.The Digital school diary application described in this project provides a
number of features that are designed to make the user more comfortable. This project
helps in understanding the creation of an interactive features and the technologies used
to implement it. The design of the project illustrates how the database is built with
different tables, how the data is accessed and processed from the tables. The building
of the project has given me a precise knowledge about how Java is used to develop a
android application, how it connects to the database to access the data and how the
data and XML pages are modified to provide the user with a Digital Diary application.
27
28
CHAPTER 5
RESULTS/SCREENSHOTS
5 Results and Screenshots
5.1 Teacher sign up

Fig. 5.1 Teacher sign up
5.2 Student Sign up

Fig. 5.2 Student Sign up
5.3 Application Front End

Fig. 5.3 Application Front End
5.4 Add Home work from teacher side

Fig 5.4 Add Home work from teacher side
5.5 Students Results

Fig. 5.5 Students Results
5.6 Students Invoices

Fig 5.6 Students Invoices
5.7 Time table

Fig 5.7 Timetable
5.8 Attendance

Fig 5.8 Attendance

CHAPTER 6
REFERENCES
6 REFERENCES
[1] A. Jain, A. Shukla, and R. Rajan, "Password protected home automation system
with automatic door lock," MIT International Journal of Electrical and
Instrumentation Engineering, vol. 6, pp. 28-31, 2016.
[2] C. Gangadhar, R. Bhargude, A. Prabhu, A. Raut, and M. D. Bhosle, "BLE Based

Lock using Atmega 328."
[3] A. Mishra, S. Sharma, S. Dubey, and S. Dubey, "Password based security lock
system," International Journal of Advanced Technology in Engineering and
Science, vol. 2, no. 5, pp. 100-103, 2014.
[4] M. Van Der Werff, X. Gui, and W. Xu, "A mobile-based home automation
system," 2005.
[5] D. G. Seo, H. S. Ko, and Y. D. Noh, "Design and implementation of digital door
lock by iot," KIISE Transactions on Computing Practices, vol. 21, no. 3, pp. 215-
222, 2015.
[6] Y. A. Badamasi, "The working principle of an Arduino," in 2014 11th

international conference on electronics, computer and computation (ICECCO),
2014: IEEE, pp. 1-4.
[7] T. Adiono, S. Fuada, S. F. Anindya, I. G. Purwanda, and M. Y. Fathany, "IoT-

enabled door lock system," International Journal of Advanced Computer Science
and Applications, vol. 10, no. 5, 2019.
[8] H. Ahn and D. Lee, "The RELAY Module Design of Multi SNS Channel Auto
Streaming Server," Journal of Korea Society of Digital Industry and Information
Management, vol. 13, no. 4, pp. 213-219, 2017.
[9] M. Yuchun, H. Yinghong, Z. Kun, and L. Zhuang, "General application research

on GSM module," in 2011 International Conference on Internet Computing and
Information Services, 2011: IEEE, pp. 525-528.
[10] H. R. Esmaeel, "Apply android studio (SDK) tools," International Journal of

Advanced Research in Computer Science and Software Engineering, vol. 5, no. 5,
2015.
[11] M. Fezari and A. Al Dahoud, "Integrated development environment “IDE” for

Arduino," WSN applications, pp. 1-12, 2018.
[12] J. Voas, R. Kuhn, and P. Laplante, "Testing IoT Systems," in 2018 IEEE
Symposium on Service-Oriented System Engineering (SOSE), 2018: IEEE
Computer Societzay, pp. 48-52.

THESIS

Uploaded by

Document Information

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

THESIS

Uploaded by

Copyright:

Available Formats

DIGITAL SCHOOL DIARY

Muhammad Javid 52325-F18

Muhammad Hussain 52325-F18

Muhammad Ibrahim Malik 52325-F18

HAZARA UNIVERSITY, MANSEHRA

Roll No: Students Name:

Muhammad Hussain 52325-F18

Muhammad Ibrahim Malik 52325-F18

1. External Examiner _________________________

2. Internal Examiner _________________________

4. Head of Department _________________________

Our Beloved Parents, family, and also our best

May Allah bless them with a very happy, successful and a

Project Title: Digital School Diary

Developed By: Muhammad Javid

Supervised By: Mr. Faisal Bahadur

Operating System: Microsoft Window 10

Tools Used: Andriod Studio, Java, XML, SQLite

1.2 Introduction of the Tools used in the Project...........................................................1

1.3 Scope of the Project.................................................................................................3

1.4 Feasibility of the Project..........................................................................................3

1.4.1 Economical Feasibility......................................................................................3

1.5 Introduction of Report..............................................................................................4

CHAPTER 2 PRESENT SYSTEM

2.2 Data flow Diagrams.................................................................................................6

2.3 Flow Chart of Present System..................................................................................8

2.5 What are available solutions for the Present issue...................................................9

2.6 Justification of the proposed system........................................................................9

CHAPTER 3 DESIGN OF PROPOSED SYSTEM

3. Design of Proposed System..............................................................................11

3.1 Introduction of Proposed System...........................................................................11

3.2 Flow Chart of the proposed system........................................................................11

3.3 Entities involved in the proposed system...............................................................12

3.5 Data base design.....................................................................................................14

3.8 Algorithm of a system............................................................................................17

3.9 Justification of the proposed system......................................................................18

4.1 Testing Introduction...............................................................................................20

4.2 Purpose of Testing..................................................................................................20

4.3. Test Cases..............................................................................................................20

5 Results and Screenshots....................................................................................26

Figure 2.1 Level 0 Data flow Diagram................................................................................6

Figure 2.2 Level 1 Data flow Diagram................................................................................7

Figure 2.3 Level 1 Data flow Diagram................................................................................7

Figure 2.4 Flow chart of present system..............................................................................8

Figure 3.1 Flow chart of the Proposed System..................................................................11

Figure 3.2 System Diagram of the Proposed System.........................................................13

Figure 3.3 Entity Relationship Diagram............................................................................16

Figure 3.4 UML Sequence Diagram..................................................................................17

1.1 Introduction to the Project and its Background

1.2 Introduction of the Tools used in the Project

The tools use in the project are the following.

1.2.1 Android Studio:

 A flexible Gradle-based build system

ACC ONLINE RANKING AND PREDICTION SYSTEM 1

ACC ONLINE RANKING AND PREDICTION SYSTEM 2

There are many languages based on XML, including XHTML, MathML, SVG, RSS,

SQLite is a C-language library that implements a small, fast, self-contained, high-

1.3 Scope of the Project

1.4 Feasibility of the Project

1.4.1 Economical Feasibility

ACC ONLINE RANKING AND PREDICTION SYSTEM 3

1.4.1.2 Transportation cost:

Does not use any hardware in my project.

1.4.1.3 Hardware cost: