1.

Introduction

1.1 Software Requirement Specification (SRS)

A software requirements specification (SRS) is a comprehensive description of the

intended purpose and environment for software under development. The SRS fully
describes what the software will do and how it will be expected to perform.

An SRS minimizes the time and effort required by developers to achieve desired goals
and also minimizes the development cost. A good SRS defines how an application will
interact with system hardware, other programs and human users in a wide variety of
real- world situations. Parameters such as operating speed, response time,
availability, portability, maintainability, footprint security and speed of recovery
from adverse events are evaluated.

1.2 Introduction of Hope Center

Hope Center is a donation based Website that can help user to donate or ask for
donations. The Main objective of this website is to help the user who want to donate
but can't because of their limitations. This website will help the user to donate easily
through bKash and also help others to collect donations easily. The easiest and
quickest way to connect with each other. Users can also see the updates of a particular
cause to know the progress.

1.3 Purpose of Hope Center

The proposed project is a smart way to donate or ask for donations. This is a web
based application that provides a medium to donate, information of causes and the
users so that they can get their need within few clicks. This is a platform for all those
who are in need of donations.

1.4 Why Hope Center

A Hope Center website enables user to create post for asking donations and also helps
to donate in any particular cause. Allows to give updates and view any user
information before donating and helps users to donate easily.

1|Page
1.5 Advantages of Uses

• Easiest way to donate: user can easily donate through bKash

• Create Post: User can create a post in need of donation and also can give updates if
required

• Look for cause: User can easily look for causes they want to donate

• Create Profile: Users can create and edit profile with required information and also
change email and password if needed

• Users Information: The donors can easily look for users information before
donating

• Register : one can ask for donations by creating a post ,give updates of a particular
post, edit post, view other fund details after creating an account.

• Comment: Register user can comment in any particular post and any user can report
unnecessary comments

2|Page
 2. Methodology

2.1 Methodology

Prototyping approach is applied while developing this system. This will involve an
iterative process to make this system is usable and easy to use by the user. The design
for the system is using the System Development Life Cycle (SDLC) approach. The
design will involve entity relationship diagram (ERD) and Data Flow Diagram (DFD)
to show the logical flow for the system.

2.2 Implementation

At this phase, all the design will be transferred into the programming language.
Prototyping approach will be used in the implementation phased. It means that the
system will be keep on building and testing until the system meet the requirement
during the design phased.

2.2.1 Functional Requirements:

 User Friendly Interface which the user can use.

 Provide accessibility to the application through Wi-Fi or cellular network.
 MySQL that stores the information to be displayed to the user.

2.2.2 Software Requirements:

 Apache will be used as a web server

 MySQL as a database
 Codeigniter, which is a PHP Framework will be used to develop this system
 Bootstrap framework will be used for HTML / CSS design
 AdminLTE Theme will be used for Admin Dashboard Design
 JavaScript will be used for Graphical Data Representation
 JQuery will be used as a scripting Language
 AJAX will be used for exchanging data with a server instantly

3. Feasibility Study

3|Page
As we know each and every project needs to have a feasibility study for the complete
understandability of the project. I will consider 3 types of feasibility study they are:

1. Technical Feasibility
2. Operational Feasibility
3. Economic Feasibility

3.1 Technical Feasibility

The technical feasibility study basically centers on alternatives for hardware, software
and design approach to determine the functional aspects of the system. The Hope
Center is a web based system so it doesn’t require to be installed on every machine.
Technical feasibility aims to answer the following questions:

- Does the necessary technology exist to do what is suggested?

- Do the system equipment’s have the technical capacity to hold the data
required to use the new system?
- Will the system provide satisfactory response to inquiries, regardless of the
number users?
- Are there technical guarantees of accuracy, reliability, ease of access and
data security?
- Can the system be upgraded if developed?
- The current system is technically feasible. It is a web based user interface
design. Thus it provides an easy access to the users.

3.2 Operational Feasibility

Operational feasibility is the ability to utilize, support and perform the necessary
tasks of a system or program. It includes everyone who creates, operates or uses
the system. To be operationally feasible, the system must fulfill a need required by
the business. Operational feasibility aspects of the project are to be taken as an
important part of the project implementation. Some of the important issues raised
are to test the operational feasibility of a project includes the following:

- Is there enough support for the management from the users?

- Will the system be used and work properly if it is being developed and
implemented?
- Will there be any resistance from the user that will undermine the possible
application benefits?

4|Page
 This system is targeted to be in accordance with the above-mentioned issues.
Beforehand, the management issues and user requirements have been taken into
consideration. So there is no question of resistance from the users that can
undermine the possible application benefits.

3.3 Economic Feasibility

The cost is not the boundary for inventions. Cost is the secondary thing for system to
execute successfully. But the primary thing is to invent new things which should
satisfy the needs efficiently and effectively. This system is a web based system so
there is no major cost. So the system is economically feasible.

5|Page
 4. Requirement Analysis

4.1 Operating Environment

