Final Project Report: Web Portal For Saif Shahid Model School

WEB PORTAL FOR SAIF SHAHID MODEL SCHOOL
Final Project Report

BSIT 2015-2019
Project Supervisor
Ghulam Irtaza
Submitted By
Muhammad Azhar 6662
Department of Information Technology,

University of Education, Lahore.
(Multan Campus)
DEPARTMENT OF INFROMATION SCIENCES 1

CERTIFICATE
This is to certify Muhammad Azhar has worked on and completed their Software Project at Department
of Information Technology , University of Education, Lahore in partial fulfillment of the requirement for
the degree of MSc IT under my guidance and supervision.
In our opinion, it is satisfactory and up to the mark and therefore fulfills the requirements of MSc in
Information Technology.
Supervisor / Internal Examiner
Ghulam Irtaza
Department of Information Technology,
University of Education, Lahore.
(Multan Campus)
___________________
(Signature)

TABLE OF CONTENTS
CHAPTER NO. 1
GATHERING & ANALYZING INFO
1.1 INTRODUCTION
1.2 PURPOSE
1.3 SCOPE
1.4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS
CHAPTER NO. 2
SOFTWARE REQUIREMENT SPECIFICATION
2.1 FUNCTIONAL REQUIREMENTS

2.2 NON-FUNCTIONAL REQUIREMENTS
2.2.1 Reliability
2.2.2 Supportability
2.2. 3 System Requirements
2.2.4 Usability
2.2.5 Efficiency
2.2.6 Portability
2.3 DOMAIN REQUIREMENTS
2.4 USE CASES AND USAGE SCENARIOS
2.4.1 Use Case Diagrams
2.4.2 Usage Scenarios
CHAPTER NO. 3
PLANNING THE PROJECT
3.1. INTRODUCTION
3.2. METHODOLOGY
3.2.1. AVAILABLE METHODOLOGIES

3.2.2. CHOSEN METHODOLOGY
3.3. REASONS FOR CHOSEN METHODOLOGY
3.4. WORK PLAN
3.5. PROJECT STRUCTURE
3.5.1. Team Structure
3.5.2. Project Schedule (Submission Calendar)
CHAPTER NO. 4
DESIGNING THE PROJECT
4.1. INTRODUCTION
4.2. PURPOSE
4.3. SCOPE
4.4. DEFINITIONS, ACRONYMS AND ABBREVIATIONS
4.5. ARCHITECTURAL REPRESENTATION (ARCHITECTURE DIAGRAM)
4.6. DYNAMIC MODEL: SEQUENCE DIAGRAMS
4.7. OBJECT MODEL/LOGICAL MODEL: CLASS DIAGRAM

4.8. DEPLOYMENT MODEL (DEPLOYMENT DIAGRAM)
4.9. DATABASE MODEL (ER-DIAGRAM, DFD)
4.10. GRAPHICAL USER INTERFACES
CHAPTER NO. 5
DEVELOPMENT AND IMPLEMENTATION
5.1 DEVELOPMENT PLAN (ARCHITECTURE DIAGRAM)
CHAPTER NO.6
TESTING
6.1 INTRODUCTION
6.2 TEST PLAN
6.2.1 UNIT TESTING
6.2.2 SYSTEM TESTING
6.2.3 INTEGRATIONT TESTING
6.2.4 USER ACCEPTANCE TESTING
6.3 TEST CASES

6.4 RESULTS
CHAPTER NO.7

CONCLUSION & FUTURE WORK
7.1 DISCUSSION
7.2 FUTURE WORK
CHAPTER NO.8
DEPLOYMENT
8.1 DEPLOYMENT PLAN (DEPLOYMENT DIAGRAM)
REFERENCES

CHAPTER 1
Gathering & Analyzing Info
1.1 Introduction:-

