Summary

The web based system is developed in such a way that it provides complete help for the people
who want to take help from the NGO for the education purpose, for the adoption of the child or
for free education.

Our web based system consists of the record of missing person which is missing in an area with
respect to its area and date of missing it. Anyone can upload the record of the missing person by
first register in the web portal and view the data of any person and uploaded the data of any
missing person with complete biography.

The importance of this system is very important in this digital era because there is no proper web
based system which is completely contains the record of the person which is missing with
respect to its complete biography and date in which he is lost. In the past people does not have
any proper channel or plate form where they can upload the data of the missing person.

Our web based system also consists of the child adoption portion in which list of child is
described in the web based system and willing person can contact to them for adoption. A
complete form is developed in the system in which a person fill the form and then the NGO
process this for and contact the willing person for the child adoption and then willing person can
adopt the child.

Our web based system can also consists of the portion of free education in which willing children
can fill the online form for their scholarship studies and then NGO process this for check the
condition and contact the willing families.

The purpose of our web based system is to provide the easiness for the orphan children who want
to study and provide the facility to those families who lost their member and want to search them
and also provide the blood facility for the patient who died in the hospital for no facility of blood
in proper time.

Our web based system also consists of fund raising module in which wiling person can donate
money by entering his amount on the text field and enter account number and amount is
extracted from the account.
Contents
1 Purpose: ................................................................................................................................ 11
1.1 Purpose of this SPMP: .............................................................................................................. 11
1.3 Client Information: ................................................................................................................... 11
2 Introduction: ........................................................................................................................ 11
2.1 Project overview: ............................................................................................................................ 11
2.2 Purpose, Scope, and Objectives: .................................................................................................... 12
Objective: ................................................................................................................................................ 12
Scope:...................................................................................................................................................... 13
2.3. Assumptions and Constraints: ...................................................................................................... 13
2.4. Project Deliverables: ...................................................................................................................... 14
2.5 Project Schedule: ............................................................................................................................ 15
Date ......................................................................................................................................................... 15
Project Phases ......................................................................................................................................... 15
Project Milestone .................................................................................................................................... 15
2.6 Evolution of SPMP: ........................................................................................................................ 16
2.7 Reference Materials: ....................................................................................................................... 16
3. Project Organization: ............................................................................................................. 16
3.1 Process Model: ................................................................................................................................ 16
3.1.2 Requirements Analysis: ............................................................................................................... 17
3.1.3 System Design: ............................................................................................................................. 17
3.1.4 Analysis Review: .......................................................................................................................... 17
3.1.5 GUI Prototype Demonstration: .................................................................................................. 17
3.1.6 Client Project Review: ................................................................................................................. 17
3.1.7 Object Design Phase: ................................................................................................................... 17
3.1.8. System Integration Prototype Demonstration: ........................................................................ 17
3.1.9 Implementation: ........................................................................................................................... 18
3.1.10 Unit Testing: ............................................................................................................................... 18
3.1.11 System Integration: .................................................................................................................... 18
3.1.12 System Testing: .......................................................................................................................... 18
3.1.13 Manual Integration:................................................................................................................... 18
3.2 Project Organization: ..................................................................................................................... 18
Role ......................................................................................................................................................... 18
 Name ....................................................................................................................................................... 18
Email ....................................................................................................................................................... 18
Phone ...................................................................................................................................................... 18
Project Manager ...................................................................................................................................... 18
Project Advisor ....................................................................................................................................... 18
3.2.1 Boundaries and Interfaces: ......................................................................................................... 18
Position ............................................................................................................................................... 20
Roles/Responsibilities ......................................................................................................................... 20
3.2.1.2 Internal Structure: .................................................................................................................... 20
3.2.1.3 Roles and Responsibilities: ....................................................................................................... 21
4. Gantt Chart: ............................................................................................................................ 23
1. Overview: ............................................................................................................................. 29
1.1 Scope: ......................................................................................................................................... 29
2. References: ........................................................................................................................... 29
3. Software Quality Assurance Plan: ..................................................................................... 30
3.1 Document Purpose: ................................................................................................................... 30
3.2 Reference documents: ..................................................................................................................... 30
3.3 Management: ................................................................................................................................... 30
3.3.1. Organization:........................................................................................................................... 30
3.3.2. Tasks: ....................................................................................................................................... 31
3.4 Documentation: ............................................................................................................................... 34
1. Introduction: ........................................................................................................................ 36
1.1 Purpose: ........................................................................................................................................... 36
1.2 Document Conventions: ................................................................................................................. 36
1.3 Intended Audience and Reading Suggestions: ....................................................................... 37
1.4 Project Scope: .................................................................................................................................. 37
1.5 Current Situation: ........................................................................................................................... 37
2. Overall Description: ............................................................................................................ 38
2.1 Product Perspective: ....................................................................................................................... 38
2.2 Product Features:............................................................................................................................ 40
3. System Features: .................................................................................................................. 41
3.1 Functional Requirements: .............................................................................................................. 41
Requirement no ....................................................................................................................................... 41
1 .............................................................................................................................................................. 41
Description .............................................................................................................................................. 41
User can upload the Picture in the Portal ................................................................................................ 41
Rationale ................................................................................................................................................. 41
User registers himself in the web system and can upload the picture in the portal and describes all of his
information.............................................................................................................................................. 41
Fit criteria ................................................................................................................................................ 41
To find the missing person. ..................................................................................................................... 41
Customer Satisfaction ............................................................................................................................. 41
5 .............................................................................................................................................................. 41
Customer dissatisfaction ......................................................................................................................... 41
4 .............................................................................................................................................................. 41
Conflict ................................................................................................................................................... 41
None ........................................................................................................................................................ 41
Requirement no ....................................................................................................................................... 41
2 .............................................................................................................................................................. 41
Description .............................................................................................................................................. 41
User can view the record of missing person. .......................................................................................... 41
Rationale ................................................................................................................................................. 41
User registers himself in the web system and can search for the found person list by name. ................ 41
Fit criteria ................................................................................................................................................ 41
To view the latest update for missing person in the web system. ........................................................... 41
Customer Satisfaction ............................................................................................................................. 41
3 .............................................................................................................................................................. 41
Customer dissatisfaction ......................................................................................................................... 41
4 .............................................................................................................................................................. 41
Conflict ................................................................................................................................................... 41
None ........................................................................................................................................................ 41
Requirement no ....................................................................................................................................... 42
3 .............................................................................................................................................................. 42
Description .............................................................................................................................................. 42
Pop Up email is send to the user id. ........................................................................................................ 42
Rationale ................................................................................................................................................. 42
The user register himself in the web portal and when the missing person is found then the emails are
sent to the respective receivers................................................................................................................ 42
Fit criteria ................................................................................................................................................ 42
To inform the family. .............................................................................................................................. 42
Customer Satisfaction ............................................................................................................................. 42
5 .............................................................................................................................................................. 42
Customer dissatisfaction ......................................................................................................................... 42
3 .............................................................................................................................................................. 42
Conflict ................................................................................................................................................... 42
None ........................................................................................................................................................ 42
Requirement no ....................................................................................................................................... 42
4 .............................................................................................................................................................. 42
Description .............................................................................................................................................. 42
User can view the lost cases of missing person. ..................................................................................... 42
Rationale ................................................................................................................................................. 42
Registration in the web system is done and then user can search the person by putting the gender,
ethnicity, age, date in which he is missed ............................................................................................... 42
Fit criteria ................................................................................................................................................ 42
For locate the desired person. ................................................................................................................. 42
Customer Satisfaction ............................................................................................................................. 42
4 .............................................................................................................................................................. 42
Customer dissatisfaction ......................................................................................................................... 42
5 .............................................................................................................................................................. 42
Conflict ................................................................................................................................................... 42
None ........................................................................................................................................................ 42
Requirement no ....................................................................................................................................... 43
5 .............................................................................................................................................................. 43
Description .............................................................................................................................................. 43
Queries or questionnaire ......................................................................................................................... 43
Rationale ................................................................................................................................................. 43
A survey form is filled in the web system which consists of lot of improvements which you suggests to
improve this web based system ............................................................................................................... 43
Fit criteria ................................................................................................................................................ 43
For improvement of the web based system. ............................................................................................ 43
 Customer Satisfaction ............................................................................................................................. 43
3 .............................................................................................................................................................. 43
Customer dissatisfaction ......................................................................................................................... 43
5 .............................................................................................................................................................. 43
Conflict ................................................................................................................................................... 43
None ........................................................................................................................................................ 43
3.2 Non Functional Requirements: ...................................................................................................... 43
3.2.1 Look and Feel Requirements: ................................................................................................. 43
3.2.2 Ease of Use Requirements: ...................................................................................................... 43
3.2.3 Performance Requirements: ................................................................................................... 44
1.Introduction .............................................................................................................................. 47
1.1 Purpose: ..................................................................................................................................... 47
1.2 Scope: ............................................................................................................................................... 47
1.3 Overview: ......................................................................................................................................... 47
1.4 References:....................................................................................................................................... 48
1. System Overview: ................................................................................................................ 48
2.1 Context of Our Web based System: ........................................................................................ 48
2.2 Modules Functionalities of Our Web Based System:................................................................... 49
2. Use Cases: ............................................................................................................................. 50
1. Missing Person Module Use case: .................................................................................................... 50
2. Child Adoption Module Use case: ................................................................................................... 52
3. Free Education Module Use case:.................................................................................................... 54
4. Fund Raising Module Use case: ....................................................................................................... 56
3. Class Diagram:..................................................................................................................... 60
4. System Architectural Design: ............................................................................................. 61
Client Server Architecture for Orphan Care: .................................................................................... 61
6. Data Design: ............................................................................................................................ 63
6.1 Entity Relationship Diagram: ........................................................................................................ 63
6.1.1 Basic Entity Relationship Diagram: ....................................................................................... 63
1. Introduction: ........................................................................................................................... 69
1.1 System Overview:............................................................................................................................ 69
1.2 Test Approach: ................................................................................................................................ 70
1.2.1 Risks: ......................................................................................................................................... 70
 1.2.2 Skills: ......................................................................................................................................... 70
