Research and Development of E-

Commerce Website From PHP

Comparative research on two web developing languages,
PHP and Python and relevant use of appropriate web
development framework to design and develop online
shopping site or an E-Commerce Site.

1
Abstract
The movement and revolution to seek information have lifted human era to new
generation and inventions. Through the use of different physical technological
inventions, human now can connect from anywhere to the accessible Internet.
Internet have provided everything to expand the knowledge of deepen analysis and
quantum mechanisms. Internet provides different services as application where one
can find anything from definite search of information. The connection of inter
networking have provided global market to the business organizations.

As humans are bounded into a system to compound lifecycle through definite views
and markets. Information system on the other side have provided different access to
data and information collection. Information system helps collect the user data, provides
business values report and aid workflow throughout the business design, analysis and
implementation. Information system is everywhere around the groups of population. Still
in Nepal, there are some places where there is no access to any technological
infrastructures. Expansion in globalization have made access to technical information
and infrastructure. Internet on the other helps vitalize the information gathered.

Ecommerce web application system is web store that shows the products for
customer/user. This application provides support for marketing any product of any
organization. Different strategies, developing methodologies and frameworks,
programming methods, scaling and scoping techniques, database management,
project management and Information System management are analyzed, defined and
implemented into the project documentation and intended project development.

3
Contents
Statement and Confirmation of Own Work ............................................................................................. 2
Abstract ........................................................................................................................................................ 3
1. Introduction ............................................................................................................................................. 6
1.1 History of E-Commerce Site/System: ........................................................................................... 8
1.2 Background of the Project: ............................................................................................................. 8
1.3 Justification of the Project: ............................................................................................................. 9
1.4 Aims: .................................................................................................................................................. 9
1.5 Objectives: ........................................................................................................................................ 9
1.6 Current System: ............................................................................................................................. 10
1.7 Problems with existing Systems: ................................................................................................. 10
1.6 Structural Overview of the Report: .............................................................................................. 11
1.6.1 Background: ............................................................................................................................ 11
1.6.2 Requirement Research & Analysis: ..................................................................................... 11
1.6.3 Design: ..................................................................................................................................... 11
1.6.4 Implementation: ...................................................................................................................... 11
1.6.5 Testing & Result: .................................................................................................................... 11
1.6.6 Evaluation & Conclusion: ...................................................................................................... 11
1.6.7 Future Work: ........................................................................................................................... 12
2. Research & Analysis: .......................................................................................................................... 12
2.1 Purpose Of Research: .................................................................................................................. 12
2.2 Project Explanation: ...................................................................................................................... 12
2.3 Research On Existing Systems: .................................................................................................. 12
2.4 Evaluation of Research Methodologies: .................................................................................... 17
2.4.1 Agile Development: ................................................................................................................ 17
2.4.2 System Development Lifecycle Model: ............................................................................... 18
2.4.3 FDD (Feature Driven Development): ................................................................................. 19
2.4.3 Hybrid Methodology (Iterative and Incremental Development): ...................................... 20
2.5 Chosen Methodology, Comparison and Findings: ................................................................... 22
2.5.1 Programming Languages: ..................................................................................................... 25
2.5.2 Developing Tools & Techniques: ......................................................................................... 27
2.6 Analysis ........................................................................................................................................... 29

4
 2.6.1 Problem Statement: ............................................................................................................... 29
2.6.2 Requirement Specification: ....................................................................................................... 29
2.6.3 Project Scope and Use Case Diagrams (UML): ................................................................ 31
3. Design & Planning: .............................................................................................................................. 33
3.1 Design Notation: ............................................................................................................................ 34
3.2 Structural/Architectural Design: ................................................................................................... 41
3.3 Data Design: ................................................................................................................................... 42
3.4 GUI Design: .................................................................................................................................... 46
3.5 Program/Algorithm Design: .......................................................................................................... 46
4. Development/Implementation of System: ........................................................................................ 47
4.1 Entity Relationship Diagram: ....................................................................................................... 48
4.2 Database Population: .................................................................................................................... 49
4.3 Code Implementation: ................................................................................................................... 50
4.4 Implemented Screen Layouts & GUI: ......................................................................................... 51
5. Testing & Iteration: ............................................................................................................................... 55
6. Conclusion & Evaluation: .................................................................................................................... 66
6.1 Original Intended Aims & Objectives: ......................................................................................... 66
6.2 Outcome Of the Project: ............................................................................................................... 66
6.3 Demonstration of Achievements: ................................................................................................ 67
6.4 Evaluation Of the Project & Achievements: ............................................................................... 68
7. Future Work .......................................................................................................................................... 68
7.1 Lesson Learnt: ............................................................................................................................... 68
8. References:........................................................................................................................................... 79

5
1. Introduction
Technological advancement have grown since the beginning of mankind. Since its
usages has grown rapidly, Electronic Business has franchised its market world-wide.
Technological advancement have functioned the different complexities with ease of
access. E-Commerce has significantly altered the traditional approach of business
actions by automating business process over the internet. Technically, static web pages
were developed onto dynamic pages and processes like search criteria and many more
functions. There are stages of implementing business strategies into web system, some
are valuation, negotiation, payment, and delivery. These actions are done between
tangible business actors (sellers) and virtual business actors (buyers) inside the
business and the web system. E-Commerce is one of the rapidly growing application for
online business transactions and marketing. It was only possible due to development of
inter networking technologies. As the implementation of currency grew, people traded
their worth with the currency in exchange. Similarly, discoveries and inventions rapidly
grew, making most of the population to bend over the currency system that was
implemented. The term commerce primarily refers to trade of goods or products, and
trade over internet or through electronic mechanism refers to E-Commerce.

An E-Commerce or the E-Commerce system comprises of different fundamental and

logical components, all are inter connected through the complex algorithms of networks
and connectivity. In simple, information are transacted via internet in any ecommerce
system. Currently, due to high growth of market and levels of technological
developments, it is easy to use those developed technical products worldwide. No
product can obtain the market without the intensity of ease in use and access. Through
the marketing of digital medias, one can use and develop any sorts of product easily.

An online system as a whole an E-Commerce system compounds transactional and

business driving factors and functions into one bounded system. Features and
Functions are timely updated into the system and one can collect desired information
through that specific system easily. Some information are not connected to the online
system like; stakeholders transactions, board meetings and overall business session
views which are external environments of business architecture. It can be incorporated
too but needs research on the management at different levels and perspectives. The
online system operates through both tangible and non- tangible units where tangible
units are the hardware components and the non tangible units are the acting or the
human resource components. The three core factors of inter networking, that makes a
system run throughout the functional requirements are:

6
- Web Application System: It shows the information online. A web page is setup with a
unique domain and are publicized onto the internet system where any browser can
enter by typing the domain at the address bar. A domain is a unique mathematical
address which defines the specific value addressed or a domain name of a website.
Here, our domain name would be www.decor8enp.com.np, as we are building an
ecommerce site for Decor 8 Enterprises.

- Network System: The network architecture gives the access to the cloud or the
internet. It connects the technological products into one single architecture for
gathering and distributing the digital information. It connects all the access gateways
and verifies the authorized actors only.

- Database System: It is simply the base of gathered data or information. Data are
managed according to the intensity and categories as per defined by the
organizational functionalities.

Figure: Conceptual System Architecture Diagram

After successfully connecting these three factors we can deploy the e-commerce
system into operational level. The system needs to update its information timely and to
do so, a content management system is implicated. A CMS or a Content Management
System is a bundle of software programs created for storage and management of
digital information. CMS is built user friendly where no experience is required at
programming level.