Saif Shahid Model School (SSMS) was established in 2002 is a premier institute of learning, committed to
maintain high academic standards, promoting students’ success and creating opportunities for life learning. The
School will inspire students to become well‐informed, active, and useful citizens who recognize and appreciate
the humanity through diverse curricula and cultural, academic, and artistic events. Therefore, it is also essential
to equip our students with excellent language skills. In order to facilitate and simplify these actions one of the
basic tool is to have an automated school management system. Automation is the utilization of technology to
replace human with a machine that can perform more quickly and more continuously.
By automating the Saif Shahid Model School (SSMS), documents that take up large storage rooms can be stored
on a single personal computer. School Management System is a large database system which can be used for
managing school’s day to day business. Allows users to store almost all of their school’s information
electronically, including information on students, employees, properties, teaching materials etc. Most
importantly, this information can be easily shared with authorized users, records can be easily searched, and
reports can be easily generated. System could make your school staff's life easier than ever. Using System,
finding student information is just a few seconds away which might have cost hours, or even days, before. At
the end of the session, printing students' statements, becomes just a few minutes' job but it could be difficult
without using School Management System
1.2 Purpose:-
The academic achievement for many students has decline, because of lake of care of them from their
parents, and this refer to that their parents do not have a free time to come to school . Headmasters and
Teachers are facing problems at the start of every new academic year, because of distribution process for
courses and classes, in addition to this , through and at the end of every year another problem is facing
them, which is the complexities of the grades entry process for their students . Lack of communication
after a school day between Headmasters, Teachers, Parents and Students, which has a bad reflection on
the educational process.
Some main Purposes are:-
- To build a responsive website to manage the different school activities.
- To track student’s grades from their parents.
- To facilitate distribution process of courses and classes for teachers.
- To facilitate grades entry process for students by teachers.
- To make a virtual community between the members of educational process.
1.3 Scope:-

Saif Shahid Model School’s Web Portal (SSMS) has been designed to provide an easy way for their students
to get their grades, and for their parents to be familiar with that grades and the academic achievement for their
kids .However this project is facing some obstacles which is deny it from achievement it’s goals, like lack of
acceptance these idea from some teachers and headmasters, because of their poor knowledge about using that
technology or they find that using computers in their works instead of the paper works so hard and difficult. And
also the same thing for some parents where they do not prefer that way for the same previous reasons.
The scope of “Saif Shahid Model Public School” covers the following:
• Detail of student information

• Date wise detail of students based on date of admission
• Detail Student Information
• Detail Student Timing information
• Details of Staff information
• Detail Staff information
• Manage Reports Of All Information
• Inform Parents via Email
1.4 Definitions, Acronyms and Definitions:-

School information system includes every information of a student like student admission information,
examination information, teacher and children timing, managing fees .
• HTML: Hyper Text Markup Language
• PHP: Hypertext Preprocessor
• SQL: Structured Query Language
• SSMS:Saif Shahid Model School

CHAPTER 2
Software Requirement Specification
2.1 System Requirement:-

Before creating any website or a mobile App, it is necessary to visualize the layout, design and all features intended
to be incorporated. In addition, how users will interact with each page and icon and how the website/App should
perform (behavior, load time etc.). Requirements are the necessary attributes in the system,
a statement that identifies a capability, characteristic or quality factor of the system in order to have value and utility
to the users. Once the requirements are set, developers can initiate the other technical work including system design,
development, testing, implementation, and operation. For any system, there are functional and non-functional
requirements to be considered while determining the requirements of the system. The functional
requirements are user “visible” features that are typically initiated by stakeholders of the system, such as generate
report, login, and signup. On the other hand, nonfunctional requirements are requirements that describe how the
system will do what it is supposed to do, for example, security, reliability and maintainability.
2.2 Functional Requirement

2.2.1 For Admin:-
- Create, edit and delete student account.
- Create, edit and delete teacher account.
- Create, edit and delete parent account.
- Post tasks or any updates for users (Teacher, Student, and Parent).
- Store, edit, delete, calculate and print student's grade.
- Add Classes and Subject and connect them with the subject’s teachers.
2.2 .2For Teacher:-

- Enter Student's grades per Subject.
- Contact with students and parents.
- Post tasks or any updates for users (Admin, Student, and Parent).
2.2.3 For Student:-

- View their grades.
- Contact with their teacher and headmaster.

2.2.4 For Parent

