Kathan Vora

5th Computer

200090107017

Software Engineering practicals

 GUJARAT TECHNOLOGICAL UNIVERSITY
C.K.PITHAWALA COLLEGE OF ENGINEERING &
TECHNOLOGY, SURAT
COMPUTER ENGINEERING DEPARTMENT

PRACTICAL

Name of Student Kathan Vora

Enrollment No. 200090107017

Subject Name Software Engineering

Subject Code 3150711

Student Class 3rd Year (5th Semester)

Academic Year 2021-22

 C.K.PITHAWALA COLLEGE OF ENGINEERING &
TECHNOLOGY, SURAT
COMPUTER ENGINEERING DEPARTMENT

CO and PSO
Course Outcome (CO)

CO
Course
Statement
Outcome

CO1 Prepare SRS (Software Requirement Specification) document and SPMP (Software

Project Management Plan) document.

CO2
Apply the concept of Functional Oriented and Object-Oriented Approach
forSoftware Design.

CO3 Recognize how to ensure the quality of software product, different quality
standardsand software review techniques.

CO4 Apply various testing techniques and test plan in.

CO5 Able to understand modern Agile Development

Program Educational Objective (PEO)

PEO Statement
Program
Outcome

PREPARATION
To prepare students to gain adequate knowledge in the field of computer
engineering for successful career in industry, research and higher studies

CORE Instilling core competence and capability in graduates to solve real world
COMPETENCE engineering and societal problems
 BREADTH
To provide opportunity to the student to interpret, analyze and design computer
programs for interdisciplinary projects

PROFESSION To develop the qualities of team work, communication skills, entrepreneurship

ALI SM and work ethics following the codes of professional practice

LEARNING To promote lifelong self-learning capability among graduates to cope up with

ENVIRONMENT technological changes

Program Specific Outcomes (PSO)

PSO Statement

Students will be able to analyze, innovate and design systems to solve real world engineering
challenges by applying the concepts of computer engineering.

Students will have the professional capabilities and adaptation of recent trends in computer
engineering for the betterment of society.
 Gujarat Technological University
C. K. Pithawalla College of Engineering and Technology, Surat
Academic Year : 2021-22
B.E. - III Semester –V (Computer Engineering)
Subject Name: Software Engineering (3150711)
Practical List

NOTE :

● Select Any Software System to be developed in any technology and perform following
activities.

● Refer Virtual Lab : http://vlabs.iitkgp.ernet.in/se/

S Problem Statement Cos
r
N
o
1 Software Development Life Cycle CO1
. Design Software Development Life Cycle (SDLC) model and analyse
various activities conducted as a part of various phases. For each SDLC
phase, identify the objectives and summaries outcomes.
2 Requirement Analysis and Specification CO1
.

Prepare Software Requirement Specification (SRS) document.

3 Design Analysis CO2
.

3.1 Draw E-R Diagram for your system.

4 3.2 Design UML Diagrams CO1

. 3.2.1 Use Case Diagrams
3.2.2 Class Diagram and Sequence Diagram
3.2.3 Activity Diagram and State Diagram CO4
5
3.3 Design DFD level -0 and level-1 for your system.
.
3.4 Prepare User interface design (Front end) and also mention
characteristics of
it. Software Project Management
Examine Project Management Tool and prepare a report. (MS Project
 Tool) Coding and Testing
5.1 Implementation
5.2 Examine various code analysis tools and prepare a comparative
analysis. 5.3
Examine various Testing tools (Win runner, Load runner) and prepare a
comparative analysis.

6 Agile Tools : CO5

. Study of Agile Tool (Any One)
(Tools : JIRA,Collab,Selenium,Appium)

7 DevOps : CO5
. Study of any two Open source tools in DevOps for Infrastructure Automation,
Configuration Management ,Deployment Automation, Performance Management,
Log Management.
Monitoring.
(Tools : Behat , Watir, Chef, Supergiant, SaltStack, Docker, Hudson etc)

Faculties Name:

Prof. Vishruti V. Desai Prof. Unnati S. Shah

HOD
Dr. Ami T. Choksi
 Gujarat Technological University

C. K. Pithawalla College of Engineering and

Technology, Surat

