Department

of computer application
M.C.A.-2018-19
Project Report On Online Services

Submitted To:
Mr.Arun Bhardwaj
Submitted By:
Shivani Tomer
Roll No. 1706914915
1
M.C.A. IIIrd year (V sem.)

2
 RADHA GOVIND GROUP OF INSTITUTIONS, MEERUT
Anuyogipuram, Garh Road, Meerut-250 004 (U.P.) India

Approved by AICTE, New Delhi & Affiliated to U.P. Technical University,

Lucknow

................2018-2019..................

SESSION

CERTIFICATE
SELF CERTIFICATE

This is to be certified that the project report entitled “ ONLINE SERVICES” is done
by me in an authentic manner carried out for the partial fulfillment for the award
of the degree of MCA under the guidance of “Mr. Arun Bhardwaj”. The matter
embodied in this project work has not been submitted earlier for the award of
any degree or diploma to the best of my knowledge and belief.

(Signature)

Shivani Tomer

1706914915

Master of computer application

Radha Govind Group of Institutions, Meerut

3
I have taken efforts in this project .However,it would not have been
possible without the kind support and help of many individuals. I would
like to extend my sincere thanks to all of them.

I wish to express my sincere gratitude to Mr. Arun Bhardwaj, Head of

the Department of MCA for providing me an opportunity to do this
wonderful project on the topic “ONLINE SERVICES”, which also helped
me in doing a lot of research and I came to know about so many new
things I am really thankful to them.

My thanks and appreciations also go to my friends in developing the

project and people who have willingly helped me out with their
abilities.

Shivani Tomer

4
S.N Contents Sign
o
1. Software Development Life Cycle
2. Software Requirement Specification
3. Introduction
4. Project Description
5. System Architect
6. Use Cases
7. Functions
8. E-R Diagram
9. Feasibility Study
10. Requirement Analysis
11. Validation and Verification
12. Test Plan
13. Test Cases
14. Approaches/Testing
15. Future Scope
16. Bibliography

5
6
7
Communication:

This is the first step where the user initiates the request for a desired software
product. He contacts the service provider and tries to negotiate the terms. He
submits his request to the service providing organization in writing.

Requirement Gathering:

This step onwards the software development team works to carry on the project.
The team holds discussions with various stakeholders from problem domain and
tries to bring out as much information as possible on their requirements. The
requirements are contemplated and segregated into user requirements, system
requirements and functional requirements. The requirements are collected using
a number of practices as given - studying the existing or obsolete system and
software, conducting interviews of users and developers, referring to the
database or collecting answers from the questionnaires.

Feasibility Study:

After requirement gathering, the team comes up with a rough plan of software
process. At this step the team analyzes if a software can be made to fulfill all
requirements of the user and if there is any possibility of software being no more
useful. It is found out, if the project is financially, practically and technologically
feasible for the organization to take up. There are many algorithms available,
which help the developers to conclude the feasibility of a software project.

System Analysis:
At this step the developers decide a roadmap of their plan and try to bring up the
best software model suitable for the project. System analysis includes
Understanding of software product limitations, learning system related problems
or changes to be done in existing systems beforehand, identifying and addressing
the impact of project on organization and personnel etc. The project team
analyzes the scope of the project and plans the schedule and resources
accordingly.
8
Software Design:

Next step is to bring down whole knowledge of requirements and analysis on the
desk and design the software product. The inputs from users and information
gathered in requirement gathering phase are the inputs of this step. The output
of this step comes in the form of two designs; logical design and physical
design.Engineers produce meta-data and data dictionaries, logical diagrams, data-
flow diagrams and in some cases pseudo codes.

Coding:
This step is also known as programming phase. The implementation of software
design starts in terms of writing program code in the suitable programming
language and developing error-free executable programs efficiently.

Testing:

An estimate says that 50% of whole software development process should be

tested. Errors may ruin the software from critical level to its own removal.
Software testing is done while coding by the developers and thorough testing is
conducted by testing experts at various levels of code such as module testing,
program testing, product testing, in-house testing and testing the product at
user’s end. Early discovery of errors and their remedy is the key to reliable
software.