- View the grades of their children.
- Contact with their children’s teachers and headmaster.
2.3 Non-Functional Requirement:-
In systems engineering and requirements engineering, a non-functional requirement (NFR) is a requirement that
specifies criteria that can be used to judge the operation of a system, rather than specific behaviors. ... Non-functional
requirements are often called "quality attributes" of a system.
2.3.1 Security:-
Every user has his own account and only authorized users can access the system with username and password.
The passwords are encrypted using a PHP function sha1 ().
2.3.2 Reliability
Reliability is an attribute of any computer-related component (software, or hardware, or a network, for example)
that consistently performs according to its specifications. It has long been considered one of three related attributes
that must be considered when making, buying, or using a computer product or component
Frequency/severity of failure, recoverability, predictability, accuracy.
2.3.3 Supportability
Supportability is the degree to which system design characteristics and planned logistics resources meet system
requirements. Supportability is the capability of a total system design to support operations and readiness needs
throughout the life-cycle of a system at an affordable cost.
2.3.4 Performance:-
Easy tracking of records and updating can be done.
2.3.5 Availability:-
The system are available to users anytime, anywhere, just need a PC and

Internet Connection. Also the system work in multiple web browsers like
(Chrome, Mozilla, Opera, and Internet Explorer).
2.3.6 User Friendly:-

The system have a friendly user interface and the system very interactive.
2.4 Domain Requirements:-

- Track student performance and progress
- Keep a check on student attendance
- Availability of the exam schedule at regular intervals
- 4. Help in two way interaction with students as well as their parents
2.5 Use cases and Usage Scenerios:-

This part contains the analysis of the functional and non-functional requirements using use-case
diagrams, and use-cases details.
Admin:-
o The functions that Admin can do after login,
o Add Teacher include (Modify/Delete).
o Add Student include (Modify/Delete).
o Add Parent include (Modify/Delete).
o Add Class include (Modify/Delete).
o Contact with teachers, students and parents.

Student:-
The functions that Student can do after login, function as shown in figure 8:
- View Personal Information.
- View Courses Marks.
- View Personal Details.
- Contact with teachers and headmaster.

Teacher:-
The functions that Teacher can do after login:
o Enter Student's grades.
o Modify or delete grades.
o Contact with students, parents and headmaster.
Teacher use case Diagram
Parent:-
The functions that Parent can do after login, as show
- View their children’s grades.
- Contact with teachers and headmaster.

2.6 Sequence Diagram:-

Describes an Interaction by focusing on the sequence of Messages that are exchanged, along with their
corresponding Occurrence Specifications on the Lifelines
Sequence Diagram
Activity Diagram:-

Describe dynamic aspects of the system. It is basically a flow chart to represent the flow form
one activity to another activity. The activity can be described as an operation of the system. So the
control flow is drawn from one operation to another.
Activity Diagram

CHAPTER 3
Planning the Project
3.1 Introduction

This chapter states the methodology used to reach the objectives of the project. The framework in which
software is designed, developed, and maintained is known as the Software Development Life Cycle
(SDLC). It shows the steps, phases, milestones, and evolution of the software development process. There
are many types of models used in software design and development. Among them are the spiral models,
rapid development model, Evolutionary model, waterfall model, prototyping model, etc
Methodology
Prototyping Model has been used to develop this application. The Prototyping model is a technique for
quickly building a function but incomplete model of the information system. There are several kinds of
prototypes but they all intend to reduce risk by building a quick and dirty replica or mockup of the intended
system. It can be used to demonstrate technical feasibility when the technical risk is high. It can also be
used to better understand and elicit user requirements. In either case, the goal is to reduce risk and limit
costs by increasing understanding of proposed solutions before committing more resources.
Prototype Model Process.
3.2 Prototype Model

3.2.1 Advantages of Prototyping
• Reduces development time.
• Reduces development costs.

• Requires user inolvement.
• Developers receive quantifiable user feedback.
• Facilitate system implementation since users know what to expect.
• Results in higher user satisfaction.
• Exposes developers to potential future system enhancements.
The Process of Prototyping
- Identify basic requirement: Determine basic requirements including the

input and output information desired. Details, such us security, can typically
be ignored.
-Develop initial prototype: The initial prototype is developed that includes

only user interfaces.
-Review: The customers, end-users, examine the prototype and provide