Academic Year : 2021-22

B.E. - III Semester –V (Computer Engineering)

Subject Name: Software Engineering (3150711)

Practical List

INDEX

Sr.No. Problem Statement Date Remarks

1. Software Development Life Cycle 24/07/2022

2. Requirement Analysis and Specification 08/08/2022

3. Design Analysis 05/08/2022

4. 12/08/2022
Software Project Management

5. 26/08/2022
Coding and Testing

6. 02/09/2022
Agile Tools

7. 16/09/2022
DevOps

Faculties Name:

Prof. Pooja D. Pariyani

 PRACTICAL: - 1 Software Development Life Cycle

Domain Name :- Hotel Management System

• Group Members: -
1. Kathan Vora - 200090107017
2. Tirth Shah - 200090107047
3. Vedant Brahmbhatt - 200090107079

• Brief introduction of our domain: -

➢ As we all know that organizations are today are becoming oriented

towards new technologies and are investing large amount of time and
money in automation and computerization of their work. Hence,
Computer software are playing crucial roles in changing the industry.

➢ The management currently uses the conventional method of string

the records in the registers. Lots of paper work is to be done which is
very time consuming and is prone to errors.

➢ In order to make the system more convenient, the system is

computerized through window-based application. The main aim of this
project is to automate the activities of the Hotel to work faster, Making
Customer experience good, better room service, better reservation
facility, better guide to hotel.
 SDLC Model

➢ Although There are many life cycle model now days but according to our
project and user convenience we have selected the waterfall model.

Phases of SDLC:-

1. Requirement Gathering and Analysis :-

In this phase, the basic requirements of the system must be understood by
analyst. The Information domain, function, behavioural requirements of the
system are understood. All these requirements are then well documented and
discussed further with the customer, for reviewing.

2. Design :-
Design focuses on program attributes such as Data Structure, Software
Architecture, Interface representation and algorithmic details. The
requirements are translated in some easy to represent form using which
coding can be done effectively and efficiently.
 3. Coding:-
In this phase design is translated into machine readable form. Programs are
created in this phase. If design is done in sufficient detail then coding can
be done effectively.

4. Testing:-
The purpose of the testing is to uncover errors, fix the bugs and meet the
customer requirements. While performing testing the major focus is on
logical internals of the software. The testing ensures execution of all the
paths, functional behaviours.

5. Maintenance:-
It is longest life cycle phases. When the system is installed and put in practical
use then error may get introduced, correcting such errors and putting it in
use is the major purpose of maintenance activity and also enhancing
system’s services as new requirements are discovered is again maintenance
of the system.

Justification – Using Waterfall Model

1. All requirements are gathered once.

2. Every stage begins when previous phase is finished. According to this model we have
prepared all stages as analysis, designing, coding, testing and then finally maintenance.

3. Every phase has well defined entry and exit criteria, which is available in our
HMS.

4. Easy to understand and cheap.

5. It provides proper feedback, to minimize the work again.

6. This is achieved through the process of review and documentation.

7. Stages and activities are well defined.

 PRACTICAL:2 Requirement Analysis and Specification

Introduction
➢ We decided to base our project on a hotel management system mainly because even
though we have come from some of ‘best’ Hotel in Pakistan, their organization and
management still lags far behind when compared to similar Hotel abroad. In this era
of technology, not having a computerized system not only wastes time but also
burdens the staff of these organizations unnecessarily.
➢ When we analysed the situation, we realized that the aversion to buying some of the
brilliant software providing Hotel management system being sold online by foreign
companies was not because of the staff training issue but was largely due to the cost,
difference of Hotel system and the risk factor associated with the implementation and
running of such software.

Main Theme

➢ The main theme of Hotel Management System is to provide a facility to costumer to buy
food online. The Hotel Management System provides a platform in which a costumer
search hotel and place his order online. In this system costumer also save his time.

Scope the Project

➢ The real of World Wide Web have spread across millions of house hold, so naturally,