Integration:
Software may need to be integrated with the libraries, databases and other
programs. This stage of SDLC is involved in the integration of software with outer
world entities.

9
Implementation:

This means installing the software on user machines. At times, software needs
post-installation configurations at user end. Software is tested for portability and
adaptability and integration related issues are solved during implementation.

Operation and Maintenance:

This phase confirms the software operation in terms of more efficiency and less
errors. If required, the users are trained on, or aided with the documentation on
how to operate the software and how to keep the software operational. The
software is maintained timely by updating the code according to the changes
taking place in user end environment or technology. This phase may face
challenges from hidden bugs and real-world unidentified problems.

Disposition:

As time elapses, the software may decline on the performance front. It may go
completely obsolete or may need intense up gradation. Hence a pressing need to
eliminate a major portion of the system arises. This phase includes archiving data
and required software components, closing down the system, planning
disposition activity and terminating system at appropriate end-of system time.

10
11
 PREFACE

Executing any software project requires skills in two key dimensions----

engineering and project management.

While engineering deals with the issues of architecture Design, Coding, Testing
etc…

Project Management deals with Planning, Monitoring, Risk management, etc...

And this project focuses on engineering approaches as well as on coding part to
make the project good and impressive.

The goal of this project is to cover online services concerned with making services
easy and less time consuming and to cope up with the current technology and
trend.

12
 REQUIREMENT SPECIFICATION

HARDWARE REQUIREMENT

 Keyboard
 Monitor
 Mouse
 4 GB RAM
 dual core Processor

SOFTWARE REQUIREMENT

 XAMPP Server
 APACHE TOMCAT 7.0
 MS-SQL 2005
 Window Xp OR 7
 MS Office 2007
 Microsoft Internet Explorer

13
1. Introduction

1.1. Purpose
The purpose of this Software Requirements Specifications (SRS) is to fully
document the specifications and requirements for the online services. The
audience of this SRS will be the clients who want the software to be built and the
technical professionals developing the software.

1.2. Scope
The objective of this project is to create and implement a website for the online
services. The website will be used primarily by users. The website will allow users
to search the services .

1.3. References
The following material was used in creating this document:
• IEEE STD 830-1998, IEEE Recommended Practice for Software Requirements
Specifications.

1.4. Overview
The rest of the SRS is organized as follows:
• Section 2 is an overall description of the project.
• Section 3 cites the specific requirements

14
2.Overall description

2.1. Product Perspective

This product is an entirely new product. It is not a component of a larger system.
The online services system will interact with one another in order to provide
services from the website.

2.2. Product Functions

The following list of function descriptions explains the major features of the
Online Services.

2.2.1. Account Registration

The registration function shall allow users to create secure accounts.
The account will track the user’s name, address, credit card information,
Username and password.
Rationale: This provides security to the account member by setting up an account
that is password protected. This also offers convenience so the user only has to
enter the information listed above once and then it is stored in the account.

2.2.2. Account Login

The account login function shall allow account members to enter their username
and password. Once verified, users will be able to Access account history, purchase
books online, and update their Account information.
Rationale: This provides a method by which the user can access the restricted
operations.

15
2.2.3. Search
The search function shall offer users the ability to search for services by title.
Rationale: This offers a way to find a service if the user does not have Complete
information about it. It also provides price and availability Information.

2.2.4. Contact Us
The contact us function shall give users the store address, telephone number,
email address. Rationale: This helps the user gain trust in the services by showing
how easy it is to have person-to-person contact .

2.2.5. Update Account Information

The update account information function shall give account members access to
edit their stored information. Rationale: This offers convenience to the account
members by allowing them to make changes to account information immediately.

2.2.6. Account Logout

The account logout function shall allow account members to exit their account
for security purposes. Rationale: This allows account members to exit their
accounts, and prevent others from accessing it.

2.2.7. Help
The help function shall give the user an overview of how to use the different
functions listed above. Rationale: This allows the user to get answers to
immediate questions on using the website.