As mentioned it is a web based application thus the system can be used by any type of
operating system either mobile or computer. This project is using PHP 5 so the
uploaded server must enable PHP 5. The system is using bootstrap framework for
responsive design so that it can be used by any size of mobile devices or tablets. This
software can be used by Google Chrome, Mozilla Firefox, Opera, Internet Explorer
(8-11) etc. It should be mentioned that the browsers must support JavaScript to get
proper functionality of the system.

4.2 Design and Implementation Constrains

The application will use PHP (Codeigniter Framework), Ajax, JavaScript, JQuery,
Bootstrap and AdminLTE Dashboard Theme as main web technologies.

HTTP and FTP protocols are used as communication protocols. FTP is used to upload
the web application in live domain and the client can access it via HTTP protocol.

Different types of validations make this web application a secured one and SQL
Injections can also be prevented.

Since Hope Center is a web-based application, internet connection must be

established.

The Hope Center is online based and will function via internet in any web browser.

4.3 User Requirements

The Requirements Specification describes the business needs for what users require
from the system. User Requirements Specifications should be written before the
system created. They are written by the system owner and end-users, with input from
Quality Assurance. Requirements outlined in the User Requirements Specification
(URS) are usually tested in the Performance Qualification or User Acceptance Testing.
User Requirements Specifications are not intended to be a technical document; readers
only with a general knowledge of the system should be able to understand the
requirements outlined in the URS.

6|Page
4.3.1 Functional Requirements

These are statements of services the system should provide, how the system should
react to particular inputs, and how the system should behave in particular situations. It
specifies the system functionality that the developers must build into the product to
enable users to accomplish their tasks.

4.3.1.1 Registered User:

4.3.1.1.1 Admin:

Features for Admin:

1. Admin is the most powerful user of the Hope Center.

2. They will control the whole system.

3. Admin can approve/delete any post.

4. Admin can view all donations or funds raised .

5. Admin can view and delete reported comments.

6. Admin can approve/delete testimonials

7. Admin can add/delete gallery.

8. Admin can View Dashboard that shows the total post

created/donations/testimonials and comment reported.

4.3.1.1.2 User:

Features for User:

1. They will View All the Sections

2. They can View cause details
3. They can create post for asking donations.
4. They can give me feedback.
5. They can view donor’s information according to their need.
6. They can comment.

7|Page
 7. They can edit update or delete any posts

8. They can edit profile

9. They can change email or password

4.3.1.2 User:

Features for User:

1. They will View All the Sections

2. They can View cause details

3. They can view user’s information.

4. They can give me feedback.

5. They can register.

6. They can donate

7. They can report comment.

4.3.2 Non-Functional Requirements

Non-functional requirements, as the name suggests, are requirements that are not
directly concerned with the specific services delivered by the system to its users. They
may relate to evolving system properties such as reliability, response time, and store
occupancy. Non-functional requirements, such as performance, security, or
availability, usually specify or constrain characteristics of the system as a whole.

4.3.2.1 Security:

The system provides Phone/Email and password to prevent the system from
unauthorized access. The staffs’ password must be greater than eight characters.

4.3.2.2 Performance/Response time:

The system response time for every instruction conducted by the user must not exceed
more than a minimum of 10 seconds.

8|Page
4.3.2.3 Error Handling:

Error should be considerably minimized and an appropriate error message that guides
the user to recover from an error should be provided.

4.3.2.4 Availability:

The system should always be available for access at 24 hours, 7 days a week.

4.3.2.5 Ease of uses

The system provides a Dashboard and a Sitemap in all interfaces except landing page
for the user to interact with the system. The user can understand the features and
activities by reading Sitemap, and also can view the graphical data f various group.

9|Page
 5. DESIGN AND ANALYSIS

5.1 Design And Analysis:

Software Requirements Specification (SRS) is a part of software development, which

is a document that fully describes the expected behavior of a software system.
Software requirement specification (SRS) is a process under software requirement
engineering process. This is the next phase after feasibility study in software
requirement engineering process. It is a comprehensive description of the intended
purpose and environment for software under development. Software requirement
specification laying out functional and non-functional requirements, and may include
a set of use cases that describe interactions the users will have with the software. The
Software requirement specification (SRS) fully describes what the software will do
and how it will be expected to perform. My project that I want to develop is a “Hope
Center “ Where an admin can easily control this System. There will be various type of
user. All registered user can view all other user information data and only can update
their data, but the admin can update all other user information data.

The whole Software requirement specification for this project is described in the
chapter with the help of different diagrams, functional and non-functional
requirements. The following diagrams are described for the Software requirement
specification. They are use case diagram, Activity diagram, Sequence diagrams, Class
diagram, and Entity Relationship Diagram.

5.2 Use Case Diagram

Use case diagram is the most known diagram type. A use case diagram is the simplest
representation of a user's interaction with the system that shows the relationship
between the user and the different use cases in which the user is involved. A use case
diagram can identify the different types of users of a system. Use case diagrams gives
a graphic overview of the actors involved in a system, different functions needed by
those actors and how these different functions are interacted. Use case diagram
include use cases, actors, include relationship, extended relationship and system
boundary. A use case represents a function or an action within the system. Actor in