Internet has become by far the best platform for Hotel Management System. Now days
when everything is online, how is it possible that Hotel Management left web application
behind? There are lot of hotels who advertise their Management so idea behind
developing this application is that their food can also sell using this and could earn
maximum revenue. These applications are not widely popular but in future, they have
large scope of growth. This website is a online hotel management through which individual
agents or buyer can maintain food document keeping and managing hotel registration
and admin can access its information and manage all the adding, updating, deleting the as
and someof its tasks. The admin can delete foods or drinks and also add new foods and
drinks and also see reviews and answer that the order has been placed. .
 Objectives of the Project

➢ We want to produce a very simple, basic, user-friendly and closest to the standard Indian
hoteling system kind of a model, for example, the foods in all the Hotels do not have
computer-based record system for handling Guests, this not only makes food for Guests
a hassle but also takes a long time.
➢ Once we have completed our project, we would want to present this system to our hotel,
so that they can benefit from the numerous advantages of technology (time saving,
efficient, faster processing, less chance of loss etc.) and also improve their overall
management and image.
➢ The objective is that in early days we have to go to hotels for place order it was really a
big problem and now just online order and no need to go at hotel. In this website of hotel
management system.
➢ The admin should have all the type of authority. The admin should maintain all records
and can add and dell all and insert new foods and drinks. Admin identify all records as it
is placed order of food or drink. The admin user can inform their customers for regarding
to foods and drinks update the information regarding property and cancellation of
property or changing buyer choice. The user should book the food. The system is very
useful for the hotel that can post and edit their foods and their personal info and admin
can monitor records of all of them. The system is also useful which also keeps track of
Account details of buyers.
➢ Project Goals Planned approach towards working: - The working in the organization will
be well planned and organized. The data will be stored properly in data stores, which will
help in retrieval of information as well as its storage.
➢ Accuracy: - The level of accuracy in the proposed system cannot be decided. Because
here user buy. There is no guarantee.
➢ Reliability: - The reliability of the proposed system will be high due to theabove stated
reasons. The reason for the increased reliability of the system is that now there would be
proper storage of information.
• Site is easy and simple to navigate
• Just on click user can see required things
• Quick response on most interaction with the website.
 SPECIFIC REQUIRMENTS
PERFORMANCE REQUIREMENTS
➢ Performance is measured in terms of reports generated weekly and monthly.
Intended Audience and Reading Suggestions. The document is prepared keeping is
view of the academic constructs of my Bachelor’s Degree / Master’s Degree from
university as partial fulfilment of my academic purpose the document specifies the
general procedure that that has been followed by me, while the system was studied
and developed.

➢ The general document was provided by the industry as a reference guide to

understand
my responsibilities in developing the system, with respect to the requirements that
have been pinpointed to get the exact structure of the system as stated by the actual
client.

➢ The system as stated by my project leader the actual standards of the specification
were
desired by conducting a series of interviews and questionnaires.
The collected information was organized to form the specification document and then
was modelled to suite the standards of the system as intended.

Required Hardware:-
➢ Pentium IV Processor.
➢ 512 MB RAM.
➢ 20 GB Hard Disk space.
➢ Ethernet card with an Internet and Internet zone.

Required Software:-
➢ Windows 8 operating system.
➢ Internet explorer11 and Netscape navigator.
➢ Oracle 11g.
➢ Servlets
➢ JSP
➢ TCP/IP Protocol suite.

Modules Description:-
Number of Modules:
➢ Accommodation Information Module
➢ Units Information Module.
➢ Bookings Information Module.
➢ Guests Information Module.
➢ Facilities Information Module.
 FEASIBILITY STUDY

GENERAL REQUIREMENTS FEASIBILTY REPORT:

• The new system should be cost effective

• To improve productivity and service and service.
• To enhance user interface.
• To improve information presentation and durability.
• To upgrade systems reliability, availability and flexibility.
• To address human factors for better and uses acceptance.

PROBLEM IN THE CURRENT SYSTEM:-

The present system is presently is an undeveloped form and the manual process of the overall
system is too clumsy and complicated. The clients in the real time consultancy systemcan be
too thick and may need many resources to be used upon the system. If the system is
developed, in a distributed over interface with centralized database is the only solution.

TECHINICAL FEASIBILITY:-
Evaluating the technical feasibility is the trickiest part of a feasibility study. This is
because, at this point in time, not too many detailed designs of the system, making it difficult
to access issues like performance, costs on (on account of the kind of technology to be
deployed) etc. A number of issues have to be considered while doing a technical