16
2.3. User Characteristics
Users of the website must know how to navigate in a Website.

2.4. Constraints
The constraints on the services and functions of the system are as follows.
• The software product must conform to online services policy.

2.5. Assumptions and Dependencies

Since the Online services is only accessible through the Internet, it is assumed
that the end user has a connection to the Internet. It is also assumed that the user
has a web browser able to display the website. (I.E. Microsoft Internet Explorer 4+
or compatible browser)

17
3. SYSTEM ARCHITECT

3.1.1. High Levels For Five Modules

According to requirements gather, the online services will be designed that
consists of five basic modules. The diagram is as follow:

18
  User Module
At first customers must login or register to the system. Customers can purchase
services after validate valid identity. Customers can modify their own account
information at any time. When customers register successful, the online services
system will save customers’ all information. One more function, when customers
forget their password, they can click on”forget password” link to get back
password.

 Services Module
The function of services module is to show all of services. When customers enter
online services website, they can view a list of all services categories and
subcategories. The system sorts services, customers browse all kinds of services
as needed. Customers can view detail information of services.

Registration Module

In this module, user can registor for the services available on the website. User
can enter the name, password, gender,email id & contact number in the
registration form & get registration on the website.

Back End of Manage Module

Here is back end database of services module. When users input ID and
password, the system verifies identity.

19
 3.1.2 Detail Levels Designing:

Customer Sitemap

This figure shows how a customer enters the online service homepage; he/she
can view top menus: login, register,services, about, home, and help. Customer
clicks on categories or subcategories to detail information of services. Also
customer can search services. When customer logins successful, he/she manage
place orders and manage account information.

20
3.1.2.2. Flow of Customer Diagram

Process diagram of customer searches, account

21
Above diagram describes the whole process of customer searching services and
purchasing service. There are main functions are customer login, register, search ,
require & provide services.
1. Customer chooses or searches required services .
2. Customer must be registered at first. Only after customer logins the online
services system, he/she can place orders.

3.2. Use Cases

3.2.1 Common Function

 Login
Every time user logins the customer or administrator application, he/she must
input both of the correct account ID and the password into the input-form. The
application will get the input data and send to the System Server, and the server
will communicate with the Database and check whether the account ID and
password are matched. If it is correct, the application will display the Welcome-
Window, and then switch to the Member Information Interface. Otherwise, the
Error-window will be instead. After that, the application will turn back to the login
interface.
 Logout
This functionality works when the user selects the “Logout” menu, the application
will be closed and return back homepage.

22
3.2.2. Customer Functions

 Register
Firstly, new customers need to register to get one account ID. Information which
should be included: customer name, password, email address, phone number and
address information. After registration, customers will get an account ID and they
can login with account ID and password. The application will insert all the
information into the corresponding database tables.

23
  Choose services
Customers can choose required services from categories or subcategories.
Customers click on the service link. They can choose required services:
teacher,carpenter, electrician and so on.

 Payment way
The way to payment is cash on delivery.

 Search SERVICES
All users can use the search engine. Users input keyword in search engine, and
click on the “GO” button. The system will search services from the relational
information in database. If there are matched existing services, the results will be
listed on search page. Or else the search page will display no matched services.

 Recommendation
According to customers choose required service, the system searches related
information, then more services are referenced, like dance teacher, cooking
teacher and so on.

24
3.2.3. Administration Functions

 Add/delete/modify/view accounts
On the account page of administration, the administrators can directly add or
delete or modify or the customers’ accounts. It includes customer’s private
information as his password, address and so on. Also administration can view all
accounts list.

Handle order
Administrators login the handle order website, they browse all customers’ orders.
There are “detail and delete” buttons after every ordering. After the
administrators click on specific customer’s “detail” button, they can view the
specific customer’s orders information. Also, administrators delete specific
customer order.
.

25
E-R DIAGRAM FOR ONLINE BOOK STORE:

Feasibility Study:

26
Technical Feasibility