7
1.1 History of E-Commerce Site/System:
Nepal as an developing country, technological advancement has been very rare due to
in sufficient access to the most of the part and land mass. Revolution have affected
different opportunities factors in present. Basic infrastructure is now all over accessed
here at Nepal. Technological and Social Development have connected various business
opportunities into many angles of advancement. Companies have developed and
deployed digital information gathering system into different fields of business activities.
Different manipulative frameworks or market have been franchised through different
social networking and social media networks. There were different initiatives at the
beginning and are still investing and franchising in many other business fields. Some
are; www.kinmel.com.np, www.foodmandu.com, www.nepbay.com.np,
www.muncha.com.np, www.rojeko.com, www.daraz.com, and many other initiating
entrepreneurs. They faced lots of problems while developing and deploying the real
time system into action. Payment Gateways are not legally validated in Nepal.
Collaborating the real time business values and dynamic or digitalized values were hard
while implementing.

1.2 Background of the Project:

These days the Internet have franchised as the basic needs of the mankind. It is broadly
accessed over different localities of Nepal. Individual expansions and processes are
obtained, features accordingly are designed and deployed into online business system,
making ease in use to the practical sites throughout the transaction point.Decor8
Enterprises have been selling furniture and shoes, the proposed system intends to
deliver online marketing option and business value explanation of the organizational
and architectural environments. This chapter intends to focus on following factors to be
underpinned:

Reasons of Initiation: As the market is increasing day by day, it is significant to have

digitalized record system for ease in possible actions. The expansion in usage of
internet has significantly increased the value of online marketing. Online shopping
have already started, but online payment options is not securely implemented with
legal documentation. It would benefit an business organization moving to Bricks and
Clicks Co module where customer can see the product online and buy it from offline or
closest retail shop.

Fundamentals of Development: Hardware and Software infrastructure needs to be

developed and implemented accordingly with business values. Network Infrastructures
can be hired, trained operators and regular attention is required to maintain the overall
system. A website is developed for practical business use. It provides a business
platform for buyer and seller where seller uploads the product and buyer browse the
product online.

8
Results and Evaluation: Project requires Research and Explanation of
developing technologies and strategies. Results after the researched contents
should be well defined throughout the documentation and development.

1.3 Justification of the Project:

The company values states different reasons for implicating online system. As they
have connected to different Shoes Production Companies and Online Marketers,
deploying online system would aid the company's business regulation and record
management. Decision could be optimized after the understanding of business supply
and value chain. Through the understanding we can find the actual existing data, its
services, processes and application.

The services, processes and application are implemented digitally. It includes software
and hardware deployment. Business Framework is obtained after the findings and
deployment of requirements and application. IT infrastructures are hired for B2B
communication. Implementation aids company to quick respond market opportunities
and challenges. Online customer experiences can be recorded and definite
functionalities can be upgraded and implemented.

The applicable solution is Ecommerce_430 online site. Ecommerce_430_CMS is a

Interface Management Application. It provides control over digital view. CMS panel adds
functions for CRUD operation. This function operates at database layer and the
resultant view is returned to the programmed layer which designs the web view and
overall control is provided at the interface layer. This management system is applicable
for many product sellers. To the customer side, they can browse and compare product
from different database list, add product to shopping, get delivery and pay.

1.4 Aims:
The core aim of the project is to underpin the procedures of developing an e-commerce
website and develop an online ecommerce site where user can browser, buy the
product online, optimize and upgrade the digitalized market.

1.5 Objectives:
- To design and develop an simple e commerce site for small production and markets.

- To iterate the management technologies into various enterprises.

- To upgrade the understanding of traditional methods over modern and Electronic

market and strategies.

- To research, analyze and implement the requirements of proposed web system.

- To research and implement different architectural development structures.

9
- To find out the values of organizational development and methodologies.

- To test and iterate the final results according to business activities.

- To analyze and evaluate the post-project documentation and to complete the final
documentation.

- To research on how to enhance the post project workflows and strategies.

1.6 Current System:

Currently, our organization, Decor 8 Enterprises, have no existing system at use.
Through the use of internet various initiators have open possibilities of online marketing
and sales. But statistically, Nepali still chooses to buy product manually by visiting retail
and wholesale shops where they can perform bargaining, social dealings and paying
actions. There is no basic standardizations maintained for producing and importing
products into the Nepali market. There are different organization who have their own
websites for marketing their products and schemas and many of them have
incorporated payment gateways for online transaction.

1.7 Problems with existing Systems:

- Customer cannot find detailed specification under websites for different
satisfying option like online bargaining and payment.

- Buyer needs to visit the store for satisfaction either way.

- Comparison of the products and user reviews are not made available at different
websites.

- Have not acquired bigger market as expectation due to major developmental issues.

- Standardizations are not maintained properly in business organizations.

- Business services are not fully reliable for operations.

- Deliver and Return policies have different risk and threat factors which should be
maintained through correct findings and applicable measures.

- Payment Gateways are not legalized yet. Assurance to customer through online payment
should be labialized by different entities of market and business organizations.

10
1.6 Structural Overview of the Report:
This section gives the architectural overview of work break downed project report and
their descriptions:

1.6.1 Background:
This chapter shows the brief introduction of project background. It includes required
goals, schedules and plans to describe the requirements, project resource, project
environment and their deliverables in summary. It mainly emphasize on the justification
and implementation of system development and solution of the analysis and problems.

1.6.2 Requirement Research & Analysis:

This chapter defines the requirements through the use of different methodologies and
approaches . It includes fact findings, matrixes, evaluations, and collection of
requirements.

1.6.3 Design:
It describes the system design and shows the implementation of the designed system. It
includes the architectural diagrams, modular workflows, and designed interfaces. After
these representation, it concludes the required information to be manipulated onto the
system. It may include pre-testing modules and hypothesis which occurs during the
system designs.

1.6.4 Implementation:
This chapter shows the implemented phases of modules that were created at
modeled design. Modules are scheduled comparing resources and implementing
environments. Data are encoded into the information database, information are
implemented into the modeled system and results are captured accordingly. It
includes hardware and software requirements and specifications. This phase simply
creates a real time application.

1.6.5 Testing & Result:

This chapter concludes procedures for revitalizing the captured test results and
changeovers. It includes test plans and test logs. These plans and logs are resulted into
the iterated system and are dynamically managed into the database and the online
system.

1.6.6 Evaluation & Conclusion:

After the system is developed, implemented and tested, the real time system is
evaluated timely with different perspectives and analysis. It includes the challenges,
advantages and limitation of the system evaluated.

11
1.6.7 Future Work:
It mainly focuses on the future maintenance of the deployed system. It includes
future risk, its management, iteration in future implementation procedure,
technological upgrades and cost management.

2. Research & Analysis:

The project aims mainly focuses on the research of development and deployment
understandings through different tools, techniques and methodologies use. Existing
System are analyzed and the features are compared according to real business
market needs. Methodologies includes different architectural procedures in use,
denoting final result the same but at different transitive timescales. Software
requirements and Hardware requirements are scoped, gathered and analyzed.

2.1 Purpose Of Research:

The main purpose of the research is to learn, define and implement the strategies
and methodologies into system development and deployment. It includes techniques
for identifying product/services and customer, choosing right web development
platform, Hosting platform, developing partners, testing approaches, and marketing.

2.2 Project Explanation:

The project will deliver an online e-commerce site where digital marketing is done
through that system website. Feasible research are done for implementing Agile
development methodology, perspectives of scopes are covered and explained to the
business sponsors i.e. Decor 8 Enterprises. This project not is just intend to learn to
develop an website, but to know the business values, ecosystem, and its management.
At the end, project should deliver an prototype of the working e-commerce system,
research and comparison of web development framework and techniques, findings of
procedural development through decided frameworks and development
methodologies, and finally the understanding of

2.3 Research On Existing Systems:

Nepal, a third world country, totally affected by the globalization and its markets nowadays,
have access to the markets heavily. The big cities where population is higher have the
highest chance to grab the opportunities of bigger market. It is all about the manipulation of
system through different levels and perspectives from both tangible and non-tangible
architectures of life. Nepal have recently been into the technological development phases
and there are higher chance for enterprises to accommodate with the revolution in
Electronics and Inter Networking Business. Different national and multi-national companies
are linked into networks, some examples which have been running