1.2.3 Objectives: ................................................................................................................................ 70
1.2.4 Regulations: .............................................................................................................................. 70
1.2.5 Product: .................................................................................................................................... 70
1.2.6 Business:.................................................................................................................................... 71
2. Objectives: ............................................................................................................................... 71
3. Scope: ....................................................................................................................................... 71
3.1 Features to be tested: ...................................................................................................................... 71
3.2 Features not to be tested. ................................................................................................................ 72
4. Testing Tools and Environment: ........................................................................................... 72
4.1 Tools: ................................................................................................................................................ 72
4.2 Environment:................................................................................................................................... 73
5. TEST PLAN: ........................................................................................................................... 73
5.1 White Box Testing: ......................................................................................................................... 73
5.1.1 White Box Testing Techniques: .................................................................................................. 74
5.2 Black-Box Testing ........................................................................................................................... 74
5.2.1 Black Box Testing Techniques: ................................................................................................... 74
5.3 GUI Testing: .................................................................................................................................... 74
5.4 Integration Testing: ........................................................................................................................ 74
5.5 Functional Testing: ......................................................................................................................... 75
5.6 System Testing: ............................................................................................................................... 75
5.7 Performance Testing: ..................................................................................................................... 75
5.8 Stress Testing: ................................................................................................................................. 75
5.9 Security and Access control testing: .............................................................................................. 75
5.10 User acceptance testing: ............................................................................................................... 75
6. Test Cases: ............................................................................................................................... 75
1. General Information:.............................................................................................................. 88
1.1 System Overview:...................................................................................................................... 88
1.2 Organization of the Manual: .................................................................................................... 89
2 System Summary: ................................................................................................................ 89
2.1 System Configuration: .............................................................................................................. 90
2.2 User Access Levels: ................................................................................................................... 90
2.3 Assumption and Dependencies: ............................................................................................... 90
3. Getting Started: ....................................................................................................................... 90
3.1. Introduction: .................................................................................................................................. 91
3.2 Supported Browser: ........................................................................................................................ 91
3.3 Home Page: ...................................................................................................................................... 91
3.5 Free Education Page: ...................................................................................................................... 96
3.6 Fund Raising Page: ......................................................................................................................... 98
1. Introduction to Post Mortem Report: ................................................................................. 100
The Project Post Mortem Report is one of the final documents for the project and is used
by the project manager and senior level management to assess the success of the project,
identify best project practices, problem areas, and provide detailed suggestions for
improvement on future projects. ............................................................................................. 100
A project post-mortem is a process, usually performed at the conclusion of a project, to
determine and analyze elements of the project that were successful or unsuccessful. Project
post-mortems are intended to inform process improvements which mitigate future risks
and to promote iterative best practices. Post-mortems are often considered a key
component of, and ongoing precursor to, effective risk management. ................................ 100
Post-mortems can encompass both quantitative data and qualitative data. Quantitative
data include the variance between the hours estimated for a project and the actual hours
incurred. Qualitative data will often include stakeholder satisfaction, end-user satisfaction,
team satisfaction, potential reusability and perceived quality of end-deliverables. ........... 100
3. Steps for Holding a Successful Post-Mortem: .......................................................................... 100
4.Project Parameters: ............................................................................................................... 101
5.Project Overview: .................................................................................................................. 102
5.1 Project Goals: ................................................................................................................................ 102
5.2 Project Success Criterion: ...................................................................................................... 103
6. Project Performance:............................................................................................................ 103
6.1 Key Accomplishments: ................................................................................................................. 103
6.1.1 What went right? ................................................................................................................... 103
6.1.2 What worked well? ................................................................................................................ 104
6.1.3 What was found to be particularly useful? .......................................................................... 104
6.1.4 Project highlights: .................................................................................................................. 105
6.2 Key Problem Areas: ................................................................................................................ 105
6.2.1 What went wrong? ................................................................................................................. 105
6.2.2 What project processes didn’t work well? .................................................................... 105
6.2.3 What specific processes caused problems? ................................................................... 106
6.2.4 What were the effects of key problems areas (i.e. on budget, schedule, etc.)? .......... 106
6.2.5 Technical challenges: ...................................................................................................... 107

Chapter No: 1

Software Project Management Plan.

1 Purpose:
1.1 Purpose of this SPMP:
The purpose of this Software Project Management Plan (SPMP) is to detail the standards,
practices, tools, and techniques the team will use during the development life cycle of this
software product. The team is the intended audience for this document.
1.2 Project Aims:
Our project aims is to develop a web based system which provided all the facility to the user with
an ease and with a complete and consistent way. We developed our web based system with the
concept of providing facility to the user whom persons are lost and there is no proper channel to
provide this facility to search the person. We also use our web based system for child adoption
such that willing person can adopt the child by simply singed in and search for the child. We
provided also a free education facility in our web based system in which willing child can apply
for scholarship and get free education.

1.3Client Information:
In our web based system client is simply any user which is willing to use our web based system.
The client can also be the organization or institute which is willing to use our web based system
complete.

2 Introduction:
2.1 Project overview:
We want to build a web based system for NGO. The web based system is developed in such a
way that it provides complete help for the people who want to take help from the NGO for the
education purpose, for the adoption of the child or for blood donation.

Our web based system consists of the record of missing person which is missing in an area with
respect to its area and date of missing it. Anyone can upload the record of the missing person by
first register in the web portal and view the data of any person and uploaded the data of any
missing person with complete biography.

The importance of this system is very important in this digital era because there is no proper web
based system which is completely contains the record of the person which is missing with
respect to its complete biography and date in which he is lost. In the past people does not have
any proper channel or plate form where they can upload the data of the missing person.
Our web based system also consists of the child adoption portion in which list of child is
described in the web based system and willing person can contact to them for adoption. A
complete form is developed in the system in which a person fill the form and then the NGO
process this for and contact the willing person for the child adoption and then willing person can
adopt the child.

Our web based system can also consists of the portion of free education in which willing children
can fill the online form for their scholarship studies and then NGO process this for check the
condition and contact the willing families.

Our web based system also consist of the portion of blood donation in which a willing person
can register their record and when the blood is required then a text is sent to their phone and the
NGO contact the person.

The purpose of our web based system is to provide the easiness for the orphan children who want
to study and provide the facility to those families who lost their member and want to search them
and also provide the blood facility for the patient who died in the hospital for no facility of blood
in proper time.

2.2 Purpose, Scope, and Objectives:

Our web based system is developed to provide the facilities to the needy and to the peoples
which are in trouble. Our web based system consists of the module in which a person can upload
the record of the person who is missed and provided all the information and when the person is
found then pop up emails are send to the relatives of the person and the record of the persons are
then put in the founded list.
Our web based system consists of the free education system in which willing child can fill the
form completely and waiting for system response. User can also get online lectures from the
website with ease. Our web based system can also consists of the blood donation system in
which the user can register himself and provided all information in the system and when the
required blood is needed then the message are send to the person with same blood group. And
user can also send donation to the NGO by simply registering himself and provided email id
name and account number and the amount is extracted from the account.
Objective:
The object of our web based system is to develop the system which can provided the complete
facility to the user to search their lost person with a proper channel. Our web based system is
also provide the facility for the user who want to adopt a child but have no proper channel before
it can search for the child in our web based system with complete ease and perfection.
The object is to develop a system which provided complete facility to the needy people which
can easily use this web based system to complete their task.

Scope:
The scope of our web based system is completely concerned with following attributes.

• User can easily search the name of missing person with respect to his area age and date of
last seen.
• User can also update the list of data by uploading the images in the web based system.
• User can search the child by name, age date of birth and location.
• User can also fill the form for free education in the web based system.
• User can fill the form in the web based system by for fund raising.

2.3. Assumptions and Constraints:

In our web based system we assumed that there is Microsoft windows XP, windows 8 or 7 is
installed on the computer with specific 32 bit platform. We also assumed that the response time
of our website is very good and user can not feel anxiety while using this web based system
completely. We also assumed that user has some knowhow of operating our web based system
and user interface of our web based system is completely user friendly. If user has problem in the
user interface then there is step by step instructions are given in the help tab module.

Our web based system has dependencies like it can only operate with XAMP or APACHE server
install on the system means it depends on external factors like XAMP or APACHE server. It also
depends upon the proper connectivity of server with the web based if the system has proper
connectivity then the communication is done properly.

The project will be planned with the following constraints:

The project “Orphan Care” must be completed and integrated by no later than 15-August-2015.

1. Schedule: 15-March-2015 to 30-August-2015.

2. Budget: This plan will state cost estimation based on $10.00 per a person-hour, 16 person-
hours per week, and team size of 4 persons.

3. Resources

3.1. Staffing: The staffing information in this plan is pre-assigned not by selective hire.
3.2. Tools: Our web based system team will only be responsible to acquire tools and software
needed for development, testing, and demos. At post-development, the user will be responsible
for maintenance cost.
2.4. Project Deliverables:
Item Date Quantity Acquirer Media

SPMP 1 NGO Document

(Software
Project
Management
Plan)

SQAP 1 NGO Document

(Software
Quality
Assurance Plan)

SRS (Software 1 NGO Document

Requirements
Specification)

SDD (Software 1 NGO Document

Design
Description)

STD (Software 1 NGO Document

Test Document)

User Manual 1 NGO Document

Working 1 NGO DVD
software

Post Mortem 1 NGO Document

Report

2.5 Project Schedule:

Date Project Phases Project Milestone

Requirement Elicitation

Project Presentation By
clients

Project Planning

Requirement Analysis

Analysis Review

System Design

Object Design

Project Review with Client

Implementation and Unit

Testing

Object design Review

Project Agreement

System Integration and

System Testing

Internal Project Review

(functional Prototype)
 Project Acceptance by Client

2.6 Evolution of SPMP:

The project will evolve in the following manner. A detailed discussion upon the functionality of
the project will be performed with our project supervisor Mr. Muhammad Hassan Jahngair The
project functionality will be clarified after the review and recommendations by supervisor.

There would be weekly group members meeting and assignment of tasks between the team
members. Any changes introduced in the functionality first will be discussed with project
coordinator then will be implemented. There would be weekly meetings with supervisor and
actions would be taken based upon the review of supervisor.

The purpose of this SPMP is to provide a documented plan for the management and control of
the organizational, developmental, and supporting processes necessary to the successful
implementation of the “Orphan Care” project. The development of “Orphan Care” follows an
agile development methodology and therefore the detailed WBS and schedules can be changed;
these changes are managed separately from this. This document, however, subject to revision
based on sudden changes in project or product requirements, risk events, or unexpected deviation
from the planned course of action. The initial version of this SPMP is placed under configuration
management; changes made to this document will be controlled and tracked completely.

2.7 Reference Materials:

ESA Software Engineering Standards (ESA PSS‐05‐0 Issue 2) ESA Board for Software
Standardization and Control (BSSC), 1991
[IEEE 828] IEEE Standard for Software Configuration Management Plans, ANSI/IEEE
Std. 828-199.
[IEEE 1058] IEEE Standard for Software Project Management ANSI/IEEEStd.1058.1-
1987.
[IEEE 1074] IEEE Standard for Developing Software Life Cycle Processes, ANSI/IEEE
Std. 1074-1991.
[Rational 97b] A Rational Approach to Software Development Using Rational Rose,
Rational Software Corporation, Santa Clara, 1997.
[Rational 97c] Round-Trip Engineering with Rational Rose/Java, Rational Software
Corporation, Santa Clara, 1997

3. Project Organization:
3.1 Process Model:
The project is started on the March 1stand terminated on end of semester on 30 August. Major
milestones are the Client Project Review on March 30, 2015 and the Client Acceptance Test on
August 25, 2015.

3.1.1 Project Planning:

Project planning includes description of project tasks, activities and functions, dependencies,
resource requirements and a detailed schedule. This activity results in the software project
management plan for the Orphan Care System. Another output of the planning phase is the
project agreement, which is issued after the design activity is completed.
3.1.2 Requirements Analysis:
The requirements analysis activity takes the problem statement and reviews it in terms of
consistency, completeness and feasibility. During this activity, a set of models of the proposed
system is determined by interacting with the clients resulting in the requirements model. The
main part of the requirements model are four models: the use case model describing the complete
functionality of the system, the object model, the functional model and the dynamic model.
3.1.3 System Design:
The purpose of the system design activity is to devise a system architecture that maps the
analysis model to the chosen target environment. The major part of the system design phase is
the design of subsystems, that is, the decomposition of the system with respect to the chosen
target platform. The system design activity also refines the use cases from the analysis model and
describes in terms of interaction diagrams how the objects interact in each specific use case.
3.1.4 Analysis Review:
Review of software project management plan, requirements analysis and design. The meetings
will take place on April 25. The Analysis Review consists of a set of presentations given by
members of the Orphan Care project. Supervisor will review these slides and post their
comments.

3.1.5 GUI Prototype Demonstration:

This activity involves the demonstration of the graphical user interface of the Orphan Care
System. The GUI prototype of the Orphan Care system is expected to be demonstrated on May 5
during the Internal Project Review. The prototype must be viewable on the project homepage.

3.1.6 Client Project Review:

Review of project plan, requirements analysis and design decisions. The client liaison will be
present at the meeting. The meeting will take place on May 30. The Client Project Review
presentation slides will be made available to the client.

3.1.7 Object Design Phase:

The object design phase specifies the fully typed API for each subsystem. New classes are added
to the analysis object model if necessitated by the system architecture. Attributes and methods
for each object are fully typed.

3.1.8. System Integration Prototype Demonstration:

This activity involves the demonstration of a fully functional system prototype based on the
subsystem decomposition. Each subsystem is represented by its service. All service operations
can be called by other subsystems using remote method invocation. The implementation of the
services can be stubbed out.
3.1.9 Implementation:
The focus of this activity is on coding the individual objects described in the object design
document.

3.1.10 Unit Testing:

During unit testing, test suites are designed and executed for objects or collections of objects in
each subsystem. Unit testing enables the individual subsystems to be tested independent from the
status of the other subsystems. The result of this activity is part of the test manual that describes
how to operate the test suite and how to interpret the test results.

