E-Commerce Report Book

Hamdard University
Usman Institute of Technology
Department of Computer Science

Batch - 2010
Software Process Implementation in E-Commerce

Portal
By
Syed Nabeel Junaid
07A-003-BS
Ahmer Hussain
09B-006-BS
Anas Ul Haq Qureshi
10B-097-BS
Supervisor
Engr. Abdul Rahman Mahmood.Assistant Professor
Project report submitted in partial fulfillment of the requirement for the award of the
Degree of BS (CS)
Karachi
Aug 2014
ST-13, Block 7, Gulshan-e-Iqbal, AbulHasanIsphani Road,
Opposite Safari Park, P.O. Box 75300, Karachi, Pakistan.
Phone: 34978274-5; 349904305, 34982476
http://www.uit.edu.pk
CHA
CERTIFICATE
The undersigned certify that they have read and accepted the Final Year Project Report
entitled
Software
Application)
Process
submitted
Implementation
by
Syed
In
E-commerce
Nabeel
Junaid
Portal
(Web
07A-003-BS,
Mohammad Ahmer Hussain 09B-006-BS and Anas Ul Haq Qureshi 10B-097-BS

in conformity with the requirements for the degree of Bachelor of Science in Computer
Science.
Dated: _________________
_____________________________
Asst. Prof. Abdul Rahman Mahmood
Project Supervisor
ii
CHA
CERTIFICATE
This is to certify that the project report entitled Software Process Implementation
In E-Commerce Portal (Web Application) being submitted by Mr. Anas Ul Haq Qureshi,
Mr. Syed Nabeel Junaid and Mr. Ahmer Hussain in partial fulfillment for the award of
the Degree of Bachelor of Computer Science in 2014 to the Hamdard University is a
record of bonafied work carried out by said students under the supervision of Engr.
Abdul Rahman Mahmood Assistant Professor and evaluated by the panel.
The results embodied in this project report have not been submitted to any other
University or Institute for the award of any Degree or Diploma
________________________________
Assoc. Prof. Engr. Parkash Lohana
HOD, CS Department
__________________________
Asst. Prof. Syed Faisal Ali
FYP, Incharge
_________________________________
Engr. Asst. Prof. Abdul Rahman Mahmood
Supervisor
iii
CHA
__________________________
External Supervisor
ACKNOWLEDGEMENT
We have taken efforts in this project. However, it would not have been possible without
the kind support and help of many individuals. We would like to extend my sincere
thanks to all of them.
This project could not have been completed without Engr. Abdul Rahman Mahmood (IT
Security Consultant-Appxone, Assistant Professor -UIT) who not only served as our
supervisor but also encouraged and challenged us throughout our academic program. And
to my panels, Asst. Prof. Syed Faisal Ali (FYP In-charge) and Engr. Abdul Rahman
Mahmood thank you for evaluating our report with fairness and objectivity.
We would also like to express our gratitude to all our friends who provide advice and
guidance. Last but not least to our parents for supporting us when we need them.
Our thanks and appreciations also go to our university in developing the project and
people who have willingly helped us out with their abilities.
iv
CHA
ABSTRACT
The purpose of this project is to study software process model and to understand how to apply
software engineering concepts in the development of E-Commerce portal. In order to understand
the concepts of analysis, architecture and design. We also prepared case studies which in future
can be taught in software development course.
The project includes all major features and functionality of a typical e-commerce website.
Including a categorize list of different products available purchase, an application to search a
specific product, shopping cart application, a sign-up / log-in application, credit card payment
application etc. This project is done under a guidance of a software house.
CHA
TABLE OF CONTENT
i List of Tables .............................................................................................................. ix
ii List Of Figures .............................................................................................................x
1 Introduction .................................................................................................................1
1.1 Four E-Commerce business models......................................................................2
1.2 Project Objective ..................................................................................................5
1.3 Project Scope ........................................................................................................5
2 Software And Hardware Requirements ...................................................................6
2.1 Hardware Requirement .........................................................................................7
2.2 Software Requirement ..........................................................................................8
3 Literature Review .......................................................................................................9
3.1 Privacy and security issue's .................................................................................10
3.2 Processes .............................................................................................................13
3.3 Methodology .......................................................................................................18
3.4 SDLC ..................................................................................................................20
3.5 Case Studies ........................................................................................................22
4 Software Requirment Analysis ................................................................................28
4.1Software Requirments ..........................................................................................29
4.2 System Modules And Their Functionalities ......................................................29
4.2.1 User ............................................................................................................30
4.2.2 Administrator .............................................................................................30
5 Software design ..........................................................................................................36
vi
CHA
5.1 System Architecture Diagram .............................................................................37

5.2 Data Flow Diagram ............................................................................................38
5.3 Class Diagram ....................................................................................................39
5.4 Object Diagram ...................................................................................................41
5.5 Deployment Diagram .........................................................................................42
5.6 Use Case .............................................................................................................43
5.6.1 Use Case Management Diagram ......................................................................45
5.6.2 Use Case Admin Diagram ..............................................................................46
5.7 Sequence Diagram ..............................................................................................47
5.7.1 Non Register User Sequence Diagram ...........................................................47
5.7.2 Register User Sequence Diagram ...................................................................48
5.7.3 Admin Sequence Diagram ..............................................................................49
5.8 Activity Diagram ...............................................................................................50
5.9 Flow Chart Diagram ...........................................................................................52
5.10 ER Diagram ......................................................................................................53
5.11 Collaboration Diagram......................................................................................55
5.12 Component Diagram .........................................................................................56
5.13 Association Model. ...........................................................................................57
5.14 Basic State Chart Diagram ................................................................................57
5.15 Communication Diagram ..................................................................................58
6 Algorithm and its complexity ....................................................................................59
6.1 Algorithm and Pseudo code ................................................................................60
6.2 Complexity of code .............................................................................................60
6.3 Dry Run Algorithm ......60
7 Testing .........................................................................................................................67
vii
CHA
7.1 PerformanceTesting ............................................................................................72

7.2 Stress Testing . ....................................................................................................82
7.3 Load Testing .......................................................................................................85
7.4 Unit Testing ........................................................................................................90
8 Conclusion ..................................................................................................................94
9 Further Enhancement/Recommendation ................................................................96
10 Reference and Bibliography....................................................................................98
11 Annexure.................................................................................................................103
11.1 Project Proposal ..............................................................................................104
11.3 Project GANTT Chart .............................................................................................116
11.4 Plagiarism ..................................................................................................................118
viii
CHA
LIST OF TABLES
Table 2.1: Hardware Requiremnts ....07

Table 6.1: Complexity of searching63
Table 6.2:Complexity of login65
Table 7.4: Unit Testing90
ix
CHA
LIST OF FIGURES
Fig. 5.1: Syatem Architecture Diagram ................................................................37

Fig. 5.2: Data Flow Diagram ..................................................................................38
Fig. 5.3: Class Diagram ..........................................................................................39
Fig. 5.4: Object Diagram ........................................................................................41
Fig. 5.5: Deployment Diagram ...............................................................................42
Fig. 5.6: Use Case Diagrams...................................................................................43
Fig. 5.7: Sequence Diagrams ..................................................................................47
Fig. 5.8: ActivityDiagram .......................................................................................50
Fig. 5.9: Flowchart Diagram ..................................................................................52
Fig. 5.10: ER Diagram ............................................................................................53
Fig. 5.11: Collaboration Diagram ..........................................................................55
Fig. 5.12: Component Diagram..............................................................................56
Fig. 5.13: AssociationModel ...................................................................................57
Fig. 5.12: Basic State Chart Diagram....................................................................57
Fig. 5.12: Communication Diagram ......................................................................58
Fig. 7.1: Performance Testing ................................................................................72
Fig. 7.2: Stress Testing ............................................................................................82
Fig. 7.3: Load Testing .............................................................................................85
Fig. 7.4: Units Testing .............................................................................................90
CHA
CHAPTER 1
_____________________________________________________________________________
CHAPTER 1
INTRODUCTION
_____________________________________________________________________________
CHA
CHAPTER 1
The software process implementation is defined as to develop software step by step acquiring
the activities which includes planning, design, coding and deployment/maintenance. To
implement these activities we developed an e-commerce application [1]. A typical e-commerce
website which includes a categorized list of different product available for purchase, an
application to search a specific product, a shopping cart application, a sign-up/ log-in application,
a credit card payment application etc.
E-commerce is a trading in products or services using computer networks, such as the internet.
Electronic commerce draws on technologies such as mobile commerce, electronic funds
transfer, supply chain management, Internet marketing, online transaction processing, electronic
data interchange (EDI), inventory management systems, and automated data collection systems.
Modern electronic commerce typically uses the World Wide Web for at least one part of the
transaction's life cycle, although it may also use other technologies such as e-mail
[2]
. E-
commerce businesses usually employ some or all of the following practices:
Provide detail or virtual storefront on websites with online catalogs, sometimes gathered into
a "virtual mall"
Buy or sell on websites or online marketplaces.
Gather and use demographic data through web contacts and social media.
Use electronic data interchange, the business-to-business exchange of data.
Reach prospective and established customers by e-mail or fax (for example, with
newsletters).
Use business-to-business buying and selling.
Provide secure business transactions
1.1 Four E-Commerce Business Models

There are four types of E-Commerce business models. The four types of E-Commerce business
models are B2C which stands for Business-to-Consumer, B2B which stands for Business-toBusiness model, C2C which stands for Consumer-to-Consumer, and B2G which stands for
Business-to-Government. When working, selling, or buying with any of these models, it is
important to be familiar with what each model contains [3]. B2C represents most of E-Commerce
websites. Businesses that sell to consumers are considered B2C. Online stores and shopping are
CHA
CHAPTER 1
all examples of B2C. B2B are businesses selling products to other businesses. B2B are usually
larger companies that are supplying a service to other businesses. For example, office max is a
business that sells office supplies to other businesses. Also, they are almost always doing
business over the web. C2C is a website that consumers sell to other consumers. People are
brought together to sell and buy products for this model
[4]
. For example, EBay is a common
place for consumers to sell and buy items. B2G consists of businesses working with the
government. For example, the IRS is a way for businesses to pay their taxes through the web.
These four E-Commerce business models are very common in this day-in-age.
1.1.1 Business-to-Consumer
Business-to- consumer (B2C) model is a business or transactions conducted directly between a
company and consumers who are the end-users of its products or services. [5] The term became
popular during the dot-com boom
[6]
of the late 1990s. While many online B2C websites shut
down, the companies such as Amazon.com and Priceline.com survived and became the most
successful companies in the world. This model is likely familiar to most people. If a person have
purchased an item online for their own use, the person e-tailed. The concept was first developed
in 1979 by Michael Aldrich, an English inventor, who connected a television set to a transaction
processing computer with a telephone line and coined the term "teleshopping."[7]
1.1.2 Business-to-Business
Business-to-business (B2B) is a type of commerce transaction that exists between businesses,
such as those involving a manufacturer and wholesaler, or a wholesaler and a retailer. A typical
supply chain involves multiple business to business transactions, as companies purchase
components and other raw materials for use in its manufacturing processes.[8] An example that
illustrates the business to business concept is automobile manufacturing such as buying tires,
glass for windscreens, and rubber hoses for its vehicles. B2B is also used in the context of
communication where employees from different companies can connect and communicate with
one another, such as through social media like Linkedin.com
CHA
CHAPTER 1
1.1.3 Consumer-to-Consumer
Consumer-to-Consumer (C2C) is a type of electronic commerce in which consumers buy, sell, or
trade products and services from one another through a third party website. [9] The third party
website can be either fee-based or free as long as transactions are between consumers. Some
popular websites known for Consumer-to-Consumer transactions include Craigslist, eBay, and
Auto Trader. There are many advantages of C2C e-commerce. Because business transactions are
done between consumers and not businesses, buyers and sellers do not need to account for taxes.
Also, the transactions are done on a personal level and there are no legal obligations like
companies might have. This allows for prices to be negotiated and sometimes bartering can take
place. Most transactions that take place on websites like Craigslist, however, are paid for with
cash, so it is difficult to return items or purchase them with credit cards. There is also a lot of
safety concerns with consumer-to-consumer transactions. Because many sales are completed
from peoples houses, there is a lack of privacy. Also, because the buyers may be going to
someones house to buy a product, there are in danger of being kidnapped. That is why many
Craigslist users suggest meeting in a public area. The best part about C2C commerce is that there
are many different websites that you can use to match both the product you are selling as well as
the way you would like to sell it. If you dont want to have someone coming to your house
through Craigslist, then you can simply sell your item through eBay and ship it to another
consumer. It is all about putting more power into the consumers hands. [10]
This project is about online shopping or e-shopping is a form of electronic commerce which
allows consumers to directly buy goods or services from a seller over the internet using a web
browser. Alternative names are: e-web-store, e-shop, e-store, Internet shop, web-shop, web-store,
online store, online storefront and virtual store.
An online shop evokes the physical analogy of buying products or services at a bricks-andmortar retailer or shopping center; the process is called business-to-consumer (B2C) online
shopping.
CHA
CHAPTER 1
1.2 Project objectives
User would need to register /login to make purchases.
It will display the product catalogue and details according to the category.
The user can make customized searches for a product.
The project will make appropriate notifications according to the situation.
Confirmation email will be send to the user after purchase.
Allow user to add/edit items into the shopping cart.
Display and allow cancelation of orders that are eligible for cancelation.
1.3 Project scope

Our project scope will be:
Admin panel is the back end of application from where the admin can manage the whole
site and its contents as well.
User will be able to purchase products online and get a confirmation email.
Also prepare case studies which in future can be taught in Software development course.
CHA
CHAPTER 2
_____________________________________________________________________________
CHAPTER 2
SOFTWARE AND HARDWARE REQUIREMENTS
_____________________________________________________________________________
CHA
Our project is about E-Commerce portal (online shopping) in which user can buy product
online. The following is the development environment of what we will be developed:
Aptana Studio
My SQL
Xampp Server
PHP
2.2 User Interface Requirement:

Each part of the user interface intends to be as user friendly as possible. The fonts and
buttons used will be intended to be very fast and easy to load on web pages. The pages
will be kept light in space so that it wont take a long time for the page to load.
2.3 Hardware Required:
2.3.1 Operating Environment
This product will be developed using Open Source server side language PHP so, we would
preferably use Microsoft Windows Operating System for developing this software.
2.3.2 Design and implementation constraints
This product will be developed using Open Source server side language PHP So, we would
preferably use Microsoft Windows Operating System for developing this software.
CHA
CHAPTER 2
2.1 Software Required:
Hardware
Microsoft
Windows
XP/
7/8.8.1 (32 or 64 Bit)
1.5 GHz 32-bit (x86)/64-bit (x64) or higher

1 GB RAM or 512 MB RAM (32-bit) or higher
2GB HDD free
Table 2.3 Hardware Requirement
2.3.3 GB RAM OR 512 MB RAM

RAM is the most important component of Computer system it is based on Memory Speed
and Performance of the System requirement for Web Application is 1 GB or 512 MB.
Below 512 MB cannot perform the task for the required speed for example in Browsing,
Searching and etc.
2.3.4 2 GB HDD
This Requirement is minimum 2GB space required for downloading the Pictures and PDF
report File and report Images.
2.3.5 OPERATING SYSTEM:
Minimum Requirement is XP or WIN 7, 8, 8.1 because it is a web application so it required a
high speed Browser like GOOGLE CHROME AND FIREFOX etc these type of browsers
only required to install in this operating systems.
CHA
CHAPTER 2
Operating System (OS)
CHAPTER 3
_____________________________________________________________________________
CHAPTER 3
LITERATURE REVIEWS
_____________________________________________________________________________
CHA
E-Commerce is the process of buying, selling, or exchanging products, services, or information

via computer networks. The main concept of our project is an e-commerce website; a storefront
which could be selling anything but would have all the features common to various e-commerce
Customers will be able to register to this site, browse product, make purchases and can update
their profile information
[11]
. Customers also have access to the internet and a valid method of
payment in order to complete a transaction
[12]
. Consumers find a product of interest by visiting
the website of the retailer directly or by searching among alternative vendors using a shopping
search engine.
Once a particular product has been found on the website of the seller, most online retailers
use shopping cart to allow the consumer to accumulate multiple items and to adjust quantities,
like filling a physical shopping cart or basket in a conventional store
[13]
. A "checkout" process
follows (continuing the physical-store analogy) in which payment and delivery information is
collected, if necessary
[14]
. Some stores allow consumers to sign up for a permanent online
account so that some or all of this information only needs to be entered once. The consumer
often receives an e-mail confirmation once the transaction is complete.
Less sophisticated stores may rely on consumers to phone or e-mail their orders (although full
credit card numbers, expiry date, and Card Security Code,[15] or bank account and routing
number should not be accepted by e-mail, for reasons of security).
Admin panel is the back end of application from where the admin can manage the whole site and
its contents as well
[16]
. User will be able to purchase products online and get a confirmation
email.
10
CHA
CHAPTER 3
websites.
3.1 PRIVACY AND SECURITY ISSUE
people nowadays have various choices to do their shopping [17]. Big companies such as eBay and
amazon.com have introduced many value added features to help the customers to decide what to
shop for. With features such as price comparison, product photos and user reviews, consumers
can shop easily and smartly without even going to the stores and having such a hard time looking
for the products they want. All they have to do are just browse for the product they want in the
website and within a few mouse clicks they are off. Such simplicity is what makes online
shopping appealing for consumers [18]. The question is, why do many people still deny shopping
online? Well, for most people, privacy and security issues are their concerns. Hence, here I will
discuss customers perception of privacy and security issues, the reality of such issues and ways
to avoid those issues, all based on some trustworthy sources I have found.
To know customers perception of customer and security issues, I reviewed a scholarly article
entitled Consumer Perceptions of Privacy and Security Risks for Online Shopping produced
in the Journal of Consumer Affairs. In the United States, more than half of the adult population
uses the Internet and from that number, approximately half have shopped online (Sefton, qtd. in
Miyazaki and Fernandez
[19]
). Previous studies had shown that Internet users as a whole agreed
that privacy and security issues are vital for them to shop online (Rohm and Milne, qtd. in
Miyazaki and Fernandez
[20]
). Most of them regard their personal information as their main
concern (U.S. FTC, qtd. in Miyazaki and Fernandez). In the research conducted by Miyazaki and
Fernandez, who are the authors of the articles themselves, privacy and security issues accounted
for more than 65 percent of consumers main concern as oppose to the other
[21]
for shopping
inconveniences and others. They also concluded that more experienced Internet users tend to
have more concern regarding privacy issues but less concern on security issues. Nevertheless,
consumers still consider both as their main concern for online shopping as suggested in the
survey.
11
CHA
CHAPTER 3
Shopping online has never been so easy. With the flourishing numbers of online merchants,
Now, after knowing that privacy and security issues are vital for consumers in online shopping, I
would like to know the emphasis in the real world. From an article titled The Myth of Secure EShopping published in PC World, the reality of such issue is revealed. While most consumers
House and IKEA, these big companies still receive frequent security threats (Kandra). Joseph
McDonnell, a CEO of online security firm I Shop Secure even confessed that all online firms
must have received threats of some sorts. He added by saying that hackers could easily infiltrate
and get customers personal information online as online shoppers are not anonymous. Experts
also discover that security measures taken by online retailers are insufficient
[22]
. For instance,
data encryption only applies in actual transfer of customer data but not in the database which is
ironically the most common targets for hackers. Some other sites however, do not even have
privacy and security policy posted implying that they do not protect their customers (Hairell).
This is what happened to Biblio find when it was hacked hence compromising its customers
credit information (Kandra) [23]. Apart from the retailers themselves, credit card processing firms
and third party sites also receive threats (Kandra).Creditcards.com once had disclosed that
someone had infiltrated its site and posted more than 55000 credit card numbers on the Internet.
So, from all these indications, I can see that online shopping is not totally safe.
However, customer rights and security aspects are not just the responsibility of online merchants.
To uphold them, the consumers themselves need to act. According to Ten Things Your Mother
Never Told You about Online Shopping published in Yahoo! Internet Life, to be an ace
consumer, online shoppers need to prepare themselves with some basics (Halpin). As the
prominent method of payment is credit card, consumers should be more aware in handling it
[24]
They should never disclose their credit information via e-mail. Some of the credit card issuers
also have some sorts of protection that consumers should apply for. Apart from that, consumers
should limit themselves from releasing unnecessary personal information such as age and income
to protect their privacy (Hood, qtd. in Halpin). Also, as Todd Richter who is the president of girl
shop (an e-commerce site) had said, consumers should always be aware of the security
technology used by merchant sites
[12]
. Technologies such as Secure Socket Layer (SSL) and
VeriSign play vital part in distinguishing one site from another. Nonetheless, consumers should
always be alert of the privacy and customer policy in each site they tend to buy from (Halpin).
12
CHA
CHAPTER 3
trust big and well established online merchant such as CD Universe, Travelocity, Columbia
Lastly, if there are still dissatisfactions, consumers could always report them to consumer-related
agencies such as Better Business Bureau or Federal Trade Commission (Halpin).
Thus, after reviewing these three reliable sources related to the privacy and security issues of
tends to shop online will think twice before they buy anything as to consider the privacy and
security issues related to it. This is proven in my first source (Consumer Perceptions of Privacy
and Security Risks for Online Shopping) through the survey. People are always conscious about
their privacy and security. However, this is not the case in the real world. As my second source
(The Myth of Secure E-Shopping) has proposed, even though online merchants have tried their
best to beef up the security, threats and attacks still prevail
[25]
. For this reason, consumer should
act fast to protect their privacy when shopping online. My third source (10 Things Your Mother
Never Told You about Online Shopping) explains many ways that consumers could do to
enhance the privacy and security aspect apart from what online merchants have done for the
same reason. Taking all these contents as a whole, I would say that in any situation, people can
still shop online safely provided they understand the reality and take some precautions above all.
3.2 PROCESSES
The process which is not implementing in the project is the discount process which is not part of
the requirement of the project. And there is an option given in the project whenever the price of
the product reduces admin will reduce the price by getting into edit option. Following are the
processes which implement in the project are
3.2.1.
Sign In Process
3.2.2.
Sign Up Process
3.2.3.
Purchase Process
3.2.4.
Order Process
3.2.5.
Shopping Cart Process
3.2.6.
Checkout Process
3.2.7.
Admin Process
3.2.8.
Confirmation Process
13
CHA
CHAPTER 3
online shopping, I can see some interconnections between them. By common sense, anyone who
Figure 3.2.1 Sign in process
User view the sign In page and enter user name and password .If the user name and
password are correct then system display the page
If the username and password are in correct then it show the message username/password
are incorrect
3.2.2 Sign Up Process:
Figure 3.2.2 Sign up process
In this process user have to register (sign Up) for this site and submit the required
information as needed.
System save the information and confirm the user to successfully to sign in
14
CHA
CHAPTER 3
3.2.1 Sign In Process:
Figure 3.2.3 Shopping cart process
In this process the shopping cart keep the track of the products which the user selected .
Before checkout if a user want to remove or change some quantity of product then user
can do it
3.2.3 Checkout Process:
Figure 3.2.3 Checkout process
This process starts when the user done with shopping cart process and user click on the
checkout button.
If the user logged In then he can buy the product give the shipment address and billing
address and give the payment online after the payment user receive the confirmation
email.
If the user not log In/Sign Up then user cant buy the product
15
CHA
CHAPTER 3
3.2.3 Shopping Cart Process:
Figure 3.2.4 Purchase Process
When user wants to buy the product user simply select the product and add the product to
shopping cart.
If user wants to buy more product he simply select more products and add to shopping
cart and change the quantity of products according to his needs and then checkout .
3.2.5 Order Process:
Figure 3.2.5 Order purchase
After selecting the product user wish to purchase the product and proceed to the shopping
cart and checkout.
After checkout user give the shipment address and billing address and give the payment
online after the payment user receive the confirmation email.
16
CHA
CHAPTER 3
3.2.4 Purchase Process:
Figure 3.2.6 Admin process
In this process the admin can add, edit the product detail, activate, deactivate the product
also
Admin can block and unblock the user
3.2.7 Confirmation Process:
Figure 3.2.7 Confirmation process
After the shipment address, billing address and online payment the user receive the email as
confirmation from system about the recent buy from the user
17
CHA
CHAPTER 3
3.2.6 Admin Process:
3.3 METHODOLOGY
The waterfall model implement in the project. The waterfall model is a sequential design process
downward through the phases of Requirement, Designing, Implementation, Testing and

Maintenance.
3.3.1 ADVANTAGES OF WATERFALL MODEL
It is very simple and easy model to use
In this model when the phases are completed it do not overlap
In each phase of this model it has specific deliverables and review process
This model works well for small projects where requirements are understood
3.3.2 DISADVANTAGES OF WATERFALL MODEL
No working software is produced until late during lifecycle
High amount of risk and uncertainty involved
Its not a good model for object oriented and complex projects
Poor model for long and ongoing projects
18
CHA
CHAPTER 3
which used in software development process in which progress is seen as flowing steadily
CHAPTER 3
3.3.3 PHASES OF WATERFALL MODEL
Figure 3.3.3 Waterfall Model
3.3.3.1 REQUIREMENTS
In this phase we gather the data for the project, analysis the user (dgs) needs and developed their
requirement. Create the functional requirement document known as SRS (Software Requirement
Specification) for the user (dgs Software House) needs
3.3.3.2 DESIGN
For high-level design we focus on system architecture and design. It provide overview of
solution platform, system, product and services .For low-level design software components are
designed. It define actual logic for each and every component of system
3.3.3.3 TESTING
In this phase once coding is complete we integrate data and design. For testing we did white box
testing and quality assurance testing. Testing software were also used for load testing and
performance testing for the system
19
CHA
3.3.3.4 IMPLEMENTATION
After the some integration and testing process we implement our system into production
3.4 SDLC (System Development Life Cycle)

Planning
Data
Requirement
Designing
Development
Integration &
Testing
Implementation
Maintenance
Figure 3.4 SDLC diagram
3.4.1.
Planning
3.4.2.
Data requirement and analysis
3.4.3.
Designing
3.4.4.
Development
3.4.5.
Integrate and Testing
3.4.6.
Implementation
3.4.7.
Maintenance
3.4.1 PLANNING
In this project we developed a plan first to gather data and made some documents of the project
which required explanation of the project, advantages of this project and mockup plan, uml
diagrams, templates and structure. Second to start the development and implementation and last
the integration and testing to be done
20
CHA
CHAPTER 3
environment and see its working properly and it worked properly
3.4.2 DATA REQUIREMENT & ANALYSIS

In this phase we gather the data for the project, analysis the user (Digital global services DGS)
SRS (Software Requirement Specification) for the user (dgs) needs
3.4.3 DESIGN
In this phase design has been made and according to the requirement the design had to be simple,
attractive and user friendly and HCI (Human Computer Interaction) principle has also been
followed in this design. For high-level design we focus on system design and architecture. It
provide overview of solution platform, system, product and services. For low-level design
software components are designed. It defines actual logic for each and every component of
system. Class diagram with all methods and relation between the classes comes under low level
diagram
3.4.4 DEVELOPMENT
In development we convert a design into complete information system which acquire some
system for which we install Xampp server, aptana studio. For Database we use My SQL. And for
coding HTML code, PHP code and codeingniter framework were used for the development.
3.4.5 INTEGERATE & TESTING

In this phase we integrate data and design. For testing we did white box testing known as unit
testing and quality assurance testing. Testing software were also used for stress testing,
performance testing and load testing for the system
21
CHA
CHAPTER 3
needs and developed their requirement. Create the functional requirement document known as
3.4.6 IMPLEMENTATION
After the some integration and testing process we implement our system into production
CHAPTER 3
environment and see its working properly and it worked properly
3.5 CASE STUDIES

3.5.1 CASE STUDY
Our Client Says...

The development team has done a
fantastic job. We are now able to
manage all the problems before it's
too late.
Figure 3.5.1 Shopping cart
Client:
Ahmed Rashid
Location:
Karachi, Pakistan
Project Name:
Software Process Implementation In E-Commerce Portal
Technology used: Php , My Sql
3.5.1.1 PROBLEM
Client is a Business man , He own one website which is on online shopping to grow his business
via internet as todays most of the economy is running through internet (i.e E-Commerce).
Users are facing problem in his website, quantity of a product in shopping cart was not updating
in the database automatically. It only update when user change the quantity and press update
button.
22
CHA
Client ask to remove update button from shopping cart and ask to put drop box in quantity so
3.5.1.2 SOLUTION
The process started with a series of requirement gathering sessions, and once we felt we had
enough information, a sketch based version of the system was developed to demonstrate how we
felt it would function. Following a number of refinements, we were able to take a detailed
specification through to development and delivered a working solution within a relatively short
timeframe. By using php and My Sql database, the system can be accessed from any internet
browser, whether it's in or out of the office and has made a dramatic improvement to this part of
the business.
3.5.2 CASE STUDY

3.5.2.1 INTRODUCTION
The shopping cart which keep the track of the products which the user selected. Before checkout
if a user wants to remove or change some quantity of product then user can do it in shopping
cart.
3.5.2.2 PROBLEM ANALYZE PHASE
Users are facing problem in his website, quantity of a product in shopping cart was not updating
in the database automatically. It only update when user change the quantity and press update
button.
3.5.2.3 REQUIREMENT PHASE
To remove update button from shopping cart and to put drop box in quantity so when user
change quantity it automatically update in database.
23
CHA
CHAPTER 3
when user change quantity it automatically update in database.
3.5.2.4 DESIGN PHASE

In this phase design of shopping cart has been made and according to the requirements. The
design had to be simple, attractive and user friendly and HCI (Human Computer Interaction)
CHAPTER 3
principle has also been followed in this design.
Figure 3.5.2.4 Shopping cart design
3.5.2.5 IMPLEMENTATION PHASE

After the development, integration and testing process we implement our system into production
environment according to the requirement and see its working properly and it worked properly
3.5.2.6 VERIFICATION PHASE
In this phase we integrate data and design. For verification we did white box testing known as
unit testing and quality assurance testing. Testing software were also used for stress testing,
performance testing and load testing for the system
3.5.2.7 DEVELOPMENT PROCESS
In shopping cart development we convert a design into complete information system which
acquire some system for which we install Xampp server, Aptana studio. For Database we use My
Sql. and for coding HTML code, PHP code and codeingniter framework were used for the
development.
We conjecture that the well-thought-out requirements document was the key element. Our
familiarity with the product domain must also have contributed to the clarity of the requirements.
24
CHA
This solid foundation allowed us to come up with a carefully thought-out analysis, which in its
turn provided the support for a complete design. Marketing contributed by supplying only a
minimal number of functionality changes during the development process. The well-thought-out
Estimates for the reuse fraction of the output of the analysis, design, and implementation phases
range between 80% and 100%.
Whether the maintenance cost for this system will be reduced is as yet unknown.
3.5.3 CASE STUDY

3.5.3.1 INTRODUCTION
The shopping cart which keep the track of the products which the user selected. Before checkout
if user want to remove or change some quantity of product then user can do it in shopping cart.
3.5.3.2 RESEARCH QUESTION
Our questions focus on two key sets of properties of development. It is remarkable that large
numbers of people manage to work together successfully to create high quality, widely used
products. Our first set of questions (Q1-Q2) are aimed at understanding basic parameters of the
process by which shopping cart came to exist.
Q1: What was the process used to develop Shopping cart?

In answer to this question, we construct a brief qualitative description of shopping cart
development.
Q2: How many people wrote code for new shopping cart functionality? How many people
Report the problems? How many people repaired defects?
We want to see how large the shopping cart development is, and identify how many people
actually occupied each of these traditional development and support roles.
25
CHA
CHAPTER 3
analysis and design accommodated these modifications readily.
3.5.3.3 SHOPPING CART DEVELOPMENT

In shopping cart development we convert a design into complete information system which
acquires some system for which we install Xampp server, Aptana studio. For Database we use
development.
We conjecture that the well-thought-out requirements document was the key element. Our
familiarity with the product domain must also have contributed to the clarity of the requirements.
3.5.3.4 PROBLEM
Our sets of questions (Q1-Q2) are aimed at understanding the problem of shopping cart which
came to exist.
Q1: What are the problems identify in the Shopping cart?

The problem that identify in the shopping cart was the quantity of a product in shopping cart was
not updating in the database automatically. It only update when user change the quantity and
press update button.
Q2: What is the solution of the problem?

The solutions are to remove update button from shopping cart and to put drop box in quantity
so when user change quantity it automatically update in database before checkout.
26
CHA
CHAPTER 3
MySql. And for coding HTML code, PHP code and codeingniter framework were used for the
CHAPTER 3
RESULT
Figure 3.5.3.3 Shopping cart
3.5.3.4 DATA SOURCE

The source which use in the development is php which is an open source
27
CHA
CHAPTER 4
SOFTWARE REQUIREMENT ANALYSIS
_____________________________________________________________________________
28
CHA
CHAPTER 4
_____________________________________________________________________________
E-Commerce stands for electronic commerce. It has two panels user and administrator. User can
sign up/login, buy, add, edit, delete items in shopping cart. Admin can add, activate/deactivate
product, reset password
Windows Operating System Windows 7/XP/8/8.1
XAMP Server
My SQL Database Management System
Aptana studio and PHP Designer.
4.2 CATEGORIES OF REQUIREMENT

There are two main categories of requirement were identified in this project
- Functional requirement
- Non-Functional requirement
4.2.1 FUNCTIONAL REQUIREMENT
4.2.1.1 SYSTEM MODULES AND THEIR FUNCTIONALITIES:
Following are the main module of the system:
4.2.1.1.1.
User
4.2.1.1.2.
Administrator
4.2.1.1.1 User:
User can simply signup/login into web self-care portal view site, buy, add, edit,
delete items in shopping cart
29
CHA
CHAPTER 4
4.1 SOFTWARE REQUIREMENTS:
4.2.1.1.2 Administrator:
Admin can add, activate/deactivate product, reset password of customer confirm
and cancel order of customer
4.2.1 NON-FUNCTIONAL REQUIREMENT
Secure access of the confidential data known as customers details.
The system should be available when needed any time.
Easy to maintain
The system should be portable to different platforms
4.3 CASE STUDIES OF SOFTWARE ANALYSIS

4.3.1 CASE STUDY:
A customer visits the online shopping portal. A customer may buy item or just visit the page and
logout. The customer can select a segment, then a category, and brand to get the different
products in the desired brand. The customer can select the product for purchasing. The process
can be repeated for more items. Once the customer finishes selecting the products the cart can
be viewed. If the customer wants to edit the final cart it can be done here. For final payment the
customer has to login the portal, if the customer is visiting for the first time he must register with
the site, else the customer must use the login page to proceed. Final cart is submitted for payment
and card details and address are confirmed by the customer
30
CHA
CHAPTER 4
Following are the non-functional requirements are
CHAPTER 4
Figure 4.3.1- Shopping Portal
31
CHA
4.3.2 CASE STUDY: (Case study of user)

Users when enter the site and view the various products in different category. Authentication
of the user is done for the payment of the shopping done. User can browses through the products
available in the shop, can select some of them and put into the shopping cart. User can anytime
change the items in the cart either by adding new items or by removing existing items. User
proceeds towards the payment counter. Finalize product list of items he finally wish to buy and
4.3.3 CASE STUDY: (Case study of admin)

Admin manage the site pages, user accounts and products. Update the details of the different
category of product. Admin can add, edit the product detail, activate, deactivate the product and
block and unblock the user
Figure 4.3.3 Admin
32
CHA
CHAPTER 4
make the final payment
4.3.4 CASE STUDY: (Case study of shopping cart)

When user buys the product user add the product to the shopping cart. The shopping cart which
keep the track of the products which the user selected. Before checkout if a user wants to remove
or change some quantity of product then user can do it in shopping cart.
4.3.4.1 PROBLEM DURING DEVELOPMENT
While development there was a problem quantity of a product was not updating. Because of this
bug the of the product was also not updating
CHAPTER 4
4.3.4.2 WORKING OF SHOPPING CART
Figure 4.3.4 Shopping Cart
33
CHA
4.3.5 CASE STUDY: (Case study Sign In and Sign Up)

User views the sign in page and enter user name and password .If the user name and password
are correct then system display the page. If the username and password are in correct then it
shows the message username/password are incorrect. If the user is new and wants to buy the
product then user have to register (sign up) for this site and submit the required information as
needed. System save the information and confirm the user successfully to sign in.
4.3.5.1 PROBLEM DURING DEVELOPMENT
user was not automatically login user had to enter username and password to login. Later that
bug was observed and the developer fixed it now after the signup process user automatically
login
4.3.5.2 WORKING OF SIGN IN & SIGN UP
Figure 4.3.5 Sign In and Sign Up
34
CHA
CHAPTER 4
There was a bug when user sign Up and fill the requirement which required the. After signup
4.3.7 CASE STUDY: (Case study of product catalogue & detail)

When user wants to view the product detail then user can view through the product categories
any product he wants to see. If users view the product from the home page user simply select
CHAPTER 4
the product and view the product detail also. User can see the product detail from any page
Figure 4.3.7 Product Catalogue & detail
35
CHA
_____________________________________________________________________________
SOFTWARE DESIGN
____________________________________________________________________________
36
CHA
CHAPTER 5
CHAPTER 5
5.1 System Architecture Diagram

A system architecture diagram is an alternate way to show s scenario. This type of diagram shows object
CHAPTER 5
interactions organized around the objects and their links to each other.
Fig. 5.1 System Architecture Diagram

In Fig. 5.1, it shows the object interaction in how they linked to each other manner, first user
provides its username and password then its verified by the server and after that user can able to
do shopping
37
CHA
5.2 DATA FLOW DIAGRAM (DFD)

Data Flow Diagram (DFD) is a graphical representation of a data flow in a system.
Admin
User
Manage site
users and
Products
Login/Sign Up
View Product
Buy Product
Fig. 5.2 Data Flow Diagram

In Fig. 5.2, it show the data flow in system, first user login into the system after that he/she has
two options (i)User has to login or signup to do shopping (ii)Admin can manage site
38
CHA
CHAPTER 5
Select
Product
5.3 CLASS DIAGRAM

The class diagram is a static diagram. It represents the static view of an application. Class
diagram is not only used for visualizing, describing and documenting different aspects of a
system but also for constructing executable code of the software application. The class diagram
is the main building block of object oriented modeling. It is used both for general conceptual
modeling of the systematic of the application, and for detailed modeling translating the models
into programming code. Class diagrams can also be used for data modeling. The classes in a
class diagram represent both the main objects, interactions in the application and the classes to be
CHAPTER 5
programmed
Fig. 5.3 Class Diagram

In Fig. 5.3, it shows six classes of the system
39
CHA
(i)
User class which is responsible to add user, update user record, delete user record and change
user password.
Administrator class which is responsible to deactivate user account and reset user password.
(iii)
Product history which is responsible for users product history.
(iv)
Shopping cart class which is responsible to add and delete the product.
(v)
Order class is used place order of customer
(vi)
Order detail class is responsible for detail of products
CHAPTER 5
(ii)
40
CHA
5.4 OBJECT DIAGRAM

Object diagram shows a snapshot of instances of things in class diagrams. Similar to class
diagrams, object diagrams show the static design of system but from the real or prototypical
CHAPTER 5
perspective.
Fig. 5.4 Object Diagram
Fig 5.4 shows the static design of system but from the real or prototypical perspectives
41
CHA
5.5 DEPLOYMENT DIAGRAM

The Deployment Diagram also helps to model the physical aspect of an Object-Oriented
software system. It models the run-time configuration in a static view and visualizes the
CHAPTER 5
distribution of components in an application
Fig. 5.5 Deployment Diagram
Fig 5.5 shows the hardware configurations together with the software components that lived on.
42
CHA
5.6 USE CASE

A Use-case diagrams are usually referred to as behavior diagrams used to describe a set of
actions (use cases) that some system or systems (subject) should or can perform in collaboration
with one or more external users of the system (actors). Each use case should provide some
observable and valuable result to the actors or other stakeholders of the system. Use-case
diagram contains the actor and the use case symbols, along with connection lines. Actors are
similar to external entities; they exist outside the system. The term actor refers to a particular role
of a user of the system. The main purpose of a use-case diagram is to show what system
functions are performed for which actor. Roles of the actors in the system can be depicted.
Used to gather requirements of a system.
Used to get an outside view of a system.
Identify external and internal factors influencing the system.
Show the interacting among the requirements are actors
43
CHA
CHAPTER 5
The purposes of use case diagrams can be as follows:
In fig 5.6 shows (i) New customer can search products, register account then purchase product (ii) Normal
customer can simply login then purchase product (iii) Admin can manage site and manage user account
44
CHA
CHAPTER 5
Fig.5.6 Use-Case Diagram (High Level Diagram)
5.6.1User Management Use Case Diagram

User management use case shows that only registered user can buy products, update profile. Non
CHAPTER 5
registered user can only browse the products but cannot buy anything
Fig.5.6.1 Use-Case Diagram (User Management Use Case Diagram)

In fig 5.6.1 shows (i) Register user can sign in, update profile and purchase product (ii) Non Register user
has to sign up to purchase product
45
CHA
5.6.2 Admin Use Case Diagram

Admin use case diagram shows that admin can manage user account, manage products and
CHAPTER 5
manage site
Fig.5.6.2 Use-Case Diagram (Admin Diagram)

In fig 5.6.2 shows that admin can manage site, products and manage user accounts
46
CHA
5.7 Sequence Diagram

A sequence diagram is an interaction diagram that shows how processes operate with one
another and in what order. It is a construct of a Message Sequence Chart. It shows object
interactions arranged in time sequence. It depicts the objects and classes involved in the scenario
and the sequence of messages exchanged between the objects needed to carry out the
functionality of the scenario. Sequence diagrams are typically associated with use case
realizations in the Logical View of the system under development.
5.7.1 Non-Register user sequence diagram
In non-register user sequence diagram user has to first sign up for the site than user can purchase
CHAPTER 5
product
Fig. 5.7.1 Sequence Diagram (Non Register user sequence diagram)

In Fig. 5.7.1, it shows object interactions of sequence, first new user have to sign up into the system then
he/she will able to buy the product
47
CHA
5.7.2 Register user sequence diagram
CHAPTER 5
In register user sequence diagram that user has simply log in for purchasing the product
Fig. 5.7.2 Sequence Diagram (Register user sequence diagram)

In Fig. 5.7.2, it shows object interactions of sequence, first registered user dont have to sign up into the
system user can only login then he/she will able to buy the product
48
CHA
5.7.3 Admin sequence diagram
CHAPTER 5
In admin sequence diagram that admin can manage products, manage user account also enable or
disable account.
Fig. 5.7.3 Sequence Diagram (Register user sequence diagram)

In Fig. 5.7.3, it shows admin can add/edit/delete product and reset user password and condirm order of
product
49
CHA
5.8 Activity Diagram

Activity diagrams represent workflows in a graphical way. They can be used to describe business
workflow or the operational workflow of any component in a system. Sometimes activity
diagrams are used as an alternative to State machine diagrams.
Activity diagrams are constructed from a limited number of shapes, connected with arrows. The
Rounded rectangles represent actions;
Diamonds represent decisions;
Bars represent the start (split) or end (join) of concurrent activities;
A black circle represents the start (initial state) of the workflow;
An encircled black circle represents the end (final state).
Arrows run from the start towards the end and represent the order in which activities
happen.
50
CHA
CHAPTER 5
most important shape types:
CHAPTER 5
Fig. 5.8 Activity Diagram
In Fig. 5.8 This activity diagram is used to identify the user and then granting him the selected
privileges
51
CHA
5.9 FLOWCHART
A flowchart is a type of diagram that represents an algorithm, workflow or process, showing the
CHAPTER 5
steps as boxes of various kinds, and their order by connecting them with arrows.
Fig. 5.9 Flowchart

In this Fig 5.9, shows the user has to sign in or sign up for the site to do the shopping
52
CHA
5.10 ER DIAGRAM
An entity-relationship diagram is a data modeling technique that creates a graphical
representation of the entities in a system, and the relationships between entities. The main
components of ER models are entities (things) and the relationships that can exist among them,
and databases.
Designs are pictures called entity-relationship diagram.
Fairly mechanical ways to convert E.R diagrams to real implementations like relational
databases exist
To create an accurate reflection of the real world in a database.
It gives us an intermediate step from which it is easy to define a database
53
CHA
CHAPTER 5
The purposes of entity relationship (E.R) diagrams can be as follows:
CHAPTER 5
Fig. 5.10ER Diagram
54
CHA
5.11 COLLABORATION DIAGRAM

A collaboration diagram resembles a flowchart that portrays the roles, functionality and behavior
CHAPTER 5
of individual objects as well as the overall operation of the system in real time.
Fig. 5.11 Collaboration Diagram

In Fig 5.11 this diagram shows the relationship between the object are shown as the lines
connecting the rectangle
55
CHA
5.12 COMPONENT DIAGRAM

The Component Diagram helps to model the physical aspect of an Object-Oriented software
system. It illustrates the architectures of the software components and the dependencies between
Fig. 5.12 Component Diagram

In Fig 5.12 shows the components are wired together to form larger component of the shopping system
56
CHA
CHAPTER 5
them
5.13 ASSOCIATION MODEL

Association diagram is a class diagram but unless class diagram which provides an overview of
the target system by describing the objects and classes inside the system, Association diagram
tells the relationships between them.
In this Fig 5.13 it tells the relationship between the login, shopping cart, checkout ,payment and email
confirmation
5.14 STATE CHART DIAGRAM

State chart diagram can show the different states of an entity also how an entity responds to
various events by changing from one state to another.
Fig. 5.14 State Chart Diagram
In this Fig 5.14 it shows the state of different nodes that user has to first login then select the
item to shopping cart then user can purchase the item
57
CHA
CHAPTER 5
Fig. 5.13 Association Model
5.15 COMMUNICATION DIAGRAM

Similar to Sequence Diagram, the Communication Diagram is also used to model the dynamic
Fig. 5.15 Communication Diagram

In Fig 5.15 shows the collaboration of objects rather than the time sequence
58
CHA
CHAPTER 5
behavior of the use case.
_____________________________________________________________________________
CHAPTER 6
Algorithm And Its Complexity
CHAPTER 6
_____________________________________________________________________________
59
CHA
6.1 Algorithm and Pseudo code

A computer program can be viewed as an elaborate algorithm. In mathematics and
computer science, an algorithm usually means a small procedure that solves a recurrent
problem
Pseudo code (pronounced SOO-doh-kohd) is a detailed yet readable description of what a
computer program or algorithm must do, expressed in a formally-styled natural language
rather than in a programming language.
6.2 Complexity of Code

Cyclomatic complexity (or conditional complexity) is a software metric (measurement).
It was developed by Thomas J. McCabe, Sir. in 1976 and is used to indicate the
instructions.
A software fragment with a CCN value between 1-4 has low complexity.
A complexity value between 5-7 is moderate and still easy to understand.
Everything between 6-10 has a high complexity, while everything greater 10 is very
complex and hard to understand.
6.3 Dry Run Algorithm

A dry run is a testing process where the effects of a possible failure are intentionally mitigated.
For example, an aerospace company may conduct a "dry run" test of a jet's new pilot ejection
seat while the jet is parked on the ground, rather than while it is in flight.
In computer programming, a dry run is a mental run of a computer program, where the computer
programmer examines the source code one step at a time and determines what it will do when
run. In theoretical computer science, a dry run is a mental run of an algorithm, sometimes
expressed in pseudo code, where the computer scientist examines the algorithm's procedures one
60
CHA
CHAPTER 6
complexity of a program. It is a quantitative measure of the complexity of programming
step at a time. In both uses, the dry run is frequently assisted by a table (on a computer screen or
on paper) with the program or algorithm's variables on the top.
The usage of "dry run" in acceptance procedures (for example in the so-called FAT = factory
acceptance testing) is meant as following: the factory - which is a subcontractor - must perform a
complete test of the system it has to deliver before the actual acceptance from the contractor side.
6.4 Search Algorithm:

1.) location = -1;
2.) while ((more than one item in list) and (haven't yet found target))
2.1) look at the middle item
2.2 ) if (middle item is target)
have found target
CHAPTER 6
else
2.3) if (target < middle item)
list = first half of list
2.4) else (target > middle item)
list = last half of list
end while
3) if (have found target)
location = position of target in original list
4) return location as the result
Pseudo Code:
location = -1;
first = 0;
last = number of items minus 1;
while ((number of items left to search >= 1) and (target not found))
middle = position of middle item, halfway between first and last
if (item at middle position is target)
61
CHA
target found
else
if (target < middle item)
search lower half of array next
last = middle - 1;
else
search upper half of array next
first = middle + 1;
end while
if (target found) (i.e., middle item == target)