The Online services is feasible technically, although there is some risk.

 The Marketing Department has little experience with Internet-based

marketing and sales.
 The IT Department has strong knowledge of the company’s existing order
systems; however, it has not worked with Web-enabled order systems.
 Hundreds of retailers that have Internet Order applications exist in the
marketplace.
 The IT Department has relied on external consultants and an Internet
Service Provider to develop its existing Web environment.
 The IT Department has gradually learned about Web systems by
maintaining the current Web site.
 Development tools and products for commercial Web application
development are available in the marketplace, although the IT department
has little experience with them.

Economic Feasibility
A cost–benefit analysis was performed; see attached spreadsheet for details. A
conservative approach shows that the Internet Order System has a Good chance
of adding to the bottom line of the company significantly.
ROI over 3 years is: 10.1%

Intangible Costs and Benefits:

27
 Improved customer satisfaction
 Greater brand recognition

Organizational Feasibility:
From an organizational perspective, this project has low risk. The objective of the
system, which is to increase sales, is aligned well with the senior Management’s
goal of increasing sales for the company. The move to the Internet also aligns with
Marketing’s goal to become savvier in Internet Marketing and sales.

REQUIREMENT ANALYSIS:

 The goal of analysis is to discover problems, incompleteness and

inconsistencies in the elicited requirement

 These are then fed back to the stakeholders to resolve them through the
negotiation process

 Analysis is interleaved with elicitation as problems are discovered when the

requirements are elicited

Requirements Analysis Methods: Object oriented analysis for our online services:

28
 It is a single paradigm

 Facilitates architectural and code reuse

 Models more closely reflect the real world

 Stability

 Increasing productivity

 Decreasing analysis activity

 Decreasing Complexity in Design

 Easier review and verification by customer

 Increasing reusability

 Most of the expenses of a software is related to maintenance

 OOA decreases maintenance expenses though it may be more

expensive in implementation and design phases

29
Overall according to the online services system functional requirements, the
system falls into the front management application and back-stage management
application. The front management application is the user visits online services
website and register user is customer. Only customer manages his/her account
and shopping cart. So in this part, specific functions are described as below:

 Login and logout.

 Register
 Services
 Payment methods
 Update account information.
 Recommendation
 Forget password

The back-stage management application is staffs manage the system. Manager’s

responsibilities are management of services; administrator’s responsibilities are
order management and customer’s management. So in the staff part, specific
functions are described as below:
 Login and logout
 Add/delete/modify account
 Manager manage services

30
Validation and verification:

A strategy for software testing integrates software test case design methods into
a well planned series of steps that result in the successful constructions of
website. An important website/software testing strategy provides a road map.
Testing is set of activities that can be planned in advanced and conducted
systematically.

VALIDATION:

At the culmination of integration testing, software is completely assembled as a

package. Interfacing errors have been uncovered and corrected and a final series
of software test-validation testing may begin.

31
VERIFICATION:
To ensure that our website/software is verifiable or not by the client’s
requirement.

Test Plan:

 Introduction: The goal of this document is to develop a test plan

for the Online services design system. This document defines all the
procedures and activities required to prepare for testing of the
functionalities of the system which are specified in Vision document.
The objectives of the test plan are to define the activities to perform
testing, define the test deliverables documents and to identify the
various risks and contingencies involved in testing.
 Features To Be Tested: The following list describes the features
to be tested:
USER:

 Registration

 Login

ADMIN:

 Create and Delete services from Category

 Create and Delete a subcategory
 Manage Orders
 Manage Members

32
Test Cases:

User:

ID TEST CASE USER INPUT PASS CRITERIA

U_REG_1 User Registration User selects Display message
already existing to choose
user name different user
name
U_REG_2 User Registration User enters Display message
different that Password
password in and Confirm
password Password fields
confirm field don't match
U_REG_3 User Registration User forgets to Display message
enter a particular The value in field
required fields is required
U_REG_4 User Registration User enters all User account
the details created
successfully

Login:

ID TEST CASE USER INPUT PASS CRITERIA

