1

NAME:

Roll No:

Project Topic: GIFT.COM

Under Guidance:
 2

GIFT.COM
Team Member:

Background:

The main objective is to develop the software that covers all the aspects related with
gift shop ranging from the suggestion to helping in selection of the gift. Now a days there are
huge number of applications for gift shop automation however none of them are helping their
customer to make selection of the gift for a particular occasion. They only have filter for
selection of price or category and then customer has to select gift without any assistance. Her in
my web-application I let my customer to either select the gift by their own or assist them to make
proper selection. Here they can also place the order for customize gift.

Gift.com is a web-based software which not only allows the user to select the gift but also assist the
customer to book the normal as well as customized gift from any part of the world.

GIFT web application is developed with the intention of helping the customer in selection of the
gift in both cost efficient and time-saving way. This application let the user to book the gift for
any occasion, customize the gift, suggest the gift and so on.

Objectives:

• Product and component based

• Creating & changing issues at ease
• Query issue list to any depth.
• Reporting & charting in more comprehensive way
• User account to control the access and maintain security.
• Simple GUI
• Multi-level priorities & severities.
• Online Help Desk
• Well-designed reports.
• Accuracy in work.
• Fast Speed Server Engine
• Secure Server
 3

Purpose:

The “Gift.com” has been developed to help the customer to select proper gift for special occasion
by providing the suggestion and assistance instead of just displaying list of items from where user
can make selection. This software is supported to eliminate and, in some cases, reduce the hardship
faced by this existing system.
The application is reduced as much as possible to prevent errors while gathering the
data. It also provides error message while elicitation of invalid data. No formal knowledge is
needed for the user to use this system.

Scope:

This application provides three types of access on the data one for Client, one for Advisor and
other for the admin. Users are able to see the details of advisor, their history and so on. They can
refer advisor to get the advice, they can lodge complaint and so on. User can give the ratings to
the advisor based on the quality of the services they provided to the user.

Advisor can update his details, view referral, and cancel the referral. Advisor can also rate the
user’s based upon their behavior with the advisor.

Admin is capable of adding new advisor, view all request and cancellation report, take the action
on complaint lodge by the user and so on.

To develop Gift.com prototype model is used as this model let the developers to develop the project
even entire requirement is not known at the very beginning. I had used this model as it let me
create the working model of this project while I still gathering the data.
 4

Applicability:

Direct Application

1. It allows the user to view history of all advisor

2. It provides online platform from where user can book gift
3. Interface is provided to user to rate gift as well advisor
4. Interface for lodging the complaint
5. Report on users
6. Reports on gift

Achievement

1. It also allows me to improve my knowledge in designing

2. It let me explore various technologies like ADO.NET, CSS, HTML5
 5

Survey of Technology
To create the Gift shop there is need of technology related to server-side scripting, client-side
scripting, designing tool and HTML5.

HTML5

HTML5 is needed in my project to design my web pages with ease. It has several advance tag that
makes the life of developer easier. HTML5 is supported by all the browser over all the platform
so it is the best and only technology that helps me to design my web pages with ease.

Server-side Scripting

To process the data submitted by the user on server we need to have server-side program. To write
the server side program we can use Servlet, JSP , ASP.NET, PHP and so on.

Servlet

Servlet is JAVA program which is store on the server machine to process the user request. Servlet
allows us to write the code and embed the HTML inside the code. It optimizes the resource
consumption, memory management and IO management. However, sometime it become very
difficult and complex. It uses the server like glassfish, apache tom-cat and so on.

JSP

JSP is another technology from JAVA to perform the server -side scripting. Unlike the Servlet
where HTML contains the java code in jsp java code contains the HTML. With JSTL and EL
server-side scripting become easier in JSP. It uses the server like glassfish, apache tom-cat and so
on.

PHP

It is an open source technology which is used as server-side scripting. PHP5 supports the OOPS
concept. It makes the use of server like XAMP AND WAMP.
 6

ASP.NET

ASP.NET is the server-side technology developed by the MICROSOFT. ASP.NET uses the
language like C#, VB.NET, F# and many more but C# is the primary language for .NET platform.
Internet Information Service i.e. IIS server is used by the ASP.NET

CSS3

CSS3 is used for controlling the look and feel of the web page. It allows us to define the style
information once and then reuse as many times as we want. It also helps us to reduce the
maintenance time as we are required to make change at one place and change get reflected
automatically throughout the web application.

JQUERY

To give some effect on the webpage I will use JQUERY. It is library of complied java script code
that let us design the complex web page very easily.