location = position of target in array (i.e., middle)
6.4.1Complexity:
To evaluate search, count the number of comparisons in the best case and worst case. This
analysis omits the average case, which is a bit more difficult, and ignores any differences
between algorithms in the amount of computation corresponding to each comparison.
The best case occurs if the middle item happens to be the target. Then only one comparison is
needed to find it. As before, the best case analysis does not reveal much.
When does the worst case occur? If the target is not in the array then the process of dividing the
list in half continues until there is only one item left to check.
The following table 6.1 summarizes the analysis for searching algorithm.
62
CHA
CHAPTER 6
return location as the result
Model
Number of Comparisons
Comparisons as a function
(for n = 100000)
of n
Best Case
(Least/fewest Comparisons)
(target is middle item)
Worst Case
16
(Most comparisons)
(target not in array)
Log2n
Table 6.3
Complexity Representation in Big O:

Best Case:
O(1)
Worst Case:
O(log2n)
The running time of sorting is a linear function of the array size, r p + 1, and the distance of q
from p, q p. This is (r p + 1).
Graphical Representation:
5
4
3
2
1
0
1
9 10 11 12 13 14 15 16 17 18 19 20
O(1)
O(Log2n)
63
CHA
CHAPTER 6
Running Time Analysis
6.5 Login Check Algorithm