U_LOG_1 User Login User enters a Display message
wrong username Login or
Password is
incorrect.
U_LOG_2 User Login User enters a Display message
wrong password Login or
Password is
incorrect.
U_LOG_3 User Login User enters User logs in
correct username successfully
and password
33
ADMIN:
Create and Delete a service from Category

ID TEST CASE ADMIN INPUT PASS CRITERIA

AD_CDB_1 Create and Admin adds a Services should
Delete a services new service to be updated in
from Category category Categories list
AD_CDB_2 Create and Admin deletes a service should be
Delete a service service from deleted in
from Category category Categories list

Create and Delete a Subcategory

ID TEST CASE ADMIN INPUT PASS CRITERIA

AD_CDC_1 Create and Admin adds a Category should
Delete a Category new category be updated to
system
AD_CDC_1 Create and Admin deletes a Category should
Delete a Category category be deleted from
system

Manage Orders:

ID TEST CASE ADMIN INPUT PASS CRITERIA

AD_MO_1 Manage Orders Admin accepts an Order is
order processed
AD_MO_2 Manage Orders Admin deletes an Order is not
order processed

34
Manage Members:
ID TEST CASE ADMIN INPUT PASS CRITERIA
AD_MM_1 Manage Admin accepts Member is
Members Members accepted
AD_MM_2 Manage Admin deletes Member is not
Members Members accepted

Approach:
This section describes the overall approach of the testing which ensures that the
each feature and the combination of the features are adequately tested. The
major tasks that are used are

 Unit Testing: Unit testing is a method of testing that verifies the

individual units of source code are working properly. The goal of unit
testing is to isolate each part of the program and show that the individual
parts are correct. The NUnit a testing tool for C#, will be used for unit
testing.

 Load testing: Load testing is the process of creating demand on a system

or device and measuring its response. It generally refers to the practice of
modeling the expected usage of a software program by simulating multiple
users accessing the program concurrently. As such, this testing is most
relevant for multi-user systems; often one built using a client/server model,
such as web servers.

 System Testing: Once the entire system has been built then it has to be
tested against the Software Requirement Specification and System
Specification to check if it delivers the features required. System testing can
involve a number of specialist types of test to see if all the functional and
non-functional requirements have been met.

35
 Performance Testing: The system should meet the performance
requirements as mentioned in the Vision document. The performance will
be evaluated based on the response time of the GUI and the database
commands. Using JMETER tool performance testing will be done.

 Manual Testing: Manual Testing will be done to ensure the correctness

of various parts of the code using test cases generated by the tester.

 Pass/fail criteria: The system should satisfy all the functional

requirements, in the Vision document. Each feature to be tested will be
evaluated against its requirement as stated in the Vision Document. The
pass or fail of a test depends on whether the system meets with all the
particular post conditions. Test cases executed on the Online services will
pass if they meet the specific requirements as mentioned in the Vision
Document.

 Suspension Criteria And Resumption Requirements:

 Suspension criteria: If the system contains one or more critical

defects like the defects in the GUI editor which provides the editing
features for one line diagrams and database locking, unlocking and
sharing features which provides the environment for multiple users
to work in parallel, the entire system should be suspended. The
testing may also be suspended if the hardware and software
components required are not available on time. The failed test cases
should be recorded along with the description for failure.

 Resumption requirements: When a new version of the system is

transmitted to the test group after a suspension of testing has
occurred, all previous tests will be rerun to ensure program changes
have not inadvertently affected other portions of the program.

36
  TEST DELIVERABLES

The following documents are the available test deliverables:-

 Test plan
 Test case specifications
 Test input and output data
 Test procedure specifications
 Test logs

FUTURE SCOPE:
37
  The project is just a prototype and has immense areas of
development. The areas of development are as follows:

 Provide the services to all the users on demand.

 Provide the part time job for literate, illiterate and students
also.
 Provide the job for the all age people whether young age(above
18) and old age people.

BIBLOGRAPHY

 www.google.com
 www.tutorialspoint.com

38