3.1.11 System Integration:

During this activity an integration strategy is devised, that specifies the order in which the
subsystems of the Orphan Care System are integrated and tested with respect to the use cases
defined in the analysis model. The system integration strategy and the subsystem tests are
described in the Test Manual.

3.1.12 System Testing:

Structural Testing:This activity tests the major data paths in the complete Orphan Care
System.Functional Testing: Tests the major functionality (use cases) with the complete Orphan
Care System. The basis for the functionaltesting activity is the test manual which is revised
according to the results of the system testing phase.
Alpha-test (Client Acceptance Test):The system is tested to make sure it passes the client
acceptance criteria as defined inthe project agreement.

3.1.13 Manual Integration:

During this activity, the project deliverables are revised. As a result, a complete set of documents
consisting of the software project management plan, requirements analysis document, software
design document, test manual and source code is made available on the project home page.
3.2 Project Organization:
In the following table, the roles which are distinguished and the person(s) assigned to each role
are given.

Role Name Email Phone

Project Manager
Project Advisor

3.2.1 Boundaries and Interfaces:

The project manager of our project is responsible for every terms and conditions which are
applicable in the project. The project manager has responsibility to manage the weekly meetings
with the project advisor.

The project advisor of our web based system can guided us about the functionality and other
technical things of the project completely.
If the Project manager is busy then the Deputy Project manager has responsibility to conduct
meetings with the advisors and other team members. The team member of the project manager
has responsibility to obey the project manager or deputy project manager orders and keep their
work in time.

3.2.1.1 External Interfaces:

Position Roles/Responsibilities
UCMS Department of Computer Science Project Review Board to provide final review on
the completion of the project.

Project Advisor (Mr.) Project advisor to professional consultant to the

Development processes and audits the progress

of the project.

Project Manager () To lead the development effort of the Orphan

Care Web Based System.

3.2.1.2 Internal Structure:

3.2.1.3 Roles and Responsibilities:
Orphan Care Project Manager Organize and manage the project team.

Define project goals and establish

measurements.

Develop project plans and processes.

Define, assign, and monitor tasks.

Monitor work progress and report

statuses.

Calculate earned values.

 Develop, review, and approve all
documents.

Coordinate with all team members for

risk

Management and issue control.

Manage configurations, builds, and

releases.

Review and approve requirements,

designs,

Codes, test scripts, and test reports.

Orphan Care Project Manager – Deputy Assist and be Orphan Care PM's backup

Orphan Care Requirements Lead Work in parallel with the Orphan Care PM in
understanding the project scope.

Initiate and lead the requirements elicitation,

prototyping, and specification.

Coordinate with the Design Lead to ensure

the designs satisfy requirements.

Review requirements, designs, codes, and

test cases.

Orphan Care Requirements Engineers Involve in requirements elicitations,

prototyping, modelling, specification, and
review.

Orphan Care Design Lead Work in parallel with the Orphan Care
Requirements Lead to design the system
architecture and software designs.

Initiate and lead the design processes.

Coordinate with the Orphan Care

Development Lead to ensure codes satisfy the
design and requirements. Involve in design
and code reviews.
Orphan Care Designers Involve in designs, modelling, and reviewing
designs, and codes.

Orphan Care Development Lead Work in parallel with the Orphan Care Design
Lead to ensure codes developed in accordance
to the designs.

Initiate and lead the coding efforts.

Coordinate with the developers and testers.

Involve in software reviews.

Orphan Care Developers Involve in coding and other reviews.

Orphan Care Test Lead Work in parallel with the Requirements Lead
and

Development Lead to develop test plans and

test cases.

Initiate and lead the test process.

Involve in other software reviews.

Orphan Care Testers Involve in developing test cases in executing

test cases and collect test results.

Involve in other software reviews.

4. Gantt Chart:
A Gantt chart, commonly used in project management, is one of the most popular and useful
ways of showing activities (tasks or events) displayed against time. On the left of the chart is a
list of the activities and along the top is a suitable time scale. Each activity is represented by a
bar; the position and length of the bar reflects the start date, duration and end date of the activity.
This allows you to see at a glance:

What the various activities are.

When each activity begins and ends.
How long each activity is scheduled to last.
Where activities overlap with other activities, and by how much.
The start and end date of the whole project.

The Gant chart of our web based system is described following.

1.

Fig 5: Gantt chart

2.

Fig 6: Gantt chart 2

3.

Fig 7: Gant Chart 3

4.

Fig 8: Gantt chart 4

Fig 9: Gantt chart 5

6.

Fig 10: Gantt chart 6

ChapterNo: 2

Software Quality Assurance Plan

1. Overview:
1.1Scope:
This plan covers SQA activities throughout the phase’s that is system requirements, software
requirements, analysis, program design, coding, testing operation and implementation of
theOrphan Care web based system. Orphan care web based system is system in which we have
four module. The missing person module, the education module, the fundraising module and the
child adoption module. This web based system is developed to the persons who is want to search
his last person and there is no proper way or method to complain for this purpose.

We also developed a system in which willing child can register himself for free education and
after some process on it the scholarships are granted to the child. Our web based system also
consists of the child adoption module for the person who have no children and want to adopt a
child and we provided a proper channel for this reason. Also it consists of fund raising module in
which willing person can funds their donation for improve and well grown our system properly

The purpose of this Software Quality Assurance Plan (SQAP) is to define the techniques,
procedures, and methodologies that will be used in the project to assure timely delivery of the
software that meets specified requirements within project resources. The use of this plan will
help assure the following:

That software development, evaluation and acceptance standards are developed,

documented and followed.
That the results of software quality review and audits will be given to appropriate
management within project. This provides feedback as to how well the development
effort is conforming to various development standards.
That test results adhere to acceptance standards.

2. References:
1. ESA Software Engineering Standards (ESA PSS-05-0 Issue 2), ESA Board for Software
Standardization and Control (BSSC), 1991.
2. IEEE Guide for Software Quality Assurance Planning.
3.Software Project Management: A Unified Framework.
4. IEEE standard for Software Quality Assurance Planning.
3. Software Quality Assurance Plan:
3.1 Document Purpose:
The Software Quality Assurance Plan (SQAP) defines the activities performed to provide
assurance that the software-related items delivered to the customer conform to the established
and contracted technical requirements. The SQAP also describes how the project will be audited
to ensure that the policies, standards, practices, procedures, and processes applicable to the
project are followed.

This document is provided as reference for team members and auditors to facilitate the process
of quality assurance.

This Software Quality Assurance Plan (SQAP) establishes the Quality Assurance program for
the Orphan Care web based system completely.

The SQAP addresses the organization, responsibilities, procedures, methods and tools employed
by the web team in implementing the Orphan Care web based system. This plan describes the
Quality Assurance (QA) organization and the specific activities applicable for the Orphan Care
Project. This plan will cover Orphan Care web based system Quality Assurance activities
performed by members of the Quality Assurance organization and directed by applicable QA
documented procedures. In addition, it will reference activities monitored by QA that are
performed by other organizations or functions.

3.2 Reference documents:

The reference documents are following:

IEEE STD 730-2002, IEEE Standard for Software Quality Assurance Plans.
Orphan Care Project Plan.
Orphan Care System Implementation Plan (SIP).
Orphan Care Software Management Plan.
IEEE Guide for Software Quality Assurance Planning.
IEEE Standard for Software Quality Assurance Planning, IEEE STD 730.1-1995.
Software Project Management: A Unified Framework.

3.3 Management:
This section describes the management organizational structure, its roles and responsibilities and
the software quality tasks to be performed.

3.3.1. Organization:
This section depicts the organizational structure that influences and controls the quality of the
software. Outlines the organizational structure of the project, including the role of user
representatives, technology experts, IS support staff, and other project logistical items
Organizational dependencies or independence of the elements responsible for SQA from those
responsible for software development and use should be clearly described or depicted.
The organization hierarchy of project at GC University defines as. The Software engineering
branch is leaded by the Head of Department .Project coordination under Project Coordinator. For
discussion of project phases Project coordinator is allocated. This software is developed as a
final year project as part of partial fulfillment of requirements for BS in Software Engineering
degree. Since there is only two member involved, it will be responsible of the development to
review the product’s usability, efficiency, reliability, and accuracy. The major professor other
than supervisor will also conduct inspections, reviews, and walk-through on a regular basis. In
addition a committee consisting of the major professor will review the documents in each phase
presentation. Major Professor's and the committee’s specifications and suggestions will be used
in places where quality decisions need to out-weigh development schedule decisions.

3.3.2. Tasks:
The main task of the SQA team is to check whether the procedure are followed properly and that
standards are handled correctly as defined in the (SQAP). Additionally the SQA team inspects
whether all group members fulfill their tasks as defined in (SPMP) according to the parts of the
(SQAP) applying to their specific tasks. . If a problem is detected, the appropriate procedure
should be adopted to solve this problem. The main tasks of SQA team are as follows

The SQA team has to check the consistency and coherence between documents.
Check whether all group members take their responsibilities as defined in (SPMP) by
talking to the team members.
Develop the requirement specification for the project.
Develop the design plan and test plan for testing the software.
Implement and test the application and deliver the application along with the necessary
documentation.
Give a formal presentation to the committee on completion of the analysis, design and
testing phases.
The committee reviews the developer’s work and provides feedback/suggestions.
Planning, coordinating, testing and assessing all aspects of quality issues.
Orphan Care Project Manager Organize and manage the project team.

Define project goals and establish

measurements.

Develop project plans and processes.

Define, assign, and monitor tasks.

Monitor work progress and report statuses.

Calculate earned values.

Develop, review, and approve all

documents.

Coordinate with all team members for risk

Management and issue control.

Manage configurations, builds, and

releases.

Review and approve requirements, designs,

Codes, test scripts, and test reports.

Orphan Care Requirements Lead Work in parallel with the Orphan Care PM
in understanding the project scope.

Initiate and lead the requirements elicitation,

prototyping, and specification.

Coordinate with the Design Lead to ensure

the designs satisfy requirements.

Review requirements, designs, codes, and

test cases.

Orphan Care Requirements Engineers Involve in requirements elicitations,

prototyping, modelling, specification, and
review.
Orphan Care Design Lead Work in parallel with the Orphan Care
Requirements Lead to design the system
architecture and software designs.

Initiate and lead the design processes.

Coordinate with the Orphan Care

Development Lead to ensure codes satisfy
the design and requirements. Involve in
design and code reviews.

Orphan Care Designers Involve in designs, modelling, and reviewing

designs, and codes.

Orphan Care Development Lead Work in parallel with the Orphan Care
Design Lead to ensure codes developed in
accordance to the designs.

Initiate and lead the coding efforts.

Coordinate with the developers and testers.

Involve in software reviews.

Orphan Care Developers Involve in coding and other reviews.

Orphan Care Test Lead Work in parallel with the Requirements Lead
and

Development Lead to develop test plans and

test cases.

Initiate and lead the test process.

Involve in other software reviews.

Orphan Care Testers Involve in developing test cases in executing

test cases and collect test results.

Involve in other software reviews.

3.4 Documentation:

Deliverables Description Due date

SPMP (Software Project Description of the software

Management Plan) approach and associated
milestones.
SQAP (Software Quality Description of plan that
Assurance Plan) consists of a means of
monitoring the software
engineering processes and
methods used to ensure quality
SRS (Software Description of the expected
Requirements Specification) software features, constraints,
interfaces and other attributes

SDD (Software Design Description of how the

Description) software will meet the
requirements. Also describes
the rationale for design
decisions taken.

STD (Software Test Description of the plan and

Document) specifications to verify and
validate the software and the
results

User Manual Description of Instructions for

hands-on users of the software

Working software Working software fulfilling all

functional and quality
requirements

Post Mortem Report Description of Individual

Reflections on Degree Project
ChapterNo: 3
SoftwareRequirement Specification
1. Introduction:
1.1 Purpose:

We want to build a web based system for NGO. The web based system is developed in such a
way that it provides complete help for the people who want to take help from the NGO for the
education purpose, for the adoption of the child or for blood donation.

