Information Technology and Computing Department

Project Title

By
Student Name ID: XXXXXX

T227: TMA, Date

Supervisor: Name of tutor
 SIGNED DECLARATION

Plagiarism Warning:

As per AOU rules and regulations, all students are required to submit their own work
and avoid plagiarism. The AOU has implemented sophisticated techniques for
plagiarism detection. You must provide all references in case you use and quote
another person's work in your assignments. You will be penalized for any act of
plagiarism as per the AOU's rules and regulations.

Declaration of No Plagiarism by the students:

We hereby declare that this submitted report is a result of our own efforts and we have
not plagiarized any other person's work. We have provided all references of information
that we have used and quoted in our assignment.

Student Name: XXXX XXXX

Student Signatures: XXXX XXXX – ID:XXXXXX
Date: XX/XX/2023
 ABSTRACT

This report outlines the comprehensive plan for the development of a multifunctional
mobile application designed for an educational institution. The project aims to create an
innovative and user-centric platform catering to various needs within the school
community.

The proposed mobile application encompasses an array of features including the

dissemination of school news, class information, detailed cost breakdowns, and an
integrated credit card payment system. Additionally, it offers comprehensive profiles of
teaching staff, exam schedules, bus timetables, event calendars, holiday dates, catering
menus, chat services, user feedback channels, contact information, and precise school
location through Google Maps.

The report details the functional requirements, technical specifications, user experience
design considerations, development plan, and implementation strategies. It also
addresses risk assessment, timelines, and milestones crucial for successful execution.
The integration of various functionalities within a user-friendly interface aims to enhance
accessibility, communication, and engagement among students, faculty, and parents.

This mobile application project serves as an essential tool to streamline communication,

improve accessibility to vital information, and foster an enriched educational experience
within the school community.
 TABLE OF CONTENTS
TITLE i

SIGNED DECLARATION ii

ABSTRACT iii

TABLE OF CONTENTS iv

ACKNOWLEDGEMENTS v

GLOSSARY of TERMS and DEFINITIONS vii

Chapter 1: Introduction 1

1.1. Background Information 1

1.2. Motivations of the Project 2

1.3. Problems of the Project 2

1.4. Aims and Objectives of the Project 3

1.5. Proposed Solution of the Project 3

1.6. Constraints of the Project 4

1.7. Structure of the Project 4

Chapter 2: A Literature Review 5

2.1. Introduction 5

2.2. Related Works 6

2.3. The relationships between Related Works and your Own Work 7

2.4. The Reasons of Developing your Own Work 8

2.5. A Comparison between Related Works and your Own Work 9

2.6. Chapter Summary 10

Chapter 3: The Teams and their Responsibilities 11

Chapter 4: Planning Phase12

4.1. Work Breakdown Structure of your Project 12

4.2. Project Cost Estimation and Budget 13

4.3. A comparison between your own project and other related projects regarding

to Cost estimation and budgeting……………………………………………………14

4.4. Network Activity Diagram of your Project 15

4.5. The Critical Path and Project Duration 15

Chapter 5: Conclusions …………….Page #

REFERENCES AND BIBLIOGRAPHY ……….……Page #

APPENDICES (If any) ……………Page #

Appendix A: XXXXX XXXXXX ……………Page #

Appendix B: XXXX XXXXXX …………….Page #

Etc…
 ACKNOWLEDGMENTS

Starting with the name of ALLAH ALMIGHTY, Most Gracious, and Most
Merciful. Firstly, who enabled us to finalize our project effectively. We
would like to thank our parents and teachers who helped us financially and
morally at all times. We would also like to thank Supervisor Name for
guiding us to work hard. We found it very helpful to discuss our plan. His
critical comments on our work have made us think of new ideas. We are
thankful to Allah Almighty who gave us all the resources to make this
project for the benefit of mankind. We are cordially grateful to our parents,
family, and friends who kept backing us up all the time. We are immensely
thankful to them for supporting us, both financially and morally. We would
also like to thank Supervisor Name for his guidance and encouragement.
He has been there all along, so much helpful while discussing the
optimization issues in this dissertation work. His critical comments on our
work are of supreme importance. Those comments surely have made me
think of new ideas and techniques in the fields of optimization and software
simulation
 GLOSSARY OF TERMS AND DEFINITIONS