ANALYSIS:

• Understand the different technologies involved in the proposed system.

• Before commencing the project, we have to be very clear about what are the technologies
that are to be required for the development of the new system.
• Find out whether the organization currently possesses the required technologies

TECHNICAL DESCRIPTION:-

The total number of databases that were identified to build the system is 10. The major
part of the Databases is categorized as administrative components and the user components.
The administrative components are useful is managing the actual master data that may;
be necessary to maintain the consistency of the system. The administrative databases are
purely used for the internal organizational needs and necessities. The user components are
designed to handle the transactional state that arise upon the system whenever the general
client makes a visit onto the system for the sake of the report-based information. The user
components are scheduled to accept parametrical information for the user as per the systems
necessity.
 PRODUCT DESIGN DESCRIPTION

PURPOSE:-
The main purpose for preparing this document is to give a general insight into the
analysis and requirements of the existing system or situation and for determining the
operating characteristics of the system.

SCOPE:-
This Document plays a vital role in the development life cycle (SDLC) As it describes
the complete requirement of the system. It is meant for use by the developers and will be
the basic during testing phase. Any changes made to the requirements in the future will
have to go through formal change approval process.
 ACCOMMODATION INFORMATION

This module maintains all the details of the Accommodation location that are available and
the units that are available under each location along with their reference unit types.

UNITS INFORMATION:-
This module maintains the information regarding all the units that are registered as per
specifications and their reference unit type. The module also takes care of the system from
the unit facilities and reference unit facilities that are available.

BOOKING MODULE:-
This module maintains the information of all the booking of the units, as pet the guest
requirements, it searches itself with the unit’s station database and the specific registered
guest who have raised the demand upon the booking.

GUEST MODULE:-
This module maintains the overall activities through which a guest is uniquely registered
is the domain the module interpreter with the specific gender status and also centrally sets
with interpretation through booking and registry to unit status.

FACILITIES MODULE:-
This module maintains the overall activities in the facilities that are available are
provided for all or some of the specified units. This module helps in registering the
reference unit facilities that may creep in into the system from time to time.
 NUMBER OF VIEWS

• Administrative View
• Guest View

Administrative View:-
This view is designed for interacting with the absolute Meta Data, which becomes the
ultimate repository to maintain the consistency.
This view is accessible only to registered administrators who are recognized by the
Watershed Development central Administration Department.
This Module takes care of the responsibility of the major Table management for
o Data Insertion
o Data Deletion
o Data Updating
o Data Selection

All the activities are validated and authenticated to proper profile to avoid un authorized
access.

Guest View:-

In this view the guest can view complete details of available accommodation list
information.
 PRACTICAL :- 3 Design Analysis

ER-Diagrams

The entity Relationship Diagram (ERD) depicts the relationship between the data objects.
The ERD is the notation that is used to conduct the date modelling activity the attributes of
each data object noted is the ERD can be described resign a data object description.
The set of primary components that are identified by the ERD are...

➢ Data object
➢ Relationships
➢ Attributes
➢ Various types of indicators.

The primary purpose of the ERD is to represent data objects and their relationships.
DESIGN UML DIAGRAMS
USE CASE DIAGRAM
CLASS DIAGRAM
SEQUENCE DIAGRAM
ACTIVITY DIAGRAM
STATE DIAGRAM
 DATA FLOW DIAGRAM

This Diagram server two purpose.

• Provides an indication of how date is transformed as it moves through the system.

• Disputes the functions and sub functions that transforms the dataflow.
 TESTING
Testing is the process of detecting errors. Testing performs a very critical role for quality
assurance and for ensuring the reliability of software. The results of testing are used later on
during maintenance also.

Psychology of Testing:

The aim of testing is often to demonstrate that a program works by showing that it has no
errors. The basic purpose of testing phase is to detect the errors that may be present in the
program. Hence one should not start testing with the intent of showing that a program
works, but the intent should be to show that a program doesn’t work. Testing is the process
of executing a program with the intent of finding errors.

Testing Objectives:

The main objective of testing is to uncover a host of errors, systematically and with
minimum
effort and time. Stating formally, we can say
➢ Testing is a process of executing a program with the intent of finding an error.
➢ A successful test is one that uncovers an as yet undiscovered error.
➢ A good test case is one that has a high probability of finding error, if it exists.
➢ The tests are inadequate to detect possibly present errors.
➢ The software more or less confirms to the quality and reliable standards.
 Installation and project description

The database as it is developed by oracle 11g can be installed only by using the export
and import concepts. Using core java and components like JSP and Servlets needs proper
deployment as per general specifications developed the front end as it.
The project can be described by the screenshots in the project as follows

The following screenshots appear when the admin login to the browser:
The following Screenshots are as follows for the guest:
 PRACTICAL:- 4 Software Project Management

Ms project tool:-

➢ Microsoft Project is a project and work management solution that enables all professionals
who manages projects to stay on the top of the changing requirements of their day to day
jobs. It provides tools that are simple for anyone to use, flexible for any project type, power
for initiatives of any size and transparent for visibility across the organization.

Use of MS Project tool:-

➢ The first Microsoft project tool was DOS program used by the company internally to manage an
Increasing number of software projects. Since its initial release in 1984, it has and continues to
Undergo improvements and enhancements to become one of Microsoft’s important products
Used in several situations like,
1. Project Management
2. Portfolio Management
3. Resource management
❖ Advantages of MS Project tool:-

1. Integration
2. Dependability
3. Customer support
4. Flexibility

❖ Disadvantages of MS Project tool:-

1. Requires training
2. Cost constraints
3. File compatibility issue
 PRACTICAL– 5:- Coding and Testing Tools

5.2 Examine various code analysis tools and prepare comparative analysis.

1. Raxis

Raxis does one better than automated tools that often discover false findings that waste time
and
effort.

Raxis scopes an amount of time that works best for your company’s code and assigns a security-
focused former developer to analyze your code for both general security and business-logic
vulnerabilities.

Raxis communicates throughout to be sure your input is used within the code review, and they
provide a report that details each finding with screenshots and remediation advice. A high-level
summary that can be provided to management and a debriefing call are also included.

2) SonarQube

SonarQube is a household name in Code Quality and Code Security, empowering all developers
to write cleaner and safer code. With thousands of automated Static Code Analysis rules in more than
25 programming languages, while integrating directly with your DevOps platform, SonarQube is your
teammate to enhance your development workflow and guide your teams.

SonarQube fits with your existing tools and proactively raises a hand when the quality or
security of your codebase is at risk.

3) PVS-Studio

PVS-Studio is a tool for detecting bugs and security weaknesses in the source code of programs,
written in C, C++, C#, and Java. It works in Windows, Linux, and macOS environment.
 It is possible to integrate it into Visual Studio, IntelliJ IDEA, and other widespread IDE. The
results of the analysis can be imported into SonarQube.

4) reshift

Reshift is a SaaS-based software platform that helps software development teams identify more
vulnerabilities faster in their own code before deploying to production.

Reducing the cost and time of finding and fixing vulnerabilities, identifying the potential risk of
data breaches, and helping software companies achieve compliance and regulatory requirements.

5) Embold

Embold is an intelligent software analytics platform that supports developers and teams in
building higher quality software in less time, by speeding up code reviews.

It automatically prioritizes hotspots in the code and provides clear visualizations. With its multi-
vector diagnostic technology, it analyses software from multiple lenses, including software design, and
enables users to manage and improve their software quality transparently.

6) SmartBear Collaborator

SmartBear Collaborator is a code review tool that is suitable for remote as well as co-located teams. It
has comprehensive review capabilities to review various documents like design, requirements,
documentation, user stories, test plans, and source code.

It can be integrated with GitHub, GitLab, Bitbucket, Jira, Eclipse, Visual Studio, etc. For the proof of
review, it offers the features of electronic signatures. It provides detailed reports. The tool can be
usedby businesses of any size.

SmartBear contains many more features like tracking & managing defects, customizing review
templates, collaborating on software artifacts & documents, etc. It can be tried for free and the price
starts at $554 per year for a 5 user pack.

