1. Project Name
Student name Artur Janka
Date of the Presentation
9th of August 2016

2. Introduction
 My name is Artur Janka.
 I’m student of Higher Diploma in Science in Cloud Computing at NCIRL.
 I’m a new Rubyist user as everything is much easier to create.
 I have a hunger for acquiring a new knowledge in every aspect and I find it
interesting.
 So, my pathway look like this for now:

3. Introduction
 The purpose of this document is to set out the
requirements for the development of Indoor
beach volleyball& soccer club with
eCommerce site.
 As we know one of the most common and
essential scenarios for business is e-
commerce.

4. Introduction
 I choose the e-commerce at this stage
because this is essential part of business site
which have no geographical limits and it
continues to gain more supporters and
constantly growing.
 It is not only the way of buying things but of
selling them as well.
 So, I decide connect ecommerce with subject
I like and have experience the most.

5. Introduction
 install rails environment
 rails install gem
 create rails application
 rails new artvballecommerce
 Start server
 cd artvballecommerce
 rails server
 rails server -b $IP -p $PORT

6. Introduction
 Next go to your localhost:3000 and you
should see

7. Introduction
 Create your navigation site & product site
 rails g controller Pages about contact rental gallery blog
 rails g scaffold Listing name description:text price:decimal

8. Introduction
 set up roots, so go to bash and type ‘rake
routes’ first.
 get '/home' => 'pages#home'
 get '/about' => 'pages#about'
 get '/contact' => 'pages#contact'
 get '/gallery' => 'pages#gallery‘
 root 'listings#index'

9. Introduction
 set up gemfile for our application

10. Introduction
 The intended customers are players of the
volleyball teams who want join for the game
or a new player which is intend to join club,
 The customers who want to buy a volleyballs
product.

11. Introduction
 First problem occur with devise gem in which I
follow instruction on github I decide to put
username into registration form

12. Introduction
 Second problem with avatar name which should be
change to image.

13. Introduction
Third issue arise during migration project to
Heroku

14. Goals
1. I have changed ‘permit’ to ‘for’
devise_parameter_sanitizer.for(:sign_up) <<
:username
And registration form start working fine without
issue.
2. avatar name which has been changed to
image.
3. Unfortunately I did not resolve this issue yet.

15. Introduction
 During planning which project I could choose I
realize as my inspiration from youth age was
always volleyball.
 I’m involved in this sport even today and I use
to play in tournament inside hall or during
summer time on the beach.

16. Introduction
 I was tried to achieve to create and image of
the sport company with e –commerce site.
 Present service with contact email which
should working fine without issue.
 Use a new skills and knowledge in a practical
setting.

17. Introduction
 The first step is to setup development and
testing environments according to the chosen
technologies.
 The second step is developing service that
allow customer to send different requests.
These requests are to allowing customer to
register to site with ability to buy any product
available on site.

18. Introduction
 The third step is developing customer
applications for sending email, chatting and
allow to join to club and participate into
volleyball game.

19. Central theories
 The technical approach is developing an
indoor beach volleyball centre with
marketplace&social blog web-based
application hosted on a Cloud platform
Heroku.
 Language: Ruby2, Ruby on Rails4/5
 Technologies: Git, GitHub, Heroku
 Web Development: HTML5, CSS3, JavaScript
and JQuery
 Application: Cloud9

20. Central theories
 Operating System: Windows 8, Linux, Ubuntu
 Database: SQLite, PostgreSQL
 Nitrous – no installation required, start coding
in our cloud IDE in sec
 Subline text – is a sophisticated text editor for
code, markup and prose. The slick user
interface, extraordinary features and amazing
performance.

21. Central theories
TOOLS WE HAD TO KNOW AND USE:
 The command line
 Ruby
 Ruby gems
 Bundler
 Rake
 Git
 Heroku
 DNS records

22. Central theories
 Help and documentation for the Ruby programming language
http://ruby-doc.org/
http://documenting-ruby.org/
https://www.ruby-lang.org/en/
 These guides are designed to make you immediately
productive with Rails, and to help you understand how all of
the pieces for together.
http://guides.rubyonrails.org/
 Free Ruby on Rails Screencasts
http://railscasts.com/
 Ruby on Rails tutorial – learn Web Development with Rails
book and screencast by Michael Hartl

23. Central theories
https://www.railstutorial.org/book
 Learn-rails.com ‘Learn Ruby on Rails’ tutorial by Daniel
Kehoe
https://updatey.com/media/uploads/projects/posts/files/jmif3s8lar
4uaf67j2ni.pdf
 A gem for every occasion: 11 great Rails libraries we use on
every project
https://infinum.co/the-capsized-eight/articles/a-gem-for-every-
occasion-11-great-ruby-libraries-we-use-on-every-project
 Learning to build a modern web application is daunting. Ruby
on Rails makes it much easier and more fun… with the
support of our large, friendly community.
http://rubyonrails.org/

24. System
Architecture

27. Design

28. Design

29. Implementation
Main classes:
 User
 Listing(product)
 Cart
 Cart_item
 Order
 Order_item
 Order_form
 Admin_user

30. Implementation
 First level navigation and all sitemap should be
working fine with easy access to registration form
and log in. Administration portal and dashboard
should let the admin to easy works across all
pages and manage ecommerce modules.
 The scope of this plan is to test all functionality
covered in the requirements specification.
 The system being tested is a volleyball club with
ecommerce site allowed customers for buying
volleyball products.