1. Start
2 Get username and password
3. Read username and password
4. If(username = database)
5. Start session, go to default redirect after login.
6. Let the person do whatever they want.
7. If( username = user)
then
GOTO Home page
9. Else if username belongs to Admin
CHAPTER 6
GOTO Admin ,GOTO view GOTO Edit.

Else return main page.
10. Exit
6.4.1 Pseudo code

PROGRAM userFirstLoginCheck
user dialing dialer
WHILE
Read user logined last session from database
END WHILE
IF(session found)
THEN
PRINT Users not first login
ELSE
PRINT Users first Login
Update user address in database
64
CHA
END IF
END
Complexity:
To evaluate search, count the number of comparisons in the best case and worst case. This
analysis omits the average case, which is a bit more difficult, and ignores any differences
between algorithms in the amount of computation corresponding to each comparison.
The best case occurs if the middle item happens to be the target. Then only one comparison is
needed to find it. As before, the best case analysis does not reveal much.
When does the worst case occur? If the target is not in the array then the process of dividing the
CHAPTER 6
list in half continues until there is only one item left to check.
The following table 6.2 summarizes the analysis for login algorithm.
Model
Number of Comparisons
Comparisons as a function
(for n = 100000)
of n
Best Case
(Least/fewest Comparisons)
(target is middle item)
Worst Case
16
(Most comparisons)
(target not in array)