Our web based system consists of the record of missing person which is missing in an area with
respect to its area and date of missing it. Anyone can upload the record of the missing person by
first register in the web portal and view the data of any person and uploaded the data of any
missing person with complete biography.

The importance of this system is very important in this digital era because there is no proper web
based system which is completely contains the record of the person which is missing with
respect to its complete biography and date in which he is lost. In the past people does not have
any proper channel or plate form where they can upload the data of the missing person.

Our web based system also consists of the child adoption portion in which list of child is
described in the web based system and willing person can contact to them for adoption. A
complete form is developed in the system in which a person fill the form and then the NGO
process this for and contact the willing person for the child adoption and then willing person can
adopt the child.

Our web based system can also consists of the portion of free education in which willing children
can fill the online form for their scholarship studies and then NGO process this for check the
condition and contact the willing families.

The purpose of our web based system is to provide the easiness for the orphan children who want
to study and provide the facility to those families who lost their member and want to search them
and also provide the blood facility for the patient who died in the hospital for no facility of blood
in proper time.

Our web based system also consists of fund raising module in which wiling person can donate
money by entering his amount on the text field and enter account number and amount is
extracted from the account.

1.2 Document Conventions:

The format of this SRS is simple. Bold face and indentation is used on general topics and or
specific points of interest. The remainder of the document will be written using the standard
font, Times New Roman.
1.3 Intended Audience and Reading Suggestions:

The document is intended to be read by managers and marketing staff, project managers,
developers, testers, and documentation writers. This document describes the features offered by
software product, classes of intended users, operating environment, design and implementation
constraints, assumptions and dependencies, external interface requirements owed by the software
and the quality attributes. Proceeding with the ‘Section-1’ which describes the purpose and scope
of the project; ‘Section-2’ gives an overall description of the software product – including
context diagram. ‘Section-3’ discusses feature of the systems, ‘Section-4’ describes external
interface requirements, and non-functional requirements are discussed in ‘Section-5’. Also, for
any query about technical concepts and terminologies, consult glossary.

1.4 Project Scope:

Our web based system is developed to provide the facilities to the needy and to the peoples
which are in trouble. Our web based system consists of the module in which a person can upload
the record of the person who is missed and provided all the information when a person is found
the record is put into the found list of the module.
Our web based system consists of the free education system in which willing child can fill the
form completely and waiting for system response. User can also send donation to the NGO by
simply registering himself and provided email id name and account number and the amount is
extracted from the account.

1.5 Current Situation:

Currently there is no proper web based system is developed in which the missing person record
is updated and if a person is found then NGO’s contact the families. And there is no proper web
based system is developed in which portion of adoption of the child is kept.
Currently there is no web based system in which properly person is register for donation of
blood. All the information of person is put it into the system for registration and when there is
need of blood then text is send to the person and the person is properly engaged.
Currently there is no proper portion is kept in the web based system for the funding purpose. The
bank account is entered in the field and email id is entered and number of amount is entered in
the field. The amount is automatically transferred in the account of the NGO.
1.6 The Context of the Work:
Missing person module:
We developed a web based system in which any person can upload the data of missing person in
the website (its contact number, picture, date of birth, address etc.).Then the admin panel can
process this data. Contact the family of the person who upload the data and verify it.. When the
data is enter or uploaded by a person it can pop up with new entry for everyone who can see this
site. The latest news section is also provided help for latest entry of the data.Once the data
uploaded by the person is matched with the person who is found then the pop up is shown that
gives the person information that the missing person is found and when the missing person is
found then data is removed from the missing person database and refresh it.
Child Adoption Module:
Our web based system also provides a portion of a child adoption module. In this module detail
list of the children will be displayed for adoption. The willing person can contact to the
organization for adoption of the children.

Free Education Module:

In this module the willing children which have better interest in the study but their family cannot
support for study can apply online for scholarship study. The scholarship form is consists in this
web page. The willing child can fill all the form and send it to NGO electronically. Then the
NGO process this scholarship form and further process is done.

Fund Raising:

Basically this is the type of org which often run on funds they always need it to support the
orphan and to run the organization .For this purpose we are introducing a form or the account
details through which the willing persons or rich families can donate funds to support the
humanity.

2. Overall Description:
2.1 Product Perspective:

Our web based system is compatible with all the browser and easily accessable for every one
who is required to use this web based system. Its user interface is easily understandable for every
one who have little experience of web system. Since this is an absolutely new, self-contained and
independent software product thus it is not a part of any other system. Our web based system
completely user friendly and easily understandable for every person who want to get help from
the NGO.
Everyone can easily upload and the record of the missing person and update all the information
and easily get notification if the person is founded.
Our web based system consists Free Education and child adoption module and fund raising
module each module is required proper registration such as name, email id, account number and
address and each module is user friendly and easily accessible.
Context diagram:
2.2 Product Features:

A High-level overview of product features is as follows:

• The user interface of our web based system is completely user friendly and easily
understands by the user which has no much more experience of the internet.
• The database storage of our web system is handsome and easily managed lot of data in
the web based system.

• The database security of our web based system is credential. No one can access the data
from database system. The security of our web based system is properly such that the
crashing of our web based system is minimal.

• Missing person: Our product consists of missing person module in which anyone can
upload the picture of the missing person with their contact number biography of the
person in detail. If the person is found then pop up message is sent to the family of that
person and the previous record of the person is removed.

• Child Adoption:Our product consists of the portion of a child adoption module. In this
module detail list of the children will be displayed for adoption. The willing person can
contact to the organization for adoption of the children.

• Free Education:Our product consists of the free education module in which the willing
child can apply online for scholarship and then further process is done and contact to the
family of the child if the criteria is fulfilled.

• Fund Raising:Our product consists of the module of fund raising in which person is put
his name his email id and account number and number of amount is added and then the
amount is transferred to the account of the NGO.
3. System Features:
3.1 Functional Requirements:

Requirement no 1

Description User can upload the Picture in the Portal

Rationale User registers himself in the web system and can upload the picture in
the portal and describes all of his information.

Fit criteria To find the missing person.

Customer 5
Satisfaction

Customer 4
dissatisfaction

Conflict None

Requirement no 2

Description User can view the record of missing person.

Rationale User registers himself in the web system and can search for the found
person list by name.

Fit criteria To view the latest update for missing person in the web system.

Customer 3
Satisfaction

Customer 4
dissatisfaction

Conflict None
Requirement no 3

Description Pop Up email is send to the user id.

Rationale The user register himself in the web portal and when the missing
person is found then the emails are sent to the respective receivers.

Fit criteria To inform the family.

Customer 5
Satisfaction

Customer 3
dissatisfaction

Conflict None

Requirement no 4

Description User can view the lost cases of missing person.

Rationale Registration in the web system is done and then user can search the
person by putting the gender, ethnicity, age, date in which he is
missed

Fit criteria For locate the desired person.

Customer 4
Satisfaction

Customer 5
dissatisfaction

Conflict None
Requirement no 5

Description Queries or questionnaire

Rationale A survey form is filled in the web system which consists of lot of
improvements which you suggests to improve this web based system

Fit criteria For improvement of the web based system.

Customer 3
Satisfaction

Customer 5
dissatisfaction

Conflict None

3.2 Non Functional Requirements:

3.2.1 Look and Feel Requirements:
3.2.1.1 Appearance Requirements:
The appearance of our web based system is completely user friendly. The Logo of our web based
system is put in the first page of the website which describes the complete description of the web
system. The system should be attractive according to the need of the user. The design and the
color should make users feel comfortable when using the system instead of flashing useless
colors on the screen.

3.2.1.2 Style Requirements:

The overall style should be built up easily in order for users to use it easily and efficiently. After
accessing the system, the users should feel comfortable while looking at it and browsing through
it. The design should not be too colorful to such that it feel very awkward system but at the same
time it should not be too boring for the eye, so that it can appear pleasant to use.

3.2.1.3Usability and Humanity Requirements:

This section is concerned with requirements that make the product usable and ergonomically
acceptable to its hands-on users.

3.2.2 Ease of Use Requirements:

The system should have an easily understandable design in order for users to use it. The Web
based system provides the much information to user if errors are occurred. If user has some
problem with regarding to some topic in which he does not understandthen help tab is provided
which describes everything step by step. Simple language is used in this Web based system so
any one which have some know how about the web can handle this.

3.2.2.1 Learning Requirements:

Our Web based system is developed for everyone who has some knowledge of operating the web
system. But for the ease of the customer we also provide the functionality in this web based
system to understand this web system completely. We design help tab in the Web based system
in which there is step by step instructions to operate the website completely.

3.2.2.2 Understand ability and Politeness Requirements:

The system will not use any term that is not specified in the Web based system catalogue. The
used in this web based system is simple and easily understandable by the user. There is some
type of dictionary of the words put in the step by step instructions.

3.2.3 Performance Requirements:

3.2.3.1 Speed and Latency Requirements:
The system is required specific speed when start the system then it shows all content in proper
time. If speed is not manage then a lot of time is used in loading the website and user does not
use this Web system properly.

3.2.3.2 Safety-Critical Requirements:

Our web based system is properly developed in such a way that the important information of the
system is or database of the system is properly managed if a crash is occurred in the system then
there is a backup in the system which can restore all the data in the web site properly.

3.2.3.3 Reliability and Availability Requirements:

Our web based system is completely reliable for the user who can use it. Our web based system
completely consists of the missing person record after the full verification from NADRA or by
contacting the person completely. The system is available for the entire user who can want to use
it by registering it.

3.2.3.4 Robustness or Fault-Tolerance Requirements:

When the system is disconnected from the internet then the web based system does not remove
its content completely. The web based system can use cookies to stores it data and there is no
loss of data in the system.

Our web based system response time is very quick such that the user cannot wait for the response
of the system and user cannot feel anxiety for this type of interruption.
3.2.3.5 Capacity Requirements:
The system should be able to manage the entire customer using it at the same time. Database of
our web based system has much more capacity and it can store large amount of data in the web
based system. The capacity of our web based system cannot slow down the performance of our
web based system.

3.2.3.6 Scalability or Extensibility Requirements:

Due to the nature of the system, as we mentioned before the capacity of processing information
is indefinite. We are fully aware that the capacity of our users are increased in our web based
system , that it is why we are designing our database in MS SQL, which is a very powerful
application to keep records save properly.

3.2.3.7 Longevity Requirements:

The system shall be expected to operate for a minimum of three years. At that time a
technological assessment will be undertaken to look for new processes for accomplishing client
goals.
ChapterNo: 4

Software Design Document

1.Introduction
The Software Design Document is a document to provide documentation which will be used to
aid insoftware development by providing the details for how the software should be built. Within
the SoftwareDesign Document are narrative and graphical documentation of the software design
for the projectincluding use case models, sequence diagrams, collaboration models, object
behavior models, and other supporting requirement information.

1.1Purpose:
The purpose of the Software Design Document is to provide a description of the design of a
system fully enough to allow for software development to proceed with an understanding of what
is to be built and how it is expected to build. The Software Design Document provides
information necessary to provide description of the details for the software and system to be
built.

1.2 Scope:
This Software Design Document is for a base level system which will work as a proof of concept
for the use of building a system this provides a base level of functionality to show feasibility for
largescale production use. This Software Design is focused on the base level system and critical
partsof the system. For this particular Software Design Document, the focus is placed on
generation ofthe documents and modification of the documents. The system will be used in
conjunction withother pre-existing systems and will consist largely of a document interaction
facade that abstractsdocument interactions and handling of the document objects.

1.3 Overview:
The Software Design Document is divided into 7 sections with various subsections. TheSections
of the Software Design Document are:
1 Introduction.
2. System Overview.
3 Use Cases.
4 Class Diagram
5 System Architectural Design.
5.1 Chosen System Architecture.
5.2 Discussion of Alternative Designs.
5.3 System Interface Description.
6. User Interface Design.
6.1. Description of user interface.
6.2. Screen Images.
7.Requirements Matrix.
8.Data Design
9. Dynamic Module
1.4 References:
Software User Manual, SPINGRID team, TU/e, Version 0.0.2, June 2006.

Practical UML: A Hands-On Introduction for Developers, Togethersoft, 2000.