Some of the repeated keyword in the document are as follows:
1. SDLC: Software Development Life Cycle.
2. WBS: Work Breakdown Structure.
3. Optimistic Time: Minimum time required to complete the task.
4. UI: User Interface.
5. R: Responsible.
6. C: Consulted.
7. A: Accountable.
8. I: Informed.
9. Early Start Time: The ES is the maximum EF of all predecessors, except for the first
task where the ES=0.
10. SMS: School Management System.
11. PERT: Project Evaluation and Review Technique
12. AND: Activity Network Diagram
 Chapter 1: Introduction

1.1. Background Information

The educational institution is seeking to improve its communication, accessibility, and

engagement within the school community. There’s a recognized need for a more
efficient and centralized means of disseminating information, managing services, and
enhancing interaction among students, parents, teachers, and administrative staff.

Challenges in effective communication, information dissemination, and engagement

among students, faculty, and parents have been identified within the school community.
These challenges include the schedule time for class, cost of each class, payment of
the course and the exact location of the institute etc. as well.

To address these challenges, the decision was made to develop a mobile application.
This choice is based on the recognition of the widespread use of mobile technology and
the need for a more efficient and accessible platform for communication and information
sharing.

The mobile application project aims to bridge these communication gaps and provide a
centralized platform for accessing crucial school-related information, enhancing
engagement, and streamlining various processes for the benefit of all stakeholders.

This condensed background provides a snapshot of the school, its identified challenges,
and the rationale behind opting for a mobile application as a solution.
1.2. Motivations of the Project

The motivation behind this project lies in revolutionizing the institution's communication
infrastructure through the development of a comprehensive mobile application. The
project team, comprising dedicated professionals, aims to address existing challenges
that hinder seamless information sharing and interaction among stakeholders.
Essentially, this is a planning and organizing tool that attempts to arrange lessons,
exams, fees, current school news, modes of payment, and precise location information
via Google map integration.

1.3. Problems of the Project

The project aims to address several key challenges, including:

 Fragmented Information: Dispersed data across various channels leading to

difficulties in accessing critical information.
 Communication Inefficiency: Lack of a centralized communication platform
causing delays and gaps in information dissemination.
 Administrative Complexity: Manual processes and disparate systems leading
to inefficiencies in service delivery.

Simplifying communication, combining data, and streamlining administrative procedures

are the goals of developing a complete mobile application to address these issues. The
project seeks to alleviate these obstacles and improve the general efficacy and
efficiency of the school's operations and communication channels by offering a
centralized platform for obtaining vital information, enabling smooth communication, and
integrating diverse functionalities.
1.4. Aims and Objectives of the Project

The main aim is to develop a multifunctional mobile application tailored specifically to

the school's requirements.
Streamlining Communication: Establishing a centralized platform for seamless
information sharing.
Enhancing Accessibility: Facilitating easy access to school-related information and
services.
Optimizing Administrative Processes: Integrating functionalities to streamline
administrative tasks.
The objective behind this application is to help the individuals, to provide the online view
about the school as well as provide the different information regarding the latest news
about the school, availability of the classes, cost of each classes, the payment services
that is integrated through credit card etc.

1.5. Proposed Solution of the Project

The proposed method entails creating a feature-rich mobile application with the
following functionalities:
 Immediately News Release.
 Listings of Classes with Extensive Prices.
 Services for Safe Credit Card Payment.
 Entire Teacher Profiles.
 Publication of Exam and Bus Schedules Holiday Dates and Event Showcasing