feedback on additions or changes.
-Revise and enhancing the prototype: Using the feedback, both the
specifications and the prototype can be improved.
This method involves a series of iterations and refinement until the prototype
product is a fully working system, and the user is satisfied

Reason of using Prototype Model
▪ Users are actively involved in the development.
▪ Since in this methodology a working model of the system is provided, the users get
a better understanding of the system being developed.
▪ Errors can be detected much earlier.
▪ Quicker user feedback is available leading to better solutions.
▪ Missing functionality can be identified easily.
▪ Confusing or difficult functions can be identified requirements validation, quick

implementation of incomplete, but functional application
3.4 Phases in prototype Model:-
Prototype Model Phases

DEPARTMENT OF INFORMTION AND SCIENCES 23

Phase 1: Identify some requirements to begin with: Get lists of some major
requirements which define the need for the new system including the main input
output information
Phase 2: Develop initial prototype: Develop a basic initial prototype which only
has UI screens.
Phase 3: Review the prototype: End users and SME’s work and examine the
prototype and provide feedback for improvements/enhancements.
Phase 4: Revise and enhance the prototype: Scope is changed based on feedback
from end users and the prototype is enhanced and refined to accommodate user
feedback.

CHAPTER 4
Designing the Project

4.1 INTRODUCTION
Saif Shahid Model School was established in 2002 is a premier institute of learning, committed to
maintain high academic standards, promoting students’ success and creating opportunities for life
learning. The School will inspire students to become well‐informed, active, and useful citizens who
recognize and appreciate the humanity through diverse curricula and cultural, academic, and artistic
events. Therefore, it is also essential to equip our students with excellent language skills.
Web Portal for Saif Shahid Model School is a large database system which can be used for managing
school’s daily work. It is configurable and can be configured to meet most individual school’s needs.
It is a multi-user system.
It will helps to overcome boring paper work in school. This Web Portal is very easy to use. It can
work accurately and very smoothly in different scenario. It reduces effort work load and increase
efficiency in work. In aspects of time value it is worthy.
4.2 PURPOSE
Now these days computer play very important role in any formal organization, because computer
works faster and accurate than human. The purpose of developing the Web portal for School system
of Saif Shahid Model School is that to make easy to management to store a large number of
data/reports into the computer. It is difficult for any management to store the large number of data
manually or in papers. In that case when any user wants to take information it is very difficult for
management to provide information immediately. It is very time consuming process. But by using
computer it takes only few minutes/seconds.
It is designed for better interaction between students, teachers, parents & management. This
management software very gracefully handles all the requirements for easy school management.
The school management system being web based can be accessed from anywhere in the world, which
enables the students, teachers, parents & the management be in touch with each other at all times
Reduces Paper Work, Improve Work Efficiency and Save Time. Relieves
Academic Staff from administrative work load. Eliminates work duplication.
Help institution's President, Principal and Registrar in making vital executive
decisions.
Parents, Students & Staff will not be required to wait for more than One Minute
for any services from offices.
To transfer your institute into an ideal institute in the area.

4.3. SCOPE
The scope of school management system is very vast. It includes; efficiency of the institution,
securing benefits of the school through practical measures, clarification of the functions of the school,
coordination of the educational programs, sound educational planning, good direction, efficient and
systematic execution.
I want to build a web portal for school teachers, students, admin which will be very easy to use for
their work purpose. Work with common server or browser which is very familiar with us. They
cannot change the customizations of fonts and colors of the web application. Security will be simple
but if it is need to be build a high security then it will be built later. I want to focus on the application
itself and the features of that application that help build a good management community
4.4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS
HTML: Hypertext Markup Language is a markup language used to design

static web pages.
User Friendly This Project is design and implement independent platform
HTTP: Hypertext Transfer Protocol is a transaction oriented client/server

protocol between web browser & a Web Server.
HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL (secure

socket layer).
Actors: An actor is a role played by an external entity that requires something
Administrator: Administrator can manage all record.
PHP: Hypertext Preprocessor is a server-side scripting language designed for