IEEE, IEEE Std 1016-1998 Recommended Practice for Software Design Descriptions, 1998-09-
23, The Institute of Electrical and Electronics Engineers, Inc., (IEEE ).

IEEE, IEEE 1016 Software Design Document (SDD) Template for CENG491.

1. System Overview:
2.1Context of Our Web based System:
We want to build a web based system for NGO. The web based system is developed in such a
way that it provides complete help for the people who want to take help from the NGO for the
education purpose, for the adoption of the child or for locating the missing person.

Our web based system consists of the record of missing person which is missing with respect to
its area and date of missing it. Anyone can upload the record of the missing person by first
register in the web portal and view the data of any person and uploaded the data of any missing
person with complete biography.

The system is very important in this digital era because there is no proper web based system
which is completely contains the record of the person which is missing with respect to its
complete biography and date in which he is lost. In the past people does not have any proper
channel or plate form where they can upload the data of the missing person.

Our web based system also consists of the child adoption portion in which list of child is
described in the web based system and willing person can contact to them for adoption. A
complete form is developed in the system in which a person fill the form and then the NGO
process this for and contact the willing person for the child adoption and then willing person can
adopt the child.

Our web based system can also consists of the portion of free education in which willing children
can fill the online form for their scholarship studies and then NGO process this for check the
condition and contact the willing families.

The purpose of our web based system is to provide the easiness for the orphan children who want
to study and provide the facility to those families who lost their member and want to search them
and also provide the blood facility for the patient who died in the hospital for no facility of blood
in proper time.
2.2 Modules Functionalities of Our Web Based System:
Our Web based system is developed for the NGO which provides facilities to all the people who
want to facilitate from our web based system. Our web based system consists of four modules.

1. Missing Person Module

2. Free Education Module
3. Child Adoption Module
4. Fund Raising Module

1. Missing Person Module:

Our Web based system consists of the missing person module in which any one can upload the
picture of the missing person. The person provides all the information regarding to that person
his name, age, sex, last date of scene, location in which he last seen etc. Then the NGO can
verify this by contacting the person and verify it completely for security reason.

Any person can search the missing person by his name, Age, Date Of last Seen and ethnicity. If a
person is founded then it is placed in the Latest update section in the website and user get
notification in his email or phone and the record of the person is wiped out from missing to the
Found person category.

2. Child Adoption Module:

Our web based system also provides a portion of a child adoption module. In this module detail
list of the children will be displayed for adoption. The willing person can contact to the
organization for adoption of the children. Any person who is willing for adoption of the child can
search the child by his name, age and location of the children. Then the willing person can
contact to the NGO for this child. Our module also consists of latest news section in which latest
list of child is placed and other news.

3. Free Education Module:

In this module the willing children which have better interest in the study but their family cannot
support for study can apply online for scholarship study. The scholarship form is consists in this
web page. The willing child can fill all the form and send it to NGO electronically. Then the
NGO process this scholarship form and further process is done.

4. Fund Raising:

Basically this is the type of organization which often run on funds they always need it to support
the orphan and to run the organization .For this purpose we are introducing a form or the account
details through which the willing persons or rich families can donate funds to support our NGO
system. The user first of all signs up and creates a user account. Then the user can provide all the
information to the form and provided all the information such as Name, Email ID, Bank
Account, Contact Number etc. Then the system verifies this account number and further process
is done.

2. Use Cases:
1. Missing Person Module Use case:
Actors:

Founder, Administrator.

Founder:

Founder is directly interacting with our web based system. The role of the Founder is to upload
the picture in missing person modules and access the information from the backend. The
Founder can view the record of the missing person. The Founder can search the missing person
by name by id or by last seen date.

Administrator:

The administrator can manage the record of our web based system completely. The administrator
has completely access to our web based system.
Use Case Diagram:
Use case Index:

Use case ID Use Case Primary Scope Complexity Priority

name Actor

1 Search Generic user In Medium 2

2 Upload The Generic user In Medium 2

image

3 View Record Generic user In Medium 2

Of Person

4 Check Found Generic user In High 1

Person
Updates

5 Manage the Administrator In High 1

Record

6 Manage The Administrator In High 1

Updates

7 Admin Log In Administrator In High 1

8 Update Administrator In Medium 2

Record

2. Child Adoption Module Use case:

Actors:

Adopter:

The adopter can search the detail list of the children with respect to their name or their age. The
adopter or user can register first of all in the web based system. Detailed list of the children can
be displayed on the page with all their information user or adopter then contact to the NGO for
further inquiry.

Administrator:

The administrator can manage the record of our web based system completely. The administrator
has completely access to our web based system.

Use case Diagram:

Use case Index:
Use case ID Use Case name Primary Scope Complexity Priority
Actor

1 Search Adopter In Medium 1

2 View the child Adopter In High 1

information

3 View Latest Update Adopter In Medium 2

4 Manage Updates Administrator In High 1

5 Manage the Record Administrator In High 1

6 Update Record Administrator In Medium 2

3. Free Education Module Use case:

Actor:

User:

The willing can apply online by fill the form and put all the fields fill in the form and press send
button and wait for the further process.

Administrator:

The administrator can manage the record of our web based system completely. The administrator
has completely access to our web based system. The administrator can check the criteria if the
wiling child can exist in this criteria and then contact to the willing child.

Use case Diagram:

Use case ID Use Case name Primary Scope Complexity Priority
Actor

1 View The form User In High 1

2 View Updates User In Medium 2

3 Fill the form User In High 1

4 Manage Updates Administrator In High 2

5 Manage the data Administrator In High 1

6 Update Record Administrator In Medium 2

4. Fund Raising Module Use case:

User:

The willing can apply online by fill the form and put all the fields fill in the form and press send
button and wait for the further process. The user also provides the details of his account number
and add amount which he wants to donate.

Administrator:

The administrator can manage the record of our web based system completely. The administrator
has completely access to our web based system. The administrator send request to the bank
server and wait for process.

Bank:

The bank server process the request of the administrator by verifying the request completely. The
bank check the balance of the regarding accounts to ensure that the account has money and then
send the amount from the user account to the system account.
Use Case Diagram:
Use case Index:

Use case ID Use Case name Primary Scope Complexity Priority

Actor

1 View The form User In High 1

2 Fill the fields User In Medium 2

3 Fill the form User In High 1

4 Manage the account Administrator In High 2
transaction

5 Manage the data Administrator In High 1

6 Process the Bank In High 1

transaction

7 View the user Bank, In High 1

account Administrator
3. Class Diagram:
4. System Architectural Design:
A systemarchitecture or systemsarchitecture is the conceptual model that defines the structure, behavior,
and more views of a system. An architecture description is a formal description and representation of a
system, organized in a way that supports reasoning about the structures and behaviors of the system.

System architecture can comprise system components, the externally visible properties of those
components, the relationships (e.g. the behavior) between them. It can provide a plan from which
products can be procured, and systems developed, that will work together to implement the overall
system. There have been efforts to formalize languages to describe system architecture.

5.1 Chosen System Architecture:

The client–server model of computing is a distributed computing structure that partitions tasks or
workloads between the providers of a resource or service, called servers, and service requesters,
called clients Often clients and servers communicate over a computer network on separate hardware, but
both client and server may reside in the same system. A server host runs one or more server programs
which share their resources with clients. A client does not share any of its resources, but requests a
server's content or service function. Clients therefore initiate communication sessions with servers which
await incoming requests.

In our web based system we chooses client server architecture or client server architecture system.
Client-server is a computing architecture which separates a client from a server It is almost always
implemented over a computer network The most basic type of client-server architecture employs only
two types of nodes: clients and servers. This type of architecture is sometimes referred to as two-tier. It
allows devices to share files and resources. The client Server architecture provides the service. Client is
considered as the customer requesting the service The server service can be shared among a number of
clients. Clients must request or initiate the service.

Internet
Client
HTML
Server Application

Client
JAVA

Client Server Architecture for Orphan Care:

6. Data Design:
6.1 Entity Relationship Diagram:
6.1.1 Basic Entity Relationship Diagram:
7 Dynamic Models:
7.1 Sequence Diagrams:
7.1.1. Missing Person Module Sequence Diagram:

7.1.2. Free Education Module Sequence Diagram:

7.1.3. Child Adoption Module Sequence Diagram:
7.1.4. Fund Raising Module Sequence Diagram:
ChapterNo: 5

Software Test Document

1. Introduction:
In this document we describe the scope of project, test approach, different test resources, and
schedule of intended testing activities. It identifies test items, the features to be tested, the testing
tasks, who will do each task, and any risks requiring contingency planning. It also tells about
pass and fails criteria of test cases.

This document will address the different standards that will apply to the unit, integration and
system testing of the specified application. The design, development and testing of these reports
will be based on clients “Project Name” management project. For testing documentation we
follow the following IEE Standard. 829-2008 - IEEE Standard for Software and System Test
Documentation.

1.1 System Overview:

We want to build a web based system for NGO named “ORPHAN CARE”. The web based
system is developed in such a way that it provides complete help for the people who want to take
help from the NGO (ORPHAN CARE) for the education purpose, for the adoption of the child or
for locating the missing person.

Our web based system consists of the record of missing person which is missing with respect to
its area and date of missing it. Anyone can upload the record of the missing person by first
register in the web portal and view the data of any person and uploaded the data of any missing
person with complete biography.

The system is very important in this digital era because there is no proper web based system
which is completely contains the record of the person which is missing with respect to its
complete biography and date in which he is lost. In the past people does not have any proper
channel or plate form where they can upload the data of the missing person.

Our web based system also consists of the child adoption portion in which list of child is
described in the web based system and willing person can contact to them for adoption. A
complete form is developed in the system in which a person fill the form and then the NGO
(ORPHAN CARE) process this for and contact the willing person for the child adoption and then
willing person can adopt the child.

Our web based system can also consists of the portion of free education in which willing children
can fill the online form for their scholarship studies and then NGO (ORPHAN CARE) process
this for check the condition and contact the willing families.

The purpose of our web based system is to provide the easiness for the orphan children who want
to study and provide the facility to those families who lost their member and want to search them
and also provide the blood facility for the patient who died in the hospital for no facility of blood
in proper time.
1.2 Test Approach:
We adopt the IEEE 829 standard for testingusing books such as [Craig, 2002] or [Drabick, 2004]
to fill in the methodological gaps. Process or standard compliance approach have in common
reliance upon an externally developed approach to testing, often with little if any customization
and may have an early or late point of involvement for testing. This approach is used as we lack
skills of test strategies. So we use standards of the test strategy for the completion of our project.

The choice of test approach is very important for the success of the test efforts and accuracy of
the test plans and estimates. This choice is of the testing engineer that which approach he
recommends for the project. There are a lot of test approaches are given but we use process or
standard compliant approach for our project. In this approach some standards are used for how to
test, what to test and who will do the testing. These standards are created by IEEE 829 and
widely used for the testing. How do we know which testing approach is to pick for the best
chance of success. There are many factors to consider, but let us discuss a few of the most
important:

1.2.1 Risks:
Risk management is very important during testing, so consider the risks and the level of risk. For
a well-established application that is evolving slowly, regression is an important risk, so
regression-averse strategies make sense. For a new application, a risk analysis may reveal
different risks if you pick a risk-based analytical strategy.

1.2.2 Skills:
Consider which skills your testers possess and lack because strategies must not only be chosen,
they must also be executed. A standard compliant strategy is a smart choice when you lack the
time and skills in your team to create your own approach.
1.2.3 Objectives:
Testing must satisfy the needs and requirements of stakeholders to be successful. If the objective
is to find as many defects as possible with a minimal amount of up-front time and effort invested
for example at a typical independent test lab then a dynamic strategy makes sense.
1.2.4 Regulations:
Sometimes you must satisfy not only stakeholders, but also regulators. In this case, you may
need to plan a methodical test strategy that satisfies these regulators that you have met all their
requirements.
1.2.5 Product:
Some products like, weapons systems and contract-development software tend to have well-
specified requirements. This leads to synergy with a requirements-based analytical strategy.
1.2.6 Business:
Business considerations and business continuity are often important. If you can use a legacy
system as a model for a new system, you can use a model-based strategy.