Table 6.2
Complexity Representation in Big O:

Best Case:
O(1)
Worst Case:
O(log2n)
65
CHA
Log2n
Running Time Analysis

The running time of sorting is a linear function of the array size, r p + 1, and the distance of q
from p, q p. This is (r p + 1).
Graphical Representation:
5
4
3
2
0
1
9 10 11 12 13 14 15 16 17 18 19 20
O(1)
O(Log2n)
66
CHA
CHAPTER 6
_____________________________________________________________________________
TESTING
_____________________________________________________________________________
67
CHA
CHAPTER 7
CHAPTER 7
7.0 TESTING:
Testing is the practice of making objective judgments regarding the extent to which the system
(device) meets, exceeds or fails to meet stated objectives.
There are two fundamental purposes of testing: verifying procurement specifications and
managing risk. First, testing is about verifying that what was specified is what was delivered: it
verifies that the product (system) meets the functional, performance, Design and implementation
requirements identified in the procurement specifications. Second, testing is about managing risk
for both the acquiring agency and the systems Vendor/developer/integrator.
The testing program is used to identify when the work has Been completed so that the contract
CHAPTER 7
can be closed, the vendor paid, and the system Shifted by the agency into the warranty and
maintenance phase of the project [31].
7.0.1 TYPES OF TESTING:
7.0.1.0 GRAY BOX TESTING
Testing to verify a product meets customer specified requirements. A customer usually does this
type of testing on a product that is developed externally.
7.0.1.1 BLACK BOX TESTING
Testing without knowledge is the internal workings of the item being tested. Tests are usually
functional.
68
CHA
7.0.1.2 COMPATIBILITY TESTING
Testing to ensure compatibility of an application or web site with different browsers, operating
syatem, and hardware platforms. Compatibility testing can be performed manually or can be
driven by an automated functional or regression test suite.
7.0.1.3 CONFORMANCE TESTING
Verifying implementation conformance to industry standards. Producing tests for the behavior of
an implementation to be sure it provides the portability, interoperability, and/or compatibility a
7.0.1.4 FUNCTIONAL TESTING
Validating an application or Web site conforms to its specifications and correctly performs all its
required functions. This entails a series of tests which perform a feature by feature validation of
behavior, using a wide range of normal and erroneous input data. This can involve testing of the
product's user interface, APIs, database management, security, installation, networking; etc
testing can be performed on an automated or manual basis using black box or white box
methodologies.
7.0.1.5 INTEGRATION TESTING
It is a testing in which the modules are combined and tested as a group. Modules are typically
code modules, individual applications, client and server applications on a network, etc.
Integration Testing follows unit testing and precedes system testing.
69
CHA
CHAPTER 7
standard defines.
7.0.1.6 LOAD TESTING
Load testing is a generic term covering Performance Testing and Stress Testing.
7.0.1.7 PERFORMANCE TESTING
Performance testing can be applied to understand your application or web site's scalability, or to
benchmark the performance in an environment of third party products such as servers and
middleware for potential purchase. This sort of testing is particularly useful to identify
performance bottlenecks in high use applications. Performance testing generally involves an
automated test suite as this allows easy simulation of a variety of normal, peak, and exceptional
CHAPTER 7
load conditions.
7.0.1.8 REGRESSION TESTING