5.3 Examine Load Runner and Win Runner and prepare a comparative analysis.
1. Load Runner

LoadRunner is a software testing tool from Micro Focus. It is used to test applications,
measuring system behavior and performance under load. LoadRunner can simulate thousands of users
concurrently using application software, recording and later analyzing the performance of key
components of the application.

LoadRunner simulates user activity by generating messages between application components

orby simulating interactions with the user interface such as keypresses or mouse movements. The
messages and interactions to be generated are stored in scripts. LoadRunner can generate the scripts
byrecording them, such as logging HTTP requests between a client web browser and an application's
webserver.

❖ Features of LoadRunner:

• Interactive User Transaction Simulation.

• Interactive User Transaction Simulation.
• Mobile Testing.
• Cloud Testing.
• Continuous Testing.
• Root Cause Analytics.
• Accurate Scalability Expense Prediction.
• Refined user interface.

❖ Advantages:

• Determines root cause of application performance issues

• Accurate detection of system, end user, and code-level bottlenecks
• Minimizes cost of application downtime stemmed from performance issues
• Allows performance testing of existing legacy applications with new technologies
• Enables testers to test for mobile applications
• Offers effective tool utilization tracking
• Gives users shorter test cycles to expedite application delivery
• Browser-based access to global test resources
• Optimal usage of load generator farm

❖ Disadvantages:
 • Debugging capability needs improvement
• Extremely expensive
• Uses a lot of memory and crashes if the system cannot meet its computing requirements
• May have compatibility issues
• Needs improvement in dump analysis and the subsequent results forwarding
• Usage license based on the number of virtual users
• Limited load generation capacity

2. WinRunner:

HP WinRunner software was an automated functional GUI testing tool that allowed a user to
record and play back user interface (UI) interactions as test scripts.
As a functional test suite, it worked with HP QuickTest Professional and supported
enterprise quality assurance. It captured, verified and replayed user interactions automatically, in
orderto identify defects and determine whether business processes worked as designed.
The software implemented a proprietary Test Script Language (TSL) that allowed customization
and parameterization of user input

❖ Features of WinRunner:

• Functionality testing tool

• Supports C/s and web technologies such as (VB, VC++, D2K, Java, HTML, Power
Builder, Delphe, Cibell (ERP))
• To Support .net, xml, SAP, Peoplesoft, Oracle applications, Multimedia we can use
QTP.
• Winrunner run on Windows only.
• Xrunner run only UNIX and linux.
• Tool developed in C on VC++ environment.
• To automate our manual test win runner used TSL

❖ Advantages:

• Reduces time consumption and tediousness.

• Reduces the amount of investment in human resources.
• Roots out most of the serious bugs.

❖ Disadvantages:
• Doesn’t apply for Stress or Load or Scalability Testing.
• Doesn’t Support .net Programming.
• Tester should have programming knowledge/experience.
• It doesn’t support multimedia systems.
 PRACTICAL – 6:- Agile Tools

❖ JIRA Tool

JIRA is an Agile Testing as well as a Project Management Tool developed by Atlassian.

Atlassian Corporation Plc is a software company that develops products for projectmanagers,
software developers, etc.

The JIRA full form is actually inherited from the Japanese word “Gojira” whichmeans
“Godzilla”. The basic use of this tool is to track issue and bugs related to your software and
Mobile apps.

❖ What is JIRA used for?

Jira software can be used for the following purposes:

• Requirements and Test case management

• In Agile Methodology
• Project Management
• Software Development
• Product Management
• Task Management
• Bug Tracking

❖ Key Features

• JIRA supports an agile methodology like Scrum, Kanban, etc.

• It has a strong reporting feature which provides access to dozens of reports
withreal-time team performance.
• Plans and forecasts roadmap and are able to make informed decisions.
• Customized filters using JIRA Query Language.
• It can be integrated with the developer tools for end to end traceability.
❖ What are some benefits of using Jira?

Jira is highly configurable and flexible to allow for usage in a wide variety of
environment and processes. The Jira workflows, issue types, and screens enable
tailoring for almost any scenario and can easily be change via the administration GUI.
Atlassian provides excellent online support resources and in person Atlassian User
Groups to help the community.