2. Objectives:
The test planning process and the plan itself serve as the means of communication with other
members of the project team, testers, peers, managers and other stakeholders. This
communication allows the test plan to influence the project team and the project team to
influence the test plan, especially in the areas of organization-wide testing policies and
motivations; test scope, objectives and critical areas to test; project and product risks, resource
considerations and constraints; and the testability of the item under test. We can complete this
communication by circulating one or two test plan drafts and through review meetings.

The test plan helps us to manage change. During early phases of the project, as we gather more
information, we revise our plans. As the project evolves and situations change, we adapt our
plans. By updating the plan at major milestone help to keep testing aligned with project needs.
As we run the tests, we make final adjustments to our plans based on the results. You might not
have the time or the energy to update your test plans every time a change is made in the project,
as some projects can be quite dynamic.

3. Scope:
The document mainly targets the GUI testing and validating data in reportoutput as per
Requirements Specifications provided by Client.
3.1 Features to be tested:
Features which are tested or necessary to test are the functionalities performed by the system are
either give expected result or not. These are the features which are tested through black box
testing.

Update Record.
Upload Missing Person Information.
Search the missing Person.
Delete Record when the missing person is found.
View Record of the Person which is found.
View Record of the Person which is not found.
Search the child (in child adoption module).
View the child Record.
User can register himself by using the online form for free education.
User can register himself and provided account number to transfer amount in the
NGO account.
 GUI.
Contact Us
Feedback.

3.2 Features not to be tested.

Features which are not necessary for testing and which are tested through white box testing.
These features are tested within internal testing. We can test these features which are the system
response are tested through good coding practices and with the experience.

These features are given below:

Validation.
Performance.
Reliability.
Maintainability.

4. Testing Tools and Environment:

4.1 Tools:
The following 3rd party “free” tools were available to scan the Web site and provide feedback:
Bobby (accessibility, performance & html syntax) – cast.org.
Freeappraisal (performance from 35 different cities) – keynote.com
Scrubby (meta tag analyser) – scrubtheweb.com
Site analysis (search engine ratings) – site-see.com
Stylet (style sheet validation) – microsoft.com
Tune up (performance & style checker) & gif lube (gif analyzer) – websitegarage.com
Websat (usability) – nist.gov
Web metasearch (search engine ratings) – dogpile.com
Webstone (performance benchmarking tool) - mindcraft.com
Windiff (file comparison) – microsoft.com.
W3C validation service (html and css syntax) – w3c.org

In addition the following “commercial” tools were available:

Aetgweb (pair-wise combinations) from Telcordia/Argreenhouse.
Astra Site Manager (linkage) from Mercury Interactive.
ETester suite (capture/reply, linkage & performance) from RSW – 100 virtual user
license.
FrontPage (spell checking) from Microsoft.
Ghost (software configuration) from Symatec.
 KeyReadiness (large scale performance testing) from Keynote systems.
LinkBot Enterprise (link checking, HTML compliance and performance estimates) from
Watchfire.
Prophecy (large scale performance testing) from Envive.
WebLoad (performance) from Radview – 1000 virtual user license.
Word (readability estimates) from Microsoft.

4.2 Environment:
All the test which is to be performed will run under Windows 95/98, Window Millennium (Me),
Window NT, Windows 2K, Windows XP and Windows Vista, Windows 8 and windows 7.

The following Windows based Browsers are readily available for the system to perform the
testing techniques to check that whether the system is properly done.
Microsoft Internet Explorer 3.0, 4.72 SP1a, 5.0 and 5.5.
Opera 3.6, 4.0 and 5.0 (a very fast browser, partly because it strictly adheres to the W3C
HTML/JavaScript standards).
Netscape Navigator 3.0, 4.5, 4.6, 4.7 & 6.0.
Safari browser.
Google Chrome.
Firefox browser.

5. TEST PLAN:
Software is tested from two different perspectives:

Internal program logic is exercised using “white box” test case design techniques.
Software requirements are exercised using “black box” test case design techniques.

In both cases, the intent is to find the maximum number of errors with the minimum amount
of effort and time.

5.1 White Box Testing:

White Box Testing is a software testing method in which the internal
structure/design/implementation of the item being tested is known to the tester. It is also known
as Clear Box Testing, Open Box Testing, Glass Box Testing, Transparent Box Testing, Code-
Based Testing or Structural Testing.
The tester chooses inputs to exercise paths through the code and determines the appropriate
outputs. Programming know-how and the implementation knowledge is essential. White box
testing is testing beyond the user interface and into the nitty-gritty of a system.
This method is named so because the software program, in the eyes of the tester, is like a
white/transparent box; inside which one clearly sees.
5.1.1 White Box Testing Techniques:
White-box testing, sometimes called glass-box testing is a test case design method that uses the
control structure of the procedural design to derive test cases.
Using white-box testing methods, the software engineer can derive test cases that:

Guarantee that all independent paths within a module have been exercised at least
once.
Exercise all logical decisions on their true and false sides.
Execute all loops at their boundaries and within their operational bounds.
Exercise internal data structures to ensure their validity.
5.2 Black-Box Testing
Black-box testing refers to tests that are conducted at the software interface. Although they are
designed to uncover errors, black-box tests are used to demonstrate that software functions are
operational, that input is properly accepted and output is correctly produced, and that the
integrity of external information (e.g., a database) is maintained. A black-box test examines
some fundamental aspects of a system with little regard for the internal logical structure of the
software.

5.2.1 Black Box Testing Techniques:

Black-box testing, also called behavioral testing, focuses on the functional of the software. That
is, black-box testing enables the software engineer to derive sets of input conditions that will
fully exercise all functional requirements for a program. Black-box testing is not an alternative to
white-box techniques. Rather, it is a complementary approach that is likely to uncover a different
class of errors than white-box methods.

Black-box testing attempts to find errors in the following categories:

Incorrect or missing functions

Interface errors
Errors in data structures or external database access,
Behaviour or performance errors, and
Initialization and termination errors.

Unlike white-box testing, which is performed early in the testing process, black box testing tends
to be applied during later stages of testing.

5.3 GUI Testing:

GUI testing will includes testing the UI part of report. It covers users Reportformat, look and
feel, error messages, spelling mistakes, GUI guideline violations.

5.4 Integration Testing:

Integration testing is systematic technique for constructing the program structure while
conducting test to uncover errors associated with interacting. Integration testing includes the
testing from respective locations.
5.5 Functional Testing:
Functional testing is carried out in order to find out unexpected behavior ofthe system. The
characteristic of functional testing are to provide correctness, reliability, testability and accuracy
of the system output/data.

5.6 System Testing:

System testing of software is testing conducted on a complete, integratedsystem to evaluate the
system's compliance with its specified requirements.

5.7 Performance Testing:

Performance testing will be done by Client.

5.8 Stress Testing:

Stress testing will be done by Client.

5.9 Security and Access control testing:

Not Applicable as this is already done by Client.

5.10 User acceptance testing:

The purpose behind user acceptance testing is to conform that system isdeveloped according to
the specified user requirements and is ready for operational use. Acceptance testing is carried out
at two levels - Alpha and Beta Testing. User acceptance testing (UAT) will be done at the Client.

6. Test Cases:
TC 1: Search the missing person.
Number TC-1 Date Created: 05-04-2016 Created By: Shahnawaz

Requirement #: 1

Description: User can Search the missing Person by the name, date of birth, date of last
seen and by Ethnicity.

Steps:

Step Type Description Expected Actual, if P/F Date By

different
from
Expected

1.1 Test to Search the Search No Pass 05-04- Shahnawaz

pass missing Result Difference, 2016
person By Shown from
Name Expectation.

1.2 Test to Search by Search No Pass 05-04- Shahnawaz

pass missing Result Difference, 2016
person Shown from
Location Expectation.

1.3 Test to Last Seen Search No Pass 05-04- Shahnawaz

pass Date Result Difference, 2016
Shown from
Expectation.
1.4 Test to Ethnicity Search No Pass 05-04- Shahnawaz
pass Result Difference, 2016
Shown from
Expectation.

Data:

Item Data Input Test Type Expected P/F Date By

Result

1.1 Muhammad Test to Valid Pass 05-04-2016 Shahnawaz

Tamoor Pass Name
Iqbal

1.2 Jhang Bazar Test to Valid Pass 05-04-2016 Shahnawaz

Faisalabad Pass Location

1.3 8-6-2015 Test To Invalid Pass 05-04-2016 Shahnawaz

Fail Date
Operating System Environment Software’s used Version

Windows 7 & 8 Normal user environment under XAMPP, MYSQL, Latest

Windows OS with Internet DREAMWEAVER Version
connection.

Executed: 05-04-2016 Executed By: Shahnawaz Passed/Failed: passed

TC: 1

TC-2:Upload Missing Person Information.

Number TC-2 Date Created: 05-04-2016 Created By: Shahnawaz

Requirement #: 2

Description: Any person can Upload the Missing person information by putting name, date
of birth, address and last seen date.

Steps

Step Type Description Expected Actual, if P/F Date By

different
from
Expected
1.1 Test to Enter the The No Pass 05-04- Shahnawaz
pass Missing Record is Difference, 2016
Person Updated from
Name Expectation.

1.2 Test to Enter The The No Pass 05-04- Shahnawaz

pass Date of Record is Difference, 2016
Birth Updated from
Expectation.

1.3 Test to Enter The The No Pass 05-04- Shahnawaz

pass Address Record is Difference, 2016
Updated from
Expectation.

1.4 Test to Enter the The No Pass 05-04- Shahnawaz

pass last date to Record is Difference, 2016
seen Updated from
Expectation.

Data:

Item Data Input Test Type Expected P/F Date By

Result
1.1 Muhammad Test to Pass Valid Name Pass 05-04-2016 Shahnawaz
Sarib

1.2 16-9-1994 Test to Pass Valid Date Pass Shahnawaz

of Birth
05-04-2016

1.3 Street No. 5 Test To Fail Valid Pass 05-04-2016 Shahnawaz

Mansoor Address
Abad
Faisalabad

Operating System Environment Software’s used Version

Windows 7 & 8 Normal user environment under XAMPP, MYSQL, Latest

Windows OS with Internet DREAMWEAVER Version
connection.

Executed: 20-07-2015 Executed By: Shahnawaz Passed/Failed: passed

TC: 2

TC-3:User can view the lost cases of missing person.

Number TC-3 Date Created: 05-04-2016 Created By: Shahnawaz

Requirement #: 3
Description: The user can search the missing person record by putting the name, date of
birth and date of last seen.

Steps:

Step Type Description Expected Actual, if P/F Date By

different
from
Expected

1.1 Test to Enter the The No Pass Shahnawaz

pass Missing Record is Difference,
Person from 05-04-
Name Shown Expectation. 2016

1.2 Test to Enter The The No Pass 05-04- Shahnawaz

pass Date of Record is Difference, 2016
Birth from
Shown Expectation.

1.3 Test to Enter The The No Pass 05-04- Shahnawaz

pass Date Record is Difference, 2016
from
Shown Expectation.

Data:
Item Data Input Test Type Expected P/F Date By
Result

1.1 Qamar Test to Pass Valid Name Pass 05-04-2016 Shahnawaz

Abbas

1.2 17-7-2000 Test to Pass Valid Date Pass 05-04-2016 Shahnawaz

of Birth

1.3 14-4-2015 Test To Valid Date Pass 05-04-2016 Shahnawaz

Pass

Operating System Environment Software’s used Version

Windows 7 & 8 Normal user environment under XAMPP, MYSQL Latest
windows OS with Internet Version
connection.

Executed: 05-04-2016 Executed By: Shahnawaz Passed/Failed: Passed

TC: 3

TC 4: View Record of the Person which is not found.

Number TC-4 Date Created: 05-04-2016 Created By: Shahnawaz

Requirement #: 4

Description:The user can view the person record by putting the gender, ethnicity, age, date
in which he is missed and record shown that the person is not found.

Steps:

Step Type Description Expected Actual, if P/F Date By

different
from
Expected

1.1 Test to Enter the View The No Pass 05-04- Shahnawaz