Similar in scope to a functional test, a regression test allows a consistent, repeatable validation of
each new release of a product or Web site. Such testing ensures reported product defects have
been corrected for each new release and that no new quality problems were introduced in the
maintenance process. Though regression testing can be performed manually an automated test
suite is often used to reduce the time and resources needed to perform the required testing.
7.0.1.9 SMOKE TESTING

A quick-and-dirty test is a test that the major functions of a piece of software work without
bothering with finer details. Originated in the hardware testing practice of turning on a new piece
of hardware for the first time and considering it a success if it does not catch on fire.
70
CHA
7.0.2.0 STRESS TESTING

Testing conducted to evaluate a system or component at or beyond the limits of its specified
requirements to determine the load under which it fails and how. A graceful degradation under
load leading to non-catastrophic failure is the desired result. Often Stress Testing is performed
using the same process as Performance Testing but employing a very high level of simulated
load.
7.0.2.1 SYSTEM TESTING

Testing conducted on a complete, integrated system to evaluate the system's compliance with its
should require no knowledge of the inner design of the code or logic.
7.0.2.2 UNIT TESTING

Functional and reliability testing is an engineering environment. Producing tests for the behavior
of components of a product to ensure their correct behavior prior to system integration.
7.0.2.3 WHITE BOX TESTING

