Location-Based Services Search Engine
Uploaded by
Prashanth KumarLocation-Based Services Search Engine
Uploaded by
Prashanth KumarLocation Based Services Search
Engine
Term: Winter 2015
Course: Object Oriented Analysis and Design
Project Title: Location Based Services Search Engine
Project Team:
Priyanka Katipally
Vikas Nagavelli
Prashanth Kumar Vuthuru
Professor:
Liberty Page
Introduction:
Objective:
To provide a bridging platform between users and service providers.
Unlike other existing search services which are like a directory. This
website allows the businesses to showcase their services with their
rich multimedia content (logos, photographs, and videos) and
provides an opportunity to customize their pages.
Having this rich content and multimedia information of various
related services the users can make a best decision with their
preferences.
Description:
A location based search service that provides the users with the list
of service providers providing them an ability to search with the
related keywords, service category and location details.
1. Facilitates Service providers to create and manage their service
pages with details of the business services they provide. The
service pages can be customized with service description,
address, location maps, contact information, pricing and other
related information.
2. Users can search for the service providers by the keywords and
the location details.
Advantages:
Simplifies the job of users by providing the relevant responses and
helps them to make a purchase decision by viewing at list of all the
related responses on a single platform.
Provides the service providers an opportunity to expand their
business visibility and there by generating qualified leads.
Project Plan:
Project Time lines
Begin Date: 14 January 2015
Target End Date: 15 March 2015
Final Release Date: 20 March 2015
Phase I Core business and high risk items
Completion Date: 23 February 2015
Phase II High priority items and completion of core business
Completion Date: 23 March 2015
Project Scope
The scope of this project includes creating a fully functioning web
application that provide users a searchable interface to find the
details of the services and businesses by location they are
interested and service providers an interface to create and manage
service pages.
The project doesn't include payment of the bills and other monetary
transactions. It is confined to providing of details of businesses and
services to the users.
Use Cases
Below is the list of the identified use cases for the project
1. User Searching for a service by Location
2. User Viewing a Service Page
3. User Adding service page to favorites list
4. User Providing Rating and Comments to the Service Pages
5. User Registration
6. User Login
7. User Logout
8. User Profile Creation
9. User Profile Update
10. Service Provider Registration
11. Service Provider Login
12. Service Provider Logout
13. Service Provider Profile Creation
14. Service Provider Profile Update
15. Create a Service Page
16. Customize a Service Page
17. Creating Service Categories
18. Creating Service Sub Categories
19. Admin Registration
20. Admin login
21. Admin logout
22. Admin Profile creation
23. Admin Profile update
24. Admin Manage Users ( Create , Update , Remove )
25. Admin Service Providers ( Create , Update , Remove )
Actors:
In this project there are three actors.
A) User :
Users can search for the service providers by the keywords and the
location details.
Users can create and rate the services.
User can select the favorite services.
B) Service Provider :
Service Providers can add the details about their services in
service pages.
The service pages can be customized with service description,
address, location
maps, contact information, pricing and other
related information.
C) Admin :
Admin can manage the total system.
Admin can create and modify the users and service providers.
Admin can remove the service pages.
High Risk Use Cases
Below is the list of the high risk use cases.
The details of each use case are provided separately for each case.
1. User Searching for a service by Location
Description: This use case details the functionality that enables
user to search the services based on the location and keywords.
User will be displayed with a list of results.
2. User Viewing a Service Page
Description: By clicking on the search results users will be
directed to the service page which contains the details and
content of that particular service.
Service page contains description, pricing, address, rating,
timings, images, videos and other related information.
3. User Registration
Description: This use case is about the registration process for
user. User is required to provide the required details (User Name,
Password, and Email) for registration. These credentials are useful
for the login functionality.
4. User Login
Description: After a successful registration the user can login in
the application using the credentials. The user login is not pre
condition to perform a services search operation. It is required in
order to make a favorites list and provide rating for the services.
5. User Logout
Description: User can logout from the application. It provides
privacy and security for the user.
6. Service Provider Registration
Description: This use case is about the registration process for
Service Provider. The Service Provider is required to provide the
required details (User Name, Password, and Email) for
registration. These credentials are useful for the Service Provider
login functionality. A registered of Service Provider is a mandatory
constraint for creation of service pages.
7. Service Provider Login
Description: After a successful registration the Service Provider
can login in to the application using the credentials. The Service
Provider login is pre condition to in order to create service pages
and profile management functionalities.
.
8. Service Provider Logout
Description: Service Provider can logout from the application. It
provides privacy and security for the Service Provider.
9. Create a Service Page
Description: This use case deals with the functionality of creation
of the service pages by the service providers.
Service Provider need to provide service page title, select
category, select sub category the service belongs while creating
the service page.
10. Customize a Service Page
Description: Service providers provide the description, pricing,
address, rating, timings, images, videos and other related
information. This use case provides the ability to provide the
business and service related information and to customize the
service according to their model.
11. Creating Service Categories
Description: The services fall under categories. Categories come
in to picture at the application level. It provides the grouping of
the services. Easies the search action of the user.
Admin creates the service categories, admin need to provide
category name, description and image to create a category.
12. Creating Service Sub Categories
Description: Sub Categories are further division of the categories.
They give detail picture of category the service page falls under.
Each service category contains the sub categories.
Admin creates the sub categories, admin need to pick the parent
service category, provide sub category name and description to
create a sub category.
High Level Use Cases
1. User Adding service page to favorite list
Description: This use case is about the functionality to select the
favorite services and mark them for future reference.
This option will be available in every service page.
2. User Providing Rating and Comments to the Service
Pages
Description: This use case is about the functionality to provide
the rating to the service pages.
This option will be available in every service page.
3. User Profile Creation
Description: After user registers and logs in , he/she will be
provided ability to create profile on first time login.
Can provide details like name, gender, contact email, image ,
phone number.
4. User Profile Update
Description: This use case deals with functionality to update the
users profile.
Can update details like name, gender, contact email, image ,
phone number.
5. Service Provider Profile Creation
Description: After Service Provider registers and logs in , he/she
will be provided ability to create profile on first time login.
Can provide details like name, gender, contact email, image ,
phone number, address.
6. Service Provider Profile Update
Description: This use case deals with functionality to update the
users profile.
Can update details like name, gender, contact email, image ,
phone number, address.
7. Admin Registration
Description: This use case is about the registration process for
Admin. Admin is required to provide the required details (User
Name, Password, and Email) for registration. These credentials
are useful for the login functionality.
8. Admin Login
Description: After a successful registration the Admin can login in
the application using the credentials. The Admin login is pre
condition to perform admin operations. After login admin can
perform users and Service providers management functionalities.
9. Admin Logout
Description: Admin can logout from the application. It provides
privacy and security for the Admin.
10. Admin Profile creation
Description: After Service Provider registers and logs in , he/she
will be provided ability to create profile on first time login.
Can provide details like name, gender, contact email, image ,
phone number.
11. Admin Profile update
Description: This use case deals with functionality to update the
users profile.
Can update details like name, gender, contact email, image ,
phone number.
12. Admin Manage Users ( Create , Update , Remove )
Description: This functionality deals with Admin managing the
Service Providers. Admin will be provided with options to create,
update , remove and restrict users.
13. Admin Service Providers ( Create , Update , Remove )
Description: This functionality deals with Admin managing the
Service Providers. Admin will be provided with options to create,
update , remove and restrict service providers.
Non-Functional Requirements
Hardware Requirements
Processor: Dual core processor
Memory: At least 4GB of RAM
Hard Disk: 320 GB
Software Requirements
Application Sever: IIS 8.5 (Internet Information Services)
Database Server: Microsoft Sql Server 2012
Web Technology: .net framework 4.5
Performance Requirements
Hosting Server: 99% availability
Database Server: 99% availability
Supportability Requirements
W3C Best Practices for Authoring HTML
Coding Practices for C#.NET and SQL throughout the Project
(Naming conventions and Commenting conventions)
Security Requirements
Firewall in development and production environments
Anti Virus in development and production environments
Use Cases:
Use
Primary
Case
Actor
ID
UC1
UC2
Use Case Name
Use Case type
User
User searching for a
High Risk
User
service by Location
User Viewing a Service
High Risk
Page
UC3
UC4
User
Service
User Login
High Risk
High Risk
UC5
UC6
Provider
User
Service
User Logout
Service Provider
High Risk
High Risk
UC7
Provider
Service
registration
Service Provider Login
High Risk
UC8
Provider
Service
Service Provider Logout
High Risk
UC9
Provider
Service
Create a Service Page
High Risk
UC10
Provider
Service
Customizing the Service
High Risk
UC11
Provider
Service
Page
Creating Service
High Risk
UC12
Provider
Service
Categories
Creating Sub Categories
High Risk
UC13
Provider
User
User Adding service page
High Level
User
to favorite list
User Providing Rating and High Level
UC14
User Registration
Comments to the Service
Pages
UC15
UC16
UC17
User
User
Service
User Profile Creation
User Profile Update
Service Provider Profile
High Level
High Level
High Level
UC18
Provider
Service
Creation
Service Provider Profile
High Level
UC19
UC20
UC21
UC22
UC23
UC24
Provider
Admin
Admin
Admin
Admin
Admin
Admin
Update
Admin Registration
Admin login
Admin logout
Admin Profile creation
Admin Profile update
Admin Manage Users
High
High
High
High
High
High
Level
Level
Level
Level
Level
Level
( Create , Update ,
UC25
Admin
Remove )
Admin Service Providers ( High Level
Create , Update , Remove
)
Use Case: UC1 User searching for
a service by Location
Use Case diagram
Select location
Search by keywords
View the Service pages
User
Select or manage favorite pages
Use Case
UC1
ID:
Use Case
User searching for a service by Location
Name:
Created
VikasNagavelli
Last
By:
Updated
Date
By:
Last
1/20/2015
Created:
Revision
Date:
Actors:
User
VikasNagavelli
1/20/2015
Server
Description:
User can select location and search the services
Trigger:
by providing keywords.
User first selects the location and then provides
Preconditions:
Postconditions
keywords.
User should provide valid location and keywords.
User gets the required details if input location
:
Normal Flow:
and keywords are valid.
1.User select the location
2.Search the services by providing the keywords
3.View the services
Alternative
4. Select or manage the favorite pages.
NA.
Flows:
Exceptions:
Invalid keywords
Includes:
Page load errors
User selects the location and Search the services
by providing the keywords in order to get the
Frequency of
services.
On demand of user.
Use:
Special
NA.
Requirements:
Assumptions:
User should have minimum knowledge about
locations and
Notes and
Issues:
Services related keywords.
NA.
Use Case: UC2 User Viewing a
Service Page
Use Case diagram
Clicks the service page
Link from search list
User
Server
Use Case
UC2
ID:
Use Case
User Viewing a Service Page
Name:
Created
VikasNagavelli
Last
By:
Updated
Date
By:
Last
1/20/2015
Created:
VikasNagavelli
1/20/2015
Revision
Date:
Actors:
Description:
User
User can clicks the service page link from search
list.
Trigger:
Preconditions:
User first selects the service page link.
The service page displayed on the successful
Postconditions
event.
User gets required service page details if input
:
Normal Flow:
information is valid.
1.User select the service page link
Alternative
2.View the services
NA.
Flows:
Exceptions:
Page not found.
Page load errors.
Includes:
Frequency of
Network errors.
NA.
On demand of user.
Use:
Special
NA.
Requirements:
Assumptions:
User should have minimum knowledge about
Notes and
Services and usage of browser.
NA.
Issues:
Use Case: UC3 User Registration
Use Case diagram
Enter Username
Enter Password
Enter Email Address
User
Click on Submit Button
Server
Use Case
UC3
ID:
Use Case
User Registration
Name:
Created
Prashanth Kumar
Last
Prashanth Kumar
By:
Vuthuru
Updated
Vuthuru
1/20/2015
By:
Last
1/20/2015
Date
Created:
Revision
Date:
Actors:
Description:
User
User can provide the personal details in order to
Trigger:
create the account.
User provides personal details.
Preconditions:
User should provide valid personal details.
Postconditions
User is not a member of the website.
User account will be created if valid details are
provided.
Normal Flow:
User is a member of the website.
User provides valid contact details User Id,
password, phone number and email address.
Alternative
Then Account will be created.
NA.
Flows:
Exceptions:
Account will not be created if already the details
exist in Database.
Includes:
Account Already exists error.
User provides valid contact details User Id,
Frequency of
password, phone number and email address.
On demand of user.
Use:
Special
NA.
Requirements:
Assumptions:
Username is unique. No two users have same
Notes and
usernames.
NA.
Issues:
Use Case: UC4 User Login
Use Case diagram
Enter Username
Enter Password
Click on Submit Button
Server
User
Use Case
UC4
ID:
Use Case
User Login
Name:
Created
Prashanth Kumar
Last
Prashanth Kumar
By:
Vuthuru
Updated
Vuthuru
1/20/2015
By:
Last
1/20/2015
Date
Created:
Revision
Date:
Actors:
Description:
User
The user logs in to authenticate his or her role in
the system and to perform a task in the system.
The system determines that the password is
incorrect for the username entered.
1. The system prompts the user to re-enter the
password.
The system determines that the re-entered
password is
incorrect.
The system provides the option for the user to
retrieve a
Forgotten password then system determines
that the username matching a username for any
Trigger:
Preconditions:
account.
User provides login details.
User should provide valid personal details.
Post
A user account has been created for the user.
User login will be successful if valid details are
conditions:
provided.
Normal Flow:
User is a member of the website.
User provides User Id, password. Then Account
will be logged in (correct credentials).
1. The user connects to the system.
2. The user enters his/her username and
password.
3. The system validates the username and
password.
4. The system determines the users role.
5. The system displays a list of actions the
Service Provider can perform based on the role
Alternative
NA.
Flows:
Exceptions:
Incorrect Username / Password.
Includes:
Frequency of
Account Already exists error.
User provides User Id, password.
On demand of user.
Use:
Special
NA.
Requirements:
Assumptions:
Username is unique. No two users have same
Notes and
usernames.
NA.
Issues:
Use Case: UC5 User Logout
Use Case diagram
Clicks Logout Button
User
Server
Use Case
UC5
ID:
Use Case
UserLogout
Name:
Created
Prashanth Kumar
Last
Prashanth Kumar
By:
Vuthuru
Updated
Vuthuru
1/20/2015
By:
Last
1/20/2015
Date
Created:
Revision
Date:
Actors:
Description:
User
Userlogout from the System. Clear users session
Trigger:
Preconditions:
Post
data take user to the home page
User performs Logout operation.
The System is in the user-logged-in state.
User cannot access any of the site features,
conditions:
Normal Flow:
Alternative
other than login.
NA.
NA.
Flows:
Exceptions:
Session Expired.
Includes:
Frequency of
Network error.
NA.
On demand of User.
Use:
Special
NA.
Requirements:
Assumptions:
Notes and
Issues:
Valid User can perform this operation.
NA.
Use Case: UC6 Service Provider
Registration
Use Case diagram
Enter Username
Enter Password
Enter Email Address
Service
Enter Mobile number
Provider
Server
Enter Resident Address
Click on Submit Button
Use Case
UC6
ID:
Use Case
Service Provider Registration
Name:
Created
Priyanka
Last
Priyanka Katipally
By:
Date
Katipally
Updated
1/20/2015
By:
Last
Created:
1/20/2015
Revision
Actors:
Description:
Date:
Service Provider
Service Provider can provide the personal details
Trigger:
Preconditions:
in order to create the account.
Service Provider provides personal details.
Service Provider should provide valid personal
details.
Postconditions
Service Provider is not a member of the website.
Service Provider account will be created if valid
details are provided.
Normal Flow:
Service Provider is a member of the website.
Service Provider provides valid contact details
User Id, password, phone number and email
address.
Alternative
Then Account will be created.
NA.
Flows:
Exceptions:
Account will not be created if already the details
exist in Database.
Includes:
Account Already exist error.
Service Provider provides valid contact details
User Id, password, phone number and email
Frequency of
address.
On demand of Service Providers.
Use:
Special
NA.
Requirements:
Assumptions:
Service Provider is unique. No two Service
Provider have same usernames.
NA.
Notes and
Issues:
Use Case: UC7 Service Provider
Login
Use Case diagram
Enter Username
Enter Password
Click on Submit Button
Server
Service Provider
Use Case
UC7
ID:
Use Case
Service Provider Login
Name:
Created
Prashanth Kumar
Last
Prashanth Kumar
By:
Vuthuru
Updated
Vuthuru
1/20/2015
By:
Last
1/20/2015
Date
Created:
Revision
Date:
Actors:
Service Provider
Description:
The Service Provider logs in to authenticate his or
her role in the system and to perform a task in
the system.
The system determines that the password is
incorrect for the username entered.
1. The system prompts the user to re-enter the
password.
The system determines that the re-entered
password is
Incorrect.
The system provides the option for the user to
retrieve a
Forgotten password then system determines
that the username matching a username for any
account.
Trigger:
Preconditions:
Service Provider provides login details.
Service Provider should provide valid personal
details.
A Service Provider account has been created for
the user.
Post
Service Provider login will be successful if valid
conditions:
details are provided.
Normal Flow:
Service Provider is a member of the website.
Service Provider provides User Id, password. Then
Account will be logged in (correct credentials).
1. The user connects to the system.
2. The user enters his/her username and
password.
3. The system validates the username and
password.
4. The system determines the users role.
5. The system displays a list of actions the
Service Provider can perform based on the role
Alternative
NA.
Flows:
Exceptions:
Incorrect Username / Password.
Includes:
Frequency of
Account Already exists error.
Service Provider provides User Id, password.
On demand of Service Provider.
Use:
Special
NA.
Requirements:
Assumptions:
Service Provider is unique. No two users have
Notes and
same usernames.
NA.
Issues:
Use case:UC9 Create a Service
Page
Use Case Diagram
Provides Title
Selects Category
Selects Subcategory
Service Provider
Server
Clicks on create button
Use Case
UC9
ID:
Use Case
Create a Service Page
Name:
Created
Vikas Nagavelli
Last
By:
Updated
Date
By:
Last
1/20/2015
Created:
Vikas Nagavelli
1/20/2015
Revision
Description:
Date:
1. Service Provider
2. Server
Service Provider to create the Service pages by
Trigger:
selecting a category and a sub category.
Service Provider first clicks a "create service
Preconditions:
page" button.
There should be the service provider created
Actors:
and available.
And the name and category and subcategory to
Postconditions
be provided/selected.
After the successful creation of a service page.
The Service Provider should be able to view the
created service page in the services list.
In case of unsuccessful attempt the service
provider should be displayed with a message
providing the reason for it.
Normal Flow:
Service Provider should provide
1. Service Name
2. Select Category
Alternative
3. Select Subcategory
NA.
Flows:
Exceptions:
Network errors
Includes:
Frequency of
Page load errors
NA.
On demand of Service Provider.
Use:
Special
NA.
Requirements:
Assumptions:
User should have minimum knowledge about the
service name and category it belongs.
Notes and
General browser and website usage.
NA.
Issues:
Use case: UC10 Customizing the
Service Page
Use Case Diagram
Selects the service page to
be customized
Provides the description, Logo, Images,
Pricing, Timings, Address, Videos other
details
Clicks on save button
Server
Service Provider
Use Case
UC10
ID:
Use Case
Customizing the Service Page
Name:
Created
PrashanthVuthur
Last
By:
Updated
1/20/2015
By:
Last
Date
Created:
PrashanthVuthuru
1/20/2015
Revision
Description:
Date:
3. Service Provider
4. Server
Service Provider to customize the Service page
Trigger:
by providing the details of it.
Service Provider first clicks "customize" button
Preconditions:
available on the service page list.
There should be the service provider and service
Post
page created and available.
After the successful customization of a service
conditions:
page.
Actors:
The Service Provider should be able to preview
the service page
In case of unsuccessful attempt the service
provider should be displayed with a message
Normal Flow:
providing the reason for it.
Service Provider to provide
1. Description
2. Pricing
3. Timings
4. Address
5. Logo
6. Images
7. Videos
Alternative
8. Other related information
NA.
Flows:
Exceptions:
Network errors
Includes:
Frequency of
Page load errors
NA.
On demand of Service Provider.
Use:
Special
NA.
Requirements:
Assumptions:
User should have minimum knowledge about the
service and other related content General
Notes and
browser and website usage.
NA.
Issues:
Use case: UC11 Creating Service
Categories
Use Case Diagram
Provides the name of the
category
Provides the description of the
category
Clicks on save button
Admin
Server
Use Case
UC11
ID:
Use Case
Creating Service Categories
Name:
Created
Priyanka
Last
By:
Katipally
Updated
1/20/2015
By:
Last
Date
Created:
Priyanka Katipally
1/20/2015
Revision
Date:
Actors:
Description:
Trigger:
Preconditions:
1. Admin
2. Server
Admin to create the Service categories.
Service Provider first clicks a "create" button
There should be the admin available and logged
Post
in.
After the successful creation of the of a service
conditions:
category.
The Service Provider should be able to see it in
the categories list.
In case of unsuccessful attempt the service
provider should be displayed with a message
Normal Flow:
providing the reason for it.
Service Provider to provide
1. Name of the Category
2. Description
3. Image of category
Alternative
NA.
Flows:
Exceptions:
Network errors
Includes:
Frequency of
Page load errors
NA.
NA.
Use:
Special
NA.
Requirements:
Assumptions:
Admin should have minimum knowledge about
the service categories the website is going to
Notes and
have.
NA.
Issues:
Use case: UC12 Creating Sub
Categories
Use Case Diagram
Provides the name of the
Sub category
Provides the description of the sub
category
Select the primary Category it
falls under
Admin
Server
Clicks on save button
Use Case
UC12
ID:
Use Case
Creating Sub Category
Name:
Created
Priyanka
Last
By:
Katipally
Updated
1/20/2015
By:
Last
Date
Created:
Priyanka Katipally
1/20/2015
Revision
Date:
Actors:
Description:
Trigger:
Preconditions:
1. Admin
2. Server
Admin to create the Sub categories.
Service Provider first clicks a "create" button
There should be the admin available and logged
Post
in.
After the successful creation of the of a service
conditions:
category.
The Service Provider should be able to see it in
the sub categories list of a selected category
In case of unsuccessful attempt the service
provider should be displayed with a message
Normal Flow:
providing the reason for it.
Service Provider to provide
1. Select the Category in falls under
2. Name of the Sub Category
3. Sub Category Description
Alternative
NA.
Flows:
Exceptions:
Network errors
Includes:
Frequency of
Page load errors
NA.
NA.
Use:
Special
NA.
Requirements:
Assumptions:
Admin should have minimum knowledge about
the service categories the website is going to
Notes and
have.
NA.
Issues:
Use Case: UC13 Admin Logout
Use Case diagram
Click on Logout Button
Server Admin
Use Case
UC8
ID:
Use Case
Admin Logout
Name:
Created
Priyanka
Last
By:
Katipally
Updated
1/20/2015
By:
Last
Date
Created:
Priyanka Katipally
1/20/2015
Revision
Date:
Actors:
Description:
Admin
Admin logout from the System. Clear users
Trigger:
Preconditions:
Post
session data take user to the home page
Admin perform Logout operation.
The System is in the user-logged-in state.
Admin cannot access any of the site features,
conditions:
Normal Flow:
Alternative
other than login.
NA.
NA.
Flows:
Exceptions:
Session Expired.
Includes:
Frequency of
Network error.
NA.
On demand of Service Provider.
Use:
Special
NA.
Requirements:
Assumptions:
Notes and
Issues:
Valid Service Provider can perform this operation.
NA.
Use Case: UC14 Admin Login
Use Case diagram
Enter Username
Enter Password
Click on Submit Button
Server
Admin
Use Case
UC14
ID:
Use Case
Admin Login
Name:
Created
Prashanth Kumar
Last
Prashanth Kumar
By:
Vuthuru
Updated
Vuthuru
1/20/2015
By:
Last
1/20/2015
Date
Created:
Revision
Date:
Actors:
Description:
Admin
The Admin logs in to authenticate his or her role
in the system and to perform a task in the
system.
The system determines that the password is
incorrect for the username entered.
1. The system prompts the user to re-enter the
password.
The system determines that the re-entered
password is
Incorrect.
The system provides the option for the user to
retrieve a
Forgotten password then system determines
that the username matching a username for any
Trigger:
Preconditions:
account.
Admin provides login details.
Admin should provide valid personal details.
Post
Admin account has been created for the user.
Admin login will be successful if valid details are
conditions:
provided.
Normal Flow:
Admin is a member of the website.
Admin provides User Id, password. Then Account
will be logged in (correct credentials).
1. The user connects to the system.
2. The user enters his/her username and
password.
3. The system validates the username and
password.
4. The system determines the users role.
5. The system displays a list of actions the
Service Provider can perform based on the role
Alternative
NA.
Flows:
Exceptions:
Incorrect Username / Password.
Includes:
Account Already exists error.
Admin provides User Id, password.
Frequency of
On demand of Admin.
Use:
Special
NA.
Requirements:
Assumptions:
Admin is unique. No two users have same
Notes and
usernames.
NA.
Issues:
Use Case: UC15 Admin
Registration
Use Case diagram
Enter Username
Enter Password
Enter Email Address
Admin
Enter Mobile number
Enter Resident Address
Click on Submit Button
Use Case
UC15
ID:
Use Case
Admin Registration
Name:
Created
Priyanka
Last
By:
Katipally
Updated
1/20/2015
By:
Last
Date
Created:
Priyanka Katipally
1/20/2015
Revision
Date:
Actors:
Description:
Admin
Admin can provide the personal details in order
Trigger:
Preconditions:
to create the account.
Admin provides personal details.
Admin should provide valid personal details.
Postconditions
Admin is not a member of the website.
Admin account will be created if valid details are
provided.
Normal Flow:
Service Provider is a member of the website.
Admin provides valid contact details User Id,
password, phone number and email address.
Alternative
Then Account will be created.
NA.
Flows:
Exceptions:
Account will not be created if already the details
exist in Database.
Includes:
Account Already exist error.
Admin provides valid contact details User Id,
Frequency of
password, phone number and email address.
On demand of Admin.
Use:
Special
NA.
Requirements:
Assumptions:
Admin is unique. No two Admin have same
Notes and
usernames.
NA.
Issues:
Use Case: UC16 Admin Profile
creation
Use Case diagram
enter name
address
phone number
Server
Admin
Use Case
UC16
ID:
Use Case
Admin profile creation
Name:
Created
Priyanka
Last
By:
Katipally
Updated
1/20/2015
By:
Last
Date
Created:
Priyanka Katipally
1/20/2015
Revision
Date:
Actors:
Description:
Admin
The Admin logs in to authenticate his or her role
in the system and to perform a task in the
system.
The system determines that the password is
incorrect for the username entered.
1. The system prompts the user to re-enter the
password.
The system determines that the re-entered
password is
Incorrect.
The system provides the option for the user to
retrieve a
Forgotten password then system determines
that the username matching a username for any
Trigger:
Preconditions:
account.
Admin provides login details.
Admin should provide valid personal details.
Post
Admin account has been created for the user.
Admin login will be successful if valid details are
conditions:
provided his details must be updated in the data
base .
Normal Flow:
Admin provides User Id, password. Then Account
will be logged in (correct credentials).
1. The user connects to the system.
2. The user enters his/her username and
password.
3. The system validates the username and
password.
4. The system determines the users role.
5. The system displays a list of actions the
Service Provider can perform based on the role
Alternative
NA.
Flows:
Exceptions:
Incorrect Username / Password.
Includes:
Frequency of
Account Already exists error.
Admin provides User Id, password.
On demand of Admin.
Use:
Special
NA.
Requirements:
Assumptions:
Admin is unique. No two users have same
Notes and
usernames.
NA.
Issues:
Use Case: UC17 Service Provider
Profile creation
Use Case diagram
Enter name
Enter address
submit
Server
Service Provider
Use Case
UC17
ID:
Use Case
Service Provider Profile creation
Name:
Created
Prashanth Kumar
Last
Prashanth Kumar
By:
Vuthuru
Updated
Vuthuru
1/20/2015
By:
Last
1/20/2015
Date
Created:
Revision
Date:
Actors:
Description:
Admin
The Service Provider logs in to authenticate his or
her role in the system and to perform a task in
the system.
Trigger:
Preconditions:
He would be able to maintain his details
Admin provides his details.
Service Provider should provide valid personal
details.
Service Provider account has been created for
the user.
Post
Service Provider details will be successfully
conditions:
updated in the database
.
Normal Flow:
Service Provider provides User Id, password. Then
Account will be logged in (correct credentials).
1. The user connects to the system.
2. The user enters his/her username and
password.
3. The system validates the username and
password.
4. Service Provider enters his details
Alternative
NA.
Flows:
Exceptions:
Incorrect Username / Password.
Includes:
Frequency of
Account Already exists error.
Service Provider provides User Id, password.
On demand of Service Provider.
Use:
Special
NA.
Requirements:
Assumptions:
Service Provider is unique. No two users have
Notes and
same usernames.
NA.
Issues:
Use Case: UC18 Admin Profile
Update
Use Case diagram
enter name
modify address
modify phone number
Server
Admin
Use Case
UC18
ID:
Use Case
Admin profile update
Name:
Created
Priyanka
Last
By:
Katipally
Updated
Priyanka Katipally
Date
1/20/2015
Created:
By:
Last
1/20/2015
Revision
Date:
Actors:
Description:
Admin
The Admin logs in to authenticate his or her role
in the system and to perform a task in the
system.
The system determines that the password is
incorrect for the username entered.
1. The system prompts the user to re-enter the
password.
The system determines that the re-entered
password is
Incorrect. He should be able to modify his
Trigger:
Preconditions:
details.
Admin provides login details.
Admin should provide valid personal details.
Post
Admin account has been created for the user.
Admin login will be successful if valid details are
conditions:
provided his details must be updated in the data
base .
Normal Flow:
Admin provides User Id, password. Then Account
will be logged in (correct credentials).
1. The user connects to the system.
2. The user enters his/her username and
password.
3. The system validates the username and
password.
4. The system determines the users role.
5. The system displays a list of actions the
Service Provider can perform based on the role
Alternative
NA.
Flows:
Exceptions:
Incorrect Username / Password.
Includes:
Frequency of
Account Already exists error.
Admin provides User Id, password.
On demand of Admin.
Use:
Special
NA.
Requirements:
Assumptions:
Admin is unique. No two users have same
Notes and
usernames.
NA.
Issues:
Use Case: UC19 Service Provider
Profile Update
Use Case diagram
enter name
modify address
modify phone number
Server
Service provider
Use Case
UC19
ID:
Use Case
Service provider profile update
Name:
Created
Priyanka
Last
By:
Katipally
Updated
1/20/2015
By:
Last
Date
Created:
Priyanka Katipally
1/20/2015
Revision
Date:
Actors:
Description:
Service Provider
The Service Provider logs in to authenticate his or
her role in the system and to perform a task in
the system.
The system determines that the password is
incorrect for the username entered.
1. The system prompts the user to re-enter the
password.
The system determines that the re-entered
password is
Incorrect. He should be able to modify his
details.
Trigger:
Preconditions:
Service Provider provides login details.
Service Provider should provide valid personal
details.
Service Provider account has been created for
the user.
Post
Service Provider login will be successful if valid
conditions:
details are provided his details must be updated
in the data base .
Normal Flow:
Service Provider provides User Id, password. Then
Account will be logged in (correct credentials).
1. The user connects to the system.
2. The user enters his/her username and
password.
3. The system validates the username and
password.
4. The system determines the users role.
5. The system displays a list of actions the
Service Provider can perform based on the role
Alternative
NA.
Flows:
Exceptions:
Incorrect Username / Password.
Includes:
Frequency of
Account Already exists error.
Service Provider provides User Id, password.
On demand of Service Provider.
Use:
Special
NA.
Requirements:
Assumptions:
Admin is unique. No two users have same
Notes and
usernames.
NA.
Issues:
Use Case: UC20 User adding
service pages to profile list
Use Case diagram
user login
favourites service
page
updates that in the profile
Server
User
Use Case
UC20
ID:
Use Case
User adding service pages to profile list
Name:
Created
Priyanka
Last
By:
Katipally
Updated
1/20/2015
By:
Last
Date
Created:
Priyanka Katipally
1/20/2015
Revision
Date:
Actors:
Description:
User
The User logs in to authenticate his or her role in
the system and to perform a task in the system.
The system determines that the password is
incorrect for the username entered.
1.search the service by location
2. If he satisfies favourites the service page
Trigger:
Preconditions:
3. updated in the profile
User provides login details.
user should provide valid personal details.
user account has been created for the user.
Post
user login will be successful and able to favourite
conditions:
his service page and should be update in the
Normal Flow:
users profile
user provides User Id, password. Then Account
will be logged in (correct credentials).
1. The user connects to the system.
2. The user enters his/her username and
password.
3.He can able to favourite his service page.
4.that should be updated in the database
Alternative
NA.
Flows:
Exceptions:
Incorrect Username / Password.
Includes:
Frequency of
Account Already exists error.
user provides User Id, password.
On demand of user.
Use:
Special
NA.
Requirements:
Assumptions:
user is unique. No two users have same
Notes and
usernames.
NA.
Issues:
Use Case: UC20 User providing
rating and comments to the
service pages
Use Case diagram
user login
rate the service page
and post the comments
updates that in the profile
Server
User
Use Case
UC21
ID:
Use Case
User providing ratings and comments to the service page
Name:
Created
Priyanka
Last
By:
Katipally
Updated
1/20/2015
By:
Last
Date
Created:
Priyanka Katipally
1/20/2015
Revision
Date:
Actors:
Description:
User
The User logs in to authenticate his or her role in
the system and to perform a task in the system.
The system determines that the password is
incorrect for the username entered.
1.search the service by location
2. If he satisfies rates the service page and post
the comments of the service page
Trigger:
Preconditions:
3. it is updated in the profile
User provides login details.
user should provide valid personal details.
Post
user account has been created for the user.
user login will be successful and able to rate the
conditions:
service page and post the comments and should
Normal Flow:
be update in the users profile
user provides User Id, password. Then Account
will be logged in (correct credentials).
1. The user connects to the system.
2. The user enters his/her username and
password.
3.He can able to rate his service page and post
the comments.
4.that should be updated in the database
Alternative
NA.
Flows:
Exceptions:
Incorrect Username / Password.
Includes:
Frequency of
Account Already exists error.
user provides User Id, password.
On demand of user.
Use:
Special
NA.
Requirements:
Assumptions:
user is unique. No two users have same
Notes and
usernames.
NA.
Issues:
Elaboration
Phase I core business and high risk items
5. UML for this Phase:
(A) UML Diagram as changed by this phase:
USECASE DIGRAMS :
1.User Registration Use case Diagram
2.Service Provider Registration Use case Diagram
3.Admin Registration Use case Diagram
4.Use case Diagram User searching for a service by Location
5.Use case Diagram for user login
6.Use case diagram for Service provider login
SEQUENCE DIAGRAMS:
1.Sequence diagram for Service Provider registration
2.Sequence diagram for Service Provider Login
3.Sequence diagram for user registration
4.Sequence diagram for User Login
5.Sequence diagram for Admin registration
6.Sequence diagram for Admin Login
COLLABORATION DIAGRAMS
1.Collaboration diagram for Service Provider registration
2.Collaboration diagram for Service Provider Login
3.Collaboration diagram for User registration
4.Collaboration diagram for User Login
5.Collaboration diagram for Admin registration
6.Collaboration diagram for Admin Login
(B)
Use Cases (Identify those Implemented):
A) User registration
B) Service provider registration
C) Admin registration
D) User and Service Provider and Admin Login
E) Search Service
F) Create category
User Registration Use case Diagram:
Enter username
Enter password
Enter Confirm Password
Enter Email Address
Server
User
Enter Mobile number
Enter EmailId
Enter Gender
Enter Address
Enter City
Enter State
Enter Zip
Click On Submit
Service Provider Registration Use case Diagram:
Enter username
Enter password
Enter Confirm Password
Enter Email Address
Server
Service Provider
Enter Mobile number
Enter EmailId
Enter Gender
Enter Address
Enter City
Enter State
Enter Zip
Click On Submit
Admin Registration Use case Diagram:
Enter username
Enter password
Enter Confirm Password
Enter Email Address
Server
Admin
Enter Mobile number
Enter EmailId
Enter Gender
Enter Address
Enter City
Enter State
Enter Zip
Click On Submit
User searching for a service by Location:
Select Location
Search by Keywords
View the service
User
Server
Select or manage favorite pages
UML Diagram for user login:
Enter username
Enter password
Click on submit
User
Server
Use case diagram for Service provider login:
Enter username
Enter password
Click on submit
Service Provider
Server
(C)
Specifications for this phase
Pre design of all the requirements collected in analysis
phase.
After this phase design all the requirements using uml
software
Using Uml software generate uml sequence collaboration
and class diagrams.
These diagrams include system specifications and
subsystem specifications.
After this we have construction phase. these UML
diagrams helps in useful in implementing the code.
(D)
Systems Sequence Diagram for this phas
SEQUENCE DIAGRAMS:
Sequence diagram for Service Provider registration:
Server
: Service Provider
1 : Enter User Name()
2 : Checks the username already exists()
3 : Choose the different username if already exists()
4 : Enter Username()
5 : Enter Password()
6 : Enter Confirm Password()
7 : Enter EmailAddress()
8 : Enter Gender()
9 : Enter Date of Birth()
10 : Enter Cityname()
11 : Enter Statename()
12 : Enter Countryname()
13 : Enter Zipcode()
14 : Click on submit button()
15 : Service Provider Account Successfully created()
Sequence diagram for Service Provider Login:
Server
: Service Provider
1 : Enter Username()
2 : Enter Password()
3 : Click on Submit Button()
4 : Validate Usename and Password()
5 : Display Service Provider Home Page if valid credentials are provided()
6 : Error Page displayed if Invalid Credentials are Provided()
Sequence diagram for user registration:
Server
: User
1 : Enter User Name()
2 : Checks the username already exists()
3 : Choose the different username if already exists()
4 : Enter Username()
5 : Enter Password()
6 : Enter Confirm Password()
7 : Enter EmailAddress()
8 : Enter Gender()
9 : Enter Date of Birth()
10 : Enter Cityname()
11 : Enter Statename()
12 : Enter Countryname()
13 : Enter Zipcode()
14 : Click on submit button()
15 : Admin Account Successfully created()
Sequence diagram for User Login:
Server
: User
1 : Enter Username()
2 : Enter Password()
3 : Click on Submit Button()
4 : Validate Usename and Password()
5 : Display User Home if valid credentials are provided()
6 : Error Page displayed if Invalid Credentials are Provided()
Sequence diagram for Admin registration:
Server
: Admin
1 : Enter User Name()
2 : Checks the username already exists()
3 : Choose the different username if already exists()
4 : Enter Username()
5 : Enter Password()
6 : Enter Confirm Password()
7 : Enter EmailAddress()
8 : Enter Gender()
9 : Enter Date of Birth()
10 : Enter Cityname()
11 : Enter Statename()
12 : Enter Countryname()
13 : Enter Zipcode()
14 : Click on submit button()
15 : User Account Successfully created()
Sequence diagram for Admin Login:
Server
: Admin
1 : Enter Username()
2 : Enter Password()
3 : Click on Submit Button()
4 : Validate Usename and Password()
5 : Display Admin Home if valid credentials are provided()
6 : Error Page displayed if Invalid Credentials are Provided()
(E) Contracts for this phase
contract1: Page Load (object sender, EventArgs e)
Reference use case: user viewing service page
Preconditions: user login /user registration
Post conditions: A page load object instance was created Pl(instance
creation)
this instance was associated with the current page
pl. sender became the object
pl object was associated with a event on which it is generated.
contract2: protected void btnSubmit_Click(object sender,
EventArgs e)
Reference Use case: User registration/user login
Preconditions: user login/user registration/admin login/admin
registration/ service provider login/service provider registration
Postconditions: click submit button action instance has been created.
this instance was associated with the current action
slc.sender became the object
slc object was associated with a event on which the button is clicked.
contract3: Response.Redirect("~/User/EditProfile.aspx")
Preconditions: when user search the service page
Postconditions: Response .redirect instance has created when we click
the submit button
this instance was associated to show that page
it directly links to user edit page
contract4: protected void
ddlCountries_SelectedIndexChanged(object sender, EventArgs e)
References usecases : User searching the service by location
Preconditions: user login with his credentials to access the services
PostConditions: searching the service based on location instance has
created.
this instance was associated to select the countries
this directly displays all the countries and countries selected based on
action of the sender.
contract5: protected void Ddmonth_SelectedIndexChanged(object
sender, EventArgs e)
References usecases: User registration in to the application
Preconditions: NA
Postconditions: User registering in to application instance has been
created.
this instance was associated with object sender
and the date is selected depending on the action of the sender.
contract6: private void deleteFile(int field)
References usecase: User accessing his files
Preconditions: user viewing the service page
Postconditions: when user accessing the file an instance has been
created.
this instance was associated with the integer field
contract7: private int
imageUpload(System.Web.UI.WebControls.FileUpload f)
Reference usecase: creating the service pages
Preconditions: creating the service page
Postconditions: When user creating the service page an instance of
uploading the image has been created.
this instance was associated file upload f.and the image is uploaded with
file upload and the web
contract8: private void loadBookMarks()
Reference usecase: user accessing the service pages
Preconditions: user accessing the service page
Postconditions: when user accessing the service page an instance has
been created for loading bookmarks on the page.
contract9: protected string GetYouTubeScript(string id)
Reference usecase: User creating the service pages\
Preconditions: service provider logs in to the website
Postconditions: when user creating the service page an instance has
been created getting YouTube script
this instance was associated with the string id of script and the service
page.
contract10: private void getRating ()
Reference usecase: user rating the service page
Preconditions: user logs in to the website and viewing the service page
Postconditions: when user rating the service rating the bookmark
instance has been created
this instance was associated with the rating of the service page.
contract11: private void getUser()
Reference usecase : user login
Preconditions: User log in page
PostConditions: when user logins in to the website getuser instance has
been created.
this instance was associated with the names of the user.
contract11: private void loadCategories()
Reference Usecase: user accessing the service pages
Preconditions: Prompts the admin page
Postconditions: when user accessing the service page an instance has
been created to load all the categories of the website.
this instance was associated with all the service id and names
contract11: private void loadCountries()
Reference Use case: user searching the service by location
Preconditions: user selects the service depending on the location
Postconditions: when user searching the service by location an instance
has been created to load all the countries of the website.
this instance was associated with all names of the countries.
Contract12: private int
brochureUpload(System.Web.UI.WebControls.FileUpload f)
References Use case: User creating the service page
Preconditions: NA
Postconditions: when user creating the service page brocher has been
created for the service page.
this instance has been associated with file upload f
Contract13: private Boolean validateInsertion()
Reference use case: user registration
Preconditions: NA
Postconditions: when user performing the registration an instance has
been created for the validating the insertion.
this instance was associated with credentials of the user.
(F)Any other UML artifacts you created for this phase
COLLABORATION DIAGRAMS:
Collaboration diagram for Service Provider registration:
2 : Checks the username already exists()
1 : Enter User Name()
Server
3 : Choose the different username if already exists()
: Service Provider
4 : Enter Username()
5 : Enter Password()
6 : Enter Confirm Password()
7 : Enter EmailAddress()
8 : Enter Gender()
9 : Enter Date of Birth()
10 : Enter Cityname()
11 : Enter Statename()
12 : Enter Countryname()
13 : Enter Zipcode()
14 : Click on submit button()
15 : Service Provider Account Successfully created()
Collaboration diagram for Service Provider Login:
1 : Enter Username()
4 : Validate Usename and Password()
Server
: Service Provider
2 : Enter Password()
3 : Click on Submit Button()
5 : Display Service Provider Home Page if valid credentials are provided()
6 : Error Page displayed if Invalid Credentials are Provided()
Collaboration diagram for User registration:
2 : Checks the username already exists()
1 : Enter User Name()
3 : Choose the different username if already exists()
: User
4 : Enter Username()
5 : Enter Password()
6 : Enter Confirm Password()
7 : Enter EmailAddress()
8 : Enter Gender()
9 : Enter Date of Birth()
10 : Enter Cityname()
11 : Enter Statename()
12 : Enter Countryname()
13 : Enter Zipcode()
14 : Click on submit button()
15 : User Account Successfully created()
Collaboration diagram for User Login:
Server
1 : Enter Username()
4 : Validate Usename and Password()
Server
: User
2 : Enter Password()
3 : Click on Submit Button()
5 : Display User Home Page if valid credentials are provided()
6 : Error Page displayed if Invalid Credentials are Provided()
Collaboration diagram for Admin registration:
2 : Checks the username already exists()
1 : Enter User Name()
3 : Choose the different username if already exists()
: Admin
4 : Enter Username()
5 : Enter Password()
6 : Enter Confirm Password()
7 : Enter EmailAddress()
8 : Enter Gender()
9 : Enter Date of Birth()
10 : Enter Cityname()
11 : Enter Statename()
12 : Enter Countryname()
13 : Enter Zipcode()
14 : Click on submit button()
15 : Admin Account Successfully created()
Collaboration diagram for Admin Login:
Server
1 : Enter Username()
4 : Validate Usename and Password()
Server
: Admin
2 : Enter Password()
3 : Click on Submit Button()
5 : Display Admin Home Page if valid credentials are provided()
6 : Error Page displayed if Invalid Credentials are Provided()
CLASS DIAGRAM:
Login
Role
+roleId
+roleName
*
0..1
+loginId
+userName
+password
+roleId
Administrator
+adminId
+firstName
+lastName
+emailId
+loginId
+phone
+gender
+dateOfBirth
+registeredDate
Category
+catId
+name
+description
Page
0..1
*
0..1
Provider
+providerId
+firstName
+lastName
+emailId
+loginId
+phone
+gender
+dateOfBirth
+registeredDate
0..1
0..1
SubCategory
*
+subcatId
+name
+catId
+description
ENTITY RELATIONSHIP DIAGRAM:
+pageId
+title
+catId
+subcatId
+description
+timings
+pricings
+phone
+emailId
+website
+country
+state
+city
+video1
+video2
+broucher
+providerId
+createdDate
+views
+keywords
Users
+userId
+firstName
+lastName
+emailId
+loginId
+phone
+gender
+dateOfBirth
+registeredDate
Rating
*
0..1
+ratingId
+pageId
+rating
+ratedBy
+ratedDate
PROJECT ARCHITECTURE DIAGRAM :
6. Description of User Interface and Functions
User searching for a service by Location:
User Interface: User can select location and search the services by providing keywords
Functions:
User select the location
Search the services by providing the keywords
View the services
Select or manage the favorite pages.
User Viewing a Service Page:
User Interface: User can clicks the service page link from search list
Functions:
User select the service page link
View the services.
User Registration:
User Interface: User can provide the personal details in order to create the account.
Functions:
User provides valid contact details User Id, password, phone number and email
address.
So then the Account will be created.
User Login:
User Interface: The user logs in to authenticate his or her role in the system and to perform a
task in the system.
if the system determines that the password is incorrect for the username entered then
The system prompts the user to re-enter the password.
The system determines that the re-entered password is incorrect.
The system provides the option for the user to retrieve a forgotten password then
system determines that the username matching a username for any account.
Functions:
The user connects to the system.
The user enters his/her username and password.
The system validates the username and password.
The system determines the users role.
The system displays a list of actions the Service Provider can perform based
on the role
Service Provider Registration:
User Interface: Service Provider can provide the personal details in order to create the
account.
Functions:
Service Provider provides valid contact details User Id, password, phone number
and email address.
So then the Account will be created.
Service Provider Login:
User Interface: The Service Provider logs in to authenticate his or her role in the system and
to perform a task in the system.
The system determines that the password is incorrect for the username entered.
The system prompts the user to re-enter the password.
The system determines that the re-entered password is incorrect.
The system provides the option for the user to retrieve a forgotten password then
system determines that the username matching a username for any account
Functions:
The user connects to the system.
The user enters his/her username and password.
The system validates the username and password.
The system determines the users role.
The system displays a list of actions the Service Provider can perform based on the role.
7. User Guide for implemented portions of system:
User Registration:
User can provide the personal details in order to create the account
User provides valid contact details User Id, password, phone number and email address.
So then the Account will be created.
Service provider registration:
Service Provider can provide the personal details in order to create the account
Service Provider provides valid contact details User Id, password, phone number and
email address.
So then the Account will be created.
Admin registration:
Admin can provide the personal details in order to create the account
Admin can provides valid contact details User Id, password, phone number and email
address.
So then the Account will be created.
User and Service Provider and Admin Login:
The user /Service Provider /Admin logs in to authenticate his or her role in the system and
to perform a task in the system.
If the system determines that the password is incorrect for the username entered then
The system prompts the user/Service Provider /Admin to re-enter the password.
The system determines that the re-entered password is incorrect.
Search Service:
User first selects the country and state and city and provide the
description in order to get the services.
Create category:
Service provider creates a category by providing the following details
1. Category name
2. Description
3. Image
4. Parent category
8. Program for this Phase
a. Program Code (Java)
b. Javadoc documentation or your own technical documentation for the
system.
c. Any data files (before testing starts).
d. Testing Documentation
Test Case 1
Test Case #
Test Case
Name[Tested Use
case]
Short Description
Prashanth Kumar
1
Tested By
Vuthuru
User searching for
a service by
Location
Designed By
Vikas Nagavelli
User can select location and search the services by Select
location Search by keywords View the Service pages Select
or manage favorite pages Server providing keywords.
Preconditions
User should provide valid location and keywords.
Ste
p
Action
Expected Response
User Select the
Country
System Displays the
Selected Country
User not Selects the
Country
User Select the State
User Select the City
User Select the State
User Click on Submit
Button
System Display the
selected Country
System Display the
selected State
System Display the
selected City
System Display the
selected state
System Perform respected
Action
Pass/F
ail
Pass
Fail
Comment
No
User should
select the
Country in
order to
search the
services by
locations
Pass
No
Pass
No
Pass
No
Pass
No
Post conditions
User gets the required details if input location and keywords are valid.
Test Case 2
2
Tested By
Prashanth Kumar
Vuthuru
Test Case #
Test Case
Name[Tested
Usecase]
User Viewing a
Service Page
Short Description
User can clicks the service page link from search list.
Designed By
Vikas Nagavelli
Preconditions
The service page displayed on the successful event.
Ste
p
1
Action
Expected Response
User select the service
System display the services
Pass/F
ail
Pass
Comment
No
description.
page link
2
User View the Services
System Display Page with
details
Pass
No
Post conditions
User gets required service page details if input information is valid.
Test Case 3
Test Case #
Test Case
Name[Tested
Usecase]
Tested By
Vikas Nagavelli
Prashanth Kumar
User Registration
Designed By
Vuthuru
User can provide the personal details in order to create the
Short Description
account.
Preconditions
User should provide valid personal details.
User is not a member of the website.
Ste
p
1
Action
User enters First Name
Expected Response
System stores selected
First Name
Pass/F
ail
Pass
Comment
No
User enters Last Name
User enters User Name
User enters Password
User enters Confirm
Password
6
7
8
User enters wrong
Confirm Password.
User Enters the email
id
User Click on Submit
Button
In database.
System stores selected
Last Name in database.
System stores selected
User Name in database.
System Prompts Password
System stores selected
Confirm Password in
database.
Pass
No
Pass
Pass
Pass
System Prompts re enter
password if password and
confirm passwords are not
matched
Fail
System stores selected
Email in database.
Pass
System performs respected
action.
Pass
Both
passwords
and confirm
passwords
should
match.
No
Post conditions
User account will be created if valid details are provided.
Test Case 4
Test Case #
Test Case
Name[Tested
Usecase]
Tested By
Priyanka
Katipally
Prashanth Kumar
User Login
Designed By
Vuthuru
The user logs in to authenticate his or her role in the
system and to perform a task in the system.
Short Description
Validate input credentials.
Preconditions
User should provide valid personal details.
A user account has been created for the user.
Ste
p
Action
Expected Response
Pass/F
ail
Comment
System checks the
Username exists in
Database.
1
2
3
4
5
User enters Username
User enters different
username not existed
in database.
User enters Password
User re enters
password if password is
not matched with the
respected username
User Click on Submit
Button
Pass
System Prompts Enter
Username
System checks the
password in database.
System Prompts Enter
Password
System Display Submit
Button(Submit Button)
Fail
No
User Should
enter valid
and existed
Username
Pass
No
Fail
No
Pass
No
Post conditions
User login will be successful if valid details are provided.
User is a member of the website.
Test Case 5
Test Case #
Test Case
Name[Tested
Usecase]
Short Description
Tested By
Prashanth Kumar
Vuthuru
Prashanth Kumar
User Logout
Designed By
Vuthuru
Userlogout from the System.Clear users session data take
user to the home page
Preconditions
The System is in the user-logged-in state.
Ste
p
Action
Expected Response
Pass/F
ail
User Click on Logout
Button
System performs respected
functionality of user logout.
Pass
User re Click on
Logout Button
System Display error if
user is not logged in state
or already logged out.
Fail
Comment
No
User should
be logged in
state in
order to
logout.
Post conditions
User cannot access any of the site features, other than login.
Test Case 6
Test Case #
Test Case
Name[Tested
Usecase]
Short Description
Tested By
Vikas Nagavelli
Service Provider
Registration
Designed By
Priyanka Katipally
Service Provider can provide the personal details in order to
create the account.
Preconditions
Service Provider should provide valid personal details.
Service Provider is not a member of the website.
Ste
p
1
2
3
4
5
6
7
8
Action
Expected Response
Service Provider
enters First Name
Service Provider
enters Last Name
Service Provider enters
User Name
Service Provider enters
Password
Service Provider enters
Confirm Password
Service Provider re
enters wrong confirm
password.
Service Provider Enters
the email id
Service Provider Click
on Submit Button
Pass/F
ail
Comment
System stores the First
Name in database.
Pass
System stores Last Name in
database.
Pass
System stores User Name in
database.
Pass
System stores password in
database.
Pass
System stores confirm
password in database.
Pass
System Prompts re enter
password if password and
confirm passwords are not
matched
System stores Email in
database.
System performs the
respected action.
Fail
No
No
Both
passwords
and confirm
passwords
should
match.
Pass
Pass
No
Post conditions
Service Provider account will be created if valid details are provided.
Test Case 7
Test Case #
Test Case
Name[Tested
Usecase]
Tested By
Priyanka
Katipally
Service Provider
Prashanth Kumar
Login
Designed By
Vuthuru
The Service Provider logs in to authenticate his or her role
in the system and to perform a task in the system.
Short Description
Validate input credentials.
Preconditions
Service Provider should provide valid personal details.
A Service Provider account has been created for the Service Provider.
Ste
p
3
4
5
Action
Service Provider
enters Username
Service Provider
enters Username that
is not existed in
database.
Expected Response
Pass
System Prompts Enter
Username
System checks the Entered
Password is Available in
database or not.
i. Testing Plan or Unit, Systems and Acceptance Testing
System Testing:
Acceptance Testing:
Comment
System checks the Entered
Username
Available in database or
not.
Service Provider
enters Password
Service Provider re
System Prompts Enter
enters invalid password Password
Service Provider Click
System Performs the
on Submit Button
respected action.
Unit Testing :
Pass/F
ail
Fail
No
User Should
enter valid
and existed
Username
Pass
No
Fail
No
Pass
No
ii. Console Output from Testing
iii. Screen Shots of GUI for testing plan put all screen shots into a single
Word document. Add comments to explain what each photo is showing.
iv. Data File Before and After the test showing changes.
9. Reflection on this phase
A. Lessons Learned from this Phase and impact on project:
1. After collecting all the requirements for the project we design our
project
2. we design project using UML diagrams.
3. using inception phase analysis all the diagrams like usecase, sequence,
collaboration and class diagrams are drawn.
4.using these diagrams we implement the code for each module.
5.The percentage of occurring of risks is more in this phase.
6. for drawing UML diagrams we need to have clear idea of the project.
7.If UML diagrams are not correct it affects implementation of code.
8.so we find any errors in these phase we need to keep track of inception
and design phase to avoid percentage of risks.
b. Impact on project (how it changed the project):
1. First we collected all the requirements which are required to the project.
2. We tried to get a clear idea of the project and proceed to Elaboration
phase.
3. In Elaboration phase while drawing Uml diagrams for the project we
found some of the requirements missing.
4. Then we tried to work on the requirements.
5. Then we first analyzed all the use cases.
6. Using Use cases we have drawn the Use case diagram.
7. After drawing usecase diagram we got an idea of the actions that are
involved in the project.
8. Depending up on the actions sequence and collaboration diagram is
drawn.
9. The most important diagram we drawn is class diagram which plays an
important role in implementation of the project.
10. Our Project Location based services search engine provides a bridge
between users and the service providers.
11. Advantage of our project is Simplifies the job of users by providing the
relevant responses and helps them to make a purchase decision by
viewing at the all the related responses on a single platform.
Elaboration
Phase I I core business and high risk items
UML for this Phase:
(A) UML Diagram as changed by this phase:
Use case Diagram for admin login
Use case diagram for Create Service Page
Use case diagram for customizing service page
Use case diagram for Creating Service Categories
Use case diagram for Creating Sub Category
(B)
Use Cases (Identify those Implemented):
User:
A) Search Services
B) My Bookmarks
C) View Profile
D) Edit Profile
E) User Logout
F) Create category
Service Provider :
A) Search Services
B) My Pages
C) Create Pages
D) My Bookmarks
E) View Profile and Edit Profile
F)Service Provider Logout
Admin :
A) Search Services
B) Create Categories and Update Categories
C) Admin Registrations
D) Lock and Unlock the Users
E) Lock and Unlock the Service Providers
F)My Book Marks
G)View and Edit Profile
H)Admin Logout
Use case Diagram for admin login:
Enter username
Enter password
Click on submit
Admin
Server
Use case diagram for Create Service Page:
Provide Title
Select category
Select Subcategory
Service Provider
Server
Click on create button
Use case diagram for customizing service page:
Select the serice page to be customized
Server
Service Provider
Provides the description, Logo, Images, Pricing, Timings, Address, Videos other details
Click on save button
Use case diagram for Creating Service Categories:
Provides the name of the category
Provides the description of the category
Server
Service Provider
Click on save button
Use case diagram for Creating Sub Category:
Provides the name of the Sub category
Provides the description of the sub category
Server
Service Provider
Select the primary Category it falls under
Click on the save button
C. Specifications for this phase
1. Managing the budget of the Project
2. Meeting all the requirements of the project while
implementing the code.
3.Assigning work to the group members
4. After implementing testing is done for every module
5.Testing is done with all the test cases
6. meeting the customer needs.
D. Systems Sequence Diagram for this phase
1.Sequence diagram for User searching services by location
2.Sequence diagram for create a service page
3.Sequence diagram for customizing service page
4.Sequence diagram for Admin creating Service category
5.Sequence diagram for Admin creating sub category
Sequence diagram for User searching services by location:
Server
: User
1 : Select Location()
2 : Search by Keywords()
3 : Validate Keywords Exists()
4 : Returns the services if exists()
5 : View the services()
6 : Select or Manage Favorite Pages()
Sequence diagram for create a service page:
Server
: Service Provider
1 : Provides Title()
2 : Select Category()
3 : Select Sub Category()
4 : Select or Manage Favorite Pages()
5 : Click on create button()
Sequence diagram for customizing service page:
Server
: Service Provider
1 : Select the service page to be cutomized()
2 : Provides the description, Logo, Images, Pricing, Timings, Address, Videos other details()
3 : Click on save button()
Sequence diagram for Admin creating Service category:
Server
: Admin
1 : Provide the name of category()
2 : Provides the description of the category()
3 : Clicks on save button()
Sequence diagram for Admin creating sub category:
Server
: Admin
1 : Provides the name of the Sub category()
2 : Provides the description of the sub category()
3 : Select the primary Category it falls under()
4 : Click on save button()
Sequence diagram for User searching services by location:
Server
: User
1 : Select Location()
2 : Search by Keywords()
3 : Validate Keywords Exists()
4 : Returns the services if exists()
5 : View the services()
6 : Select or Manage Favorite Pages()
Sequence diagram for create a service page:
Server
: Service Provider
1 : Provides Title()
2 : Select Category()
3 : Select Sub Category()
4 : Select or Manage Favorite Pages()
5 : Click on create button()
Sequence diagram for customizing service page:
Server
: Service Provider
1 : Select the service page to be cutomized()
2 : Provides the description, Logo, Images, Pricing, Timings, Address, Videos other details()
3 : Click on save button()
Sequence diagram for Admin creating Service category:
Server
: Admin
1 : Provide the name of category()
2 : Provides the description of the category()
3 : Clicks on save button()
Sequence diagram for Admin creating sub category:
Server
: Admin
1 : Provides the name of the Sub category()
2 : Provides the description of the sub category()
3 : Select the primary Category it falls under()
4 : Click on save button()
E. Contracts for this phase
Contract14: private void getProvider()
Reference use case: Service Provider login
Preconditions: service provide performs login
Postconditions: when service provider logins in to the applications an
instance has been created for getting all the service names of the service
Provider.
This instance as associated with names of all the service provides
Contract 15: private void loadYears()
References use case : user registration/ service provider registration
Preconditions: Displays registration page
Postconditions: when user registers/service Provider register an
instance has been created for the loading he years
This instance was associated with the integer
Contract 16: private void loadDays()
Reference use case: user registration/ service provider registration
Preconditions: Displays registration page
Postconditions: when user registers/service Provider register an
instance has been created for the loading he years
This instance was associated with the integer
Contrat17: private void loadStates(string country)
Reference use case: user searching the service by location.
Preconditions: Displays user service page
Postconditions: when user searching the service b location an instance
has been created for loading all the sates.
This instance was associated with all the names of the state.
Contract18: private void loadSubcategories(int catid)
Reference use case: user searching the service by location.
Preconditions: Displays admin page.
Postconditions: when user searching the service by location an instance
has been created for loading all the subcategories.
This instance was associated with all the names of the services of all the
categories.
Contract19: private string formatVideoLink(string str)
Reference usecase: customising service page.
Preconditions: Displays service page
Postconditions: when user customising or creating the service an
instance has been created for formatting the video link
This instance was associated with the name of the string of the video.
Contract20: private void getAdmin()
Reference use case: Admin login
Preconditions: Admin login
Postconditions: when ever admin log in to the website an instance has
been created for getting all the admin names from the database.
This instance has been associated with the names of the admin.
Contract21: public Boolean checkCaptcha()
Reference Use case: User registration/service provider registration.
Preconditions: User registration/service provider registration/ admin
registration
Postconditions: when service Provider or user registering in to the
website. an instance has been created for the checking the captcha
This instance was associated with the capctha name.
Contract22: public Boolean checkUser()
Reference Use case: User login/user rating/user favouriting he services
Preconditions: user rating or book marking the service page
Postconditions: when user login or rating the service or favouriting the
service an instance has been created for checking the user
This instance as associated with the user name in the database
Contract23: public Boolean checkEmail()
Reference Use case: user Registration/service Provider registration
Preconditions: User registration
Postconditions: when user/ service Provider performing the registration
in to the website. an instance has been created for checking the email.
This instance was associated with the verification of the email
Contract24: private Boolean checkPswd()
Reference Use case: User login/service provider login/admin login
Preconditions: user login/admin login/service provider login
Postconditions: when user/service provider /admin log in to the website
an instance has been created for checking passwords for Particular user
service provider or admin.
Contract25: public void createAdmin()
Reference Use case: use case creating admin
Preconditions: NA
Postconditions: when admin registering in to the website an instance
has been created for creating the admin.
This instance was associated with the details of the admin like username
and password.
Contract26: Generic.GetSHA256 (txtPassword.Text)
Reference Use case: user registration/service provider registration/user
login/service provider login/admin login/admin registration.
Preconditions: Displays login /registration page
Postconditions: when user login /register or service provider login
/registers or admin login /registers an instance has been created for
hashing the password.
This instance as associated with text of the password.
Contract27: protected byte[] getImageBytes()
Reference Use case: customising the service page
Preconditions: image upload to service page
Postconditions: when an Image is uploaded in to the customising or
creating the service page an Instance has been created getting the bytes
of the Image.
Contract28: protected void btnLogin_Click(object sender,
EventArgs e)
Reference Use case: use case Admin login or service provider login or
user login
Preconditions: Displays login /registration page
Postconditions: whenever user or admin or service provider performs
the login action an instance has been created for button click.
This instance was associated with the action of the sender.
F. Any other UML artifacts you created for this phase:
1.Collaboration diagram for User searching services by
location
2.Collaboration diagram for create service page
3.Collaboration diagram for customizing service page
4.Collaboration diagram for Admin creating Service category
5.Collaboration diagram for Admin creating Sub Category
Collaboration diagram for User searching services by location:
3 : Validate Keywords Exists()
1 : Select Location()
Server
: User
2 : Search by Keywords()
4 : Returns the services if exists()
5 : View the services()
6 : Select or Manage Favorite Pages()
Collaboration diagram for create service page:
1 : Provides Title()
Server
: Service Provider
2 : Select Category()
3 : Select Sub Category()
4 : Select or Manage Favorite Pages()
5 : Click on create button()
Collaboration diagram for customizing service page:
1 : Select the service page to be cutomized()
Server
: Service Provider
2 : Provides the description, Logo, Images, Pricing, Timings, Address, Videos other details()
3 : Click on save button()
Collaboration diagram for Admin creating Service category:
1 : Provide the name of category()
Server
: Admin
2 : Provides the description of the category()
3 : Clicks on save button()
Collaboration diagram for Admin creating Sub Category:
1 : Provides the name of the Sub category()
Server
: Admin
2 : Provides the description of the sub category()
3 : Select the primary Category it falls under()
4 : Click on save button()
Description of User Interface and Functions
User creating a service page
User Interface: Generally Service provider creates the service page
Service provider log in to the website
it displays the option to create the service page
he clicks on that tab
then creates the service page
Functions:
to promote his service . service provider log in to the website
he selects the option create service page
create the service page
customizing the service page:
User Interface: In order to modify the service page service provider log in to the website
there find many options like create the service page or view the service pages
when he view the service pages .he gets three options either to edit delete or view.
.
Functions:
Service Provider can modify the service pages depending on his
requirements
he can edit details
he can upload the image
or can upload a file
Admin creating the service category:
User Interface: Admin in order to create the service category he log in to the system
there he create the service categories depending up on the services in the website
Functions:
Admin connects to the system
He log in to the website with user name and password
There he find the options to create the service categories
Depending up on the services in the website he create service categories
Admin creating the sub category:
User Interface: Admin in order to create the sub category he log in to the system
there he create the sub categories depending up on the services in the website
Functions:
Admin connects to the system
He log in to the website with user name and password
There he find the options to create the service categories
Depending up on the services in the website he create service categories and
sub categories
User searching the service by location:
User Interface: User log in to the website to get the services from the website.
it displays the page to select the countries state and city .
Functions:
user connects to the system
He log in to the website with user name and password
There he find the options to get the service by the location
He type the location and the keyword to get the service from the website
User rating the service
User Interface: User After viewing the service page if he satisfies he rate the website or the
service .
Functions:
User must be register to rate the service or the website
he log in to the website with his credentials
after logging he search the service
after getting the service if he satisfies he rate the website
User bookmarking the service :
User Interface:
User After viewing the service page if he satisfies he bookmarks the website
Functions:
User must be register to rate the service or the website
he log in to the website with his credentials
after logging he search the service
after getting the service if he satisfies he bookmarks the website
User Guide for implemented portions of system
User searching the service by location:
user logs in to the website to get the services from the website .website
displays the page showing the options to select the country state and the
city. user selects the country state and the city. and types the keyword of
the service. application displays the services with that keywords
User creating the service page:
Service provider log into the system to create the service pages
.whenever he logs in to the system the application displays the options to
create the service page. He selects that and create the service page
User customizing the service page:
whenever user log in to the website to view the services. the website
displays service with options that he can view edit or delete. in edit option
he can customize the pages .
Admin creating service category:
In our project we have multiple admin who can manage service providers
and users. Admin depending up on the services create the service
category. so that user can access the services quickly
Admin creating sub category services:
Admin who created service categories can create sub categories of the
services in the website depending up on the services
8. Program for this Phase
a. Program Code (Java)
b. Javadoc documentation or your own technical documentation
for the system.
c. Any data files (before testing starts).
d. Testing Documentation
Test Case 8
Test Case #
Test Case
Name[Tested
Usecase]
Tested By
Vikas Nagavelli
Service Provider
Prashanth Kumar
Logout
Designed By
Vuthuru
Service Provider logout from the System.Clear users session
Short Description
data take Service Provider to the home page
Preconditions
The System is in the Service Provider -logged-in state.
Ste
p
1
Action
Service Provider Click
on Logout Button
Expected Response
System performs the
Logout functionality.
Pass/F
ail
Pass
Comment
No
Service Provider re
Click on Logout Button
System Display error if
Service Provider is not
logged in state
Or already logged out.
Fail
Service
Provider
should be
logged in
state in
order to
logout.
Post conditions
Service Provider cannot access any of the site features, other than login.
Test Case 9
Test Case #
Test Case
Name[Tested
Usecase]
Tested By
Prashanth Kumar
Vuthuru
Create a Service
Page
Designed By
Vikas Nagavelli
Service Provider to create the Service pages by selecting a
category, sub category ,location details, description, timing,
Short Description
pricing, images, videos, and selected keywords .
Preconditions
There should be the service provider created and available.
and the name and category and subcategory to be provided/selected.
Ste
p
1
2
Action
Expected Response
System stores Entered
service provider enters Title in database.
Title
System stores Entered
service provider select Category in database.
Category
Pass/F
ail
Comment
Pass
No
Pass
No
3
4
service provider not
select Category
service provider select
Sub Category
service provider not
select Sub Category
service provider enters
Description
System prompts select the
Category.
Fail
System stores Entered Sub
Category in database.
Pass
System prompts select the
Sub Category.
Fail
Pass
service provider not
enters Description
service provider Select
Address
service provider not
Select Address
Fail
Pass
Fail
Service
provider
should select
the Address
because it's
mandatory.
Service
provider
should select
the State
because it's
mandatory.
Pass
Pass
No
No
Pass
service provider not
select the State.
System prompts select
State.
10
11
12
Service
provider
should enter
the
Description
because it's
mandatory
filed.
System stores Entered
Address in database.
System prompt the service
provider
to select the address.
Service
provider
should select
the Sub
Category
because it's
mandatory
filed.
System stores Entered
Description in database.
System prompts the service
provider to enter
description
Service
provider
should select
the Category
because it's
mandatory
filed.
System stores Entered
service provider Enters phone number in database.
phone number
service provider Enters System stores Entered
Email Id
Email in database.
13
service provider Enters
Website
14
service provider
uploads image1
15
service provider
uploads image2
16
service provider
uploads image3
17
service provider
uploads image4
18
service provider
Provides video link1
19
20
21
22
service provider
Provides video link2
service provider
uploads brochure
service provider enters
the related keywords
Service provider click
on create service page
button
System stores Entered
Website in database.
Pass
No
Pass
No
Pass
No
Pass
No
Pass
No
Pass
No
Pass
No
Pass
No
Pass
No
pass
No
System stores Entered
image1in database.
System stores Entered
image2 in database.
System stores Entered
image3 in database.
System stores Entered
image4 in database.
System stores Entered
video link1 in database.
System stores Entered
video link2 in database.
System stores Entered
brochure in database.
System stores Entered
keywords in database.
System perform the
respected functionality.
Post conditions
After the successful creation of a service page.
The Service Provider should be able to view the created service page in the
services list.
In case of unsuccessful attempt the service provider should be displayed with a
message providing the reason for it.
Test Case 10
Test Case #
Test Case
Name[Tested
Usecase]
10
Tested By
Prashanth Kumar
Vuthuru
Customizing the
Prashanth Kumar
Service Page
Designed By
Vuthuru
Service Provider to customize the Service page by providing
Short Description
the details of it.
Preconditions
There should be the service provider and service page created and available.
Ste
p
1
2
Action
Expected Response
System stores Entered
service provider enters Title in database.
Title
service provider select System stores Entered
Pass/F
ail
Pass
Pass
Comment
No
No
Category in database.
Category
3
4
service provider not
select Category
service provider select
Sub Category
service provider not
select Sub Category
service provider enters
Description
service provider not
enters Description
service provider Select
Address
10
11
service provider not
Select Address
System prompts select the
Category.
Fail
Service
provider
should select
the Category
because it's
mandatory
filed.
System stores Entered Sub
Category in database.
Pass
System prompts select the
Sub Category.
Fail
Service
provider
should select
the Sub
Category
because it's
mandatory
filed.
System stores Entered
Description in database.
Pass
System prompts the service
provider to enter
description
Fail
Service
provider
should enter
the
Description
because it's
mandatory
filed.
System stores Entered
Address in database.
Pass
System prompt the service
provider
to select the address.
System prompts select
service provider not
State.
select the State.
service provider Enters System stores Entered
phone number
phone number in database.
Pass
Fail
Pass
Service
provider
should select
the Address
because it's
mandatory.
Service
provider
should select
the State
because it's
mandatory.
No
12
service provider Enters
Email Id
13
service provider Enters
Website
14
service provider
uploads image1
15
service provider
uploads image2
16
service provider
uploads image3
17
service provider
uploads image4
18
service provider
Provides video link1
19
service provider
Provides video link2
20
service provider
uploads brochure
21
22
service provider enters
the related keywords
Service provider click
on create service page
button
System stores Entered
Email in database.
Pass
No
Pass
No
Pass
No
Pass
No
Pass
No
Pass
No
Pass
No
Pass
No
Pass
No
Pass
No
pass
No
System stores Entered
Website in database.
System stores Entered
image1in database.
System stores Entered
image2 in database.
System stores Entered
image3 in database.
System stores Entered
image4 in database.
System stores Entered
video link1 in database.
System stores Entered
video link2 in database.
System stores Entered
brochure in database.
System stores Entered
keywords in database.
System perform the
respected functionality.
Post conditions
After the successful customization of a service page.
The Service Provider should be able to preview the service page
Test Case 11
Test Case #
Test Case
Name[Tested
Usecase]
Short Description
11
Creating Service
Categories
Tested By
Designed By
Admin to create the Service categories.
Preconditions
There should be the admin available and logged in.
Prashanth Kumar
Vuthuru
Priyanka Katipally
Ste
p
1
2
3
4
5
Action
Expected Response
Pass/F
ail
Comment
System stores entered
Category name in database.
Admin Enters
Category name
Pass
No
Pass
No
Pass
No
Pass
No
Pass
No
System stores entered
description name in
database.
Admin Enters
Description
Admin upload the
image
Admin select the
parent category
Admin Clicks on
Submit button.
System stores entered
image in database.
System stores entered
Parent Category name in
database.
System performs respected
action when admin clicks on
submit Button.
Post conditions
After the successful creation of the of a service category.
The Admin should be able to see it in the categories list.
Test Case 12
Test Case #
Test Case
Name[Tested
Usecase]
12
Update Service
Categories
Tested By
Short Description
Admin to update the Service categories.
Designed By
Prashanth Kumar
Vuthuru
Priyanka Katipally
Preconditions
There should be the admin available and logged in.
Ste
p
Action
Expected Response
Pass/F
ail
Comment
2
3
System stores entered
Category name in database.
Admin Enters
Category name
Pass
No
Pass
No
Pass
No
Pass
No
Pass
No
System stores entered
description name in
database.
Admin Enters
Description
Admin upload the
image
Admin select the
parent category
Admin Clicks on
update button.
System stores entered
image in database.
System stores entered
Parent Category name in
database.
System performs respected
action when admin clicks on
submit Button.
Post conditions
Service category details are updated successfully.
The Service Provider should be able to see it in the categories list.
Test Case 13
Test Case #
Test Case
Name[Tested
Usecase]
13
Tested By
Vikas Nagavelli
Admin Registration Designed By
Priyanka Katipally
Admin can provide the personal details in order to create the
Short Description
account.
Preconditions
Admin should provide valid personal details.
Admin is not a member of the website.
Ste
Action
Expected Response
Pass/F
Comment
1
2
3
4
5
6
7
8
ail
Admin enters First
Name
Admin enters Last
Name
Admin enters User
Name
Admin enters Password
Admin enters Confirm
Password
Admin re enters wrong
confirm password.
Admin Enters the email
id
Admin Click on Submit
Button
Admin the First Name in
database.
Pass
System stores Last Name in
database.
Pass
System stores User Name in
database.
Pass
System stores password in
database.
Pass
System stores confirm
password in database.
Pass
System Prompts re enter
password if password and
confirm passwords are not
matched
System stores Email in
database.
System performs the
respected action.
Fail
No
No
Both
passwords
and confirm
passwords
should
match.
Pass
Pass
No
Post conditions
Admin account will be created if valid details are provided.
Test Case 14
Test Case #
Test Case
Name[Tested
Usecase]
14
Tested By
Priyanka
Katipally
Prashanth Kumar
Admin Login
Designed By
Vuthuru
The Admin logs in to authenticate his or her role in the
system and to perform a task in the system.
Short Description
Preconditions
Validate input credentials.
Admin should provide valid personal details.
Admin account has been created for the Service Provider.
Ste
p
Action
Expected Response
Admin enters
Username
Admin enters
Username that is not
existed in database.
4
5
Comment
System checks the Entered
Username
Available in database or
not.
Pass/F
ail
Pass
Admin enters Password
Admin re enters
invalid password
Admin Click on
Submit Button
System Prompts Enter
Username
System checks the Entered
Password is Available in
database or not.
System Prompts Enter
Password
System Performs the
respected action.
Fail
No
Admin
Should enter
valid and
existed
Username
Pass
No
Fail
No
Pass
No
Post conditions
Admin login will be successful if valid details are provided.
Admin is a member of the website.
Test Case 15
Test Case #
Test Case
Name[Tested
Usecase]
Short Description
15
Tested By
Vikas Nagavelli
Prashanth Kumar
Admin Logout
Designed By
Vuthuru
Admin logout from the System. Clear admin session data
and take him to the home page.
Preconditions
The System is in the Admin -logged-in state.
Ste
p
1
Action
Expected Response
Pass/F
ail
Admin Click on Logout
Button
System performs the
Logout functionality.
Pass
Admin re Click on
Logout Button
System Display error if
admin is not logged in state
Or already logged out.
Fail
Comment
No
Admin
should be
logged in
state in
order to
logout.
Post conditions
Admin cannot access any of the site features, other than login.
Test Case #
Test Case
Name[Tested
Usecase]
16
Tested By
Priyanka katipally
User adding
service pages to
Prashanth Kumar
favourite list
Designed By
Vuthuru
When the user favourites the service page that service
Short Description
should be easily accessible to the user.
Preconditions
The System is logged in by the user viewing service pages
Ste
p
Action
Expected Response
When the user clicks
the favourite button
When the user clicks
the favourite button
Test Case #
Test Case
Name[Tested
Usecase]
System should book marks
the service page .
When the does not book
mark the service page
17
User providing
rating and
comments to the
Pass/F
ail
Pass
Fail
Tested By
Designed By
Comment
No
No
Priyanka Katipally
Prashanth Kumar
Vuthuru
service pages
Whenever user feels comfortable with the service page he
Short Description
should able to rate and post the comments
Preconditions
User should log in to the system
Ste
p
Action
Expected Response
He should rate by
selecting the choices
poor ,bad, good and
excellent and he
should also able to
post the comments
If he is not able to
select the ratings and
not able to post the
comments
Pass/F
ail
He should able to rate the
service page and rating for
the service page must be
posted and comments for
the service page must also
be posted
Pass
Then user cannot rte the
service page
Fail
Comment
No
No
Post conditions
Website can be post the ratings of the service page
Test Case #
Test Case
Name[Tested
Usecase]
18
Tested By
User profile
creation
Designed By
Priyanka Katipally
Prashanth Kumar
Vuthuru
Short Description
Preconditions
The System is in the Admin -logged-in state.
Ste
p
Action
Expected Response
1
2
Admin Click on Logout
Button
Admin re Click on
Logout Button
System performs the
Logout functionality.
System Display error if
admin is not logged in state
Or already logged out.
Pass/F
ail
Pass
Fail
Comment
No
Admin
should be
logged in
state in
order to
logout.
Post conditions
Admin cannot access any of the site features, other than login.
Test Case #
Test Case
Name[Tested
Usecase]
19
Tested By
User profile
creation
Short Description
Maintaining the details of the user
Designed By
Priyanka Katipally
Prashanth Kumar
Vuthuru
Preconditions
User should log in to the system
Ste
p
1
2
Action
Expected Response
User should able to
enter his details
If the user enter his
details
Admin should able to get
the details.and display
them
information is not updated
Pass/F
ail
Pass
Fail
Comment
No
No
Post conditions
Application maintains user details
Test Case #
Test Case
Name[Tested
Usecase]
20
Tested By
User profile
update
Short Description
Whenever user want to customize his details
Designed By
Priyanka Katipally
Prashanth Kumar
Vuthuru
Preconditions
User should log in to the system
Ste
p
Action
User should log in to
system he should able
to modify the changes
If he re able to modify
the changes
Expected Response
The changes should be
updated in the database
Changes are not updated
in the data base
Pass/F
ail
Pass
Fail
Comment
No
No
Post conditions
User must be able to modify the changes
Test Case #
Test Case
Name[Tested Use
case]
Short Description
21
Tested By
Priyanka Katipally
Service provider
Prashanth Kumar
profile creation
Designed By
Vuthuru
Service provider should be able to create his details like
name phone number what service he his providing
Preconditions
Service provider should log in to the system
Ste
p
Action
Service provider
should be able to
create his details like
name address phone
number etc
Service provider
should be able to
create his details like
name address phone
number etc
Post conditions
Expected Response
Pass/F
ail
The details should be
created in the database
whenever user wants to
view service provider
details. he should able to
see that
Pass
Details are not updated in
the database4
Fail
Comment
No
No
Test Case #
Test Case
Name[Tested
Usecase]
22
Tested By
Priyanka Katipally
Service provider
profile update
Short Description
Service provider able to modify his profile
Prashanth Kumar
Vuthuru
Designed By
Preconditions
Service provider should log in to the system
Ste
p
Action
Expected Response
Service provider
should be able to
modify his profile like
he can able to update
his information like
name address etc
Service provider
should be able to
modify his profile and
can be able to update
his information
Pass/F
ail
Service provider what ever
he changes made that
should be updated in the
database
Pass
If Changes are not
updated in the data base
Fail
Comment
No
No
Post conditions
Service Provider must be able to modify the changes
Test Case #
Test Case
Name[Tested
Usecase]
23
Tested By
Admin profile
update
Short Description
Whenever Admin want to create his details
Designed By
Priyanka Katipally
Prashanth Kumar
Vuthuru
Preconditions
Admin should log in to the system
Ste
p
Action
Expected Response
Pass/F
ail
Comment
1
2
Admin should log in to
system he should able
create his information
If he re able to create
his information
The information should be
stored in the database
Information is not updated
in the databse
Pass
Fail
No
No
Post conditions
Admin must be able to create his information
Test Case #
Test Case
Name[Tested
Usecase]
24
Tested By
Priyanka Katipally
Admin profile
update
Short Description
Whenever Admin want to customize his details
Prashanth Kumar
Vuthuru
Designed By
Preconditions
Admin should log in to the system
Ste
p
Action
Admin should log in to
system he should able
to modify the changes
If Admin re able to
modify the changes
Expected Response
Pass/F
ail
The changes should be
updated in the database
Changes are not updated
in the data base
Post conditions
Admin must be able to modify the changes
i. Testing Plan or Unit, Systems and Acceptance Testing
Pass
Fail
Comment
No
No
ii. Console Output from Testing
iii. Screen Shots of GUI for testing plan put all screen shots into
a single Word document. Add comments to explain what each
photo is showing.
iv. Data File Before and After the test showing changes
Reflection on this phase
a. Lessons Learned from this Phase
1. Need to go in a sequence order to satisfy all the requirements of the
user
2.we need to divide the project in to modules
3.this modules should be assigned to team members
4. Each team member will work on the modules
5.getting feedback from team mates is very important so that we can
improve our module according to our requirements
6. After each module testing should be done
7. Estimating the hours worked by the group mates
8. so that we can improve our efficiency in building the project.
10.If we find any mistakes they should be note down to avoid
confusion between the modules
11. Getting the clear idea of the tools to be used in the project
12. Through knowledge on the environment what we are using
b. Impact on project (how it changed the project)
1. Up to first phase we designed some of the
pages for the user and service provider
2. After facing some of the difficulties with
password encryption. we user Sh256 password
encryption method for the password encryption
3. we used captcha for registration of user admin
and the service provider
4. for creating the service pages we used
filleZilla to upload the the files relate to the
webpage
6. Inserting images in to service pages
creating the options like edit view and delete for
the service pages in the website
7.User rating the website has been implemented
8. User book marking the website has been
implemented
9.creating you tube links for the service pages
has been implemented
17. List of Use cases for the Next Phase
Functionality to facilitate users to send email to the Providers
Functionality to facilitate users to interact with the Providers Online
Functionality to facilitate Providers to view their page statistics
Dashboard for Providers , To manage Pages
18. Tools Used
(image ref: howtodoinjava.com)
1) Web Server : Internet Information Services
A Web server is a program that, using the client/server model and the
World Wide Web's Hypertext Transfer Protocol ( HTTP ), serves the files
that form Web pages to Web users (whose computers contain HTTP clients
that forward their requests).
2) Internet Information Services (IIS, formerly Internet
Information Server) is an extensible web server created by Microsoft for
use with Windows NT family.[2] IIS supports HTTP, HTTPS, FTP, FTPS, SMTP
and NNTP. It has been an integral part of the Windows NT family since
Windows NT 4.0, though it may be absent from some editions (e.g.
Windows XP Home edition
3) Application Server : ASP.NET , Windows Hosting
The application server is the middleman between browser-based frontends and back-end databases and legacy systems. In many usages,
the application server combines or works with a Web (Hypertext Transfer
Protocol) server and is called a Web application server.
4) Development Environment: Visual Studio 2012
Microsoft Visual Studio is an integrated development environment (IDE)
from Microsoft. It is used to develop computer programs for Microsoft
Windows, as well as web sites, web applications and web services.
5) Database Server:
Microsoft SQL Server is a relational database management system
developed by Microsoft. As a database, it is a software product whose
primary function is to store and retrieve data as requested by other
software applications, be it those on the same computer or those running
on another computer across a network (including the Internet). There are
at least a dozen different editions of Microsoft SQL Server aimed at
different audiences and for workloads ranging from small single-machine
applications to large Internet-facing applications with many concurrent
users. Its primary query languages are T-SQL and ANSI SQL.)
6) FTP Client: FileZilla
FileZilla is free, cross-platform FTP application software, consisting of
FileZilla Client and FileZilla Server. Binaries are available for Windows,
Linux, and Mac OS X. It supports FTP, SFTP, and FTPS (FTP over SSL/TLS).
Support for SFTP (SSH File Transfer Protocol) is not implemented in FileZilla
Server.
7) Software used to produce your documentation
1. Microsoft Office Word
2. Microsoft Office Presentation
3. Microsoft Office Excel
4. Rational Rose UML
To work with documents and presentations.
8) Server side scripting : C#.NET
Server-side scripting is a technique used in web development which
involves employing scripts on a web server which produce a response
customized for each user's (client's) request to the website.
9) Client side scripting: HTML, CSS , JavaScript, JQuery , XML
Client-side scripting generally refers to the class of computer programs on
the web that are executed client-side, by the user's web browser, instead
of server-side (on the web server).
Reference : www.wikipedia.com
19. Source Code, files and user guide of final system all
phases.
20. Reference Documents and Appendices anything else I
should see.
LBSSE Project Tracker.xls
LBSSE Project
Tracker.xlsx
Web References:
1. http://www.microsoft.com/net
2. https://msdn.microsoft.com/en-us/library/bb545450.aspx
3. https://www.wikipedia.org/
4. http://www.connectionstrings.com/
5. http://www.w3schools.com/
You might also like
- Name: Mabangula Cindy Student No.: 218121970 Group: 3E Assignment 1No ratings yetName: Mabangula Cindy Student No.: 218121970 Group: 3E Assignment 18 pages
- Web ServicesWeb Services and Service Oriented ArchitectureNo ratings yetWeb ServicesWeb Services and Service Oriented Architecture54 pages
- Google Cloud Architect Design and Process WorkbookNo ratings yetGoogle Cloud Architect Design and Process Workbook23 pages
- Proposed Marketplace Platform Development PlanNo ratings yetProposed Marketplace Platform Development Plan18 pages
- Computer Service Management System 21497No ratings yetComputer Service Management System 2149738 pages
- A Web Based Application On Temporary Job Home Services During Pandemic SituationNo ratings yetA Web Based Application On Temporary Job Home Services During Pandemic Situation4 pages
- For Artnatar: Prepared By: Sadia Bibi Reg #: 1441-11600 MCS (Morning)No ratings yetFor Artnatar: Prepared By: Sadia Bibi Reg #: 1441-11600 MCS (Morning)26 pages
- Docs Google Com Document D 1waf CKBLk25fkwF R4KS7wLq4KTIPhUcAtj6if5N Zo PubNo ratings yetDocs Google Com Document D 1waf CKBLk25fkwF R4KS7wLq4KTIPhUcAtj6if5N Zo Pub3 pages
- SRS File (Sales Inofrmation Web Portal)No ratings yetSRS File (Sales Inofrmation Web Portal)13 pages
- Chapter 18 Service Oriented EngineeringNo ratings yetChapter 18 Service Oriented Engineering8 pages
- Intelligent Service Provider With Location Access: Alochana Chakra Journal ISSN NO:2231-3990No ratings yetIntelligent Service Provider With Location Access: Alochana Chakra Journal ISSN NO:2231-39907 pages
- Spring 2025 - CS619 - 10708 - 35471 - S250243ECENo ratings yetSpring 2025 - CS619 - 10708 - 35471 - S250243ECE22 pages
- Rent Buddy: Department of Computer Science and Engineering Report OnNo ratings yetRent Buddy: Department of Computer Science and Engineering Report On16 pages
- Using Splunk For Business Process AnalyticsNo ratings yetUsing Splunk For Business Process Analytics4 pages
- Softimage User Guide - Snapping To TargetsNo ratings yetSoftimage User Guide - Snapping To Targets3 pages
- Test Cases: Project Name: Virtual ClassroomNo ratings yetTest Cases: Project Name: Virtual Classroom5 pages
- Cloud Federation - Slas: Christian Temporale, Hewlett PackardNo ratings yetCloud Federation - Slas: Christian Temporale, Hewlett Packard79 pages
- How To Use Ntdsutil To Manage Active Directory Files From The Command Line in Windows Server 2003No ratings yetHow To Use Ntdsutil To Manage Active Directory Files From The Command Line in Windows Server 20034 pages
- Ruahacollege University: RCS 201: Database Design 3 Unit CourseNo ratings yetRuahacollege University: RCS 201: Database Design 3 Unit Course43 pages
- Space Mouse: Presented by P.Satya Siva Teja 17A51A05E9 Cse-CNo ratings yetSpace Mouse: Presented by P.Satya Siva Teja 17A51A05E9 Cse-C17 pages
- Introduction To Cmos Vlsi Design: Datapath Functional UnitsNo ratings yetIntroduction To Cmos Vlsi Design: Datapath Functional Units54 pages