31. Implementation
 The new registration can be created by a new
customer-user. After registration the new user can
edit his profile, check navigation bar without issue,
make review of products. The user can add the
items into basket – items and if he/she change a
mind can easily remove all items from basket as
we.
 The user has ability to purchase product typing
into the site form his address and make a
payment.
 The customer can also make the reservation and
book the volleyball area for playing game.

32. Implementation
Project Nam e:
Artorius inside beach volleyball club
and ecommerce
Artur Janka
Module Name: numbers of test case 29/07/2016
Release Version: #
#
Test Case number Test Title Test Data Expected Result Actual Result
test case 1: Testing the Registration form 29/07/2016
Registration form is displayed and
after full the form with valid data
c ustomer rec eive message
suc c essful registration
PASS
test case 2:
Testing the Log in and Log out
of the new c ustomer
29/07/2016
If use valid email and password
the ac c ess to website is granted
PASS
test case 3:
Testing the new registered user
Edit Profile
29/07/2016
Customer c an easily make
c hanges into his profile
PASS
test case 4:
Testing Administration site with
ability to c hec k users and
purc hase via dashboard
29/07/2016
The Admin has a right to log into
dashbourd and manage c ustomer
and orders
PASS
test case 5:
Testing the Home, Contac t,
About pages
29/07/2016
As expec ted the User has been
brought to Navigation site without
delay
PASS
test case 6:
Testing the ability for register
user to add one or more items
into basket and review and
delete them
29/07/2016
As Expec ted applic ation allowed
the c ustomer to add items into
c art, to remove items from basket-
c art and to add more items and
detec t the sum of pric e
PASS
test case 7: Produc t c ategory page 29/07/2016
As expec ted. The applic ation let
the reg.c ustomer to searc h
produc t type and pic k up any type
of items
PASS
test case 8:
Testing the ability of register
user to make a purc hase
29/07/2016 As expec ted pass PASS
test case 9:
CRUD operation for reservation
volleyball c ourt for play a game
29/07/2016 As expec ted pass PASS
Test Designed by:
Test Designed date:
Test Executed by:
Test Execution date:

33. Implementation
Step # Step Details Expected Results Actual Results Pass / Fail / Not
executed /
Suspended
1 Navigate to the site Site should open As Expected. The application opened the site Pass
2 Sign up Enter valid
Username & valid Email with valid
Password
The application should display the home page and customer have a
right to show items, add items to cart and make a payment
As Expected, the application should display ability for
buying stuff. Login processed
Pass
3 Sign up with leaving empty
username box
The application should display an error message and ask customer to
enter username
As expected. Error message displayed FAIL
4 Sign up with leaving empty email
box
The application should display an error message and ask customer to
enter email for confirmation
As expected. Error message displayed FAIL
5 Sign up with leaving empty
password box
The application should display an error message and ask customer to
enter password for confirmation
As expected. Error message displayed FAIL
6 Sign up with leaving empty
password box
The application should display an error message and ask customer to
enter password for confirmation
As expected. Error message displayed FAIL
7 Sign up with email already taken The application should display an error message and ask customer to
enter a new email due old one was already taken
As expected. Error message displayed FAIL
8 Sign up with misspell password The application should display an error message and ask customer to
type in the correct password duplicated in first box
As expected. Error message displayed FAIL
9 Sign up with short password The application should display an error message and ask customer to
type in the proper long password
As expected. Error message displayed FAIL
9 Sign up with invalid partition of
password
The application should display an error message and ask customer to
type in the proper long password
As expected. Error message displayed FAIL

34. Evaluation
 During development the application I decide
add gem active_admin to let administrator to
access and manage app data through
ActiveAdmin, a Rails engine that runs ––
separately from the core of your app to give
you full control over your data.
 I realize that I need email functionality so I
added gem ‘mail_form’.

35. Evaluation
Additional of futures:
1. ActiveAdmin, - a Rails engine that runs ––
separately from the core of your app to give
you full control over your data.
2. Gem mail_form with sendgrid Heroku
addons let me send message from my site to
email without issue

36. Discussions
Advantages:
 I have created site where register user have
access to view volleyball products. He/she
can check information about product.
 Customer can add to cart(basket) many
products he want and ability to make
transaction. The register customer also have
a right to remove items from basket.

37. Discussions
Disadvantages
 Order is not connect with any ability to make
transaction. Unfortunately I did not have
enough spare time to add gem stripe or
PayPal functionality.
 Ability to book the court by team is not
finished I started with view html but again
PayPal is not added.

38. Discussions
Opportunities and limits
 More interested for active people, addictive
into sport.
 My idea was to give opportunities to play a
beach game inside club, warehouse in rainy
days.

39. Discussions
Future perspectives
 Increase my future prospect of the volleyball club
careful planning challenging part and execution.
 My contributions to the projects included
researching of beach indoor volleyball club’s in
Ireland upon learning that there are no any club’s
around.
 So, I have opportunity to create structure to help
me with market and corporation with union
institution to open such one in Dublin.

40. Demonstration
Home page

41. Discussions
 Home page part 2

42. Discussions
 Home page part 3

43. Discussions
 Hope page registration form part 4

44. Discussions
 About page

45. Discussions
 Contact page

46. Discussions
 Rental page

47. Discussions
 Products Sale Page

48. Discussions
 Show item and Add to Basket

49. Discussions
 Check and Checkout

50. Discussions
 Payment site