pass Missing Record Difference, 2016
Person from
Name Expectation.

1.2 Test to Enter The View The No Pass 05-04- Shahnawaz

pass Date of Record Difference, 2016
Birth from
Expectation.

1.3 Test to Enter The View The No Pass 05-04- Shahnawaz

pass Date Record Difference, 2016
from
Expectation.

Data:
Item Data Input Test Type Expected P/F Date By
Result

1.1 Sira Afzal Test to Pass Valid Name Pass 05-04-2016 Shahnawaz

1.2 15-6-1995 Test to Pass Valid Date Pass 05-04-2016 Shahnawaz

of Birth

1.3 15-3-2015 Test To Valid Date Pass 05-04-2016 Shahnawaz

Pass

Operating System Environment Software’s used Version

Windows 7 & 8 Normal user environment under XAMPP, MYSQL Latest
windows OS with Internet Version
connection.

Executed:05-04-2016 Executed By:Shahnawaz Passed/Failed:passed

TC: 4

TC 5: User can View the Child record.

Number TC-5 Date Created: 05-04-2016 Created By:Shahnawaz

Requirement #: 5
Description:In the child Adoption Module user can view the child record his name, date of
birth, and contact info is written in it. User can contact to the NGO for further detail.

Steps:

Step Type Description Expected Actual, if P/F Date By

different
from
Expected

1.1 Test to Enter the The No Pass 28-07- Shahnawaz

pass child name Record of Difference, 2015
Child is from
Shown Expectation.

1.2 Test to Enter the The No Pass 28-07-

pass Date of Record of Difference, 2015
Birth Child is from Shahnawaz
Shown Expectation.

1.3 Test to Enter The The No Pass 28-07- Shahnawaz

pass Contact Record of Difference, 2015
Number Child is from
Shown Expectation.

Data:

Item Data Input Test Expected P/F Date By

Type Result
1.1 Zara Asghar Test to Valid Name Pass 28-07-2015 Shahnawaz
Pass

1.2 13-5-2014 Test to Valid Date Pass 28-07-2015 Shahnawaz

Pass of Birth

1.3 0321-7660775 Test To Valid Pass 28-07-2015 Shahnawaz

Pass Contact
Number

Operating System Environment Software’s used Version

Windows 7 & 8 Normal user environment under XAMPP, MYSQL Latest
windows OS with Internet Version
connection.

Executed:05-04-2016 Executed By: Shahnawaz Passed/Failed:Passed

TC: 5
 ChapterNo: 6

User Manual for Orphan Care Web Based System

1. General Information:
General Information section explains in general terms the system and the purpose for which it is
intended.

1.1 System Overview:

The web based system is developed in such a way that it provides complete help for the people
who want to take help from the NGO for the education purpose, for the adoption of the child or
for blood donation.

Our web based system consists of the record of missing person which is missing in an area with
respect to its area and date of missing it. Anyone can upload the record of the missing person by
first register in the web portal and view the data of any person and uploaded the data of any
missing person with complete biography.

The importance of this system is very important in this digital era because there is no proper web
based system which is completely contains the record of the person which is missing with
respect to its complete biography and date in which he is lost. In the past people does not have
any proper channel or plate form where they can upload the data of the missing person.

Our web based system also consists of the child adoption portion in which list of child is
described in the web based system and willing person can contact to them for adoption. A
complete form is developed in the system in which a person fill the form and then the NGO
process this for and contact the willing person for the child adoption and then willing person can
adopt the child.

Our web based system can also consists of the portion of free education in which willing children
can fill the online form for their scholarship studies and then NGO process this for check the
condition and contact the willing families.

We also developed a fund raising module basically this is the type of org which often run on
funds they always need it to support the orphan and to run the organization .For this purpose we
are introducing a form or the account details through which the willing persons or rich families
can donate funds to support the humanity.

1.2 Organization of the Manual:

The user’s manual consists of five sections: General Information, System Summary, Getting
Started, Using the System, and Reporting.
General Information: Section explains in general terms the system and the purpose for which it
is intended.
System Summary Section provides a general overview of the system. The summary outlines the
uses of the system’s hardware and software requirements, system’s configuration, user access
levels and system’s behavior in case of any contingencies.
Getting Started Section explains how to useand operate our web based system. The section
presents briefly system menu.
Using the System: Section provides a detailed description of system functions.
Reporting: Section describes in what way information collected by the application are presented
and how to access the information.

2 System Summary:
Our web based system consists of four modules each modules describes the functionality of the
system completely.

These modules are describes following:

Missing person module:

We developed a web based system in which any person can upload the data of missing person in
the website (its contact number, picture, date of birth, address etc).Then the admin panel can
process this data. Contact the family of the person who upload the data and verify it.. When the
data is enter or uploaded by a person it can pop up with new entry for everyone who can see this
site. The latest news section is also provided help for latest entry of the data.Once the data
uploaded by the person is matched with the person who is found then the pop up is shown that
gives the person information that the missing person is found and when the missing person is
found then data is removed from the missing person database and refresh it.
Child Adoption Module:
Our web based system also provides a portion of a child adoption module. In this module detail
list of the children will be displayed for adoption. The willing person can contact to the
organization for adoption of the children.

Free Education Module:

In this module the willing children which have better interest in the study but their family cannot
support for study can apply online for scholarship study. The scholarship form is consists in this
web page. The willing child can fill all the form and send it to NGO electronically. Then the
NGO process this scholarship form and further process is done.

2.1 System Configuration:

The Web system is compatible to work under Microsoft Windows platform which include
Windows 95/98, Window Millennium (Me), Window NT, Windows 2K, Windows XP and
Windows Vista, Windows 8 and windows 7. It also consists of a server like WAMP Server or
APACHE Server.

2.2 User Access Levels:

Everyone can use application and every user are able to save data to database.

2.3 Assumption and Dependencies:

In our web based system we assumed that there is Microsoft windows XP, windows 8 or 7 is
installed on the computer with specific 32 bit platform. We also assumed that the response time
of our website is very good and user can not feel anxiety while using this web based system
completely. We also assumed that user has some knowhow of operating our web based system
and user interface of our web based system is completely user friendly. If user has problem in the
user interface then there is step by step instructions are given in the help tab module.

Our web based system has dependencies like it can only operate with XAMP or APACHE server
install on the system means it depends on external factors like XAMP or APACHE server. It also
depends upon the proper connectivity of server with the web based if the system has proper
connectivity then the communication is done properly.

3. Getting Started:
Getting started section explain how our web based system is completely started his work. It
explain the parts and its modules how the system is worked properly.
3.1. Introduction:
The Orphan Care web based system is a web system which is developed for NGO. The Orphan
Care web based system is consists of four modules which are active modules in our web based
system completely.

Orphan Care Web based system is consists of Missing Person Module. In which there is
two more sub branches. “Search for Missing” and “Looking for Parents ” in search for
missing user can upload the record of the missing person completely and send it to the
admin panel and “Looking For Parent Module” is search for parents to the lost person or
child.
Orphan Care Web based system consist of free Education Module in which a scholarship
form is filled by willing child and send to the server then it is processed and result is send
through emails and contact to the willing child.
Orphan Care Web based system also consists of child adoption module in which willing
families can search the child and provided her info in a form placed in the Web page and
send it to the server then server processed t and contact to the willing families.
Orphan Care Web based system also consists of Fund raising module in which donor can
send donation through our pay pall account by providing all info in the form and send it
to the server.

3.2 Supported Browser:

The following browsers have been tested for use with the Orphan Care Web based system. It is
recommended that you use the most current revision of the browser you choose. The minimum
browser revisions supported by the Orphan Care Web based system are shown below:

Internet Explorer 7
Firefox 2.0.0.7
Chrome
Opera
Safari

3.3 Home Page:

Home Page 1
Home Page 2

Home Page 3
3.4Missing Person Page:

Missing Person Page 1

Missing Person Page 2

 Missing Person Page 3

The missing person page is user friendly any one can use this with some knowledge to use the
web based system. The page consists of report us button by clicking on this page we have a
dialogue box with two entries “Report us if anyone is missing” and “Report if your person is
found for record deletion”.

By clicking on the “Report us if anyone is missing” a form is open in a dialogue box in which
you upload the missing person record and send it to the database server. For further process.

By clicking on the “Report if your person is found for record deletion” the form is open in which
user provided info which he provided before and send it to the database server.

User can also search the missing person child by putting name, date of birth, date of lost by
entering in the search bar and result is shown on the page.

There is also a tab of “quick links” in which a missing person record is randomly shown if user
can click on it then the missing person record is shown in the page.
3.5 Free Education Page:

Free Education Page consists of the Guidelines, criteria and full description of the scholarship
which is provided to the willing child. It consists of a form in which all the information is
provided in with respect to the willing child and send it to the database server.
3.5 Child Adoption Page:

The child adoption Page of our web based system consists of list of child images by clicking on
child image his info is shown on the page. If any person want to adopt the child then he just fill
the form which is on our web page and send it to the database server.

Then our administration verify your identity by sending you emails and contacting you and then
you can adopt the child.
3.6 Fund Raising Page:

Our Fund Raising Page consists of a system in which a user want to donate some money to save
the life of a child. Then the user click on the donate button then our PayPal account is open
where user log in to and donate amount which he wants to donate.
ChapterNo: 7

Post Mortem Report

1. Introduction to Post Mortem Report:
The Project Post Mortem Report is one of the final documents for the project and is used by the
project manager and senior level management to assess the success of the project, identify best
project practices, problem areas, and provide detailed suggestions for improvement on future
projects.

A project post-mortem is a process, usually performed at the conclusion of a project, to

determine and analyze elements of the project that were successful or unsuccessful. Project post-
mortems are intended to inform process improvements which mitigate future risks and to
promote iterative best practices. Post-mortems are often considered a key component of, and
ongoing precursor to, effective risk management.

Post-mortems can encompass both quantitative data and qualitative data. Quantitative data
include the variance between the hours estimated for a project and the actual hours incurred.
Qualitative data will often include stakeholder satisfaction, end-user satisfaction, team
satisfaction, potential reusability and perceived quality of end-deliverables.
A postmortem is a process in which you look at a project’s history and analyze its positive and
negative aspects. The goal is to help you learn from your successes and mistakes. But don’t let
the morbid name fool you a postmortem is an extremely effective way to improve and establish
best business practices.

2. Post Mortem Report Goals:

The Project Post Mortem Report aims to:
Review and validate the deliverables and success of the project.
Identify project highlights and accomplishments for future projects.
Identify problem areas and how problems were mitigated/dealt with.
It helps project team members share and understand each other’s perspectives.
It integrates individual and team learning.
It identifies hidden problems.
It documents good practices and problems (so as not to repeat bad practices).
It increases job satisfaction by giving people feedback about their work.
It can even improve project cost estimation.
3. Steps for Holding a Successful Post-Mortem:

Ensure the project post-mortem is listed as a task on your project planWhen you
review the project plan with the team at the beginning of the project, explain the concept
so everyone knows what to expect at the end.
Think about the outcomes of a successful post-mortemand work backwards to plan the
meeting. Who should be invited? What are the “rules of engagement?” How will the
results be used?
 Develop a set of possible questions as a guideline. These questions might refer to
different phases of the project or different topic areas such as communication, planning,
vendor management, or user feedback. Reading these questions gives participants a
structure to help them think through the issues they want to bring up, so no key project
areas are missed.
Engage a facilitator and a scribe if possible. Especially for a large project, this provides
a neutral presence so that everyone is on equal footing and in the same role as a
participant.
Invite the participants. Remind them of the purpose of the post-mortem and send the
questions in advance. The goal is to make everyone feel comfortable, so provide enough
information beforehand so participants know what to expect.
State the “rules of engagement” either in your invitation or at the outset of the meeting.
The goal is to maintain trust throughout the exercise; you may want to change these
guidelines based on how well the team has worked together throughout the project.
Conduct the post-mortem. Make sure the room is comfortable and that participants
won’t be disturbed. If possible, ask them not to multi-task or use laptops during the
process, so everyone is equally engaged. Make sure you have flip charts and pens (or the
high tech equivalent) to record key concepts.
Compile the report. It’s helpful to have a summary section where you discuss the
process, share major findings, and list the lessons the team can apply to the next project.
In the appendix, you can share the details. Be sure to send all the participants a draft of
the report to make sure their ideas were heard. Once the report is final, store it in a place
that is easily accessible to everyone.
Share the “lessons learned” with your organization. This kind of sharing helps all the
project teams to do a better job — to learn from your successes and avoid some of your
missteps.