Information on Food and Beverages is shown.
 Services for Chat, Complaints, Queries, and Feedback.
 Get in touch with us and integrate Google Maps.
1.6. Constraints of the Project

A few of the project's constraints are limited funds, following data security regulations,
needing to integrate with current systems seamlessly, and interoperability with different
devices. Sometimes the non-functional requirements such as the integrity security,
availability, response time, maintainability and performance of the application may act
as the constraint. But the main aim is to provide such application which have minimum
number of the constraint.

1.7. Structure of the Project

The project will follow the organized Agile Software Development Life Cycle (SDLC),
which includes phases for testing, deployment, requirement analysis, design,
development, and maintenance. The main aim to follow this structure is because Agile
is based on the iterative process. The phases will be explained in more detail in the
report's later sections. This structured SRS report outline will address Background
Information, Motivations, Problems, Aims and Objectives, Proposed Solution,
Constraints, Project Structure, Literature Review, Team and their responsibility and
planning phase etc. all of which are in line with the features that have been identified for
the educational school's mobile application.
 Chapter 2: A Literature Review
2.1. Introduction

This section introduces the literature review by describing the importance and goal of
reviewing the literature that has already been written about developing a mobile
application for an educational institution. It highlights how crucial it is to comprehend
earlier research and how it relates to the current project.

In this section, we present a general review of previous work on education school

applications. There are some school websites/application that provides services at
home and office. The applications/websites like School Management by Ustaad, , etc.
uploaded on the Google play store but these apps don’t have the same functionalities
as our application our School mobile application.

The primary drawbacks of applications such as School Management by Ustaad are their
lack of services and payment integration systems, schedule of buses, chat services as
well as provide the information about the cafeteria in the school as well. Our primary
goal in developing this app is to use it to help those who want all services about the
school application in just one click.
The rapid penetration of increasingly sophisticated technologies into every facet of
society is causing significant shifts in how, when, and, where we work, how individuals
and companies organize themselves, and how our apps should be structured to
complete the other app development companies

2.2. Related Works

This section conducts a thorough review of research papers, educational institution-

specific mobile applications, and pertinent literature. It concentrates on works that deal
with features and functionalities akin to those envisioned for the suggested mobile
application.
In our app we have many function requirements or features like latest news, availability
of the classes, cost, and information about faculty, payment, and schedule of the exam,
chat services and many more. In this section we examine the already solution features
with our proposed solution.
 SMS By Ustaad
This application can only focus on the availability of classes’ exam schedule and
complaint cell etc. This application cannot provide payment method, latest news to
students or provide much more information about the school as well.
 My Skool

This application provides the information about the latest news, availability of classes’,
payment, exam schedule and complaint cell etc. This application cannot provide cost
per class, café menu and location to students or provide much more information about
the school as well.
  GPS SMS

This application provides the information about the availability of classes’, faculty
information, exam schedule, schedule of buses and complaint cell etc. This application
cannot provide much more information like the cost per class, information about café
menu and location to students or provide much more information about the school as
well.

2.3. The relationships between Related Works and your Own Work

The objective of this subsection is to create links and associations between the results
from the body of current literature and the suggested creation of the educational
institution's mobile application. It highlights the ways in which the features,
functionalities, and difficulties found in related works correspond with or diverge from
the goals and objectives of the project.

The main relationship between the proposed solution and the given solutions are that
both create such application which enhance the quality of the education. The features
like:
 Availability of Classes
 Exam Schedule
 Complaints Cell
The above feature same in our mobile application and the already system such as
MySkool, School Management by Ustaad, School log and GPS School Management
System.

Availability of Classes shows classes that are available or courses that are being
offered by educational institutions may be present in existing applications. We also have
a feature in our proposed mobile application that shows the classes that are available. It
may, however, seek to offer more thorough information than what is offered by the
current apps.