Testing based on an analysis of internal workings and structure of a piece of software. Includes
techniques such as branch testing and path testing. Also known as Structural Testing and Glass
Box Testing. By the analysis of Florida Institute of Technology, Quality Assurance Institute
Worldwide Annual Software Testing Conference the best testing for a web application is [33].
71
CHA
CHAPTER 7
specified requirements. System testing falls within the scope of black box testing, and as such,
7.1 PERFORMANCE TESTING

The goal of performance testing is not to find bugs, but to eliminate bottlenecks and establish a
baseline for future regression testing. To conduct performance testing is to engage in a carefully
controlled process of measurement and analysis. Ideally, the software under test is already stable
enough so that this process can proceed smoothly.
Performance testing is testing that is performed, to determine how fast some aspect of a
system performs under a particular workload.
It can serve different purposes like it can demonstrate that the system meets performance
criteria.
It can compare two systems to find which performs better. Or it can measure what part of
the system or workload causes the system to perform badly.
This process can involve quantitative tests done in a lab, such as measuring the response
time or the number of MIPS (millions of instructions per second) at which a system
CHAPTER 7
functions.
72
CHA
Fig 7.1.1
Failed unit tests tell which assert (file:line) failed, but not which validation resulted in the
failure.
Blue Line Shows the Users
In Failed Validation the User Line Shows that how many user use the application at a
time.
73
CHA
CHAPTER 7
Yellow Line Shows Failed Validations
Fig 7.1.2
Pink Line Shows Pages/steps/seconds

If your pages/steps/second for static content is high, then you may have reached the
hardware/configuration limits of your server.
If your pages/steps/second for your static content is low but dynamic content is high, then
your application or server configuration may be to blame.
Blue Line Shows Users
In Failed Validation the User Line Shows that how many user use the application at a
time.
74
CHA
CHAPTER 7
Fig 7.1.3
Brown Line Shows Response Transfer Speed
because it gives an unambiguous measure of speed of response. However, even having

two time constants complicates the issue.
Speed of response is an important measure of how quickly a system

responds. When you evaluate how well a system is performing you need to measure
speed of response with some metric. When you are designing a system you need to be
able to predict speed of response. Your goals for this lesson relate to that.
Given a system in which you need to predict speed of response.
Be able to predict speed of response using time domain methods.
Be able to predict speed of response using frequency domain methods.
75
CHA
CHAPTER 7
The concept of a time constant works - and works well - for first order systems

In Failed Validation the User Line Shows that how many user use the application at a time.
Description:
The Performance Graphs shows the performance of the system when the program runs. The fig
7.1.1 shows the failed validation process second fig 7.1.2 shows the request time to first process
third fig 7.1.3 shows the CPU performance and final graph shows the response time of the
system
Intel core i5 3.0GHZ
8 GB RAM
500 GB Hard Drive
Conclusion:
Execution time depends upon the following factors
Numbers of users
Speed
Files transfer rate
Speed of system
76
CHA
CHAPTER 7
Hardware Configuration:
RESPONSE TIME GRAPH+PERFORMANCE TESTING
Pages
The Page
Load
Time section
contains three tabbed
pages: With
Virtual
Users, Scroll
Chart and Chart by Region. These tabs show graphs with page load time statistics in different
modes. The sections below contain a detailed description of the tabbed pages and graphs
With Virtual Users Page
Scroll Chart Page
Chart by Region Page

CHAPTER 7
mentioned above.
With Virtual Users Page
This tab contains a graph that shows how the page load time and the number of virtual users
changed during the test run. Note that during the test run, you can view the same information
plotted in real in the Load time graph in Runtime Graphs.
Below is a sample image of the graph. It may be different for your website, for example, if you
used continuous load or a non-default load profile.
77
CHA


Red Line shows Bandwidth Out
Bandwidth out (Uploading speed) can take to 100 kbps to 1.2.Mbps
78
CHA
CHAPTER 7
Individual graph lines can be turned off and on by clicking the line name in the graph legend.To
see the exact value of a metric at a specific moment, however the mouse pointer over the needed
data point on the graph - the metric value will be shown in a tooltip.
Printing the Contents of the Report Panel
Note that Load UI Web shows the data shown in the graph in the tabular format. An appropriate
table is shown under the Page Load Time graph when you start printing the contents of the
Report panel, that is, when you click Print on the panel's toolbar.
Column
Description
Time
The time scale from 0 to the test duration, in one-second increments.
Page load The total page loading time (loading of all images, scripts, CSS files, and so
on) measured at the specified moment. Note that this value does not include
time
the think time simulated for pages.
Users
The number of virtual users running at the specified time moment.
More Information
For more information on working with the graphs and charts shown in the Report panel,
see viewing the reports charts & graphs.
79
CHA
CHAPTER 7
The above-mentioned table contains the following columns:
Scroll Chart Page

This tab contains a graph that shows how the page load time changed during the test run. Below

80
CHA
CHAPTER 7
is a sample image of the graph:
You can zoom into this graph in and out. You can also select the desired area of the graph and
then overlay it with another area. For more information on working with scroll graphs,
see Working with Scroll Graphs.
CHAPTER 7
Average Response Time in Load Testing
Conclusion:
Numbers of users
Speed
Files transfer rate
Speed of system
81
CHA
7.2 STRESS TESTING

Stress testing is a software testing activity that determines the robustness of software by testing
beyond the limits of normal operation. Testing conducted to evaluate a system or component at
or beyond the limits of its specified requirements to determine the load under which it fails and
how. A graceful degradation under load leading to non-catastrophic failure is the desired result.
Often Stress Testing is performed using the same process as Performance Testing but employing
CHAPTER 7
a very high level of simulated load.
Fig 7.2.1
Green Line shows Bandwidth Out

Bandwidth out is uploading speed which can take 12secconds if net speed is slow.

82
CHA
Fig 7.2.2
Green Line shows Bandwidth Out

Bandwidth out is uploading speed which can take 12secconds if net speed is slow.
Description:
Table 7.2.1 shows different parameters on which stress testing is performed but there are two
main parameters first one is uploading speed time which shows the time taken to execute and
second one is downloading speed which shows the record retrieve from database. Fig.7.2.2
shows all this activity is graph form.
Intel core2duo 2.0GHz
1GB RAM
80 GB Hard Drive
83
CHA
CHAPTER 7
Conclusion:
Size of the page
Number of images
Quality of the image
Number of data
Transfer speed of the server
Uploading speed of the internet
How large the database is
CHAPTER 7
84
CHA
7.3 LOAD TESTING

In the testing literature, the term "load testing" is usually defined as the process of exercising the
system under test by feeding it the largest tasks it can operate with. Load testing is sometimes
called volume testing, or longevity/endurance testing. [26]
Load testing is a type of non-functional testing.
A load test is type of testing which is conducted to understand the behavior of the
application under a specific expected load.
Load testing is performed to determine a systems behavior under both normal and at
peak conditions.
The popular load testing tools available also provide insight into the causes for slow
performance. There are numerous possible causes for slow system performance, including, but
not limited to, the following:
Application server
Database server
Network
Client-side processing
Load balancing between multiple servers
CHAPTER 7
Fig 7.3.1
85
CHA
Yellow Line Shows Average Page Duration
The duration of the Average Page duration period, expressed in format. Individual tests
within a load test might still be running when the load test finishes. During the cool-down
period, those tests can continue until they complete or the end of the cool-down period is
reached. By default, there is no cool-down period, and individual tests are terminated
when the load test finishes based on the Run Duration setting.
The maximum number of threshold violations to save for this load test. You can increase
this number if you have to, but doing this will also increase the size and processing time
of the load test result.
Pink Line Shows Minimum Page Duration
The minimum number of unique Web Load test request URLs on which to report results
in this load test. You can increase this number if you have to, but doing this will also
increase the size and processing time of the load test result.
86
CHA
CHAPTER 7
Red Line Shows Maximum Page Duration
Figure 7.3.1 shows the load testing perform on the system, there are two main columns in
it, first one is user which shows how many users are login into the system at the time of
testing and second important column is execution time which the time taken by the
CHAPTER 7
algorithm to analysis the picture
87
CHA
Fig 7.3.2
The primary goal of load testing is to define the maximum amount of work a system can
handle without significant performance degradation.
Figure.7.3.2 shows start time and end time in graph format.
88
CHA
CHAPTER 7
Green Line Shows the Passed Goals
Description:
Load testing is same as performance testing; the little difference in performance and load testing
is that load testing is done when more than one user accessing server at the same time. A load
test enables you to measure response times, throughput rates, and resource-utilization levels, and
to identify your applications breaking point, assuming that the breaking point occurs below the
peak load condition.
Intel core2duo 2.0GHz
1GB RAM
80 GB Hard Drive
Size of the page
Number of images
Quality of the image
Number of data
Transfer speed of the server
Uploading speed of the internet
How large the database is
89
CHA
CHAPTER 7
Conclusion:
7.4 UNIT TESTING

Unit testing is a white box testing. In white box testing method by which individual units
of source code, sets of one or more computer program modules together with associated control
data, usage procedures, and operating procedures are tested to determine if they are fit for use
Web-Interface
Bug Condition(H/L)
Login
Fix
Count
Fix
Sign Up
Fix
Shipment Address
Fix
Billing Address
Fix
Shipment Method
Fix
Table 7.4 Unit Testing
Fig 7.4.1
Fig 7.4.2
90
CHA
Fix/Notfix
CHAPTER 7
S-no
Fig 7.4.3
Sign up bug has been fix
Fig 7.4.4
.
Fig 7.4.5
Billing address has been fix
Fig 7.4.6
Shipment address has been fix
91
CHA
CHAPTER 7
Shipment address has been fix
In the context of performance testing, a unit test is any test that targets a module of code where
that module is any logical subset of the entire existing code base of the application, with a focus
on performance characteristics. Commonly tested modules include functions, procedures,
routines, objects, methods, and classes. Performance unit tests are frequently created and
conducted by the developer who wrote the module of code being tested
No of Bugs in graphical Form