ARCHITECTURAL REPRESENTATION (ARCHITECTURE DIAGRAM)
Web development
The Web Portal will trade the paper-based information gathering and informative content trade
framework around the different bureaus of a specific school. The Web Portal for school record-
keeping tests. This school administration programming will give you room to handle your obligations
if you’re in the process of beginning or are an encountered master
The presence of your learner records states a great deal concerning the value of your school. Different
instructors and enlistment centers make judgments dependent upon person records that can for all

time influence a scholar’s existence. Web Portal competencies incorporate the rudiments for example
report cards, participation, and additionally countless different specially designed competencies,
incorporating parental access to constant understudy evaluations on the Internet.

4.6 Dynamic Model: Sequence Diagrams

Sequence diagrams show the interaction between participating objects in a given use case. They are
helpful to identify the missing objects that are not identified in the analysis object model. Those the
interaction between objects, the following describe the sequence diagram of each identified use
cases.
In Figure below, once the user has activated the registration module by interacting with the boundary
object “New Registration Button” button, the control object named “Registration Control” manages
the activities involved in “register Student” use case. First the “Registration Control” creates
registration form which will be filled by the secretary and submitted. The registration control
sends the record to a persistent storage
For Admin

Relation
Student

4.7 Object Model/Logical Model: Class Diagram

4.8 Deployment Model (Deployment Diagram)

4.9 Database Model (ER-diagram, DFD)

E-R (Entity-Relationship) Diagram is used to represents the relationship between entities in a table.
ER diagrams represent the logical structure of databases. ER Diagram represent relationship between
two database tables.
E-R diagram means Entity Relationship diagram. Entity is an object of system, generally we refer
entity as database table, and the e-r diagram represent the relationship between each table of database.
E-R diagram represent entity with attributes, attributes is a properties of entity. If we assume entity
is a database table then all the columns of table are treat as attributes.
Entity: Entities are represented by rectangle. All table of database are treat as entity. Attributes:
Attributes are represented by ellipses. Attributes are properties of entities.

4.11. GRAPHICAL USER INTERFACES

HEADER
Footer

Admin Panel
login

Add Teacher
View Teacher

CHAPTER 5
DEVELOPMENT AND IMPLEMENTATION

5.1 DEVELOPMENT PLAN
System development life cycle is the successful implementation of the new system design. The
process of converting as new system into an operational one is known as system development.
This includes all those activities that take place to convert from an old manual system to a new
technical system.

Application Development
The major functionality of this system is divided into some categories.
1) Administrative User Functions
2) Teacher User Functions
Administrative User Development Functions: Administrators can perform the following task
and more
• Login/Logout
• Create/Update/Delete staff
• View number of students in school
• Update status of student
• View student fee
• Register students
• View/Update student
• Assign student to class
• View class member
• Register staff, non-staff on school payroll
• View/Update staff, non-staff payment status e.g. payment balance with date
Teacher User Functions: This user can perform the following task and more
• Sign attendance
• Create student mark
• Update student mark
• Grading
CHAPTER NO.6
TESTING


6.1 Introduction
A document describing the scope, approach, resources and schedule of intended test activities. It
identifies amongst others test items, the features to be tested, the testing tasks, who will do each
task, degree of tester independence, the test environment, the test design techniques and entry and
exit criteria to be used, and the rationale for their choice and any risks requiring contingency
planning. It is a record of the test planning process.
6.2 TEST PLAN

Test Plan is a critical aspect of Software Quality Assurance (SQA) and represents the ultimate
review of specification, design and coding. Testing is a process of executing a program with the
intent of finding an error. A good test is one that has a probability of finding an as yet undiscovered
error. The purpose of testing is to identify and correct bugs in the developed system. Nothing is
complete without testing. Testing is vital to the success of the system.
To enhance performance, the automated system developed was tested at four levels, namely:
• Unit Level
• Module Level
• Integration & System
• Regression
6.2.1 UNIT TESTING
In unit testing, each modules developed were tested to affirmed is error-free.
6.2.2 MODULE LEVEL TESTING
Module Testing is done using the test cases prepared earlier. Module is defined
during the time of design.