ADO.NET

To make the connectivity between the database and asp.net web pages we are using the ado.net
technology. This technology allows us to connect with SQLSERVER, ORACLE, ACCESS and
many other databases. It is capable of working in connected and disconnected mode.

JDBCJDBC i.e. java database connectivity is used to connect the servlet or jsp with the database
such as ORACLE, MYSQL, ACCESS and many more. However, it works only in connected
mode,

I will use the ASP.NET with C# to develop my project and will use SQLSERVER as my backend
technology. I have selected ASP.NET with C# because at current it is the only technology that
support the language interoperability and due to the development of .net core now .net is also going
to be platform independent in future. So I have selected ASP.NET as my server side scripting
technology and for backend I used SQLSERVER simply because it is already implemented in the
visual studio IDE for supporting asp.net application and it is default backend of asp.net
 7

Problem Definition
• Assistance and suggestion in selection of gift for special occasion online
• Difficulties in getting information on timely manner
• No proper management of member
• System is not transparent

HARDWARE & SOFTWARE REQUIREMENT

HARDWARE

• Processor: Core 2 Duo or above

• Processor Speed: 2.00 Ghz
• RAM: 4.00 GB
• Hard Disk: 80 GB or above

SOFTWARE (S)
• Operating System: Windows
• Microsoft Visual Studio Ultimate 2010
PROGRAMMING & PRESENTATION TECHNOLOGY
• C#
• ASP.NET
• ADO.NET
 8

Requirement Specification
To understand the data requirement of the system we have used the following technique
1. Survey
Survey has been conducted to get the answer of following question.
a. Need of assistance while planning for gift?
b. How much they can pay for assistance?
c. What should be done to improve the services?
d. Is assistance charge fixed or variable?

2. Brainstorming
Brainstorming has been conducted to obtain the accurate information from the users
of the application as well as form the helpers.
 9

Gantt Chart:
 10

Modules

1. Booking
a. It allows the clients to book gift
b. It allows buddy to view booking
c. It allows the admin to view all booking

2. Cancellation
a. Client can cancel the booking
b. Advisor can cancel the booking
c. Admin views the cancellation report

3. Rating
a. Admin can view the ratings of all clients and all buddies
b. Advisor can rate the clients
c. Client can rate the advisor

4. Complaint
a. Advisor can lodge the complaint against clients
b. Clients can lodge the complaint against advisor
c. Admin resolve the complaint by taking decision

5. Security
a. User and admin can change their password
b. Password recovery is possible
 11

EVENT TABLE

Event Trigger Source Use Case Response Destinati

on
User click on Register User Register the user Registration User
Submit Button in Request Successful
Registration Form
User log in with Login Request User User login Login Successful. User
valid Email Id & Show user profile
Password page
User log in with Login Request User User login Login User
invalid Email Id & Unsuccessful.
Password Show error
message.
User clicks on Logout Request User User Logout Successfully User
Logout button Logout
User clicks on Book Request User Book Gift book Page User
book Gift

Admin Update or Gift Request Admin Update / Delete Successfully Admin

delete Gift data updated data
User makes Book Payment User Process the Payment Admin
payment for payment Successful
Booking
User receives the Report Admin Process the bill Generate the bill User
bill or receipt of Generation and print it
the payment
User send a data Contact Request User Send the data Data will be User
through contact submitted and
page thanks giving
message will
appear
 12

Use Cases:
 13

E-R DIAGRAM:
 14

Class Diagram:
 15

Activity Diagram:
 16

Sequence Diagram

DEPLOYMENT Diagram:
 17

PROCEDURAL DESIGN

Pages Description

MasterPage.Master Master page of the website which will provide a consistent look
throughout the website.

Default.aspx Main page of the website which will contain a slider, main content and
some quick links.

registrationClient.aspx Registration page for new users from where they can enroll with travel
agency

login.aspx Login page for existing users of travel agency

contact.aspx Contact page from which a user can ask any query to the representative
of the customer support section.

about.aspx About page will give most of the useful information about our agency as
well as our complete address.

admin.aspx This is a page from where Admin can see the information about Clients,
booking and Payments. Admin will have privileges to insert, update and
delete client data. Access to this page is restricted for other users.
 18

TABLE LIST:
Admin_Master

Column Name Data Type Allow Nulls

UserName nvarchar(50) Checked
Password nvarchar(50) Checked
Question nvarchar(50) Checked
Answer nvarchar(50) Checked
Email nvarchar(50) Checked