Applications that are already in use may contain a section or feature that shows exam
schedules for students enrolled in schools. There's an exam schedule feature in my
mobile application as well with user friendly interface.

There may be a complaints or feedback section in some current apps. The suggested
mobile application has a complaints service as well. It might, however, seek to enhance
this feature by putting in place a more user-friendly interface.

2.4. The Reasons of Developing your Own Work

There are a number of different factors that may motivate us to develop own work, in
this case, a mobile application for the educational institution. There are some
relationship between the proposed solution and the given solutions.

The features are same in both our solution and the related work like:
 Availability of Classes
 Exam Schedule
 Complaints Cell

The above feature same in our mobile application and the already system such as
MySkool, School Management by Ustaad, School log and GPS School Management
System.

But the reason of developing the own work or solution was made for the following main
reasons and these are discussed below:
 The interface is very user friendly and easy to use.
 The app include all the necessary information about school.
 Reduced the number of constraint as much as possible.
 Integration of the Google Map to find the location as easy as possible.
  Provide the information about the school cafeteria and all the necessary
information regarding school.
 Payment method is integrated which will be easy for everyone.
 Focus both on the functional requirement as well as the non-function
requirements.

2.5. A Comparison between Related Works and your Own Work

The functionalities, features, strengths, and weaknesses found in related works and
those suggested for the creation of the institution's mobile application are compared and
contrasted in this section. It highlights novelties, enhancements, or aspects of the
suggested solution that set it apart from others. The comparison between the proposed
solutions and the related work are as follow
2.6. Chapter Summary

This structured chapter address that when creating a mobile application for a learning
institution, the introduction section emphasizes the value of reviewing the literature
already in existence and stresses the need to understand past research and how it
relates to the current project. It outlines the features of several current school apps as
well as their drawbacks, highlighting the necessity for a comprehensive app that
incorporates features lacking in existing solutions, such as exam schedules, class
availability, and a complaints cell.
The sections that follow examine how these current features relate to the suggested
mobile application, emphasizing how to improve user interfaces, provide thorough
information, and enhance functionalities. The planned app was developed for a number
of reasons, including its user-centered design, extensive school information, less
restrictions, integration of Google Maps, cafeteria details, payment options, and a
balance between functional and non-functional requirements. The ultimate goal is to
provide an all-inclusive and intuitive solution, combining various educational services
into a single, user-friendly platform.

Chapter 3: The Teams and their

Responsibilities
This chapter include the role and responsibility of the team member or stockholders of
your Project.
Our Project has a team leader, frontend and backend developers and a financial analyst
as well. The R shows that who is responsible for the particular task. The C shows that
the respective task must be consulted to particular team member. A shows the
accountable and I denotes the Informed, before after that task the member must ask to
sponsor to give the feedback about task

Chapter 4: The Planning Phase

4.1. Work Breakdown Structure of your Project
The project's deliverables were arranged hierarchically in the WBS. It implies that the
project is actually monitored and organized by the actual structure. It gives us a
reporting structure that incorporates planning and performance capture, and it enables
us to divide the scope into more manageable chunks. We can examine the project at its
lowest level, rolled up to look at it as a whole, or somewhere in between thanks to the
hierarchical structure. The Work Break down structure of our project are as follows:

4.2. Project Cost Estimation and Budget

4.3. A comparison between your own project and other related projects regarding

to Cost estimation and budgeting

As in our related work they does not provide so much information about the cost
estimation so it is very difficult to compare the cost estimation and budget.

4.4. Network Activity Diagram of your Project

Activity Network diagram also known as PERT diagram that is used for identifying the
sequence of the events and the time sequence as well. Some of the important events of
our app are as follow

 Design 12 Days
 Prototype 2 Days
 Front End 5 Days
 Backend 10 Days
 Integration 5 Days
 System Testing 1 Day
 Beta Testing 2 Days

The above figure shows that the front end is not done before the prototype and the
integration will be done after the completion of the front end and backend. On the other
hand the design is the first step and the beta testing is the last step in our Activity
Network Diagram.