6.2.3 INTEGRATION & SYSTEM TESTING
This is used to verify the combining of the software modules and their functionality. It addresses
the issues associated with the dual problems of verification and program construction. System
testing is used to verify, whether the developed system meets the requirements.
6.2.4 REGRESSION TESTING
Each modification in software impacts unmodified areas, which results into serious injuries to that
software. So the process of re-testing for rectification of errors due to modification is known as
regression testing.
Apart from these tests, there are some special tests conducted which are given below:
Peak Load Tests: This determines whether the new system will handle the volume of activities
when the system is at the peak of its processing demand. The test has revealed that the new system
developed is capable of handling the demands at the peak time.
Storage Testing: This determines the capacity of the new system to store data on a disk or on
other files. The proposed system has the required storage space available, because it had been spelt
out in system requirement.
Performance Time Testing: This test determines the length of the time used by the system to
process data.
INSTALLATION AND DELIVERY
Installation and delivery is the process of delivering the developed and tested software to the school
after the system have satisfied all the set objectives and is deliverable.
SYSTEM IMPLEMENTATION
Implementation includes all those activities that take place to convert from the old system to the
new. The old system consists of manual operations, which is operated in a very different manner
from the proposed new system. A proper implementation is essential to provide a reliable system
to meet the requirements of the school. An improper installation may affect the success of the
computerized system.
IMPLEMENTATION PLAN:
This includes a description of all the activities that must occur to implement the new system and
to put it into operation. It identifies the personnel responsible for the activities and prepares a time
chart for implementing the system.
The implementation plan consists of the following step
• List all files required for implementation.
• Identify all data required to build new files during the implementation.
• List all new documents and procedures that go into the new system.
The plan was designed to anticipate possible problems and deal with them.

CHAPTER NO.7
CONCLUSION & FUTURE WORK

7.1 Discussion
Working on the project was good experience. I understand the importance of Planning and
Designing as a part of software development. But it’s very difficult to complete the program for
single person.
system provide major advantages such as speed and accuracy of operation, Time Efficiency, Cost
Efficiency, Automatic data validation, Data security and reliability, Easy performance check
,Dynamic and User Friendly. Generates real-time, comprehensive reports and ensures access to
complete and critical information, instantly.
The system has been developed with much care that it is free of errors and at the same time it is
efficient and less time consuming. The important thing is that the system is robust and all events
happened on real-time. Avoid malfunction from outsiders. It goes through all phases of software
development cycle. So product is accurate.
7.2 FUTURE RECOMMENDATION
Nothing is perfect in this world. So, we are also no exception. Although, we have tried our best to
present the information effectively, yet, there can be further enhancement in the Application.
We have taken care of all the critical aspects, which need to take care of during the development of
the Project.
Like the things this project also has some limitations and can further be enhances by someone,
because there are certain drawbacks that do not permit the system to be 100% accurate.
The application is yet to be released and a lot of enhancements are already thought of which are
proposed to be implemented in the final version of the web-application. The web-application has
also provided feedback page on its home page so that the users can provide their inputs of any
functionalities/facilities they would like to have in the web application.
The system is highly flexible one and is well efficient to make easy interactions with the client. The
key focus is given on data security, as the project is online and will be transferred in network. The
speed and accuracy will be maintained in a proper way.
This will be a user-friendly one and can successfully overcome strict and severe validation checks.
The system will be a flexible one and changes whenever can be made easy.

CHAPTER NO.8
DEPLOYMENT

8.1 DEPLOYMENT PLAN
Deployment modeling is used to show the hardware of the system, the software that will installed
in the hardware and also the middleware that is used to connect the disparate machines to one and
other. It also shows how the software and the hardware components.
8.2 SPECIFICATION
Specification of Hardware and software

A)Hardware
• Printer: For printing Documentation
• Computers
• Hard Disk
B)Software
To create the web pages that actually interacts with your visitors. HTML can create useful and
well formatted web pages
• Notepad use to write html code.

• MY SQL server Latest
• Xampp server
• Chrome browser