12
at Nepal; Daraz.com(www.daraz.com), www.ebay.com, www.aliexpress.com,
www.foodmandu.com, and many more.

Following report shows the information about current working system deployed in
Nepal:

Daraz - This site also known as Kamyu, is growing market rapidly through the Nepali
Network and have been selling various products in international markets. They deliver
products within ranged nation, payment is done after delivery, good market value is
created and free good return & exchange policy is provided to the customer.

13
AliExpress - They are one of the leading B2C marketers from around the globe.
They are second largest online sellers across different continent.

Foodmandu - As an organization they have grown their market heavily throughout the
city population, this site provides online details about different food markets and
restaurants where customers can buy online.

14
Ebay - Echo Bay Technology group also known as Ebay is an ecommerce platform
recognized over more than 30 countries. They provide B2C and C2C business
platform for market and sales operation.

15
Kinmel- This site provides online description about Technological market available at
Nepali market. The user can buy product directly from the internet via different
payment gateways available.

All these system have the features or functions to drive the products and markets
ecosystem. They have targeted the basic needs of market population. Our developing
Online site will give the product view to the customer where customer places the
business values into operation. Similar system have deployed payment gateways. It
creates easier transaction points for the customer, where customer legal data are
accessed, definite function is done over authentication, and business activity is matched
with result to provide secure business transaction over the internet. All of the listed
system have Search Engine Optimization(SEO) Feature. Any customer can add product
to cart and get policies documents for online transaction. By this research I have found
following features to be developed and integrated into the projected system:

- Search Feature.

- Add to Cart Feature.

- Add and Delete Product, Banner and Category Feature.

- User Registration and Login Feature.

- Browse Product Feature.

16
2.4 Evaluation of Research Methodologies:
Software development methodologies are the key framework used for better
structuring, planning, scoping and controlling the process of information system
development. It helps to procedurally structure architectural workflow of the proposed
project development.

2.4.1 Agile Development:

Figure: Agile Development Cycle

Agile simply denotes to iterating or doing again and again. Its conceptual framework
concludes software development and engineering. It emphasizes on real time
communication, scheduled meetings and comprises of better team management. Time
boxes are managed which is also known as iteration, agile development typically

17
procedures processes through short time boxes, including planning, requirement
analysis, design, code, test and documentation. This methodology intends to release
new software at the end of every iteration providing required functionalities and
warrants of operations of those functionalities. There are principles of agile
development for better execution and agility:

- Early delivery of Value.

- Enhances changes and requirements at every delivery time point.

- Continuous workflow management with shorter timescales.

- Optimizes environmental communication, creating scheduled meetings

with developers and business requirements analyzers.

- Provides sustainable development environment through scheduled and

continuous delicacy, creating simplicity as essential.

- Tuned team workflow and management with better architectural and organizational
overview.

2.4.2 System Development Lifecycle Model:

The SDLC is a conceptual modeling project management procedures. Models are
fragments of procedures applied, from feasibility study to project completion and
maintenance. Fragmented models are combined and documentation is maintained
with parallel development processes. The cycle flows through- conceptual
development, planning, requirement analysis, design, develop, integrate & test,
implement, operate & maintain and finally the project closure and disposition.

18
 Figure: SDLC Phases of Development

SDLC includes different models of lifecycles; waterfall model, V model, spiral model,
and Joint Application Development (JAD) Rapid Application Development (RAD). The
most common and traditional approach is Waterfall Model of development lifecycle. It is
firm and linear approach of development. Its main defect is unsupportive changes at
developing time.

2.4.3 FDD (Feature Driven Development):

19
 Figure: Feature Driven Development Methodology (FDD)

This methodology mainly includes five stages of development. The initiation develops
the overall module or model and certain required features are analyzed and captured.
As per the captured feature, planning are done for the designing and coding the
features. A design package is developed according to the modeled object and a
complete client-valued function is obtained. This methodology specifically focuses on
delivering physical working software through iterative time management. The five
principles are:

- Overall Model Analysis and Prototype Development.

- Analyze Features and build a feature bundle according to requirements.

- Analyzed features are planned for design according to project owners and company's
business values and market record.

- Design the Planned Features, Creating Object Models as a

Feature/Function/Requirement.

- Function/Feature is Developed and Completed.

2.4.3 Hybrid Methodology (Iterative and Incremental Development):

Iterative and Incremental Development combines iterative designs and iterative builds
for software development. It includes iterative refinement and incremental development.
Iterative refinements is done via feedback based improvements. Refinements are
implicated continuously at coding, processing and developing stages. Iteration provides
repetition of development cycles and incremental development provides chunks of
action in certain definite portion of time. Project developed through Hybrid Method
intends to value client needs at primary side. By using this method, requirements and
feature both are researched and analyzed. Iterative development is used in
combination with incremental development which has longer system development cycle
and are fragmented into smaller segments. Iterations are time-boxed and end of the
iteration provides expected demonstration for the user. The purpose of iteration and
incremental development is to allow flexibility for changes.

The use of iterative and incremental development includes following iteration modules:

First iteration should provide login functionality to user.

- Website with login form is created.

- HTML creates login form.

20
- Index Page is designed and is created through HTML which will be static webpage.

Second Iteration enhances the login functionality.

- Code Validation is done and rules are developed around input parameters.

- CSS is added into Login Page.

- Error messages are developed for invalid inputs.

Third Iteration processes incremental development of login functionality.

- Forgot Password Functionality.

- Redirect Pages.

Similarly, add product, banner and category feature is iterated through same process
into the system.

Figure: Iterative and Incremental Development Methodology

21
2.5 Chosen Methodology, Comparison and Findings:
FDD or Feature Driven Development methodology is chosen for moving forward to
development and deployment. As this project is intended for individual practice, I have
been working out through different team supports and management. And to understand
the principles of approaches and procedures which are applied through this
methodology, I have found out the followings:

The procedural and operational entities of Agile development have significant values at
current site development and to the current markets. The Feature Driven Development
is one of the component of Agile Methodology and is best practice to be researched. It
is widely used over different organizations from complex to simple application
development and use. FDD in web development aids in efficiency, constraints,
adaptability, planning, conditioning and risk management. It can be applied into web-
oriented tools and techniques such as PHP, ASP, JSP. New processes while
development could be easily handled through modeling of the process as features.

The FDD approach of web development, and initiatives for usage:

- FDD is easy to understand and set up. Initial phase of development is finding
the limitation of the system and setting up the team.

- Explaining project as sets of function helps finding the requirements and optimizing
the project complexity.

- Planning development strategies as per functionalities required. Requirements

gives the need of the system and timeframe are captured for developers to finalize
the applicable programming language and technological usage.

- Reviewing the periodical status confirms the progression of the project reports. It
helps in sustaining the project development and deliveries, making problems and
solutions into definite sets of action as required.

The finding of research shows that FDD web development does not requires
requirement analysis before the project development. Rather, taking use of Hybrid
Developing Method at project development lifecycle, I have used Requirement
Gathering technique, which is beyond FDD development methods, for understanding
the basic infrastructure of data flow and design. Basically, system requirements,
resource requirements, and planning are analyzed and a framework is maintained for
future manipulation.

The developed application provides business functionalities and operations at both digital
and physical environments. It basically enhances the organization with a system services
for buying and selling different products. Comparing the existing e-commerce

22
applications, Search optimization, Customer Reviews, and different other features
are integrated.

Advantages of Hybrid Software Development:

- Includes adaptability options by iterating methods into system development lifecycle.

- Reduces time at analyzing, designing and planning stages of developing lifecycle.

- Increased pace at development through short iteration of processes.

- Provides fast recycling procedures for continuous product development and release.

- Keep records of resource management and provide plans in definite time and
deadlines.

- Provide confidence in auditing and regulation of the requirements.

Advantages of Agile Development:

- Provide transparency in project development and development strategies and

methodologies.

- Gives early report of the product deliverables using time boxed and schedules
of sprints.

- Delivers features quickly and frequently with high level of predictability.

- Provides analysis of team resource costs and schedules for team developments.

