Date post: | 12-Dec-2015 |
Category: |
Documents |
Upload: | prasanga-wdz |
View: | 227 times |
Download: | 0 times |
INDIVIDUAL ASSIGNMENT
BY
PRIMAL PRASANGA WADANAMBY (CB003340)
MODULE TITLE
ENTERPRISE WEB APPLICATION
MODULE CODE
CE00318-2
INTAKE CODE
GF1171COM
LECTURER
MR. THANGAVEL SARAVANAN
DATE ASSIGNED
23RD NOVEMBER 2011
DATE DUE
21ST FEBRUARY 2012
ABSTRACT
Web applications are playing a vital role in present world scenarios to provide solutions and
services to the mankind. Unlikely in early ages, web sites are used in more general aspects
and embedded with greater technological features. These sudden improvements are caused
due to the complexity of requirements of the people. Therefore the application needs to be in
standard that can fulfill user requirements and answer to real world problems.
Supermarket websites have become the new trend in modern online marketing arena.
Unfortunately, such kind of websites are hosted by merchants who are willing sell their own
products. Therefore a customer has to visit many other such site or stepped into their shops.
To overcome these problems, the proposed solution provides facilities to both customers and
merchants to get into a portal where they can purchase and sell products only using a single
website.
The main task of the proposed market portal is to handle multiple merchants in order to
provide competitive services to their customers. Therefore the site behaves dynamically to
select merchants that are available in customer’s area and furthermore provides deals and
offers to the customer.
Same as the customer, proposed solution provides many more features to the merchants and
administrators which they can fulfill their requirements from the system.
ACKNOWLEDGEMENTS
I would like to extend my sincere gratitude for our lecturer, Mr. Thangavel Saravanan, for his
continuous advice and guidance given to me throughout this module. Without his immense
guidance and supervision, it would be hard for me to continue studies properly.
My heartfelt gratitude also goes to my parents for their continuous support guiding me in all
aspects throughout my carrier.
My thanks also go to the administration of APIIT for laboratory and library facilities
provided to me whenever I needed.
Finally, the support given by my classmates is also highly appreciated.
TABLE OF CONTENTS
ABSTRACT...............................................................................................................................ii
ACKNOWLEDGEMENTS......................................................................................................iii
1.0 INTRODUCTION................................................................................................................1
1.1 Project Background..........................................................................................................1
1.2 Project Objective..............................................................................................................1
1.3 Project Scope....................................................................................................................1
1.4 Assumptions.....................................................................................................................2
2.0 REQUIREMENT SPECIFICATION...................................................................................3
2.1 Target Audience...............................................................................................................3
2.2 Hardware & Software Requirements...............................................................................3
3.0 REQUREMENT MODELING............................................................................................5
3.1 Function Specification.....................................................................................................5
3.1.1 Use Case Diagram.....................................................................................................5
3.1.2 Activity Diagram.......................................................................................................6
4.0 LOGICAL DESIGN...........................................................................................................16
4.1 Entity Relationship Diagram..........................................................................................16
4.2 Table Design..................................................................................................................17
4.3 Navigation Map..............................................................................................................18
5.0 IMPLEMENTATION........................................................................................................19
5.1 Form Sketches................................................................................................................19
5.2 Screenshots.....................................................................................................................23
6.0 CONCLUSION..................................................................................................................27
7.0 REFERENCES & BIBLIOGRAPHY................................................................................28
LIST OF FIGURES
Figure 1 – Use Case Diagram....................................................................................................5
Figure 2 – Activity Diagram – Manage Merchant Accounts...................................................12
Figure 3 – Activity Diagram – Merchant Registration............................................................13
Figure 4 – Activity Diagram – View/Search Products.............................................................13
Figure 5 – Activity Diagram – Manage Customer Accounts...................................................14
Figure 6 – Activity Diagram – Generate Reports....................................................................15
Figure 7 – Activity Diagram – Manage Payments...................................................................15
Figure 8 – Entity Relationship Diagram..................................................................................16
Figure 9 – Table Design...........................................................................................................17
Figure 10 – Site Map 1.............................................................................................................18
Figure 11 – Site Map 2.............................................................................................................18
Figure 12 – Form Sketches – Main Page.................................................................................19
Figure 13 – Form Sketches – Product Page.............................................................................19
Figure 14 – Form Sketches – Login Page................................................................................20
Figure 15 – Form Sketches – User Home Page.......................................................................20
Figure 16 – Form Sketches – Product Description Page..........................................................21
Figure 17 – Form Sketches – Deals Page.................................................................................21
Figure 18 – Form Sketches – Payment Page............................................................................22
Figure 19 – Screenshot - Main Page........................................................................................23
Figure 20 - Screenshot - User Login Page...............................................................................24
Figure 21 - Screenshot - Customer Account Page...................................................................24
Figure 22 - Screenshot - Customer Registration Page.............................................................25
Figure 23 - Screenshot - Add Deal Page..................................................................................26
Figure 24 - Screenshot - Reports Page.....................................................................................26
LIST OF TABLES
Table 1 - Use Case Description - View/Search Products...........................................................6
Table 2 - Use Case Description - View Deal/Offers..................................................................6
Table 3 - Use Case Description - Handle Messages..................................................................7
Table 4 - Use Case Description - View Purchase Details..........................................................7
Table 5 - Use Case Description - Manage Payments.................................................................8
Table 6 - Use Case Description - Manage Shopping Cart.........................................................8
Table 7 - Use Case Description - Manage Products..................................................................9
Table 8 - Use Case Description - Manage Offers......................................................................9
Table 9 - Use Case Description -Merchant Registration.........................................................10
Table 10 - Use Case Description - Manage Customer Account..............................................10
Table 11 - Use Case Description - Generate Reports..............................................................11
CHAPTER 1
1.0 INTRODUCTION
1.1 Project Background
The proposed solution is to provide online supermarket services by gathering multiple
merchants into single market portal. Online supermarket is a popular concept in most parts of
the world which facilitates the customers to order product through online and delivered it to
the customer’s doorstep. Though it provide such kind of facilities, the customer needs to log
into several such websites to know which merchant has the lowest price to the required list of
products. In Sri Lanka, most of the merchants are not aware of providing online services to
their customers. So that the customers require stepping in to their super markets to purchase
goods he/she needs. Then also the customer is not aware of the product prices of other super
markets and might have to pay higher price for a good than other super markets.
Therefore a web solution is required to overcome above issues and imitations and to provide
related services to both customers and merchants in Sri Lanka.
1.2 Project Objective
The primary objective of the market portal is to provide competitive market solutions and
services to customers as well as merchants by enabling administrative tasks to manage both
customers and merchants.
1.3 Project Scope
Project scenario is consists with three user types which are assigned to behave as three
different entities of the application. Administrator is the entity of the system that got the
highest priority level which contains superiorities as follows;
Perform all the administrative functionalities such as creating/ updating/ deleting user
accounts, adding or updating products/locations/sub locations, Search records and
generating reports.
Creating and validating merchant accounts.
Can handle messages from customers and merchants.
Handles payment gateways.
Superiorities of merchant as follows;
Can add/update prices to the existing products and add locations/sub locations.
Post and maintain deals
Generate report of inventory details.
Can send messages and reply to customers.
Generate report of product price list.
Superiorities of customer as follows;
Can perform purchase products and edit and update user account.
Ability to view merchant’s details.
Send messages to admin or merchant.
Generate report of purchase history or receipt.
1.4 Assumptions
Payments are handling through a payment gateway.
Location identification through IP address handles when the site is hosted in web
server.
Merchant registration is handled after informing to the administrator.
Web site is only available for local users (Customers and Merchants).
Market Portal’s payment method is handled through third party operator.
CHAPTER 2
2.0 REQUIREMENT SPECIFICATION
2.1 Target Audience
The proposed web solution is targeted mainly for customers who are interested in purchasing
goods through online. And those who are interested in stepped in purchases from super
markets are also become potential audience that needs to be attracted to online markets.
Targeted customers can vary from teenagers to adults. It will mainly decide by the products
and services which are available by the market portal. Furthermore the appearance of the site
and functionality should fulfill each age category in order to keep a trusted relationship
between the site and the customers.
Merchants such as super market companies are the next target audience which is not
providing such online services to their customers. Though they provide such services, they
are limited with their competitive advantage points in online market that might affect them
negatively to their image in the market. Therefore the site should provide competitive
functionalities from its core to basic functions that attract the customers by developing
merchant’s state to the top from other competitors.
These two target audiences should be mainly aware about technological and educational
aspects such as,
Computer literacy
Internet usability
2.2 Hardware & Software Requirements
Hardware is not a main requirement to develop as well as to operate the web solution. It will
only require a computer which has basic configurations such as,
Processor – Pentium 4 3.0GHz or higher
RAM – 1GB or higher
to develop and operate the proposed web solution.
Software is a critical factor to develop the proposed web solution. Given below is the
software with its uses which required creating and developing the site.
Visual Studio 2008 – Develop the functionality
MS SQL Server 2008 – Create the database
Adobe Photoshop CS3 – Design the front end buttons and banners
Adobe Flash CS3 – Design flash slideshows
CHAPTER 3
3.0 REQUREMENT MODELING
3.1 Function Specification
3.1.1 Use Case Diagram
Given below is the use case diagram for the proposed system which shows the involvement
of the users with the system components.
Figure 1 – Use Case Diagram
3.1.2 Use Case Description
View/Search Products
Characteristic Information
Group in Context Used when customer or visitor look for products. Pre - ConditionSuccess End Condition Successfully display products.Failed End Condition Unable to display products.Primary Actor Registered customer/ visitor Trigger Event Enter product details
Main Success Scenario
Customer/visitor enter product details(Category/Name)
Display the products list
Table 1 - Use Case Description - View/Search Products
View Deals/Offers
Characteristic Information
Group in Context Used when customer or visitor look for deals or offers. Pre - ConditionSuccess End Condition Successfully display deals or offers.Failed End Condition Unable to display deals or offers.Primary Actor Registered customer/ visitor Trigger Event Enter merchant details
Main Success Scenario
Customer/visitor select merchant
Display the deals or offers list
Table 2 - Use Case Description - View Deal/Offers
Handle Messages
Characteristic Information
Group in Context Used when customer or merchant or admin send or reply messages
Pre - ConditionSuccess End Condition Successfully sent or receive messagesFailed End Condition Unable to send or receive messages.Primary Actor Registered customer/ merchant/admin Trigger Event Enter message details
Main Success Scenario
Customer/merchant/admin enter message details
Send or receive messages.
Table 3 - Use Case Description - Handle Messages
View Purchase Details
Characteristic Information
Group in Context Used when customer request for view purchase history Pre - ConditionSuccess End Condition Successfully display purchase history.Failed End Condition Unable to display purchase history.Primary Actor Registered customer Trigger Event Enter duration details
Main Success Scenario
Customer enters duration details and requests.
Display purchase history.
Table 4 - Use Case Description - View Purchase Details
Manage Payments
Characteristic Information
Group in Context Used when customer requests for payments Pre - ConditionSuccess End Condition Successfully done transaction.Failed End Condition Unable to proceed with transaction.Primary Actor Registered customer Trigger Event Enter payment details
Main Success Scenario
Customer enters payment details and requests.
Done transaction.
Table 5 - Use Case Description - Manage Payments
Manage Shopping Cart
Characteristic Information
Group in Context Used when customer request for view/edit shopping cart. Pre - ConditionSuccess End Condition Successfully update shopping cart.Failed End Condition Unable to update shopping cart.Primary Actor Registered customer Trigger Event Select shopping cart option
Main Success Scenario
Customer selects shopping cart option.
Display shopping cart in updates.
Table 6 - Use Case Description - Manage Shopping Cart
Manage Products
Characteristic Information
Group in Context Used when merchant request for enter products. Pre - ConditionSuccess End Condition Successfully added products.Failed End Condition Unable to add products.Primary Actor Registered merchantTrigger Event Enter product details
Main Success Scenario
Merchant enters product details.
Save product details.
Table 7 - Use Case Description - Manage Products
Manage Offers
Characteristic Information
Group in Context Used when merchant request for add offers. Pre - ConditionSuccess End Condition Successfully added offers.Failed End Condition Unable to add offers.Primary Actor Registered merchant Trigger Event Enter offer details
Main Success Scenario
Merchant enters offer details.
Save offer details.
Table 8 - Use Case Description - Manage Offers
Merchant Registration
Characteristic Information
Group in Context Used when merchant request for registration. Pre - ConditionSuccess End Condition Successfully registered merchant.Failed End Condition Unable to register merchant.Primary Actor Administrator Trigger Event Enter merchant details
Main Success Scenario
Admin enter merchant details.
Merchant get registered.
Table 9 - Use Case Description -Merchant Registration
Manage Customer Account
Characteristic Information
Group in Context Used when administrator update customer accounts. Pre - ConditionSuccess End Condition Successfully updated.Failed End Condition Unable to update.Primary Actor Administrator Trigger Event Enter customer details
Main Success Scenario
Admin enter customer details.
Customer account gets updated.
Table 10 - Use Case Description - Manage Customer Account
Generate Reports
Characteristic Information
Group in Context Used when administrator/merchant request for reports. Pre - ConditionSuccess End Condition Successfully report generated.Failed End Condition Unable to generate reports.Primary Actor Administrator/ merchant Trigger Event Enter report details
Main Success Scenario
Admin/merchant enters report details.
Reports generate.
Table 11 - Use Case Description - Generate Reports
3.1.3 Activity Diagram
Manage Merchant Accounts
Figure 2 – Activity Diagram – Manage Merchant Accounts
Merchant Registration
View/Search Products
Figure 3 – Activity Diagram – Merchant Registration
Figure 4 – Activity Diagram – View/Search Products
Manage Customer Accounts
Figure 5 – Activity Diagram – Manage Customer Accounts
Generate Reports
Figure 6 – Activity Diagram – Generate Reports
Manage Payments
Figure 7 – Activity Diagram – Manage Payments
CHAPTER 4
4.0 LOGICAL DESIGN
4.1 Entity Relationship Diagram
The above diagram in Figure 1 is the Entity Relationship Diagram of the proposed market
portal. Entities of the diagram can be show as follows.
Users, Customer, Admin, Merchant, Product, Branch, Location, Stock, Category,
Subcategory, Deals
Relationships between entities of the proposed solution are one-to-one, one-to-many and
many-to-many. And it represents the context among two entities while they are in database
design form.
Figure 8 – Entity Relationship Diagram
4.2 Table Design
Figure 9 show the database table structure of the system which plays vital role to handle
accurate connectivity and data related processes.
Figure 9 – Table Design
4.3 Navigation Map
Figure 10 – Site Map 1
Figure 11 – Site Map 2
CHAPTER 5
5.0 IMPLEMENTATION
5.1 Form Sketches
Main Page
Products Page
Figure 12 – Form Sketches – Main Page
Figure 13 – Form Sketches – Product Page
User Login Page
User Home Page (Form)
Figure 14 – Form Sketches – Login Page
Figure 15 – Form Sketches – User Home Page
Product Description Page
Deals Page
Figure 16 – Form Sketches – Product Description Page
Figure 17 – Form Sketches – Deals Page
Payments Page
Above form sketches are designed at the design stage of the application development process.
It will provide general ideas of how the system design and form placement is going to take
place.
Figure 18 – Form Sketches – Payment Page
5.2 Screenshots
Main Page
Main page which is shown in figure 19 is the first page that will appear for a user request. It
will facilitate the user to navigate different page according to the user’s preference. Mainly
the above page will navigate user to the login/register page as well as products and other
supportive pages.
Figure 19 – Screenshot - Main Page
User Login Page
The above login page will allow the all user in three different types to login to the site.
Customer Account Page
The page that appears for a registered customer to update/view his/her details.
Figure 20 - Screenshot - User Login Page
Figure 21 - Screenshot - Customer Account Page
Customer Registration Page
Figure 22 shows the customer registration page that only allows registering customers.
Figure 22 - Screenshot - Customer Registration Page
Add Deals Page - Merchant
Reports Page - Administrator
Figure 23 - Screenshot - Add Deal Page
Figure 24 - Screenshot - Reports Page
CHAPTER 6
6.0 CONCLUSION
Web applications are playing a vital role in present world scenarios to provide solutions and
services to the mankind. Unlikely in early ages, web sites are used in more general aspects
and embedded with greater technological features. These sudden improvements are caused
due to the complexity of requirements of the people. Therefore the application needs to be in
standard that can fulfill user requirements and answer to real world problems.
Developing such system like Online Market Portal requires immense development effort with
constant analysis of real world issues. Therefore the proposed web solution of market portal
is designed and developed as web application prototype with general functionalities which
only allow a customer or merchant or admin to interact with basic activities of the system.
Use of ASP.Net to develop the site’s front end with using C# as programming language and
database in Microsoft SQL Server, provides greater advantage point on adding more
advanced web services and other functions. Including advanced functions such as Geo
locators and mobile accessibility will improve the web site’s usability. Furthermore the
validation and security features needs to be improved as well as included general features.
7.0 REFERENCES & BIBLIOGRAPHY
Boehm, A & Murach, J. (2008). Murach's ASP.NET 3.5 Web Programming with C# 2008. Murach & Associates, Inc
Hoffman, J. (1996-2001). Introduction to Structured Query Language [Online] Available
from: http://www.highcroft.com/highcroft/sql_intro.pdf [26th January 2012]
LearnVsualStudio.Net. (2002). ASP.NET, C#, Visual Basic Tutorials and Training on
LearnVsualStudio.Net [Online] Available from: http://www.learnvisualstudio.net/ [Accessed:
6th January 2012]
Sprouse, W. (2004). Structured Query Language (SQL) Tutorial [Online]. Available from:
http://www.cemml.colostate.edu/assets/pdf/LCTASQL.pdf [24th January 2012]