12
6
No of Bugs in graphical Form
4
0
Login
Count
Sign Up Shipment Billing Shipment

Address Address Method
Figure 7.4.7Unit testing Bugs Graph
92
CHA
CHAPTER 7
10
Description:
Table shows different forms on which unit testing is performed and describes the bugs
conditions and also defines that are fixed or not fixed.
Intel core2duo 2.0GHZ
1GB RAM
80 GB Hard Drive
Conclusion:
the bugs, there are numbers of bugs which are fix and shown in figure 7.4.7. The biggest
benefits by doing unit testing are
It reduces the level of bugs in production code. .
Automated tests can be run as frequently as required.
Unit testing makes it easier to change and refactor code.
Unit Testing can improve the design of code especially with Test-Drive
93
CHA
Development.
CHAPTER 7
Unit test also known as white box testing .It refectories the code and by doing unit testing it fix
_____________________________________________________________________________
CHAPTER 8
CONCLUSION
CHAPTER 8
_____________________________________________________________________________
94
CHA
After careful observations, it has come to my conclusion that e-commerce has undeniably
become an important part of our society. The World Wide Web is and will have a large part in
our daily lives. It is therefore critical that small businesses have their own to keep in competition
with the larger websites. Since web developers have lowered down the prices for their services, it
has become more affordable for small businesses to use the World Wide Web to sell their
products. Although there are negative aspects of e-commerce, small businesses have tried to
accommodate to the needs of the consumers. For example, one of the negative aspects of ecommerce is that consumers lack the advice and guidance of sellers, to accommodate that, they
have customer service through the phone of online to answer any questions. It is also important
to note that e-commerce does not benefit all small companies equally. How much revenue a
business gets from e-commerce depends on what kind of service it gives. For example, most
people would like to try on clothes before they buy them, so it probably would not benefit a
small business that sells clothes as much as a small business that sells home supplies or specialty
books. Nevertheless, e-commerce does benefit any business even in small ways. This is why it is
crucial to understand how e-commerce affects small businesses because it is becoming such a
huge part of how society functions that it affects the economy greatly and whatever happens to
the economy affects us. This is why is it important to understand this subject because in the long
E-commerce is an effective and efficient way of doing business. It can not only offer a wide
range of functionality to compete with or complement the physical trade but also brings with it
the added advantages of convenience, presentation and security.
. There are benefits of the project are

Persistent connection with customers
New value for customers
Access to new customers
95
CHA
CHAPTER 8
run, it will affect all of us.
_____________________________________________________________________________
CHAPTER 9
FURTHER
ENHANCEMENT AND RECOMMENDATIONS
CHAPTER 9
_____________________________________________________________________________
96
CHA
This project Software Process Implementation In E-Commerce Portal is working

fine and accurately with the hardware mention earlier in 2nd chapter but there are some
areas in the project which needs further enhancements and modification. The area which
is listed below.
- The design of our web application is according the HUMAN COMPUTER

INTERACTION rule and very much user friendly. But there is little need improvement
CHAPTER 9
of shopping cart design.
97
CHA
_______________________________________
CHAPTER 10
REFERENCES/BIBLIOGRAPHY
CHAPTER 10
_______________________________________
98
CHA
[1]. Arnold, Mark J.; Kristy E. Reynolds; Nicole Ponderc; Jason E. Lueg (August
2005)."Customer delight in a retail context: investigating delightful and terrible shopping
experiences". Journal
of
Business
Research 58 (8):
1132
1145.doi:10.1016/j.jbusres.2004.01.006. Retrieved 3 July 2012.

[2]. Jump up^ Martin, Brett A. S. (2012), "A Strangers Touch: Effects of Accidental
Interpersonal Touch on Consumer Evaluations and Shopping Time", Journal of Consumer
Research, 39 (June), 174-184.
[3]. M. Harada, K. Hamashima, K. Sato, and Y. Tanada, A study on personal identification by
combination of partial face-images," Technical Report of IEICE, PRU95-212, pp. 13-18,
1996.
[4]. P. Stucki, \Faces, skulls, and models anoverview," Proceedings of International
Workshopon Automatic Face- and Gesture-Recognition, pp. 1, 1995.
[6].The structure of phenotypic personality traits. Goldberg, Lewis American Psychologist, Vol
48(1), Jan 1993, 26-34. http://dx.doi.org/10.1037/0003-066X.48.1.26
[7].LR Goldberg - American psychologist, 1993 - psycnet.apa.org.
[8].The Human Resources Scorecard: Measuring the Return on Investment (Improving Human
Performance)Jack J. Phillips PhD in Human Resource Management., Ron Stone,Patricia Phillips
[9].The Chief Learning Officer: Driving Value within a Changing Organization through
Learning and Development (Improving Human Performance) Tamar Elkeles, Jack J. Phillips
PhD in Human Resource Management.
99
CHA
CHAPTER 10
[5]. H Aldrich, C Zimmer - Research Reference in Entrepreneurship, 1986 - papers.ssrn.com
[10]. The ROI Field book: Startegies for implementing ROI in H.R and training
Patricia
Phillips, Jack J. Phillips PhD in Human Resource Management., Ron Stone, Holly Burkett M.A.
SPH.R
[11].John, O. P., Neumann, L. P., & Soto, C. J. (2008). Paradigm Shift to the Integrative BigFive Trait Taxonomy: History, Measurement, and Conceptual Issues. In O. P. John, R. W.
Robins, & L. A. Pervin (Eds.), Handbook of personality: Theory and research (pp. 114-158).
New York, NY: Guilford Press.
[12].Measelle, J. R., John, O. P., Ablow, J. C., Cowan, P. A., & Cowan, C. P. (2005). Can
children provide coherent, stable, and valid self-reports on the Big Five dimensions? A
longitudinal study from ages 5 to 7. Journal of Personality and Social Psychology, 89, 90-106.
[13].Helson, R., Kwan, V. S. Y., John, O. P., & Jones, C. (2002). The growing evidence for
personality change in adulthood: Findings from research with personality inventories. Journal of
[14]. http://pdepend.org/documentation/software-metrics/cyclomatic-complexity.html. A saying

by
Mason
Holloway.
[http://www.astd.org/Education/Programs/Human-Performance-
Improvement-Programs]
[15].Srivastava, S., John, O. P., Gosling, S. D., & Potter, J. (2003). Development of personality
in early and middle adulthood: Set like plaster or persistent change? Journal of Personality and
Social Psychology, 84, 1041-1053.
[16] Online Educational web-app that provide plenty of online courses and educational material
http://online.stanford.edu/courses
100
CHA
CHAPTER 10
Research in Personality, 36, 287-306.
[17].BA Kitchenham, SL Pfleeger, LM Pickard - Software , 2002 - ieeexplore.ieee.org 2000

Speak Easy Software Failures in Hiding, META Group Research Publication - Bohner -1999.
1, DFAS on the XML Road to Better Interoperability, White paper for Defense Finance
and Accounting Service - Bohner 2001, the researcher conducting case studies, for reviewers
of case study manuscripts and for readersof case study papers.P Runeson, M Hst Empirical software engineering, 2009 Springer
[19].RL Glass, I Vessey, V Ramesh - Information and Software technology, 2002 Elsevier
[20] http://www.slideshare.net/min22laura/balanced-scorecard-in-human-resource-management
http://en.wikipedia.org/wiki/Human_performance_technology
[21].Michael Jackson; Engineering and Software; in Bashar Nuseibeh and Pamela Zaveeds,
Software Requirements and Design: The Work of Michael Jackson; Good Friends Publishing
[22].Formalism and Intuition in Software Engineerings in JrgenMuench and Klaus Schmideds,

Perspectives on the Future of Software Engineering: a Festschrift in Honors of Dieter Rombach,
Springer verlag 2013.
[23].(UML)one
that
harnesses
insights
and
makes
them
useful
for
communicating across a wide range of research groups. JJ Odell, HVD Parunak, B Bauer Agent-oriented software engineering, 2001 Springer.
[24].B Bauer, JP Mller, J Odell - Agent-oriented software engineering, 2001 - cin.ufpe.br
101
CHA
CHAPTER 10
Company, Chatham NJ, USA, 2010
[25].UML for ontology development P Kogut, S Crane field, L Hart, M Dutra - The
Knowledge , 2002 - Cambridge Univ Press
[26].From UML activity diagrams to Stochastic Petri nets: application to software performance
engineering JP Lpez-Grao, J Merengue, J Campos - ACM SIGSOFT software , 2004 dl.acm.org
[27]. Simple diagnostic tests for spatial dependence L Anselin, AK Bera, R Florax, MJ Yoon Regional science and urban , 1996 Elsevier
[28]. Qualitative research methods for the social sciences BL Berg, H Lune - 2004 - sisis.rz.htwberlin.de and Categories 350 Classes and Categories 351 Discourse Analysis and Content
Analysis 352 Open Coding 353 Coding Frames 356 A Few More Words on Analytic Induction
358
[29]. Prior to 2012, PLTA was published by the Language Testing Research Centre at the
University of Melbourne under the name, Melbourne Papers in Language Testing. The full
be downloaded, can be found at the MPLT Back Issues web page.

[30].The test of significance in psychological research.DBakan - Psychological bulletin, 1966 psycnet.apa.org
[31]. http://tmcpfs.ops.fhwa.dot.gov/cfprojects/uploaded_files/Final%20Q&A.pdf
[33].Exploratory Testing, Cem Kaner, Florida Institute of Technology, Quality Assurance
Institute Worldwide Annual Software Testing Conference, Orlando, FL, November 2006.
102
CHA
CHAPTER 10
catalogue of back issues of Melbourne Papers in Language Testing, where individual papers can
_____________________________________________________________________________
CHAPTER 11
ANNEXURES
ANNEXURE
_____________________________________________________________________________
103
CHA
______________________________________________________________________________
11.1 PROJECT PROPOSAL
ANNEXURE
______________________________________________________________________________
104
CHA
SOFTWARE PROCESS IMPLEMENTATION IN ECOMMERCE PORTAL
Name
Mohammad Ahmer Hussain
Enrolment
09B-006-BS
Name
Anas Ul Haq Qureshi
Enrolment
10B-097-BS
Name
Syed Nabeel Junaid
Enrolment
07A-003-BS
Batch 10B
DEPARTMENT OF COMPUTER SCIENCE