Booking_Master

Column Name Data Type Allow Nulls

GiftID nvarchar(50) Checked
BookingID nvarchar(50) Checked
BookingDate nvarchar(50) Checked
BookingTime nvarchar(50) Checked
BookingBy nvarchar(50) Checked
Completed nvarchar(10) Checked

Booking_Purpose

Column Name Data Type Allow Nulls

BookingID cc Checked
Purpose nvarchar(150) Checked
Address nvarchar(500) Checked

Client_Master

Column Name Data Type Allow Nulls

ID nvarchar(50) Checked
Name nvarchar(50) Checked
Address nvarchar(250) Checked
Gender nvarchar(50) Checked
Contact nvarchar(50) Checked
Email nvarchar(250) Checked
Ocupation nvarchar(50) Checked
 19

Username nvarchar(50) Checked

Password nvarchar(50) Checked
SQ nvarchar(250) Checked
Answer nvarchar(50) Checked

Complaint_Master

Column Name Data Type Allow Nulls

cid nvarchar(50) Checked
Cby nvarchar(50) Checked
Complaint nvarchar(500) Checked
Cof nvarchar(50) Checked
Action nvarchar(500) Checked

Feed_Master

Column Name Data Type Allow Nulls

FeedID nvarchar(50) Checked
FeedBackBy nvarchar(50) Checked
FeedBack nvarchar(MAX) Checked
Date nvarchar(50) Checked

LogIn_Detail

Column Name Data Type Allow Nulls

ID nvarchar(50) Checked
LogInDate nvarchar(500) Checked
LogInTime nvarchar(500) Checked
IP nvarchar(MAX) Checked

Ratings_Master
 20

Column Name Data Type Allow Nulls

BookingID nvarchar(50) Checked
RatingFor nvarchar(150) Checked
RatingOf nvarchar(50) Checked
Ratings numeric(18, 0) Checked
Date nvarchar(50) Checked

Advisor_Master

Column Name Data Type Allow Nulls

ID nvarchar(50) Checked
Name nvarchar(50) Checked
Address nvarchar(500) Checked
Experience nvarchar(50) Checked
Gender nvarchar(50) Checked
Qualification nvarchar(50) Checked
Photo nvarchar(MAX) Checked
Email nvarchar(250) Checked
Contact nvarchar(50) Checked
21
 22

SYSTEM TESTING
TEST CASE DESIGN:

Scenario ID Scenarios Test Case Test Case description

ID
SC_OSS_01 Login TC_OSS_01 To check the user input valid User
Page name and Password
To check the validation for the User
name input string
To check the validation for the
Password input string

SC_OSS_02 Password TC_OSS_02 To check the user input valid User

recovery name and Password
To check the validation for user name
To check the validation for security
question
To check the validation for security
answer
To check the validation of reset button
To check the validation for submit
button

SC_OSS_03 Apply for TC_OSS_03 To check the validation for applicant

job name
To check the validation for Email
To check the validation for proper
email password
To check the validation for contact
number
To check the validation for auto
Applicant ID
To check the validation for auto
system date
To check the validation for upload CV
To check the validation for postback of
selectCode dropDown box
To check the validation for submit
button and cancel button
 23

SC_OSS_04 Buddy TC_OSS_04 To check the validation of buddy name

To check the validation of contact
number
To check the validation of Email ID
To check the validation of address
To check the validation of User name
To check the validation of password
field
To check the validation of save and
cancel button
SC_OSS_05 change TC_OSS_05 To check the validation of enter
password password
To check the validation of new
password
To check the validation of re-enter
password
To check the validation of change
button
 24

TESTING STRATEGIES:

Critical success factors:

• End-to-End business functionality
o The objective of E2E is to look at the state of the system as well as its behavior.
The End-to-End cases would be tested to ensure the business functionality is
working as expected.
o The steps to be vehicleried out would be checking the functional check-point across
all the modules and interfaces

• Navigation
o Navigation testing is to test whether the availability levels of various options and
features in the software are at the acceptable navigation depth levels or not. Test
team to ensure that navigation across all should be based on access rights to users.

• Links
o The Goal is to test each and every link that forms part of the design once the initial
code is developed. All the link and re-direction links will be covered as part of this
functionality.

• Performance
o It is done to determine how a system performs in terms of responsiveness and
stability under a particular workload. The overall performance of the website
should be at acceptable level.

• Integration between modules

o Individual software modules are combined and tested as a group. Test cases are
constructed to test that all components within interfaces interact correctly.