- Adapts changes with required subsets of iteration in account providing refinement and
reprioritizing options.

- Primarily focuses on Business Values and User interaction for featuring the functions
at both management and customer sides.

- Work Breakdown into manageable units provides high level participation and
interaction of team work which enables high quality development and supports.

Disadvantages of Agile Development:

- It requires high level project manager.

- Cost over iteration and development can arise higher if required resource
management is not implemented.

23
- As the project cycles through iterative approaches, definite requirements and
objectives can vary at the end of the project development.

Advantages of System Development Lifecycle:

- Provides Clear-cut project Objectives.

- Prioritizes and Stabilizes project requirements and analysis.

- Easily understandable and simple to manage.

- Flexibility is not required cause project timeline is designed at respective manner.

- Procedural development through phase wise development and are completed at

specific phase intervals.

- Provides full functional system at required and proposed time if done faithfully.

Disadvantages of Traditional SDLC/Waterfall Model:

- Change response is not applicable at traditional development procedures.

- This model highly focuses on initial requirements and sometimes requirements

cannot be liable or feasible at all.

- Project needs to be restarted if any change is required during development.

- Project developed through SDLC are tested after the completion of design and
implementation of programming tools and techniques. Higher rate of error
without continuous testing.

Advantages of Feature Driven Development Methodology:

- Supports parallel working environment for multiple team.

- Every requirements and analysis are attended as features for development.

- Easy to understand and adopt through feature development.

- Scopes of project and project team is scalable.

- Better team co ordination with architectural understandings.

- Offers tracking and reporting capabilities for team development, deployment and
progress.

Disadvantages of Feature Driven Development Methodology:

24
- Not applicable for small projects.

- No written Documentation.

- Requires reliable and knowledgeable programmer into development.

2.5.1 Programming Languages:

Programming Languages are the compiling programs written in computer
understandable form. Languages can be written at compiling form or interpreting form.
Java and C# are the semi-compiled languages, JavaScript and HTML/CSS runs
through interpreting programs.

The programming languages interprets client sides function onto server and operates
on both client and server sides machines. It interprets the high level languages through
assembling languages and converts into machine level language through hardware
use.

High level language is the human language, which are further compiled and interpreted.

Python Language: Python is a interpreted language highly used for general purpose
programming. It serves as a scripting language for web application through included
standard API. There are different web framework for Python Web Development like;
Django, Tornado, and Zope. The framework helps support the management and control
services. It is used for general purposes and supports different programming standards
and functional programming styles.

It is a object oriented approached language. It mainly composes functions, classes,

modules(collection of functions & classes) and packages(collection of modules). Functions
and classes are incorporated into modules and packages are created by collecting
modules. Function contains blocks of statements or syntax which is executed into the
programs. Python modules includes mathematical calculations, character manipulation,
web programming, graphical programming and string manipulation. The module uses
standard libraries. Packages are called in several location. Name collision is prevented
everywhere while implementing and operating packages. Variables are scoped are
determined for access control over certain actions.

PHP Scripting Language: PHP, a structured high level programming language, provides
structural breakdown of the functional operation through detailed coding of syntax; class,
functions, and conditions. It is a free format language, where conditions and information are
conveyed through lines of statements. It is widely used open source scripting language
where PHP scripts are executed on servers. PHP can generate dynamic page content, do
various operations on server, collect data and information, send and receive cookies,
control user-access, and encrypt data and information. It can

25
run on cross platform applications, compatible with all servers and supports wide
ranges of database applications.

It is based on server side scripting. It develops both static and dynamic websites or web
application. PHP can only be interpreted through PHP servers installation. Scripts are
the sets of programming instructions which are interpreted at specific runtimes.
Scripting Language interprets the scripts at runtimes. Scripts are embedded into the
software environments. Server side scripting are interpreted on server machines and
client on client machines. JavaScript is client sided and PHP incorporates it with server
side. Simply PHP starts with "<? php" and ends with "?>".

Chosen Language & Comparison:

To develop the proposed project, I have used PHP programming language for system
development. PHP offers ease, control, cost efficiency, access support, platform
independencies, server supports, and security features. Python in other side is have
various advantages and disadvantages over PHP language in comparison.

Programming Language Pros Cons

Python Supports system script and Smaller use base.
desktop tools.
Supports async/await Performance issues.
function.
Clean and clear syntax. Interpreted Language
slower than compiling
languages.
Better design support. Supporting CMS needs
higher level of operation.
Better interaction with C
libraries.
Flexibility through different
Python servers

PHP Simpler Ecosystem. Complex code

Lighter Language and
Runtime.
Easy to learn.
User base and resources.
Better opportunities at
market.
Can be embedded in
HTML.
combinations.
Poor perspective at level of
understandings.
Not full cross platform
compatible at some cases.
Needs various background
knowledge to operate.
Does not support
async./await function.

26
Table: Comparison Between PHP and Python Usages and Development.

2.5.2 Developing Tools & Techniques:

Visual Paradigm: This software helps build the graphical representation of different
stages of development lifecycle. It is a world-wide renown enterprise management and
software development sets which creates enterprise architecture, project management,
software development and team collaboration diagrams. It supports different modeling
languages and standards such as UML, SysML, XMI, etc. It simply provides report
generation and code engineering capabilities for the system analyzer and developer. In
aid it have reverse engineering capability. For example, ER diagrams can be reverse
engineered for converting and creating database create queries.

Adobe Photoshop CC: The pre project designs are made through Photoshop
software. Initial Wireframes are modeled conceptually and are digitalized through the
use of Photoshop Software. Front-End and Back-End Interfaces are designed and
sliced by the Photoshop Software. Iteration of such designs are also done. In the
proposal of the project, initial wireframe were created, but iteratively, new ecommerce
site design is created and implemented. Different UI elements, web graphics,
wireframes, and functional mock ups are designed and created. Web graphics are
optimized for better performance and speed.

Xampp: Xampp is a free open sourced cross platform web server solution. It consist
Apache HTTP server, database, and interpreters for scripts written in PHP language X
stands for cross platform, A stands for Apache, M stands for Database, PP stands for
PHP and Perl.

Sublime Text: An open source code editing tool. Sublime text is used for editing cross
platform code with Python Application Programming Interface(API).

HTML5/CSS3: To develop the website, HTML & CSS is used at the basics. HTML
makes the bones of the web layout and CSS helps add the muscles as features and
operation from class and connections. The interface section is built through the use
of this Languages. JavaScript enhances the functionality, creating attractive and
fancy interfaces.

Bootstrap: It is free open sourced collection of tools supporting web application

development. The libraries includes pre-coded HTML/CSS syntax for creating buttons,
navigation, charts, forms and many other functional components. It offers responsive
frame layout of the website, and shorter time requirement for development.

JavaScript: JavaScript makes HTML pages more interactive and dynamic. In

JavaScript, <script> tab defines the client side scripts. Script elements contains scripting

27
statements, and connects the external scripting files through definite source attributes.
The common use of JS are; image manipulation, form validation, and dynamic change
of content.

MVC Pattern: MVC, Module View Controller, provides break down of the application
into three parts: the model, the view and the controller. The three architect flows through
input-processing-output, controller-model-view.

A model is an object which represents a data or an activity. It manages the behavior

and data of application domain. After it responds to request for state information and
change in states. The model simply represents the enterprise data and business
rules. Real world modeling is applied while defining the models of the system.

A view shows or visualizes the state of the models. It manages the graphical or textual
output for the mapped display from the application. It helps generate HTML, PDF, CSV,
and XML output. It renders the content of the model which gives accesses to enterprise
and business data through models and specifies the data activities.

A controller provides facilities to change the states of the models. It interprets the inputs
from the user, and commands the model to view the changes. It translates the
interaction with the views into actions which are to be performed by the models.

A use case controller is used for dealing with system events. Simply, Banner, Product
and Category Add and Delete have on single Add/Delete Controller.

Figure: Module, View & Controller Relationships.