4.5. The Critical Path and Project Duration

This phase include the step by step project management process in which the project is
divided into the most smaller, critical task that progress from the idea generation to the
completion of the project.. Critical Path helps to determine which task has zero slack
time or most critical and which task can be delayed or low prioritize. The Critical Path and
Project Duration of our project is given below.
 Chapter 5: Conclusions
This Application has now gone to the last stage. Application is created with a lot of care
in flutter utilizing Dart Language. This Application is free of errors, and mistakes and in
meantime very much effective, beneficial, and easy to use. By this proposed system it is
to help the individuals, to provide the online view about the school as well as provide the
different information regarding the latest news about the school, availability of the
classes, cost of each classes, the payment services that is integrated through credit
card etc. The android application can therefore save our time in difficult situations. In
future, this system can be implement in hardware and we can even have the payment
through online. The main aim behind this application is to help individuals, to provide
online services and also to give essential for both students and the faculty of the school.
The application we are going to reduce the student workflow when they face some
problems in exam time, to check class availability, bus schedule time and the latest
news about school. In our application student will be able to check this services. Every
individual will be available on our app. The purpose of our app is to provide business
ease to our country in the new technological world. In the current decade we know
education is very important. So, in this case, we are created an application that will help
people to save their precious time and it also benefit for student and school as well.
 REFERENCES AND
BIBLIOGRAPHY
It is essential to include a reference or bibliography of the reference material you
consulted during your research for the report. A bibliography is a list of all the
reference material you consulted during your research for the report while a reference
list is a list of all the references cited in the text of your report, listed in alphabetical
order at the end of the report. Each reference in the reference list needs to contain all of
the bibliographic information from a source.

Throughout the text of your report you will also need to provide references when you
have included an idea in your report which is not your own original idea. You don't need
to reference an idea, however, if it is common knowledge (i.e. enzymes are proteins) or
if it has been established by you in your experiment (i.e. in scientific reports reporting on
an experiment). A reference is the bracketed or footnoted piece of information within the
text of your writing that provides an acknowledgment that you are using someone else's
ideas.

At AOU, we use the Harvard Referencing System.

 APPENDICES
Information that is not essential to explain your findings, but that supports your analysis
(especially repetitive or lengthy information), validates your conclusions or pursues a
related point should be placed in an appendix (plural appendices). Sometimes excerpts
from this supporting information (i.e. part of the data set) will be placed in the body of
the report but the complete set of information (i.e. all of the data set) will be included in
the appendix. Examples of information that could be included in an appendix include
figures/tables/charts/graphs of results, statistics, questionnaires, transcripts of
interviews, pictures, lengthy derivations of equations, maps, drawings, letters,
specification or data sheets, computer program information.

There is no limit to what can be placed in the appendix providing it is relevant and
reference is made to it in the report. The appendix is not a catch net for all the semi-
interesting or related information you have gathered through your research for your
report: the information included in the appendix must bear directly relate to the research
problem or the report's purpose. It must be a useful tool for the reader.

Each separate appendix should be lettered (Appendix A, Appendix B, Appendix B1,

Appendix B2, Appendix C, etc). The order they are presented in is dictated by the order
they are mentioned in the text of the report. It is essential to refer to each appendix
within the text of the report; for example,

For the manufacturer's specification, see Appendix B

or

Appendix C: Formula for Calculation of Rates/Cost

This appendix includes the various details on how the cost or the rate were calculated
for various aspects of the project. The formula to calculate the hourly rate is:
Hourly Rate Cost= (Total Project Cost- Other Expenses) / Total Estimated Hours
We also include the total project cost and that is approximately $6630. Here we just add
other cost with the summation of Hourly rates into estimated hours.
The Formula for calculate the project cost is:
Total Project Cost= Sum of (Hourly Rates * Estimated Hours) + Other Costs.