• Data Integrity
o Assuring that the accuracy and consistency of data within the application and
throughout all the interfaces. The details of one particular user once entered in the
system should be correct for the other modules. User rights will also be considered
to access a particular link/Data/Web page
 25

System Integration Testing (End To End Testing):

• Our Role: Tester
o As a tester, we would be involved in the overall testing cycle to cover the Business
scenario cases and its functionality for across the modules.

SIT approach:

• Initially will understand the user stories and get an update from Business Analyst team
about their priorities.
• Once all the inputs are finalized, we will try to understand the complete End-to-End
functionalities from Business process point of view. We will then come up with End-to-
End Test scenarios, which will encompass all Systems and all Modules. Then we will get
this reviewed from Business Analyst. Once we have the signed off test scenario suit, we
will start preparation of detailed Test Cases. While preparing the detailed Test Cases, the
approach would be Top-Down approach.
• As mentioned above, initially we will prepare End-to-End business scenarios, which will
then split into sub-scenarios and again into system/Application level Test Cases. After
completion of Test Cases, will get them reviewed and signed off from Business Analyst.
• In Contrast, while executing these scenarios we will have a Bottom-Up approach along
with Risk based approach. So as per the priority (Critical to Low) we will get a sprint for
particular User Story. We will try to execute the test cases, then sub-scenarios and then
End-to-End scenarios respectively.
• So we will be testing a sprint at a time which is High Priority, so conceptually we will be
using Hybrid approach which is a combination of Time-boxed and Risk based testing
approach.

• Entry Criteria:
• Before Test Items are made available for the Test Team to test it’s expected that:

• All test tools are available and test infrastructure are available for use during testing such
as the User story list, Testing environment (Staging) and relevant documents.
• We will start SIT only when given module/User Story is completely developed and unit
tested and there are no Unit test defects.
• Access to Youtrack for Defect management is required.
• The correct versions of the code have been deployed to the correct test environments.
• Test Data should be provided before testing.
 26

Exit Criteria:
• For the Test Items to exit testing the following conditions will have to be met:

• All the assigned high priority User stories will be tested.

• The Test Summary/Defect log Report will be completed.
• All planned testing activities have been completed to agreed levels.
• All high priority bugs have been fixed, retested and passed.
• Low priority bugs can be allowed max of 5-10% of the entire testing.
• Any outstanding defects or deviations must have been accepted by the Business,
Operations and Technology organizations.
• Sign-off by Testing management

User Accepatance Testing:

o Our Role: Support (We are not repsonsible to vehiclery the UAT testing)
• Tester would provide support to the end user in terns of application navigation,
walkthrough if required.
• Support would be given if any Re-testing is required.

Performance Testing:
• It is done to determine how a system performs in terms of responsiveness and stability
under a particular workload. The overall performance of the website should be at
acceptable level.
• We recommend performance testing should be done, However as discussed with all
stakeholders, it is Out Of Scope.

Regression Testing.:
• Regression testing is to determine whether a change in one part of the application affects
other parts of the software or not.
• In this release, we will not be doing regression testing as it is 1st phase. However, we will
be doing it from next phase and we will use the current SIT test cases/Scenarios as a
baseline for Regression suit.

Automation Testing:.
• We would perform this testing using Regression suit in Phase 2 as a baseline and prior to
it we would be doing proof-of concept to decide the exact tool for automation
 27

User Interface Diagram:

Element Description

Registration id The Id of the current user

Enter Name User will enter his/her name.

Enter User will enter his/her contact number which must be a valid number
Contact Number as RAA will use this number for further enquiries.

Enter Address User will enter his/her full address.

Enter Email Address User will enter his/her current email Address. User will get an email
after successful registration.

Enter username The Login name of ther user to login for booking

Enter Password Password must be at least 8 characters, which can be a string or

numbers but space is not allowed.

Re-enter Password User must retype the exact same password.

Submit For submission of a form.

 28

Coding Conventions

ASP.NET Control Abbreviation

Standard Controls
Button Btn
CheckBox Cbx
DropDownList Ddl
Image Img
Label Lbl
ListBox Lsb
RadioButton Rb
Table tbl
TextBox Txt
Validation Controls
CompareValidator Cv
CustomValidator Cv
RangeValidator Rv
RegularExpressionValidator Rev
RequiredFieldValidator Rfv
ValidationSummary Vs
 29

CONCLUSION AND FUTURE SCOPE

Conclusion

Future Enhancement