28
Microsoft Visio: It is used for making project plan timeline of the proposed project.
It can be used for creating complicated diagrams. It is not a free tool or software. So
in alternate Gantt Project is used for alternative Project Timeline creation.

EdrawMax: This is also a diagram creation tool or software. Basically it is used onto
the project development to create system architectural diagram of the project.

CASE Tool: CASE tool also known as Computer Aided Software Engineering Tool,
provides automated assistance for software development. It helps reduces the time
and cost factor of software development and enhances the qualities of development
procedures and implementations. It supports features for developing procedures and
business environment. It also gives performance analysis, system simulations,
automatic report generation, requirements traceability, layering and database supports.
It includes requirement analysis tool, structure analysis, software design, code
generation, test case, document production and reverse engineering tool.

2.6 Analysis
This section of document shows the detail analysis of operation workflows inside the
system architecture. It defines the function and specification of Ecommerce_430.
Specification shows the primary activities of functionalities of the system, Activity, Class
and Sequence Diagrams are made for this purpose.

2.6.1 Problem Statement:

- Buyers browse the product online yet requires physical shop for full satisfaction.

- Online relationship between buyer and seller is not completely accumulated.

- Legal payment options are not made available by the government itself.

- Customer bargaining and comparing power is lesser, customer needs to visit various
shop for reviewing products.

- Authentication of seller and buyer is required.

- Database connection required at organization view and deployment of

comparing functionality required from system and technical view.

- Cash on delivery system is not quiet trustworthy in the market. Internet have
different options for marketing and sales operations.

2.6.2 Requirement Specification:

Requirement Specification comprises stakeholders and interacting actors requirements
as a whole. There are functional and non-functional requirements of the system. It
circulates within the projected purpose and scopes of development. The primary

29
stakeholders of the project are Customers, Administrator and Developer. Administrator
have vital role at the project, Customer supports the primary operation values and
Developer connects the requirements and administrative business objectives.

There are different requirements finding methods, some are researching existing
documentation and system, site visits, hypothesis and questionnaires, prototyping,
and joint planning. Currently, I have analyzed the existing system and researched
about developing methodologies. This helped me observe work environment and joint
planning architecture.

Ecommerce_430 is an online ecommerce site which provides features as functions to

the interacting models of the system. The site must be built compatible with any
cross platform software.

As Hybrid methodology is researched and implemented for certain action, both

requirements and featured are analyzed with respect to system interaction.

Functional Requirements:

Functionality is categorized through Actors and System requirements.

User Requirements:

- The system should provide online product browsing websites with Categories.

- The system should access the authenticated users.

- The system should provide shopping cart option.

- The system needs CMS for easy administrative operations.

- The system should support and generate reports according to information

analysis. System Requirements:

- Each entities inside the product table requires unique identification.

- Products are classified as Special and Branded options in the interface.

- Administrator can search banners and alter banner table.

- The customer can add details for registration and alter respective tables
from database.

- Secure Login and Logout of users is required.

30
- User will have specific username and password where each login gets captured in
unique session.

- Customer can add product to cart, carts can have various products.

- Customer can order product online and each order description are stored at order
table where order_time is valued high priority with unique identification.

- The Administration can perform CRUD operation from the system.

Non-Functional Requirements:

Non functional requirements are the external or the environmental factor of the
system scope. It basically covers the architectural infrastructure requirements for the
deployment of the system. It includes:

- Efficiency: System should support efficient time management through operation.

- Reliability: System should operate at higher failure interactions.

- Maintainability: System requires incorporation of database management for data

and information protection.

- Recovery: System should recover the failure at less time.

- Convenient: System should be build cross platform or platform independent for

adaptability and supports.

- Sustainability: System should update timely with required needs and changes.

Features Modulations: Functional Requirements are primary value of the system.

They are observed as feature for integration onto system interfaces. Modulation of
requirements into feature acquires different constraints. Feature modulation is
required for Agile Methodology. Features are researched and analyzed for three
different models of the system, i.e. User, Administrator and Non-Users.

User or Non-User both can browse the online page, user can sign up for new
registration, and administration can add, update and delete products, banners
and categories of the online the system.

2.6.3 Project Scope and Use Case Diagrams (UML):

The system, Ecommerce_430 is a website where customer can see the desired product
and seller can sell the market values. It will aid automatic support to the marketing and
sales department of the organization by keeping the track and record of product and

31
market relation timely. It will allow User Registration, Product Reviews, Search Product,
and Manage Database functions. This project will not have the online payment option.
Following figure shows the limitation of the system and its operations:

Use Case Diagram:

An use case defines the functionalities of actors who operates throughout the system
architecture. It organizes the requirements of the application. It breakdowns the
applications into models and describes the clear objectives of the operations.

In this project, our Ecommerce_430 sets system boundary, connecting actors who are
involved in system roles are specified as the use cases and relationships are represented.
The following use case shows the operations of actors across web system. An user as an
actor can register, login, search, view, and logout from the system.

32
3. Design & Planning:
This chapter includes problem identification and its solution through different notable
diagrams, models and architectural designs. Basically, it provides framework designs for
the overall development of the project. There are layers of system architecture to be
observed while designing the system. The workflow of OSI architectures are analyzed and
designs are maintained accordingly. The GUI or the User Interface, Business values and
functions as feature of Interfaces, and design of database and information are the three
factors that needs account while designing the system and the project.

33
3.1 Design Notation:
This chapter delivers the UML Static and Dynamic Models. Static Models represents the
static components such as Class, Object, Interfaces and Relationships. It includes
Class and Object Diagram. Dynamic Modeling helps to represent different stages of
behavioral, interaction and workflow of static models. It includes Interaction Diagram,
Sequence Diagram and Activity Diagram.

Structure Diagram:

Static modeling include analysis of system requirements, data and associations. It

defines the structure of system through different abstraction and implementation
levels with relations. It does not utilizes time constraints.

Class Diagram Of the Modeled System:

The class diagram comprises of three basic components. Named as Upper, Middle and
Bottom section. These sections provides the name, attribute, and operation of the
classes. These sections composes classes, signals, data type, packages, interfaces,
enumerations, objects, artifacts and interactions, depending on the conditions it can
represent main object of the interaction in the application.
In our system, User class includes operational attributes at the Roles class. User data
are classified as object inside the user class. Similarly, different other classes have
objects. The arrow represents the signals for packages transmissions. Data types of
the objects are enumerated by the user with respective data interfaces. Interaction
between some classes are inherited and are unidirectional associated.

34
Object Diagram of the System:

Object diagram contains objects, class title, class attributes and Links. Objects are
the modules of the a class. It is used for testing the overall structure of the system
using object representation for specific use cases.

In our system, Product is a class, Groceries is the object of the class. The object
specifies class as parent and child. Class titles specifies the attributes of the
specific classes. Class attributes indicates the software requirements for the divided
environment. And, Links connects the objects of the classes.

Behavioral Diagram:

Behavior diagram shows the interacting activities in between the objects within the
system. It helps describe series of changes over requirements and time. It describes the
set of action performed through collaborative use of system by any external users of the
system and provides results to stakeholders and actors of the specific system.

35
Sequence Diagram of the System:

This diagrams focuses on identifying behavior within the projected system.

Login User:

Add User Detail:

36
Add Product:

Add Category:

37
Add Banner:

Add Product to Cart:

38
Update/Edit Product:

Update/Edit Banner:

39
Update/Edit Category:

Search Product:

40
Activity Diagram of the System:

It simply is a flowchart which represents flow from one to another activities. Activities
are defined as operations of the system. Flow of these operations are coexisting, split
and chronological in nature. Activity Diagram also uses reverse engineering techniques
to construct executable system.

Figure: Activity Diagram of the User throughout the System.

3.2 Structural/Architectural Design:

A structural design incorporates three stages of implication, planning, designing and
constructing. It defines the processes of defining the collection of hardware and
software components and their interfaces for starting the framework of online system.
It can be further defined through detail specification diagrams and techniques.