❖ Disadvantages

• Not the best mobile app

• Complex Integration and Mitigation
• Reports are not reusable
• Limited file size upload
• Confusing UI
 PRACTICAL – 7 :- DevOps

Docker

It is a software container technology platform that enables its users to create, deploy, run,
and manage applications within the containers. Its modular design enables users to build
applications securely, both on-premises and in the cloud. Additionally, it uses a number of the
Linux kernel’s features such as namespaces, cgroups, AppArmor profiles, and more, to
sandbox processes into existing configurable virtual environments. Also, due to the least
compatibility issues, applications can run wherever one wants without causing compatibility
hurdles. Companies like Twitter, Spotify, Pinterest, PayPal, Vox media use Docker.

❖ Features :

Three main features of Docker products are the most distinguishing:

• Quick deployment in a variety of environments;

• Greatly facilitated testing;
• Possibility of using Docker as a development environment.

❖ Why use Docker?

The main feature of Docker usage is the absence of the need to install a guest
OS. Instead, the kernel of the needed operating system (Mac, Windows or Linux) is
included in a container itself. This greatly facilitates the process of running Docker
applications.
❖ When to use Docker?

In practice, the Docker system is the most effective in the following cases:

• When there is a need to deploy large-scale software in physically remote

locations
• When there is a need to ensure shared access to the application by
geographically dispersed staff members or customers
• When you need to optimize the operation of a constantly upgraded
applicationsuch as a mobile game and launch it as soon as possible without
downtimes
• When you need to ensure that your service can scale automatically
dependingon the load.

❖ When not to use Docker?

The cases when using Docker would be disadvantageous:

• When the requirements for software efficiency is high;

• When your app uses a rich GUI;
• When you need to provide access to data used in the application to third-
partyenvironments;
• When there is a need to use different OSes for hosting software images (it
makessense to use hypervisor in such case).
Chef

Chef is an open source technology developed by Opscode. Adam Jacob, co-founder

of Opscode is known as the founder of Chef. This technology uses Ruby encoding to
develop basic building blocks like recipe and cookbooks. Chef is used in infrastructure
automation and helps in reducing manual and repetitive tasks for infrastructure
management.
Chef have got its own convention for different building blocks, which are required to
manage and automate infrastructure.

❖ Why Chef?
Chef is a configuration management technology used to automate the
infrastructure provisioning. It is developed on the basis of Ruby DSL language. It is
used to streamline the task of configuration and managing the company’s server. It has
the capability to get integrated with any of the cloud technology.
In DevOps, we use Chef to deploy and manage servers and applications in-
house and on the cloud.

❖ Features
Following are the most prominent features of Chef −
• Chef uses popular Ruby language to create a domain-specific language.
• Chef does not make assumptions on the current status of a node. It uses
itsmechanisms to get the current status of machine.
• Chef is ideal for deploying and managing the cloud server, storage, and
software.
❖ Advantages
Chef offers the following advantages −
• Lower barrier for entry − As Chef uses native Ruby language for configuration,
a standard configuration language it can be easily picked up by anyone having
some development experience.
• Excellent integration with cloud − Using the knife utility, it can be easily
integrated with any of the cloud technologies. It is the best tool for an
organization that wishes to distribute its infrastructure on multi-cloud
environment.

❖ Disadvantages
Some of the major drawbacks of Chef are as follows −
• One of the huge disadvantages of Chef is the way cookbooks are controlled. It
needs constant babying so that people who are working should not mess up
with others cookbooks.
• Only Chef solo is available.
• In the current situation, it is only a good fit for AWS cloud.
• It is not very easy to learn if the person is not familiar with Ruby.
• Documentation is still lacking.
 CONCLUSIONS AND RECOMMENDATIONS

The entire project has been developed and deployed as per the requirements stated by the
user, it is found to be bug free as per the testing standards that are implemented.

Any specification untraced errors will be concentrated in the coming versions, which are
planned to be developed in near future. The system at present does not take care of the
money payment methods, as the consolidated constructs need SSL standards and are critically
to be initiated in the first face, the application of the credit card transactions is applied as a
developmental phase in the coming days. The system needs more elaborative technicality for
its inception and evolution.