10 | P a g e
a use case diagram is any entity that performs a role in one given system. The use
case diagram of the system is given below

5.2.1 Admin Use Case Diagram

Figure: Use Case Diagram of the Admin.

11 | P a g e
5.2.2 Registered User Use Case Diagram:

Figure: Use Case Diagram of the registered user.

12 | P a g e
5.2.3 User Use Case Diagram:

Figure: Use Case Diagram of the User.

5.3 Activity Diagram

Activity diagram is basically a flow chart to represent the flow form one activity to
another activity. The activity can be described as an operation of the system. It can be
used to describe business workflow or the operational work flow of any component in
a system. The activity diagram is given below:

13 | P a g e
5.3.1 Admin Activity Diagram:

Figure: Activity Diagram of the Admin.

5.3.2 Registered User Activity Diagram:

14 | P a g e
 Figure: Activity Diagram of the Registered User.

5.3.3 Login Activity Diagram:

Figure: Login Activity Diagram.

5.3.4 User Activity Diagram:

Figure: Activity Diagram of the User.

15 | P a g e
5.4 Sequence Diagram

The Sequence Diagram is a type of diagram that shows how object interact with each
other and the order those interactions occur. Sequence diagram also shows the
interactions for a particular scenario. The processes are represented vertically and
interactions are show as arrows. The Sequences Diagrams will show the General user
and Register user processes and interactions.

5.4.1 Admin approve, delete post Sequence Diagram:

Figure: Sequence Diagram of Admin approve, delete post.

16 | P a g e
5.4.2 Admin delete comment Sequence Diagram:

Figure: Sequence Diagram of Admin deletes comment.

17 | P a g e
5.4.3 Add/ Delete Gallery or Testimonial Sequence Diagram:

Figure: Sequence Diagram of Add/ Delete Gallery or Testimonial.

18 | P a g e
5.4.4 User post Sequence Diagram:

Figure: Sequence Diagram of User post.

19 | P a g e
5.4.5 Create post Sequence Diagram:

Figure: Sequence Diagram of Create post.

20 | P a g e
5.4.6 Donate money Sequence Diagram:

Figure: Sequence Diagram of Donate money.

21 | P a g e
5.4.7 User add/report Sequence Diagram:

Figure: Sequence Diagram of User add/report.

22 | P a g e
5.5 Entity Relationship Diagram:

Figure of Entity Relationship Diagram

23 | P a g e
 6. System Overview (SNAPSHOTS)

6.1 Home Page

6.2 About Us

6.3 Donation Causes

24 | P a g e
6.4 Fund Raised Successfully

6.5 Add Testimonial

25 | P a g e
6.6 Gallery

6.7 View post details

26 | P a g e
6.8 Updates

6.9 Comments

27 | P a g e
6.10 Donation Form

28 | P a g e
6.11 User Dashboard

29 | P a g e
6.12 Donation Campaign

6.13 Post updates

30 | P a g e
6.14 View, Confirm, Delete Donations

31 | P a g e
6.15 Create Post

6.16 Admin Dashboard

32 | P a g e
6.17 Admin approve / delete post and view comments to filter

6.18 Admin Add Gallery

33 | P a g e
6.19 Admin approves or delete testimonial

34 | P a g e
 7. References

1. https://www.codeigniter.com/docs
2. https://www.codeigniter.com/user_guide/
3. https://www.youtube.com/watch?v=sLRyh-BIuxE
4. https://www.youtube.com/watch?

v=6Ekqeiz1sV0&list=PL5rdWLtPBQ3KPg9PTpR-sRur7fQzVLdiu
5. https://getbootstrap.com/docs/4.1/getting-started/introduction/
6. https://bootsnipp.com/tags/template
7. https://www.youtube.com/watch?
v=jnjjzATOgIM&list=PLh89M5lS1CIATULcdS4UHx9pj3GGW8nNM
8. https://www.youtube.com/watch?
v=7CHiREqfjqY&list=PLh89M5lS1CIATULcdS4UHx9pj3GGW8nNM&index
=2
9. https://dashboard.nexmo.com/sign-up
10. https://github.com/Nexmo/nexmo-laravel
11. https://getbootstrap.com/
12. https://stackoverflow.com/questions/44586473/update-method-not-working-in-
codeigniter
13. https://getbootstrap.com/docs/4.0/components/forms/
14. https://www.youtube.com/watch?

v=6Ekqeiz1sV0&list=PL5rdWLtPBQ3KPg9PTpR-sRur7fQzVLdiu&index=1
15. https://api.jquery.com/
16. https://www.youtube.com/watch?

v=QK4AglZDl_0&index=5&list=PL5rdWLtPBQ3KPg9PTpR-sRur7fQzVLdiu
17. https://www.youtube.com/watch?

v=STlOSK2wEv8&index=10&list=PL5rdWLtPBQ3KPg9PTpR-
sRur7fQzVLdiu
18. https://forum.codeigniter.com/archive/index.php?thread-68901.html

35 | P a g e