TABLE OF CONTENT

ACKNOWLEDGEMENT………………………………………………………………………
DECLARATION………………………………………………………………………………..
CERTIFICATE………………………………………………………………………………......

1. INTRODUCTION…………………………………………………………………………….…
2. OBJECTIVE……………………………………………………………………………………..
3. SYSTEM ANALYSIS……………………………………………………………………….…..
3.1 Existing System……..……………………………………………...................................
3.2 Proposed System………………………………………………………………………..
3.3 Technology Description ………………………………..
4. IDENTIFCATION OF NEED……………………………………………………………….
5. FEASIBILITY STUDY…………………………………………………………………………..
5.1 Technical Feasibility…………………………………………………………….………
5.2 Economical Feasibility…………………………………………………………………..
5.3 Operational Feasibility………………………………………………………….……….
6. PROJECT SCHEDULING…………………………………………………….....................
6.1 Gant Chart………………………………………………
6.2 Pert Chart……………………………………………………….
7. SOFTWARE ENGINEERI NG PARADIGM………………………………………………
8. SYSTEM DESIGN………………………………………………………………………………..
8.1 Use Case Diagram………………………………………………………………………
8.3 Data Flow Diagram ……………………………………………………………………………..
8.4 ER Diagram ……………………………………………………………………………..
8.6 DATA MODELS…………………………………………………………………….
9. USER INTERFACE (UI) DESIGN……………………………………………………………..
10. TESTING ……………………………………………………………………………….
10.1 Functional Testing……………………………………..
 10.2 Interface Testing…………………………………
10.3 Compatibility Testing……………………………………………………………..
11. SYSTEM SECURITY MEASURES………………………………………………………
12. COST ESTIMATION MODEL……………………………………………………………
13. REPORTS……………………………………………………
14. FUTURE SCOPE OF THE PROJECT …………………………………………………….
15. APPENDICES ………………………………………………………………………………..
16. BIBILIOGRAPHY…………………………………………………………………………………

LIST OF TABLES

Sr. No. Table Numbers Table Name

1. Table No. 1 Gantt Chart
2. Table No. 2 Pert Chart
 List of Figures

Figure 1:Pert Chart...............................................................................................................................

Figure 2: Gantt Chart…………………………………………………………………………………………………………………………
Figure 3: SDLC Phase………………………………………………………………………………………………………………………
Figure 4: Use Case Diagram……………………………………………………………………………………………………………
Figure 5: DFD 0-Level…………………………………………………………………………………………………………………….
Figure 6: DFD 1-Level………………………………………………………………………………

Figure 7: ER Diagram……………………………………………………………………………….

Figure 8: DATA MODELS………………………………………………………………………

Figure 9: Interface 1..............................................................................................................................

Figure 10: Interface 2............................................................................................................................
Figure 11: Functional Testing 1............................................................................................................
Figure 12: Functional Testing 2............................................................................................................
Figure 13: Home Page………………………………………………………………………………….

Figure 14: Interface Testing 1...............................................................................................................

Figure 15: Interface Testing 2...............................................................................................................
Figure 16: Interface Testing 3...............................................................................................................
Figure 17: - Microsoft Edge- Compatibility Testing...........................................................................
Figure 18: Google Chrome- Compatibility Testing.............................................................................
Figure 19: Internet Explorer- Compatibility Testing.........................................................................

6. Project Scheduling

6.1 Gantt Chart

Table 1: Gantt Chart

Figure 1: Gantt Chart
6.2 Pert Chart

Table 2: Pert Chart

Figure 2: Pert Chart
 Software Engineering Paradigm
For development of our project, we have used Software Development Life Cycle (SDLC) model.
This is because it is a very systematic way of developing any project. It ensures project’s quality
and improves the way of building a project.
Let us understand the phases of SDLC with the help of diagram or figure: -

Figure 3: SDLC Phases