4.Project Parameters:
Project Name: Orphan Care

Department: Computer Secince

Project Sponsor:

Project Manager:

Target Completion Date:

Actual Completion Date:

5.Project Overview:
Our web based system consists of the record of missing person which is missing in an area with
respect to its area and date of missing it. Anyone can upload the record of the missing person by
first register in the web portal and view the data of any person and uploaded the data of any
missing person with complete biography.

The importance of this system is very important in this digital era because there is no proper web
based system which is completely contains the record of the person which is missing with
respect to its complete biography and date in which he is lost. In the past people does not have
any proper channel or plate form where they can upload the data of the missing person.

Our web based system also consists of the child adoption portion in which list of child is
described in the web based system and willing person can contact to them for adoption. A
complete form is developed in the system in which a person fill the form and then the NGO
process this for and contact the willing person for the child adoption and then willing person can
adopt the child.

Our web based system can also consists of the portion of free education in which willing children
can fill the online form for their scholarship studies and then NGO process this for check the
condition and contact the willing families.

The purpose of our web based system is to provide the easiness for the orphan children who want
to study and provide the facility to those families who lost their member and want to search them
and also provide the blood facility for the patient who died in the hospital for no facility of blood
in proper time.

5.1 Project Goals:

Our web based system is developed to increase the easiness of the people who want to found a
missing person. In past there is no proper channel through which a person can complain to find a
missing person. Our goals are to increase the easiness in our web based system so that a user can
easily understand our web based system and easily achieve his goal.

Increase the easiness in our web based system so that user can easily understand the
system and perform his/her actions.
System is developed such that a lay man can also easily understand the contents of our
web based system.
User can easily search the person which he want to search in Missing person module.
The look and feel of our web based system is easily understand by the user who have little bit
knowledge of it.
We developed our web based system in such a way that user is satisfied with it.
 User can also give Feed back to us for further development in our web based system
completely.
We developed our web based system with the purpose to facilitate the user with the lot of
extent.

5.2Project Success Criterion:

In our Web based system project success criteria are set as finishing project on time and
under budget and proper decision making will be complicated.
We developed our web based system such that it does not allow us to interpret the
significance and if the project exceeds the planned budget but is finished earlier than
expected or if it is finished late but saves some money.
Our web based system will fails to evaluate the consequences if the project was on time
and within planned budget but expected revenues were not achieved.
In our web based system we suggest to set one single project success criterion that
integrates project schedule, cost and business goals.
Establishing this single criterion is complex since it must include project scheduling,
project budgeting, estimating of the future business benefits from the project product
delivery, and risk analysis and simulation.
In our web based system if the project profit meets or exceeds the target profit then
performance is successful.

6. Project Performance:
6.1 Key Accomplishments:
6.1.1 What went right?
In our web based system (Orphan Care) we developed a system which consists of four module.
These modules are given below:

Missing person module:

We developed a web based system in which any person can upload the data of missing person in
the website (its contact number, picture, date of birth, address etc).Then the admin panel can
process this data. Contact the family of the person who upload the data and verify it.. When the
data is enter or uploaded by a person it can pop up with new entry for everyone who can see this
site. The latest news section is also provided help for latest entry of the data

Child Adoption Module:

Our web based system also provides a portion of a child adoption module. In this module detail
list of the children will be displayed for adoption. The willing person can contact to the
organization for adoption of the children.
Free Education Module:

In this module the willing children which have better interest in the study but their family cannot
support for study can apply online for scholarship study. The scholarship form is consists in this
web page. The willing child can fill all the form and send it to NGO electronically. Then the
NGO process this scholarship form and further process is done.

Fund Raising:

Basically this is the type of org which often run on funds they always need it to support the
orphan and to run the organization .For this purpose we are introducing a form or the account
details through which the willing persons or rich families can donate funds to support the
humanity.

The missing person module of our web based system is went right properly in our web based
system because we focused completely on this module. We spent our lot of time on this module
and our project 60 percent effort is added on this module.

6.1.2 What worked well?

In our web based system (Orphan Care) we consists of four module. These modules are fully
functional and provided lot of facilities to the user of our web based system. We focused
completely on our user interface and the content we used in our web based system completely.
We focused on these things because anyone who is want to get facilitation from our web based
system completely facilitated if he has little bit knowledge of it.

The content we used in our web based system can easily understandable by a lay man. The user
interface we used is well defined and easily understand by everyone. This thing of our web based
system is worked well.

6.1.3 What was found to be particularly useful?

In our web based system we used Dreamviewer tool in our web based system to develop the
system completely. This tool is very easy tool to developers end. This tool has increases the
efficiency of system. This tool is time consumption tool completely. This tool is found particular
useful in our system.

We use PHP not WordPress in our web based system completely this tool PHP is very efficient
tool and we prefer this tool in our web based system completely.

PHP code can be simply mixed with HTML code, or it can be used in combination with
various tempting engines and web frameworks. PHP code is usually processed by a
PHP interpreter. Which is usually implemented as a web server's native module or common
Gateway Interface (CGI) executable. After the PHP code is interpreted and executed, the web
server sends resulting output to its client, usually in form of a part of the generated web page; for
example, PHP code can generate a web page's HTML code, an image, or some other data. PHP
has also evolved to include a command-line interface (CLI) capability and can be used
in standalone graphical applications

This PHP language is particularly useful in our web based to complete our system with lot of
functionalities.

6.1.4 Project highlights:

Our web based system is developed to provide the facilities to the needy and to the peoples
which are in trouble. Our web based system consists of the module in which a person can upload
the record of the person who is missed and provided all the information and when the person is
found then pop up emails are send to the relatives of the person and the record of the persons are
then put in the founded list.
Our web based system consists of the free education system in which willing child can fill the
form completely and waiting for system response. User can also get online lectures from the
website with ease. Our web based system can also consists of the blood donation system in
which the user can register himself and provided all information in the system and when the
required blood is needed then the message are send to the person with same blood group. And
user can also send donation to the NGO by simply registering himself and provided email id
name and account number and the amount is extracted from the account.

6.2 Key Problem Areas:

6.2.1 What went wrong?
In our web based system we consists of four module. Each Module has its own functionality and
set of criteria.

We have problem with our project is that we have lack of communication meetings.
Communication meetings is the most important factor of successful project management.Without
regularly and clearly communicating, the project will fall apart. The communication meetings is
one problem which went wrong in our web based system and we hardly know how we added the
functionalities in our project completely.

One thing also went wrong in our web based system the fund raising module. We want to
develop a fund raising module in which a person add his/her bank account and amount and the
amount is transfer to the NGO account and pop up email is send to the user account. But we have
faced some type of technical problem in this module.

6.2.2 What project processes didn’t work well?

In our web based system project planning phase of our web based system does not work well
properly.
Project planning is one of the main project management processes. In this process, the project
plan is derived in order to address the project requirements such as, requirements scope, budget
and timelines. Once the project plan is derived, then the project schedule is
developed.Depending on the budget and the schedule, the resources are then allocated to the
project.

In our web based system the planning of our project is not properly done and handled. The
scope of our requirements is not properly managed. The budget of our project is not handled
properly. The timelines of our project means project completion is not properly managed such
that the timeline of our project is increased. The schedule of our project is not properly planned
and the resource allocation is not properly delivered in our web based system. We managed all
this with extent of time.

6.2.3 What specific processes caused problems?

In our web based system (Orphan Care) Project planning process is caused problem in our system
completely.

In our web based system the project specification is not described completely and in proper manner. The
errors ambiguities and other technical problem is not handled in this project completely. It is not clear,
incomplete and rigorous and does not eliminate misunderstandings, contradictions, oversight of
technical difficulties.

The problem we faced are:

The work duplicates or negates work already done

The deliverable is not appropriate
The time frame is unrealistic
The work depends on work of others
The resources are not available
The cost is prohibitive
6.2.4 What were the effects of key problems areas (i.e. on budget, schedule, etc.)?
The key problem areas have great effect on budget and schedule of our web based system
completely. The budget of our web based system is increases because the planning phase of our
system is not properly done and lot of functionalities which we want is understand to us or given
us at the time of testing so lot of extra work is done to meet our expectations that’s why budget
of our system is effect. The schedule of our system is effect also because at the time of testing
phase the functionalities are added and we move towards on design and implementation phase so
extra effort is done and extra time is spent on it so schedule is also effected.
6.2.5 Technical challenges:

Unrealistic deadlines - Some would argue that the majority of projects have "schedule
slippage" as a standard feature rather than an anomaly. The challenge of many managers
becomes to find alternate approaches to the tasks and schedules in order to complete a
project "on time", or to get approval for slipping dates out. An "absolute" time-based
deadline such as a government election, externally-scheduled event, or public holiday
forces an on-time completion. In our web based system unrealistic deadline is a challenge
for our team and we have managed all the resources to meet this goal. We have need to
manage the stress of "the immovable rock and the irresistible force" (i.e. the project
deadline and the project issues) with creative planning, alternatives analysis, and
communication of reality to the project participants. Also determine what deadlines are
tied to higher level objectives, or have critical links into schedules of other projects in the
organization's portfolio.
Communication deficit - Many project managers and team members do not provide
enough information to enough people, along with the lack of an infrastructure or culture
for good communication.
In our web based system we Determine proper communication flows for project members
and develop a checklist of what information (reports, status, etc.) needs to be conveyed to
project participants. The communications checklist should also have an associated
schedule of when each information dissemination should occur.
Scope changes - As most project managers know, an evil nemesis "The Scope Creep" is
usually their number one enemy who continually tries to take control. In our web based
system there is no anti-scope-creep spray in our PM utility belts, but as with many project
management challenges, document what is happening or anticipated to happen.
Communicate what is being requested, the challenges related to these changes.
Resource competition - Projects usually compete for resources (people, money, time)
against other projects and initiatives, putting the project manager in the position of being
in competition. In our web based system we define and set project priority across all
projects. Also realize that some projects seemingly are more important only due to the
importance and political clout of the project manager, and these may not be aligned with
the organization's goals and objectives.
Uncertain dependencies - As the project manager and the team determine project
dependencies, assessing the risk or reliability behind these linkages usually involves
trusting someone else's assessment. "My planner didn't think that our area could have a
hurricane the day of the wedding, and now we're out of celebration deposits for the hall
and the band, and the cost of a honeymoon in Tahiti!”. In our web based system we use
several people - use brainstorming sessions - pick at the plan elements and dependencies,
doing "what if?" scenarios. Update the list of project risk items if necessary based on the
results.
Insufficient team skills -The team members for many projects are assigned based on
their availability, and some people assigned may be too proud or simply not
knowledgeable enough to tell the manager that they are not trained for all of their
assigned work.In our web based systemstarting with the project manager role, document
the core set of skills needed to accomplish the expected workload, and honestly bounce
each person's skills against the list or matrix. Using this assessment of the team, guide the
team towards competency with training, cross-training, additional resources, external
advisors, and other methods to close the skills gap.
Lack of accountability - The project participants and related players are not held
accountable for their results - or lack of achieving all of them. In our web based system
we Determine and use accountability as part of the project risk profile. These
accountability risks will be then identified and managed in a more visible manner.
Vision and goals not well-defined - The goals of the project along with the sub-projects
or major tasks involved, are not always clearly defined. Clearly communicating these
vague goals to the project participants becomes an impossible task. In our web based
system we Determine which parts of a project are not understood by the team and other
project participants - ask them or note feedback and questions that come up. Check the
project documentation as prepared, and tighten up the stated objectives and goals - an
editor has appropriate skills to find vague terms and phrasing. Each project is, hopefully,
tied into to the direction, strategic goals, and vision for the whole organization, as part of
the portfolio of projects for the organization.