41
3.3 Data Design:
Data design results less complexity through the system development. It helps in
modulating the efficiency of the program structure. The information domain created
under Appendix section, a logical structural model, is transformed into data structures
as per needed into system development account. ER diagram and the Data dictionary
provides base for the data design regulations. Data types are specified into designing
phases of the data models and structures. Language used for development, i.e. PHP,
HTML/CSS and JavaScript all supports abstract data types, a library of error log is
maintained for system messages and modules are managed according with the
relationship that are analyzed and maintained. Following diagrams shows the Data
Dictionary of Tables that were created into the ECommerce Database:

42
43
44
45
3.4 GUI Design:
It is a User Interaction perspective of the system. User interact through either keyword
input or mouse input. It uses graphical icons and visual indicators. They are functioned
by direct manipulation of the graphical elements into operation throughout the system.

3.5 Program/Algorithm Design:

The Algorithm simply means the mathematical or the complex extraction of any
knowledge. Programming Algorithms helps define the perspectives of the program
initiation and structure of the programming methods. Algorithm designs can be the
flowchart of the system which helps to demonstrate the business value and user
perspective values, and helps in creating exact codes into development cycle and
throughout the system development.

Algorithm simply denotes instruction for definite task. It is the mix ups of conditions that
are applied into the coding and which helps operate different minor and complex task
into the system and function of the system.

46
4. Development/Implementation of System:
This chapter organizes the implementation of structural and behavioral architecture
of the system. Defined analysis and designs are implemented with correct software
and hardware applications.

Implementation process ensures operational flow of information system. It

allows operational actors to use and evaluate.

Implementation onto any technical system requires hardware and software

level specifications.

Hardware Specification:

There are two hardware level actor i.e. User/Client and System Operation. To operate
system,

Server Side Requirement:

- Intel Core 2 Duo or greater.

- 1.5GB of RAM or greater.

- More than 40GB of Storage.

- External Disk Storage Required for Back-Up operation.

User Side Requirement:

- Mobile Device or Desktops/Laptops.

- Any Web Browser.

- Internet Connectivity.

Software Specification:

- Apache Web Server

- MySQL Web Server Management

- Windows/Linux

- PHP

- Chrome/Firefox/Tor browser

47
4.1 Entity Relationship Diagram:
The ER model provides the relational database view. The entity relational model is the
conceptual data model which represents the real world entities and relationships. There
are different basic components of the ER model which are used for visually
representing data objects. It maps the relational models, constructed models can be
easily transformed into relational tables. ER diagram is simple and easy to understand
which helps to create communication channel to design database design to end user. In
addition, models can be used for design plans and helps database developer to
implement data models is specific database management software.

There are three types of connectivity of data models, one-to-one, one-to-many, and
many-to-many connection. This relationship helps to define the connectivity and
cardinality issues. At our system, user browse the product, an user can browse many
product and haves one-to-many relationships with product, user have roles for browsing
content and have one -to-many relationships with Roles, many product can be obtained
from many vendors and have many to many relationships, product order is done
through status report where product status have one-to-many relationship with order.

Figure: Entity Relationship Diagram of the Ecommerc_430 System.

48
 Figure: Ecommerce Database Structure
PHPmyadmin/MySQL 4.2 Database Population:
This section provides actual data insertion into respective tables of the database for
overall system interaction and functions.

Figure: Category Table Populated

Figure: Banner Table Populated

Figure: Roles Table Populated