As per the Figure 4, there are six different phases in SDLC model where each phase is connected
with other.
In our project, we are using Agile model as it follows an Iterative approach which was needed in
our project. As per agile model, large or big task is divided into small tasks so that every single
task is followed properly and further more we can go back to any of previous phases without
following incremental approach.
Different phases of Agile model are as follow: -
Requirement Analysis: This is the initial phase of the Software Development Life Cycle where
we analyze the requirement of our project and gather information/data regarding the project
which would help us throughout the development of the project.
In this phase we have marked the importance of our project ‘Creative-Care’ like here we find the
need for the project that how this project can be useful for mass.
System Design: System Design is the second and very important phase of the project
development. Here we try to understand the design of our project as well as we try finalize the
resources that we are going to use for the project development.
In this phase, we finalized the design f the interface as per the requirement then we finalized the
requirement of the software and hardware for the project development.
Implementation: Implementation is the phase where start development or we can say we start the
coding for the required specification of the project as per its design.
In this phase, we started coding for our project on the required tool. But this is the phase where
problem occurs in our project because in this phase the requirement of the project is increased
and we have to go through the initial phase of entire cycle and then again started the
implementation phase as per new requirement.

Testing: Testing is one of the most important phases of the entire cycle because this is where we
test the functionalities of the project and tends to find the unexpected bugs and error in the
project that had occurred during the implementation phase.
In this phase, we have used different kind of testing techniques for the testing of our website. All
of those testing techniques are mentioned in testing point of the document.

Deployment: Deployment is the phase where we implement our project on the desired place.
After this phase user can get access to the project.
Maintenance: Maintenance is the phase after the delivery of the project where specialist try to
maintain the project as well as update the project if it is dynamic as per the time and client
requirement.
 System Design

Use Case Diagram

Figure 4: Use Case Diagram

Data Flow Diagram

0-level:

Figure 5: DFD 0-level

Level 1:

Figure 6: DFD 1-level

ER Diagram

Figure 7: ER Diagram
DATA MODELS

Figure 8: ER Diagram
 User Interface (UI) Design

User Interface design is basically the interface that is used at the user’s end. It basically focuses
on the maximum usability and providing best experience to the user.
Here is the output screen as we click on the Button of login.

Figure 9: Interface 1– Login page

Figure 10: Interface 2– Register page
 Testing

Testing is one of the most important aspects of project building. It can check out the presence of
unknown bugs that may not have been detected while designing the project.
Our project is a web application (website) and according to Katalon “testing of website is done
by four different techniques”. Out of which we have used some of the techniques to test our
project under certain circumstances.

Functional Testing: - Firstly, we have done the functional testing of our project which includes
the proper functioning of the project, data input, result analysis and many more.

We have checked the interface and functionality of each button and found that every
functionality is working as we have intended to do it. Here is a snap of some of its functionality.

Firstly we have to register in website so we can able to login in website.

Figure 11: Functional Testing 1

 Figure 12: Functional Testing 2

Now, we have tested the Login form where form is validated correctly as per our testing then we
tested it by giving it inputs where we founded that the output provided is absolutely correct.
Here is a proof for this testing.
Interface Testing: - where we tested the interface of the website that whether it is User-friendly
or not.

Here are some snapshots of the interface of every division and their functionality on click.

Figure 13: Home Page

Figure 14: Interface Testing 1
Figure 15: Interface Testing 2

Figure 16: Interface Testing 3

Compatibility testing: where we have tried to execute our website over different browsers
present over our system. Here are some snapshots of the website over different browsers namely
Chrome, Microsoft Edge and Internet Explorer.

Figure 17: Microsoft Edge - Compatibility Testing

Figure 18: Google Chrome - Compatibility Testing
 Figure 19: Internet Explorer - Compatibility Testing

We don’t have multiple operating systems installed on our Systems that’s why we have not
tested the project functionality over different operating systems. Also, we have not tested it over
mobile view.
 Reports

 List of Rooms
 List of Domination
 List of Volunteer
 List of Payment