REFERENCES
• https://creately.com/diagram/example/iihv7k1v2/School%20Management%20System%20
Architecture
• http://www.academia.edu/4699500/SCHOOL_MANAGEMENT_SYSTEM
• http://1000projects.org/school-management-system-architecture-design.html
• https://www.slideshare.net/gememohsin/school-management-system-ppt
• • https://www.scribd.com/doc/65038044/School-Management-
• https://www.google.com/search?q=methodology+for+research+proposal+of+school+man
System- Documentation
agement+system+on+web+wiki&rlz=1C1CHBF_enPK827PK827&tbm=isch&tbo=u&so
urce=univ&sa=X&ved=2ahUKEwjnqqvz29nfAhWMxIUKHYEBCGoQsAR6BAgEEAE
&biw=1366&bih=657
• https://www.academia.edu/
• https://www.quora.com/search?q=problem+defination+of+school+managment+system
• https://fedena.com/blog/2018/02/top-7-benefits-of-student-management-system.html
• https://fedena.com/feature_tour



Final Project Report: Web Portal For Saif Shahid Model School

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Final Project Report: Web Portal For Saif Shahid Model School

Загружено:

Авторское право:

Доступные форматы

WEB PORTAL FOR SAIF SHAHID MODEL SCHOOL

Final Project Report

Muhammad Azhar 6662

Department of Information Technology,

DEPARTMENT OF INFROMATION SCIENCES 1

Supervisor / Internal Examiner

DEPARTMENT OF INFROMATION SCIENCES 2

GATHERING & ANALYZING INFO

1.4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS

SOFTWARE REQUIREMENT SPECIFICATION

2.1 FUNCTIONAL REQUIREMENTS

DEPARTMENT OF INFROMATION SCIENCES 3

2.2 NON-FUNCTIONAL REQUIREMENTS

2.2. 3 System Requirements

2.4 USE CASES AND USAGE SCENARIOS

2.4.1 Use Case Diagrams

2.4.2 Usage Scenarios

PLANNING THE PROJECT

3.2.1. AVAILABLE METHODOLOGIES

DEPARTMENT OF INFROMATION SCIENCES 4

3.2.2. CHOSEN METHODOLOGY

3.3. REASONS FOR CHOSEN METHODOLOGY

3.4. WORK PLAN

3.5. PROJECT STRUCTURE

3.5.1. Team Structure

3.5.2. Project Schedule (Submission Calendar)

DESIGNING THE PROJECT

4.4. DEFINITIONS, ACRONYMS AND ABBREVIATIONS

4.5. ARCHITECTURAL REPRESENTATION (ARCHITECTURE DIAGRAM)

4.6. DYNAMIC MODEL: SEQUENCE DIAGRAMS

4.7. OBJECT MODEL/LOGICAL MODEL: CLASS DIAGRAM

DEPARTMENT OF INFROMATION SCIENCES 5

4.8. DEPLOYMENT MODEL (DEPLOYMENT DIAGRAM)

4.9. DATABASE MODEL (ER-DIAGRAM, DFD)

4.10. GRAPHICAL USER INTERFACES

DEVELOPMENT AND IMPLEMENTATION

5.1 DEVELOPMENT PLAN (ARCHITECTURE DIAGRAM)

6.2 TEST PLAN

6.2.1 UNIT TESTING

6.2.2 SYSTEM TESTING

6.2.3 INTEGRATIONT TESTING

6.2.4 USER ACCEPTANCE TESTING

6.3 TEST CASES

DEPARTMENT OF INFROMATION SCIENCES 6

CONCLUSION & FUTURE WORK

7.2 FUTURE WORK

8.1 DEPLOYMENT PLAN (DEPLOYMENT DIAGRAM)

DEPARTMENT OF INFROMATION SCIENCES 7

DEPARTMENT OF INFROMATION SCIENCES 8

DEPARTMENT OF INFROMATION SCIENCES 9

• Detail of student information

1.4 Definitions, Acronyms and Definitions:-

DEPARTMENT OF INFROMATION SCIENCES 10

2.1 System Requirement:-

DEPARTMENT OF INFROMATION SCIENCES 11

2.2 Functional Requirement

2.2 .2For Teacher:-

2.2.3 For Student:-

DEPARTMENT OF INFROMATION SCIENCES 12

2.2.4 For Parent

2.3 Non-Functional Requirement:-

Frequency/severity of failure, recoverability, predictability, accuracy.