49
 Figure: User Table Populated`

4.3 Code Implementation:

The system is developed through PHP programming language,
HTML5/CSS3,JavaScript(JS) and MySQL Queries Syntaxes. All the codes are available
at the project folder, Ecommerce_430, where MVC pattern is utilized for application and
web interface communications. The screen shots of the codes are represented at
Appendix section and are summarized respectively.

Figure: Code Implemented Folder- Ecommerce Folder

50
4.4 Implemented Screen Layouts & GUI:
This chapter shows the Web pages or the Graphical User Interface of the Overall
System.

Index Page, GUI for Customer:

51
 Figure: Index/Home Page Of the System.

Login & Sign-Up button from the Index Page of the Customer:

Figure: Click Login Link

Figure: Click Sign Up Link

52
Login & Sign-Up Pages:

Figure: Login Page

Figure: Sign Up Page

53
Index Page of Administrative Usage:

Figure: Ecommerce_430 CMS Page

Dashboard Of CMD:

Figure: Ecommerce_430 CMS Dashboard Page

54
5. Testing & Iteration:
System testing provides the determination from results and iterations. System testing
helps optimizing time, quality and confidence in debugging and coding processes. It
extends the focuses of implementing aspects of the system development and external
environment development. The test framework is application independent. I have used
Agile and Hybrid testing methodology for testing and implementing system
architecture, since, agile development methodology was researched for practice.

Testing provides evaluation of the system and system components through manual or
automated mediums, to verify and satisfy the requirements.

Functionality Testing:

The functionality testing checks the overall links of the web pages, database
connection, and cookie testing. All the outgoing and internal links from Home, Login &
Sign-Up, CMS and Dashboard are tested.

Cookie testing uses stored files from user machine. This maintains the login sessions.
Testing are done by enabling and disabling cookies from the browser. Cookies expires
at the end of the session and testing is done for login session and user status after
session end. Affects after testing is checked on application by deleting cookies.

Figure: Session.php code for session record and cookies

HTML and CSS are validated for optimization at site use and search operation. Syntax
errors are omitted after site validation.

Database testing confirms data consistency in application architecture. Data integrity

and errors are checked while performing edit, delete, update and insert operations.

55
Usability Testing:

It includes navigation, content checking, and ease in usage test of the overall system
sites. Main or the Home Page is linked over all pages.

Content are coded into logical and understandable format. Spelling errors are checked.
Color combination themes are used for site development. Standards are used for
building web pages and contents. User requirements are analyzed and user
functionalities such as search option, sitemap, are presented in the web links with
proper hierarchical navigation defined through different structural diagrams.

56
 Figure: Navigation Codes for usability testing
Interface Testing:

There are three interfaces providing functionalities to the respective actors of the
system. They are web, application and database interface. Test are acquired form
interaction checking between these three models of interfaces. Error handling is done
through creation of error entries at log database. It checks the connectivity issues of
web server application and user interactions.

Compatibility Testing:

The HTML5/CSS3 coding provides cross platform support for functioning. JavaScript
and Ajax is used for UI functionality and security validation through PHP programming.
Different test are driven through various web browsing applications.

Operating system compatibility, Mobile browsing compatibility and printing options are
included in this testing session. The system need to operate at both Linux/Unix and
Windows/C programmed system. Responsiveness is maintained at every User
Interfaces.

57
 Figure: Ajax.php code for sanitizing compatibility issues

Performance Testing:

Web application is tested over sustainable load deriving performance information

and measures. It includes Web Load Testing and Web Stress Testing. Application is
test over different internet speeds to check loading time and stress from functioning
database operations. Stress testing breaks the sites by giving system reaction and
recovery measures.

Security Testing:

Security testing provides test over authentication to the web directories and system
functionalities. Internal links are pasted directly without login, test success shows error
opening internal pages. User login is in accessible without full detail. User cannot give
invalid input to the system. Error messages are logged in log files where security
breaches are installed.

58
 Figure: Error.Log file for Security Options

Actor/Roles Statement Actor/User Story Objectives

Administrator/Manager Check Banner List Add Banner Add database
at CMS update at banner
table.
Delete Banner Delete database
record from banner
table.
Edit Banner Alter Database
record at banner
table.
Add Category Add database
update at Category
record.
Check Category Edit Category Edit Database
Show List at CMS Update at Category
table.
59
 Delete Category Delete database
record from
Category records.
Check Product List Add Product Add Products
at CMS records at Product
table.
Edit Product Edit Product details
from Product
records.
Delete Product Delete product
details from
product table.
User/Customer Insert User Details Register User Add User Details at
User table.
Validate User Login User Authenticate user
from user records.
Add cart Add Product Cart Add product to cart
table.
Check Cart Button Check Product Check cart details
Cart from cart table.

Figure: Checking User Authentication

60
Figure: Checked Authentication Result

Figure: Authenticated Result, Dashboard of CMS

Figure: Testing Logout Function

Figure: Logout Result

61
Figure: Testing Banner Add Functionality

Figure: Adding Banner Descriptions

Figure: Banner Add Successful

62
Figure: Test Edit Button

Figure: Edit Button Test Successful

63
Figure: Test New Edit Action

Figure: New Edit Successful

Figure: Test Banner Delete Button

64
 Figure: Banner Delete Message

Figure: Banner Delete Successful

Figure: Test Category Add

Figure: Category Add Successful

65
6. Conclusion & Evaluation:
This chapter concludes the final analysis of the entire documentation and reports.
Original Intended Aims and Objectives are analyzed and compared against developed
system features. It also includes achievement report of the system development. The
designs are carried out through graphical software like Photoshop, where web
elements are created, and the system was developed through PHP, HTML5, CSS3,
JavaScript, and Ajax. Xampp was used for testing purposes where it provides server
interactive operation within the implemented system.

6.1 Original Intended Aims & Objectives:

- Understand the business values of capitalization and marketing.

- Research existing system and find out the requirements of features integration
onto the system.

- Research, Compare and Learn Programming Concepts and Development

Methodologies.

- Research on practical implication of development strategies.

- Identify, Evaluate and Specify the requirements of the system design and
development.

- Design and represent system and database architectures, Static and Dynamic
diagrams, and workflow of information throughout the system.

- Learn the various testing methodologies, frameworks and architecture.

- Develop testing result and evaluation for verification of functionalities.

- Evaluate and Conclude final documentation and overall developed system.

- Provide User Manuals and Final Documentation of the project.

6.2 Outcome Of the Project:

The main objective of the project was to research and understand the development of
key architecture of online shopping system. In aid, to ease the procedures of buying and
selling product online.

The final outcome of the project is an online site, Ecommece_430 web application and
documentation of the system lifecycle, implementation and deployment . The site is
useful for online marketing and business transaction making different processes in
ease for customer, buyer and organization. It helps keep the track of market, ease in
making different marketing decisions and optimizes business workflows with systematic
application in operation.

66
Using PHP language over web development frameworks, ECommerce_430 can
be applicable for any domestic and international product marketing and selling
organization.

Advantages of the ECommerce_430 System:

- Provides custom regulation of the information gathering processes.

- Enhances business marketing and opportunities.

- Gives efficiency in business transaction.

- Provide trustful feature by implicating cash on delivery policy.

- Extends the accuracy of data categorization and manipulation respectively.

- System will eliminate different customer level threats by providing respective

policies and functionalities into system integration.

- Provides higher level perspective view for the initiative users through reviews and RSS
feedback Options.

Drawbacks of ECommerce_430 System:

- Does not support online transaction, payment gateway is not integrated.

- Product and Category List are still static functionality, data can be inserted but list
does not shows the actual result.

- User Review and Rating is not provided by the system functionalities.

6.3 Demonstration of Achievements:

Initiating the technological use for data and information transaction through the
designed and developed system is a significant achievement of this project. The project
achievement includes following notes:

- Successful development of prototype of an E-Commerce System.

- Understandings of various technical information.

- Finds of requirement matrix and use of procedural work break down structure.

- Practical use of development technology and methodology.

- Scoping of any system architecture and deepen analysis of development and usages.

67
6.4 Evaluation Of the Project & Achievements:
After and throughout the system development lifecycle, the related stakeholders are
used for evaluating the projected outcome or result from the development of the
system. It helps provide the network architecture and the feedback to make
improvements throughout and after the development of the proposed web system.
Evaluation includes estimation of the valued decisions and helps simulate the
information theory for better interaction and development of the intended system. As like
test cases, or stories, there are also stories and cases for evaluating portions of
development and procedures. There are different approaches for evaluating the system
through and after the development. The information system can be evaluated through
six values or modules of evaluations, namely, possession utility, form utility, place utility,
time utility, actualization utility, and goal or objectives utility. At this final documentation,
objectives utility, time utility and actualization utility have been evaluated and developed
accordingly into demonstration module of the Conclusion chapter.

7. Future Work
The developed system fulfills the requirements of the current and needed business
functions. Following Factors shows the future enhancement for the projected system:

- Detailed Specification of further Project Requirement needs to be developed and

analyzed.

- Different Risk Management Techniques and Methods needs to be learned, developed,

and enhanced to the deployed system.

- Maintenance of the system after deployment as a future work of the project.

- Project Management and Procedures needs upgrades timely and needs to be learned
iteratively throughout different sessions of business transactions.

- As the projected system covers very little functionalities throughout the operations,
future work for managing different operations and business transaction into coding and
into web application action as per requirements.

7.1 Lesson Learnt:

The only lesson I learned throughout the development of the project system and
documentation is that, one needs standardization to be onto the standardization of the
business function and ecosystem. Everything we are learning and doing is for just to
live purpose. To learn is to earn and to earn is to run the ecosystem of the projected
environments. Mainly, I have learned the connection and the interactive propagation for
business as an Education and system as a Slavery action for the market and economic

68
ecosystem. We all are bounded by one entity, i.e. Time, and we are doing nothing but
passing the time to learn what and who we are.

Appendix:
The appendix section includes extra knowledge that was acquired during and after the
analysis and research of system development and throughout the system
development. Mainly it includes Use Case Summaries and User Manual for System
Installation and Operation.

The following use case defines the operations of user while searching content from
the web system. Both user which have roles and non roles can browse the contents of
the system easily.

Basically, the projected system includes definite functionalities and operation.

Perspectives of Logical Use cases and overall use cases are defined thoroughly at
research and design section of the documents and following diagrams are the
added use cases for the projected system.

69
 Search Content

Visit Site

«uses» Keyword
*

* «uses»
* Type Details On
Search Bar Name
*

Member / Non-Member «uses»

Category

*
Click Search Button

«extends»

Display Search
Result

70
71
72
 Registration

Click The Register

Link

Display
registration Form

«extends»

Enter Personal
Details
* *

*
*
*

Click Submit Button

Non - Member
*

Verify Details

*
** Activate Member
*

Admin

Send Activated
* Message

Receive Activated
Message

73
 Login

Enter Login Details

*
*

Admin / Member

Validate Details

«extends»

Display Dashboard

74
User Manual for Operating the System:
Install:

- WAMP For Linux

-Xampp For Windows

After installation of Xampp Or WAMP:

- Extract the ecommerce_430/program.zip file into C:/Xampp/htdocs:

- Run Xampp Or WAMP

- Start Apache Tomcat Server & MySQL server.

- Open any web browser.

- Type: localhost/ for xampp configuration

- Type: localhost/ecommerce_430 and see the web pages

PHP MVC CODES OF ECOMMERCE_430 WEB SYSTEM:

LOGIN.PHP (CONTROLLER)

75
INDEX.PHP ( VIEW )

76
DATABASE.PHP (MODELS)

77
USER.PHP(MODELS)

78
8. References:
Khosrow-Pour, Mehdi, 2017. E-Commerce & E-Business. Encyclopedia Of E-
Commerce, E-Government & Mobile Commerce, [Online]. ISBN 1-59140-800-8, 150-
750. Available
at: https://books.google.com.np/books?id=lLeNQu2qFvkC&pg=PA656&dq=journals+of+
ecommerce+free&hl=en&sa=X&ved=0ahUKEwjltc66ucXXAhUDXrwKHfR4DwcQ6AEIJj
AA#v=onepage&q&f=false [Accessed 14 November 2017].

Design. 2007. Architectural Design. [ONLINE] Available at: http://www.math-

cs.gordon.edu/courses/cs211/lectures-2009/ArchitecturalDesign.pdf . [Accessed 22
November 2017].

Derek H.T. Walker, Guillermo Aranda-Mena, Mario Arlt and Justin Stark.
2017. Business and Project Procurement. [ONLINE] Available
at: http://citeseerx.ist.psu.edu/viewdoc/download?
doi=10.1.1.473.1583&rep=rep1&type= pdf. [Accessed 14 November 2017].

Mohammad Ehtasham Akhtar. 2011. Business and Project Procurement. [ONLINE]

Available at: https://www.scribd.com/doc/55598711/Introduction-to-e-Business-Project-
Report. [Accessed 17 November 2017].

Jie Zhang. 2010. Development of Ecommerce Application using WAMP. [ONLINE]

Available at: https://www.scribd.com/doc/55598711/Introduction-to-e-Business-Project-
Report. [Accessed 2 November 2017].

IT portal. 2015. IT Standards & Methodology. [ONLINE] Available

at: http://www.itinfo.am/eng/software-development-methodologies/. [Accessed 7
November 2017].

SmartSheet. 2016. Agile Vs Scrum Vs Waterfall Vs Kanban. [ONLINE] Available

at: https://www.smartsheet.com/agile-vs-scrum-vs-waterfall-vs-kanban. [Accessed 28
November 2017].

Macronimous. 2015. Feature Driven Development. [ONLINE] Available

at: https://www.macronimous.com/resources/feature-driven-development.asp .
[Accessed 26 November 2017].

Gayatri Ghanakota. 2014. Testing Frameworks. [ONLINE] Available

at: https://www.cs.colorado.edu/~kena/classes/5828/s12/presentation-
materials/ghanakotagayatri.pdf. [Accessed 27 November 2017].

Margaret Rouse. 2016. What Is UseCase. [ONLINE] Available

at: http://whatis.techtarget.com/definition/use-case-diagram . [Accessed 28 November
2017].

79
UML. 2014. UML. [ONLINE] Available at: http://whatis.techtarget.com/definition/use-
case-diagram. [Accessed 8 November 2017].

Scott W. Ambler. 2010. Agile Modeling. [ONLINE] Available

at: http://agilemodeling.com/essays/fdd.htm . [Accessed 13 November 2017].

Dimitri Ponomareff. 2014. Agile Testing Framework. [ONLINE] Available

at: https://www.slideshare.net/dimka5/agile-testing-framework-the-art-of-automated-
testing. [Accessed 11 November 2017].

Quora. 2015. PHP Testing Framework. [ONLINE] Available

at: https://www.slideshare.net/dimka5/agile-testing-framework-the-art-of-automated-
testing. [Accessed 11 November 2017].

Josh Davis. 2013. TDD and BDD. [ONLINE] Available

at: http://joshldavis.com/2013/05/27/difference-between-tdd-and-bdd/ . [Accessed 12
November 2017].

Vin D’Amico. 2002. Building Ecommerce Architecture. [ONLINE] Available

at: http://www.damicon.com/resources/Architecture_Practices.pdf. [Accessed 14
November 2017

Saurabh Kumar. 2013. Dynamic and Static Modeling. [ONLINE] Available

at: https://www.slideshare.net/100arab/dynamic-and-static-modeling . [Accessed 16
November 2017].

OLGA REKOVSKAYA. 2014. PHP framework for ecommerce development. [ONLINE]

Available at: http://www.issart.com/blog/php-framework-ecommerce-website-
development/. [Accessed 20 November 2017].

Segue Technologies. 2015. Benefits of Agile. [ONLINE] Available

at: https://www.seguetech.com/8-benefits-of-agile-software-development/ . [Accessed 21
November 2017].

Thought Co. 2015. Programming Languages. [ONLINE] Available

at: https://www.thoughtco.com/what-is-a-programming-language-958332. [Accessed 20
November 2017].

Ruhaim Izmeth. 2014. FDD. [ONLINE] Available

at: https://www.slideshare.net/RuhaimIzmeth/feature-driven-development-38369182.
[Accessed 8 November 2017].

LucidChart. 2017. Object Diagram. [ONLINE] Available

at: https://www.lucidchart.com/pages/uml/object-diagram. [Accessed 23 November
2017].
80
Technology Conversations. 2016. Software Development Models: IIDM. [ONLINE]
Available at: https://technologyconversations.com/2014/01/21/software-development-
models-iterative-and-incremental-development/ . [Accessed 17 November 2017].

UML Diagrams. 2012. UML Diagram Overviews. [ONLINE] Available

at: https://www.uml-diagrams.org/uml-23-diagrams.html. [Accessed 22 November
2017].

Lucid. 2017. Class Diagram. [ONLINE] Available

at: https://www.lucidchart.com/pages/uml/class-diagram. [Accessed 13 November
2017].

Tutorial. 2015. Activity Diagram. [ONLINE] Available

at: https://www.tutorialspoint.com/uml/uml_activity_diagram.htm . [Accessed 13
November 2017].

W3Schools. 2016. PHP 5. [ONLINE] Available

at: https://www.w3schools.com/php/php_intro.asp. [Accessed 24 November 2017]

UMSL. 2016. CASE Tool. [ONLINE] Available

at: https://www.w3schools.com/php/php_intro.asp. [Accessed 25 November 2017].

SlideShare. 2016. Python program. [ONLINE] Available

at: https://www.slideshare.net/ranelpadon/python-programming-iv-program-
components. [Accessed 26 November 2017].

Tony Marston. 2004. MVC Pattern. [ONLINE] Available

at: https://www.tonymarston.net/php-mysql/model-view-controller.html . [Accessed 26
November 2017].

SDP, (2015), Software Development Processes [ONLINE]. Available

at: https://www.google.com.np/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja
&uact=8&ved=0ahUKEwiiv7qP9tTXAhXCNJQKHQH7Ce4QjRwIBw&url=https%3A%2F
%2Fen.wikipedia.org%2Fwiki%2FSoftware_development_process&psig=AOvVaw192n
NddD4jqUU4QlvU-PJw&ust=1511534128173429 [Accessed 26 October 2017].

Prabhat Singha, (2016), Agile Methodologies Of Development [ONLINE]. Available

at: https://www.google.com.np/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja
&uact=8&ved=0ahUKEwiqo-
eg9tTXAhWII5QKHUn0A_MQjRwIBw&url=https%3A%2F%2Fwww.slideshare.net%2FP
rabhatSinha15%2Fchoosing-right-agile-methodology-for-your-project-
67044794&psig=AOvVaw2GwL6FOnoKB7wHfptvAIqI&ust=1511534224600801 [Acces
sed 31 October 2017].

81
TechTarget, (2015), Software Quality [ONLINE]. Available
at: https://www.google.com.np/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja
&uact=8&ved=0ahUKEwjK5I6I99TXAhXFmZQKHZ9tAT0QjRwIBw&url=http%3A%2F%
2Fsearchsoftwarequality.techtarget.com%2Fdefinition%2Fagile-software-
development&psig=AOvVaw1eNmzqdvVFA15oKFaPt1vj&ust=1511534367606082 [Acc
essed 1 November 2017].

WIKI, (2017), SDLC [ONLINE]. Available

at: https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&u
act=8&ved=0ahUKEwi4xuyhtdbXAhXGMI8KHXOsBpwQjRwIBw&url=https%3A%2F%2
Fen.wikipedia.org%2Fwiki%2FSystems_development_life_cycle&psig=AOvVaw3s5PI1
QZIkwxxB5Xf1-MRP&ust=1511585585330481 [Accessed 6 November 2017].

P. Isaias and T. Issa. 2015. IS System Development Lifecycles. [ONLINE] Available

at: https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&ved=0ahUK
Ewi726PXmcfXAhUBkZQKHXxyBwcQFggrMAE&url=http%3A%2F%2Fwww.springer.co
m%2Fcda%2Fcontent%2Fdocument%2Fcda_downloaddocument%2F9781461492535-
c2.pdf%3FSGWID%3D0-0-45-1479416-
p175478101&usg=AOvVaw1bfu_L8N8PnmmbuZTqGeHV . [Accessed 25 October
2017].

82