USMAN INSTITUTE OF TECHNOLOGY
105
CHA
ANNEXURE
Date: 12th of Oct, 2013
HAMDARD UNVIERSITY
Usman Institute of Technology
Department Of Computer Science
FINAL PROJECT APPROVAL FORM
The Head of Department,
Computer Science Department,
Usman Institute of Technology,
Karachi.
Subject:
Date:
Batch: __10B___
Bachelor of Science in Computer Science Final Year Project
Respect Sir,
We, the below listed students of final Year BS __BS(CS)___ class, desire to undertake work
on the following project.
SOFTWARE PROCESS IMPLEMENTATION IN E-COMMERCE PORTAL
1. I have selected this project on my own.

2. I have no objection working under the supervision of male/female supervisor,
or if my project work is evaluated by male/female externals.
3. I am sure I can complete this project till ___
4. In next meeting I will provide the GANTT CHART of my project.
5. I am eager to work under the supervision of advisor assigned to this project.
6. I understand that FYP committee can modify the scope of the project as and
when required.
7. I know that if do not appear in regular project progress presentations my
project will be disqualified.
8. I know that if I do not appear in mid project presentation, whenever it is
scheduled, I will not be eligible for final project viva
9. I fully understand that cheating* may lead to cancelation of my project.
10.I understand that the decision of the FYP evaluation committee, for all issues,
would be final, and no objections will be accepted.
11.I have no objection presenting my project to external or internal examiner
assigned by the Head of the Department.
12.Project and Product deliverables at the time of submission of final year
project every group is responsible to submit complete running system along
with printed reports, source code, hardware (if any) etc to the project
coordinator.
13.It would be the responsibility of Project coordinator to keep record of all
projects in a system (in running
form) as it would help to continue
106
CHA
ANNEXURE
We request you to kindly grant approval for undertaking the work on the above-cited
project. I abide by all terms and conditions mentioned below.
next
project
in
continuation,
depends
upon
the
scope
and
application of
project.
14.Proper dressing and way of presentation should be in English during proposal
defend session, milestones
and final presentations.
15.Marking of milestones and final presentation should be based on individual
evaluation of each faculty members and marks would be granted during
session.
16.When we go for proposal defends session a list of all previous projects with
their brief introduction must be available during session for our reference.
(Introduction, Scope of project, tools and technology and batch must be
available).
17. I understand that it is my responsibility to update my advisor and FYP
committee members with the status of my project and submit reports on
time.
Copying code from any resources

Using off the shelf components without prior permission
Outsourcing your project
Hire a resource for the completing the FYP code or any part of the project.
18. The Usman Institute of Technologys higher management has decided to promote and reward
creative, innovative and professional final year projects that have been successfully
implemented by the students.
The selected projects will be rewarded as follows:
First Price
Second Price
Third Price
100,000
75,000
50,000
1 Lac PKR
Seventy Thousand PKR
Fifty Thousand PKR
Yours sincerely,
S.No. Roll No.
Name
Email
1.
10B-097-BS
2.
07A-003-BS Syed Nabeel Junaid
jnabeel@hotmail.com
3.
09B-006-BS
ahmer_hussain61@hotmail.com
Signature
Ahmer Hussain
ANNEXURE
Anas Ul Haq Qureshi ngrqureshi@gmail.com
107
CHA
TABLE OF CONTENTS
PROJECT EXECUTIVE SUMMARY ..................................................................................................................109
PROJECT OVERVIEW .........................................................................................................................................109
PROJECT OBJECTIVES .......................................................................................................................................109
PROJECT SCOPE ..................................................................................................................................................109
PROJECT ESTIMATED EFFORT/COST/DURATION.....................................................................................110
ESTIMATED EFFORT HOURS ...........................................................................................................................110
ESTIMATED DURATION .....................................................................................................................................110
PROJECT ASSUMPTIONS ...................................................................................................................................111
PROJECT RISKS ....................................................................................................................................................111
PROJECT APPROACH .........................................................................................................................................112
TOOLS AND TECHNOLOGIES ...........................................................................................................................112
EXPECTED FINAL PRODUCT ............................................................................................................................113
LIST DOWN SIMILAR PRODUCTS AVAILABLE ONLINE WITH URL.PRODUCTS AVAILABLE ......114
ANNEXURE
PROJECT APPROVAL ...........................................................................................................................................115
108
CHA
Project executive summary overview

E-Commerce stand for Electronic Commerce. It is a process of buying and selling or exchanging
products, services and information via computer networks main concept of our project is an ecommerce website; a storefront which could be selling anything but would have all the features
common to various e-commerce websites. Customers will be able to register to this site, browse
product, make purchases and can update their profile information.
Project objectives
User would need to register /login to make purchases.
It will display the product catalogue and details according to the category.
The user can make customized searches for a product.
The project will make appropriate notifications according to the situation.
Confirmation email will be send to the user after purchase.
Allow user to add/edit items into the shopping cart.
Display and allow cancelation of orders that are eligible for cancelation.
Project scope
Admin panel is the back end of application from where the admin can manage the whole
site and its contents as well.
User will be able to purchase products online and get a confirmation email.
109
CHA
ANNEXURE
Our project scope will be:
Project estimated effort/cost/duration

We are estimating to work on our project 10 hours in a week individuals. In beginning we cannot
estimate the cost of our project
Number of developers: 3
Working hr/day/person = 2hrs/day approx.
Total effort hours/person = 6*5=30hrs/week
Estimated time: 6 months
Estimated duration
Working
Estimated
Durations
1 week
Planning
4 weeks
Database design
2 weeks
Coding
8 weeks
Testing
3 weeks
Documentation
4 weeks
Reporting
2 weeks
ANNEXURE
Requirement
110
CHA
Project assumptions
We assume that customer will have a proper internet connection for this project.
For our project it requires a web browser
Project risks
Risk Area
Level
(H/M/L)
Risk Plan
1. Database risk
Make backup of db
2.Run time Exception
This risk is tightly couple with project and it
our work side by side to reduce it to 90%

3. Server down
111
CHA
ANNEXURE
cannot easily solve .We just can keep testing
Project approach
We will follow the SDLC (Software Development life cycle) to build the system in different
phases which are:
Planning
Data Requirement or Analysis
Design
Development
Integrate and Testing
Implementation
Maintenance
The project will start from requirement gathering than we will do planning of our project then we
will move towards the designing phase after that the coding will be done which will take some
time, than we will do testing to find out the bugs and errors and how to solve them. After that we
will submit our project.
PHP
Xampp Server
My Sql
Aptana Studio
ANNEXURE
Tools and technologies
112
CHA
Expected Final product
ANNEXURE
Our expected final year product will be like :
113
CHA
List of products available online with URL with their features
Common Name
Features
www.3dcart.com
3dcart
Build & Design Your Website
www.bigcommerce.com
Bigcommerce
build and grow an online business
www.amazon.com
Amazon
Sold your product online
www.1and1.com
1&1
Manage your domain
ANNEXURE
URL
114
CHA
Project approvals:
Add any signatures that are important for the approval of the project. (Remove this comment
Name:
Project Supervisor
Signature
Name:
Project Supervisor
Signature
Head of Department of CS
Signature
FYP Coordinator, UIT
Signature
Member, FYP Committee, UIT
Signature
Signature
Signature
Signature
115
CHA
ANNEXURE
section from final document.)
11.3 PROJECT GANTT CHART
ANNEXURE
______________________________________________________________________________
116
CHA
117
CHA
ANNEXURE
______________________________________________________________________
11.2 PLAGIRISM REPORT
118
CHA
PLAGIRISM
______________________________________________________________________________
CHAPTER 1 INTRODUCTION
119
CHA
PLAGIRISM
CHAPTER 2 SOFTWARE AND HARDWARE REQUIREMENT
CHAPTER 3 LITERATURE REVIEWS PILAGIRISM
120
CHA
PLAGIRISM
CHAPTER 4 SOFTWARE REQUIREMENT ANALYSIS PILAGIRISM
CHAPTER 5 SOFTWARE DESIGN PILAGIRISM
121
CHA
PLAGIRISM
CHAPTER 6 ALGORITHM PILAGIRISM
CHAPTER 7 TESTING PILAGIRISM
122
CHA
PLAGIRISM
CHAPTER 8 CONCLUSION PILAGIRISM
CHAPTER 9 FURTHER ENHANCEMENT AND RECOMMENDATION

PILAGIRISM
123
CHA
PLAGIRISM
CHAPTER 11 (11.1 PROJECT PROPOSAL)

E-Commerce Report Book

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

E-Commerce Report Book

Uploaded by

Copyright:

Available Formats

Hamdard University

Usman Institute of Technology

Department of Computer Science

Software Process Implementation in E-Commerce

Syed Nabeel Junaid

Anas Ul Haq Qureshi

Mohammad Ahmer Hussain 09B-006-BS and Anas Ul Haq Qureshi 10B-097-BS

5.1 System Architecture Diagram .............................................................................37

7.1 PerformanceTesting ............................................................................................72

Table 2.1: Hardware Requiremnts ....07

Fig. 5.1: Syatem Architecture Diagram ................................................................37

commerce businesses usually employ some or all of the following practices:

Buy or sell on websites or online marketplaces.

Use electronic data interchange, the business-to-business exchange of data.

Use business-to-business buying and selling.

Provide secure business transactions

1.1 Four E-Commerce Business Models

. For example, EBay is a common

of the late 1990s. While many online B2C websites shut

User would need to register /login to make purchases.

The user can make customized searches for a product.

The project will make appropriate notifications according to the situation.

Confirmation email will be send to the user after purchase.

Allow user to add/edit items into the shopping cart.

1.3 Project scope

2.2 User Interface Requirement:

2.1 Software Required:

7/8.8.1 (32 or 64 Bit)

1.5 GHz 32-bit (x86)/64-bit (x64) or higher

Table 2.3 Hardware Requirement

2.3.3 GB RAM OR 512 MB RAM

Operating System (OS)

E-Commerce is the process of buying, selling, or exchanging products, services, or information

. Customers also have access to the internet and a valid method of

payment in order to complete a transaction

. Consumers find a product of interest by visiting

. Some stores allow consumers to sign up for a permanent online

. User will be able to purchase products online and get a confirmation

3.1 PRIVACY AND SECURITY ISSUE

). Previous studies had shown that Internet users as a whole agreed

). Most of them regard their personal information as their main

. Technologies such as Secure Socket Layer (SSL) and

. For this reason, consumer should

Shopping Cart Process

Figure 3.2.1 Sign in process

3.2.2 Sign Up Process:

Figure 3.2.2 Sign up process

3.2.1 Sign In Process:

Figure 3.2.3 Shopping cart process

3.2.3 Checkout Process:

Figure 3.2.3 Checkout process

3.2.3 Shopping Cart Process:

Figure 3.2.4 Purchase Process

3.2.5 Order Process:

Figure 3.2.5 Order purchase

3.2.4 Purchase Process:

Figure 3.2.6 Admin process

Admin can block and unblock the user

3.2.7 Confirmation Process:

Figure 3.2.7 Confirmation process

3.2.6 Admin Process:

downward through the phases of Requirement, Designing, Implementation, Testing and

3.3.1 ADVANTAGES OF WATERFALL MODEL

It is very simple and easy model to use