swing2/3.Integration Test Plan Document/ITPD.lyx

2365 lines
39 KiB
Plaintext
Raw Normal View History

2017-01-11 11:27:49 +00:00
#LyX 2.2 created this file. For more info see http://www.lyx.org/
\lyxformat 508
\begin_document
\begin_header
\save_transient_properties true
\origin unavailable
\textclass article
\begin_preamble
\usepackage{listings}
\usepackage{xcolor}
\usepackage{pdflscape}
\usepackage{courier}
%\usepackage{mathtools}
\usepackage{graphicx}
\usepackage{booktabs}
\usepackage[T1]{fontenc}
\usepackage{lmodern}
\usepackage{listings}
\lstset{columns=fullflexible}
\usepackage{charter}
\usepackage{xspace}
\usepackage{algorithmicx}
\usepackage{algpseudocode}
% Definizione intestazioni e pie' di pagina
\usepackage{fancyhdr}
% _____________________________
\lstdefinelanguage{JS}{
keywords={typeof, new, true, false, catch, function, return, null, catch, switch, var, if, in, while, do, else, case, break},
keywordstyle=\color{blue}\bfseries,
ndkeywords={class, export, boolean, throw, implements, import, this}, ndkeywordstyle=\color{darkgray}\bfseries,
identifierstyle=\color{black},
sensitive=false,
comment=[l]{//},
morecomment=[s]{/*}{*/},
commentstyle=\color{purple}\ttfamily,
stringstyle=\color{red}\ttfamily,
morestring=[b]',
morestring=[b]"
}
\definecolor{dkgreen}{rgb}{0,0.6,0}
\definecolor{gray}{rgb}{0.5,0.5,0.5}
\definecolor{mauve}{rgb}{0.58,0,0.82}
\lstset{frame=tb,
language=JS,
aboveskip=3mm,
belowskip=3mm,
showstringspaces=false,
columns=flexible,
basicstyle={\small\ttfamily},
numbers=none,
numberstyle=\tiny\color{gray},
keywordstyle=\color{blue},
commentstyle=\color{dkgreen},
stringstyle=\color{mauve},
breaklines=true,
breakatwhitespace=true,
tabsize=3 }
% _____________________________
\end_preamble
\use_default_options true
\begin_modules
InStar
graphicboxes
fix-cm
fixltx2e
fixme
customHeadersFooters
pdfform
\end_modules
\maintain_unincluded_children false
\begin_forced_local_layout
Format 60
Style "In Preamble"
Category "FrontMatter"
Margin Static
LatexType Paragraph
InTitle 0
InPreamble 1
TocLevel -1000
NeedProtect 0
KeepEmpty 0
NextNoIndent 0
CommandDepth 0
LatexName "dummy"
ItemCommand item
LabelType No_Label
EndLabelType No_Label
ParagraphGroup "0"
ParIndent MM
ParSkip 0.4
ItemSep 0
TopSep 0
BottomSep 0
LabelBottomSep 0
ParSep 0
NewLine 1
Align Block
AlignPossible Block, Center, Layout, Left, Right
FreeSpacing 0
PassThru 0
ParbreakIsNewline 0
RefPrefix OFF
HTMLLabelFirst 0
HTMLStyle
div.standard {
margin-bottom: 2ex;
}
EndHTMLStyle
HTMLForceCSS 0
HTMLTitle 0
Spellcheck 1
ForceLocal 1
End
Style "In Title"
Category "FrontMatter"
Margin Static
LatexType Paragraph
InTitle 1
InPreamble 0
TocLevel -1000
NeedProtect 0
KeepEmpty 0
NextNoIndent 0
CommandDepth 0
LatexName "dummy"
ItemCommand item
LabelType No_Label
EndLabelType No_Label
ParagraphGroup "0"
ParIndent MM
ParSkip 0.4
ItemSep 0
TopSep 0
BottomSep 0
LabelBottomSep 0
ParSep 0
NewLine 1
Align Block
AlignPossible Block, Center, Layout, Left, Right
FreeSpacing 0
PassThru 0
ParbreakIsNewline 0
RefPrefix OFF
HTMLLabelFirst 0
HTMLStyle
div.standard {
margin-bottom: 2ex;
}
EndHTMLStyle
HTMLForceCSS 0
HTMLTitle 0
Spellcheck 1
ForceLocal 1
End
\end_forced_local_layout
\language english
\language_package default
\inputencoding auto
\fontencoding global
\font_roman "default" "default"
\font_sans "default" "default"
\font_typewriter "default" "default"
\font_math "auto" "auto"
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100 100
\font_tt_scale 100 100
\graphics default
\default_output_format default
\output_sync 1
\bibtex_command default
\index_command default
\float_placement H
\paperfontsize default
\spacing single
\use_hyperref true
\pdf_bookmarks true
\pdf_bookmarksnumbered false
\pdf_bookmarksopen false
\pdf_bookmarksopenlevel 1
\pdf_breaklinks false
\pdf_pdfborder false
\pdf_colorlinks false
\pdf_backref false
\pdf_pdfusetitle true
\papersize default
\use_geometry true
\use_package amsmath 1
\use_package amssymb 1
\use_package cancel 1
\use_package esint 1
\use_package mathdots 1
\use_package mathtools 1
\use_package mhchem 1
\use_package stackrel 1
\use_package stmaryrd 1
\use_package undertilde 1
\cite_engine basic
\cite_engine_type default
\biblio_style plain
\use_bibtopic false
\use_indices false
\paperorientation portrait
\suppress_date false
\justification true
\use_refstyle 1
\index Index
\shortcut idx
\color #008000
\end_index
\leftmargin 2.5cm
\rightmargin 2.5cm
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\paragraph_indentation default
\quotes_language english
\papercolumns 1
\papersides 1
\paperpagestyle default
\tracking_changes false
\output_changes false
\html_math_output 0
\html_css_as_file 0
\html_be_strict false
\end_header
\begin_body
\begin_layout Standard
\begin_inset ERT
status open
\begin_layout Plain Layout
\backslash
begin{titlepage}
\end_layout
\end_inset
\end_layout
\begin_layout Standard
\begin_inset ERT
status open
\begin_layout Plain Layout
\end_layout
\begin_layout Plain Layout
\backslash
newcommand{
\backslash
HRule}{
\backslash
rule{
\backslash
linewidth}{0.5mm}}
\end_layout
\begin_layout Plain Layout
\backslash
center
\end_layout
\begin_layout Plain Layout
\backslash
textsc{
\backslash
LARGE Politecnico di Milano}
\backslash
\backslash
[1.5cm]
\backslash
textsc{
\backslash
Large PowerEnjoy}
\backslash
\backslash
[0.5cm]
\end_layout
\begin_layout Plain Layout
\backslash
textsc{
\backslash
Large Software Engineering 2}
\backslash
\backslash
[0.5cm]
\end_layout
\begin_layout Plain Layout
\end_layout
\begin_layout Plain Layout
\backslash
HRule
\backslash
\backslash
[0.4cm] {
\backslash
huge
\backslash
bfseries Integration Test Plan Document}
\backslash
\backslash
[0.4cm]
\backslash
HRule
\backslash
\backslash
[1.5cm]
\end_layout
\begin_layout Plain Layout
\backslash
begin{minipage}{0.4
\backslash
textwidth}
\backslash
begin{flushleft}
\backslash
large
\backslash
emph{Authors:}
\backslash
\backslash
Giancarlo
\backslash
textsc{Colaci}
\backslash
newline Giulio
\backslash
textsc{De Pasquale}
\backslash
newline Francesco
\backslash
textsc{Rinaldi}
\backslash
end{flushleft}
\backslash
end{minipage} ~
\backslash
begin{minipage}{0.4
\backslash
textwidth}
\backslash
begin{flushright}
\backslash
large
\backslash
emph{Supervisor:}
\backslash
\backslash
Elisabetta
\backslash
textsc{De Nitto}
\backslash
end{flushright}
\backslash
end{minipage}
\backslash
\backslash
[3cm]
\end_layout
\begin_layout Plain Layout
\end_layout
\end_inset
\end_layout
\begin_layout Standard
\begin_inset Graphics
filename res/img/logopm.pdf
width 30text%
\end_inset
\end_layout
\begin_layout Standard
\begin_inset ERT
status open
\begin_layout Plain Layout
\backslash
vfill
\end_layout
\begin_layout Plain Layout
{
\backslash
large
\backslash
today}
\backslash
\backslash
[3cm]
\end_layout
\end_inset
\end_layout
\begin_layout Standard
\begin_inset ERT
status open
\begin_layout Plain Layout
\backslash
end{titlepage}
\end_layout
\end_inset
\begin_inset Newpage newpage
\end_inset
\end_layout
\begin_layout Standard
\begin_inset ERT
status open
\begin_layout Plain Layout
\backslash
mbox{}
\backslash
thispagestyle{empty}
\backslash
newpage
\end_layout
\end_inset
\end_layout
\begin_layout Standard
\begin_inset Newpage newpage
\end_inset
\end_layout
\begin_layout Standard
\begin_inset CommandInset toc
LatexCommand tableofcontents
\end_inset
\begin_inset ERT
status open
\begin_layout Plain Layout
\backslash
thispagestyle{empty}
\end_layout
\end_inset
\end_layout
\begin_layout Standard
\begin_inset Newpage newpage
\end_inset
\end_layout
\begin_layout Standard
\begin_inset ERT
status open
\begin_layout Plain Layout
\backslash
setcounter{page}{1}
\end_layout
\end_inset
\end_layout
\begin_layout Section
Introduction
\end_layout
\begin_layout Subsection
Revision History
\end_layout
\begin_layout Standard
\align center
\begin_inset Tabular
<lyxtabular version="3" rows="3" columns="4">
<features tabularvalignment="middle">
<column alignment="center" valignment="top">
<column alignment="center" valignment="top">
<column alignment="center" valignment="top">
<column alignment="center" valignment="top">
<row>
<cell alignment="center" valignment="top" topline="true" bottomline="true" leftline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Version
\end_layout
\end_inset
</cell>
<cell alignment="center" valignment="top" topline="true" bottomline="true" leftline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Date
\end_layout
\end_inset
</cell>
<cell alignment="center" valignment="top" topline="true" bottomline="true" leftline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Author(s)
\end_layout
\end_inset
</cell>
<cell alignment="center" valignment="top" topline="true" bottomline="true" leftline="true" rightline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Summary
\end_layout
\end_inset
</cell>
</row>
<row>
<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
1.1
\end_layout
\end_inset
</cell>
<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
14/01/2017
\end_layout
\end_inset
</cell>
<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Giancarlo Colaci, Giulio De Pasquale, Francesco Rinaldi
\end_layout
\end_inset
</cell>
<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Minor fixes
\end_layout
\end_inset
</cell>
</row>
<row>
<cell alignment="center" valignment="top" topline="true" bottomline="true" leftline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
1.0
\end_layout
\end_inset
</cell>
<cell alignment="center" valignment="top" topline="true" bottomline="true" leftline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
08/01/2017
\end_layout
\end_inset
</cell>
<cell alignment="center" valignment="top" topline="true" bottomline="true" leftline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Giancarlo Colaci, Giulio De Pasquale, Francesco Rinaldi
\end_layout
\end_inset
</cell>
<cell alignment="center" valignment="top" topline="true" bottomline="true" leftline="true" rightline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Initial Release
\end_layout
\end_inset
</cell>
</row>
</lyxtabular>
\end_inset
\end_layout
\begin_layout Standard
\end_layout
\begin_layout Subsection
Purpose and Scope
\end_layout
\begin_layout Standard
The Integration Test Plan Document (
\series bold
ITPD
\series default
) mainly serves to describe how integration tests are to be performed.
The tests here described focus on the information's flow between modules
opposed to the modules themselves.
Specifically it describes the adopted methodologies ranging from the sets
of all tests to be performed to the tools used throughout the whole process.
The system will be an optimization of a pre-existing system for renting
electric cars already in use in some cities.
The new system will let users to check reservability and status of available
cars, rent or reserve them through a mobile or a web application in a more
simple and effective way.
\end_layout
\begin_layout Subsection
Definitions, Acronyms, Abbreviations
\end_layout
\begin_layout Standard
Below there are definitions of some terms that will be used in the document,
in order to avoid any ambiguity in their use and their understanding.
\end_layout
\begin_layout Standard
\begin_inset Note Note
status open
\begin_layout Plain Layout
[REMOVE ME WHEN YOU HAVE DONE THIS: DA COMPLETARE]
\end_layout
\end_inset
\end_layout
\begin_layout Subsubsection*
Definitions
\end_layout
\begin_layout Description
Component: each of the low level components realizing the functionalities
of a subsystem
\end_layout
\begin_layout Description
Subsystem: a high-level functional unit of the system
\end_layout
\begin_layout Description
[..]
\end_layout
\begin_layout Subsubsection*
Acronyms
\end_layout
\begin_layout Description
DBMS: DataBase Management System, a software that control the creation,
maintenance and use of a database.
(e.g.
MySQL)
\end_layout
\begin_layout Description
API: Application Programming Interface
\end_layout
\begin_layout Description
RASD: Requirement Analysis and Specification Document
\end_layout
\begin_layout Description
DD: Design Document
\end_layout
\begin_layout Description
[..]
\end_layout
\begin_layout Subsubsection*
Abbreviations
\end_layout
\begin_layout Description
Req.
as for Requirement
\end_layout
\begin_layout Description
WebApp as for Web Application
\end_layout
\begin_layout Description
[..]
\end_layout
\begin_layout Standard
\begin_inset Newpage newpage
\end_inset
\end_layout
\begin_layout Subsection
Reference documents
\end_layout
\begin_layout Itemize
Requirements Analysis and Specification Document produced before: [RASD.pdf]
\end_layout
\begin_layout Itemize
Design Document produced before: [DD.pdf]
\end_layout
\begin_layout Itemize
Specification Document: [ASSIGNMENTS AA 2016-2017.pdf]
\end_layout
\begin_layout Itemize
The documentation of any tool you plan to use for testing [REMEMBER TO UPDATE]
\end_layout
\begin_layout Standard
\begin_inset Note Note
status open
\begin_layout Plain Layout
TODO
\end_layout
\end_inset
\end_layout
\begin_layout Subsection
Document Structure
\end_layout
\begin_layout Standard
\begin_inset Note Note
status open
\begin_layout Plain Layout
Se decidiamo di tenere la Document Structure, dobbiamo ultimarla.
È un qualcosa che va fatto alla fine.
\end_layout
\end_inset
\end_layout
\begin_layout Enumerate
\series bold
Introduction
\series default
: this section introduces the Integration Test Plan Document.
It contains a justification of his utility and ...
\end_layout
\begin_layout Enumerate
\series bold
Integration Strategy
\series default
: this section is divided into different parts.
\end_layout
\begin_deeper
\begin_layout Itemize
\shape italic
Entry Criteria
\shape default
: this sections explains the criteria that must be met before integration
testing of specific elements may begin (e.g., functions must have been unit
tested).
\end_layout
\begin_layout Itemize
\shape italic
Elements to be Integrated
\shape default
: this sections gives a global view of the components of the application
to be integrated, in a consistent way with our design.
\end_layout
\begin_layout Itemize
\shape italic
Integration Testing Strategy
\shape default
: this sections gives a more detailed view of the integration testing approach
(topdown, bottomup, functional groupings, etc.) and about the reasons
for the choosing that approach.
\end_layout
\begin_layout Itemize
\shape italic
Sequence of Component / Function Integration
\shape default
: [..]
\end_layout
\begin_deeper
\begin_layout Itemize
\shape italic
Software Integration Sequence
\shape default
: this section shows, for each subsystem, the sequence in which the software
components will be integrated within the subsystem.
\end_layout
\begin_layout Itemize
\shape italic
Subsystem Integration Sequence
\shape default
: this section shows the order in which subsystems will be integrated.
\end_layout
\end_deeper
\end_deeper
\begin_layout Enumerate
\series bold
Individual Steps and Test Description
\series default
: this section describes, for each step of the integration process above,
the type of tests that will be used to verify that the elements integrated
in this step perform as expected.
(REMOVE: Describe in general the expected results of the test set.
You may refer to Chapter 3 and Chapter 4 of the test plan example [1] as
an example of what we expect.)
\end_layout
\begin_layout Enumerate
\series bold
Tools and Test Equipment Required
\series default
: this section presents all tools and test equipment needed to accomplish
the integration.
(REMOVE: Refer to the tools presented during the lectures.
Explain why and how you are going to use them.
Note that you may also use manual testing for some part.
Consider manual testing as one of the possible tools you have available)
\end_layout
\begin_layout Enumerate
\series bold
Program Stubs and Test Data Required
\series default
: this section aims to identify any program stubs or special test data required
for each integration step, based on the testing strategy and test design.
\end_layout
\begin_layout Enumerate
\series bold
Appendix
\series default
: in this section will be listed the different tools we used and the hours
of work spent by each member of the team.
\end_layout
\begin_layout Standard
\begin_inset Newpage newpage
\end_inset
\end_layout
\begin_layout Section
\series bold
Integration Strategy
\end_layout
\begin_layout Subsection
Entry Criteria
\end_layout
\begin_layout Standard
This section lists all the prerequisites that need to be met
\shape italic
before
\shape default
any integration testing begins in order achieve valid and worthwhile results.
\end_layout
\begin_layout Standard
All the classes and methods will be
\series bold
tested
\series default
against several unit tests to detect major faults in algorithms and classes'
structure.
Each unit test has to cover at least the 90% of lines of code and will
be run automatically on each build.
However unit testing is not in the scope of this document and will not
be specified in further detail.
\end_layout
\begin_layout Standard
The whole project will be
\series bold
constantly inspected
\series default
to ensure maintainability, detect possible issues and coding conventions
breakages which could increase the testers' effort in next testing phases.
Continuous code inspection must be performed using automated tools as much
as possible: manual testing should be reserved for the most difficult features
to test.
\end_layout
\begin_layout Standard
Finally, the
\series bold
documentation
\series default
has to be complete and up-to-date to be used as a reference for integration
testing development.
In particular, the public interfaces of each class and module should be
well referenced.
Where necessary, a formal specification language can be used.
\begin_inset Newline newline
\end_inset
\end_layout
\begin_layout Standard
\series bold
The following documents must be delivered before integration testing can
begin:
\end_layout
\begin_layout Itemize
\shape slanted
Requirement Analysis and Specification Document of PowerEnjoy
\end_layout
\begin_layout Itemize
\shape slanted
Design Document of PowerEnjoy
\end_layout
\begin_layout Itemize
\shape slanted
Integration Testing Plan Document of PowerEnjoy
\end_layout
\begin_layout Subsection
Elements to be Integrated
\end_layout
\begin_layout Standard
For a detailed description of each components function and interaction refer
to the
\series bold
Design Document
\series default
, section 2.3.
\end_layout
\begin_layout Subsection
Integration Testing Strategy
\end_layout
\begin_layout Standard
The chosen strategy for the integration testing is the
\series bold
bottom-up
\series default
approach.
\end_layout
\begin_layout Standard
It allows the testers to focus on each main component as little as possible
since each test will be developed in great detail starting from the inner
classes in our specification: from that point on, each component will rely
on a strong codebase which reduces the time spent on reviewing the project
internals.
\end_layout
\begin_layout Subsection
Component / Subsystem Testing
\end_layout
\begin_layout Standard
Due to the complex nature of testing an entire system, we planned the integratio
n testing following two point of views, both of them catalogued through
a
\series bold
dependency-driven
\series default
order: the detailed
\shape slanted
component
\shape default
testing and the top-view
\shape slanted
subsystem
\shape default
testing.
\end_layout
\begin_layout Subsubsection
Component testing
\end_layout
\begin_layout Standard
This section illustrates how every component will be integrated along in
order to constitute a subsystem.
\end_layout
\begin_layout Subsubsection*
Core Data
\end_layout
\begin_layout Standard
The first two elements to be integrated are the
\series bold
Data Manager
\series default
and the
\series bold
Database Management System
\series default
components.
We start from here because every other component relies on Data Access
Utilities to perform queries on the underlying data structure.
\end_layout
\begin_layout Standard
\begin_inset Float figure
wide false
sideways false
status collapsed
\begin_layout Plain Layout
\align center
\begin_inset Graphics
filename res/img/Core Data.png
width 60text%
height 60theight%
keepAspectRatio
\end_inset
\end_layout
\begin_layout Plain Layout
\begin_inset Caption Standard
\begin_layout Plain Layout
Core Data
\end_layout
\end_inset
\end_layout
\end_inset
\end_layout
\begin_layout Subsubsection*
Account Management
\end_layout
\begin_layout Standard
The
\shape slanted
Account Management
\shape default
subsystem relies on the
\series bold
Authentication Manager
\series default
and the
\series bold
AccountInformation Manager
\series default
.
The first one manages the correctness of user data submitted by the clients
to provide access to the PowerEnjoy services; the latter, instead, edits
and provides access to every account in the DBMS.
\end_layout
\begin_layout Standard
They both need the
\series bold
Core Data
\series default
subsystem to operate correctly.
\end_layout
\begin_layout Standard
\begin_inset Float figure
wide false
sideways false
status collapsed
\begin_layout Plain Layout
\align center
\begin_inset Graphics
filename res/img/Account Management 1.png
width 60text%
height 60theight%
keepAspectRatio
\end_inset
\end_layout
\begin_layout Plain Layout
\begin_inset Caption Standard
\begin_layout Plain Layout
Authentication Manager
\end_layout
\end_inset
\end_layout
\end_inset
\begin_inset Float figure
wide false
sideways false
status collapsed
\begin_layout Plain Layout
\align center
\begin_inset Graphics
filename res/img/Account Management 2.png
width 60text%
height 60theight%
keepAspectRatio
\end_inset
\end_layout
\begin_layout Plain Layout
\begin_inset Caption Standard
\begin_layout Plain Layout
AccountInformation Manager
\end_layout
\end_inset
\end_layout
\end_inset
\end_layout
\begin_layout Subsubsection*
Car Management
\end_layout
\begin_layout Standard
The
\shape slanted
Car Management
\shape default
subsystem relies on the
\series bold
ADS_Application Manager
\series default
and the
\series bold
Car Manager
\series default
.
The
\series bold
ADS_Application Manager
\series default
has to guarantee the correct communication between the
\series bold
Car Manager
\series default
and every ADS installed on each car.
The
\series bold
Car Manager
\series default
handles the status of each car by communicating the ADS installed on each
car.
\end_layout
\begin_layout Standard
They both need the
\series bold
Core Data
\series default
subsystem to operate correctly.
\end_layout
\begin_layout Standard
\begin_inset Float figure
wide false
sideways false
status collapsed
\begin_layout Plain Layout
\align center
\begin_inset Graphics
filename res/img/Car Management 1.png
width 60text%
height 60theight%
keepAspectRatio
\end_inset
\end_layout
\begin_layout Plain Layout
\begin_inset Caption Standard
\begin_layout Plain Layout
ADS_Application Manager
\end_layout
\end_inset
\end_layout
\end_inset
\begin_inset Float figure
wide false
sideways false
status collapsed
\begin_layout Plain Layout
\align center
\begin_inset Graphics
filename res/img/Car Management 2.png
width 100text%
height 80theight%
keepAspectRatio
\end_inset
\end_layout
\begin_layout Plain Layout
\begin_inset Caption Standard
\begin_layout Plain Layout
Car Manager
\end_layout
\end_inset
\end_layout
\end_inset
\end_layout
\begin_layout Subsubsection*
Reservation Management
\end_layout
\begin_layout Standard
The
\shape slanted
Reservation Management
\shape default
subsystem relies on the
\series bold
CheckAvailability Manager
\series default
and the
\series bold
Reservation Manager
\series default
.
The
\series bold
CheckAvailability Manager
\series default
is responsible for searching available cars in a specific location.
The
\series bold
Reservation Manager
\series default
handles each reservation by creating new entries, checking active entries
information and terminating active ones.
\end_layout
\begin_layout Standard
They both need the
\series bold
Core Data
\series default
and the
\series bold
Car Management
\series default
subsystems to operate correctly.
\end_layout
\begin_layout Standard
\begin_inset Float figure
wide false
sideways false
status collapsed
\begin_layout Plain Layout
\align center
\begin_inset Graphics
filename res/img/Reservation Management 1.png
width 100text%
height 80theight%
keepAspectRatio
\end_inset
\end_layout
\begin_layout Plain Layout
\begin_inset Caption Standard
\begin_layout Plain Layout
CheckAvailability Manager
\end_layout
\end_inset
\end_layout
\end_inset
\begin_inset Float figure
wide false
sideways false
status collapsed
\begin_layout Plain Layout
\align center
\begin_inset Graphics
filename res/img/Reservation Management 2.png
width 100text%
height 80theight%
keepAspectRatio
\end_inset
\end_layout
\begin_layout Plain Layout
\begin_inset Caption Standard
\begin_layout Plain Layout
Reservation Manager
\end_layout
\end_inset
\end_layout
\end_inset
\end_layout
\begin_layout Subsubsection*
Events Handler
\end_layout
\begin_layout Standard
The
\shape slanted
Event Handler
\shape default
subsystem relies on the
\series bold
Payment Manager
\series default
and the
\series bold
Notification Manager
\series default
.
The
\series bold
Payment Manager
\series default
calculates the fees for the rides at the end of each reservation and send
a payment request to an external service.
The
\series bold
Notification Manager
\series default
handles every notification sent by the system to both server and client
side.
\end_layout
\begin_layout Standard
They both need the
\series bold
Core Data
\series default
and the
\series bold
Reservation Management
\series default
subsystems to operate correctly.
\end_layout
\begin_layout Standard
\begin_inset Float figure
wide false
sideways false
status collapsed
\begin_layout Plain Layout
\align center
\begin_inset Graphics
filename res/img/Events Handler 1.png
width 100text%
height 80theight%
keepAspectRatio
\end_inset
\end_layout
\begin_layout Plain Layout
\begin_inset Caption Standard
\begin_layout Plain Layout
Payment Manager
\end_layout
\end_inset
\end_layout
\end_inset
\begin_inset Float figure
wide false
sideways false
status collapsed
\begin_layout Plain Layout
\align center
\begin_inset Graphics
filename res/img/Events Handler 2.png
width 100text%
height 80theight%
keepAspectRatio
\end_inset
\end_layout
\begin_layout Plain Layout
\begin_inset Caption Standard
\begin_layout Plain Layout
Notification Manager
\end_layout
\end_inset
\end_layout
\end_inset
\end_layout
\begin_layout Subsubsection*
Interfaces
\end_layout
\begin_layout Standard
The
\shape slanted
Interface
\shape default
subsystem relies on the
\series bold
App GUI
\series default
and the
\series bold
Web GUI
\series default
.
\end_layout
\begin_layout Standard
They both need the
\series bold
Core Data, Reservation Management
\series default
and
\series bold
Account Management
\series default
subsystems to operate correctly.
\end_layout
\begin_layout Standard
\begin_inset Float figure
wide false
sideways false
status collapsed
\begin_layout Plain Layout
\align center
\begin_inset Graphics
filename res/img/Interfaces 1 bis.png
width 100text%
height 80theight%
keepAspectRatio
\end_inset
\end_layout
\begin_layout Plain Layout
\begin_inset Caption Standard
\begin_layout Plain Layout
PowerEnjoyApp GUI
\end_layout
\end_inset
\end_layout
\end_inset
\begin_inset Float figure
wide false
sideways false
status collapsed
\begin_layout Plain Layout
\align center
\begin_inset Graphics
filename res/img/Interfaces 2 bis.png
width 100text%
height 80theight%
keepAspectRatio
\end_inset
\end_layout
\begin_layout Plain Layout
\begin_inset Caption Standard
\begin_layout Plain Layout
PowerEnjoyWeb GUI
\end_layout
\end_inset
\end_layout
\end_inset
\end_layout
\begin_layout Standard
\end_layout
\begin_layout Subsubsection
Subsystem Testing
\end_layout
\begin_layout Standard
This section shows the order in which subsystems will be integrated.
\end_layout
\begin_layout Standard
\begin_inset Float figure
wide false
sideways false
status collapsed
2017-01-11 11:27:49 +00:00
\begin_layout Plain Layout
\align center
\begin_inset Graphics
filename res/img/2.4.2.png
width 100text%
height 100theight%
keepAspectRatio
\end_inset
\end_layout
\begin_layout Plain Layout
\begin_inset Caption Standard
\begin_layout Plain Layout
Subsystem Integration Sequence
\end_layout
\end_inset
\end_layout
\end_inset
\end_layout
\begin_layout Standard
\begin_inset Newpage newpage
\end_inset
\end_layout
\begin_layout Section
\series bold
Individual Steps and Test Description
\end_layout
\begin_layout Standard
This section describes, for each step of the integration process above,
the type of tests that will be used to verify that the elements integrated
in this step perform as expected.
\end_layout
\begin_layout Standard
In the Sequence Diagrams shown in the Section 2.5 of the Design Document
can be found a more detailed representation of the components interaction.
\end_layout
\begin_layout Subsubsection*
Account Management
\end_layout
\begin_layout Standard
Functions implemented by
\series bold
Authentication Manager
\series default
:
\begin_inset VSpace smallskip
\end_inset
\end_layout
\begin_layout Standard
\family typewriter
register
\family default
: This function creates a new entity
\family typewriter
user
\family default
in the system with all the information provided by the user.
If the entered data are correct, an email is sent to the user address to
confirm the correct registration to the service.
\end_layout
\begin_layout Standard
\align center
\begin_inset Tabular
<lyxtabular version="3" rows="2" columns="1">
<features tabularvalignment="middle" tabularwidth="50page%">
<column alignment="center" valignment="top" width="0pt">
<row topspace="1pt" bottomspace="1pt">
<cell alignment="center" valignment="top" topline="true" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
\family typewriter
register
\end_layout
\end_inset
</cell>
</row>
<row>
<cell alignment="center" valignment="top" topline="true" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
\begin_inset Tabular
<lyxtabular version="3" rows="4" columns="2">
<features tabularvalignment="middle">
<column alignment="left" valignment="top">
<column alignment="left" valignment="top" width="44col%">
<row topspace="1pt" bottomspace="1pt">
<cell alignment="center" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
\series bold
Description
\end_layout
\end_inset
</cell>
<cell alignment="center" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
This is a cool description
\end_layout
\end_inset
</cell>
</row>
<row topspace="1pt" bottomspace="1pt">
<cell alignment="left" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
\shape slanted
Input
\end_layout
\end_inset
</cell>
<cell alignment="left" valignment="top" bottomline="true" leftline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
\shape slanted
Effect
\end_layout
\end_inset
</cell>
</row>
<row topspace="1pt" bottomspace="2pt">
<cell alignment="left" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
A null parameter
\end_layout
\end_inset
</cell>
<cell alignment="left" valignment="top" leftline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
A NullArgumentException is raised.
\end_layout
\end_inset
</cell>
</row>
<row topspace="1pt" bottomspace="2pt">
<cell alignment="left" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
A non-null user
\end_layout
\end_inset
</cell>
<cell mroffset="0.5pt" alignment="left" valignment="top" leftline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
The user data are correctly inserted in the database.
\end_layout
\end_inset
</cell>
</row>
</lyxtabular>
\end_inset
\end_layout
\end_inset
</cell>
</row>
</lyxtabular>
\end_inset
\end_layout
\begin_layout Standard
\begin_inset VSpace smallskip
\end_inset
\end_layout
\begin_layout Standard
\align center
\begin_inset Tabular
<lyxtabular version="3" rows="2" columns="1">
<features tabularvalignment="middle" tabularwidth="50page%">
<column alignment="center" valignment="top" width="0pt">
<row topspace="1pt" bottomspace="1pt">
<cell alignment="center" valignment="top" topline="true" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
\family typewriter
register
\end_layout
\end_inset
</cell>
</row>
<row>
<cell alignment="center" valignment="top" topline="true" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
\begin_inset Tabular
<lyxtabular version="3" rows="4" columns="2">
<features tabularvalignment="middle">
<column alignment="left" valignment="top">
<column alignment="left" valignment="top" width="44col%">
<row topspace="1pt" bottomspace="1pt">
<cell alignment="center" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
\series bold
Description
\end_layout
\end_inset
</cell>
<cell alignment="center" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
This is a cool description
\end_layout
\end_inset
</cell>
</row>
<row topspace="1pt" bottomspace="1pt">
<cell alignment="left" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
\shape slanted
Input
\end_layout
\end_inset
</cell>
<cell alignment="left" valignment="top" bottomline="true" leftline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
\shape slanted
Effect
\end_layout
\end_inset
</cell>
</row>
<row topspace="1pt" bottomspace="2pt">
<cell alignment="left" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
A null parameter
\end_layout
\end_inset
</cell>
<cell alignment="left" valignment="top" leftline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
A NullArgumentException is raised.
\end_layout
\end_inset
</cell>
</row>
<row topspace="1pt" bottomspace="2pt">
<cell alignment="left" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
A non-null user
\end_layout
\end_inset
</cell>
<cell mroffset="0.5pt" alignment="left" valignment="top" leftline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
The user data are correctly inserted in the database.
\end_layout
\end_inset
</cell>
</row>
</lyxtabular>
\end_inset
\end_layout
\end_inset
</cell>
</row>
</lyxtabular>
\end_inset
\end_layout
\begin_layout Standard
\begin_inset VSpace smallskip
\end_inset
\begin_inset VSpace smallskip
\end_inset
\end_layout
\begin_layout Standard
\begin_inset VSpace smallskip
\end_inset
\family typewriter
login
\family default
: This function allows any registered user to log into the system using
his username and password.
If the credentials are correct, the function returns a token to be used
in the future requests to identify the user.
Otherwise, an error is returned.
\end_layout
\begin_layout Subsubsection*
\series bold
AccountInformation Manager
\end_layout
\begin_layout Standard
Functions implemented by
\series bold
AccountInformation Manager
\series default
:
\begin_inset VSpace smallskip
\end_inset
\end_layout
\begin_layout Standard
\begin_inset ERT
status open
\begin_layout Plain Layout
\backslash
texttt{edit
\backslash
_profile}
\end_layout
\end_inset
: This function allows registered users to edit their profile information.
\begin_inset VSpace smallskip
\end_inset
\end_layout
\begin_layout Standard
\begin_inset ERT
status open
\begin_layout Plain Layout
\backslash
texttt{enable
\backslash
_mso}
\end_layout
\end_inset
: This function allows registered users to enable the money saving option.
\begin_inset VSpace smallskip
\end_inset
\end_layout
\begin_layout Standard
\begin_inset ERT
status open
\begin_layout Plain Layout
\backslash
texttt{disable
\backslash
_mso}
\end_layout
\end_inset
: This function allows registered users to disable the money saving option.
\begin_inset VSpace smallskip
\end_inset
\end_layout
\begin_layout Standard
\begin_inset ERT
status open
\begin_layout Plain Layout
\backslash
texttt{consult
\backslash
_history}
\end_layout
\end_inset
: This function allows registered users to consult their reservation history.
\end_layout
\begin_layout Standard
\begin_inset Newpage newpage
\end_inset
\end_layout
\begin_layout Subsubsection*
Car Management
\end_layout
\begin_layout Subsubsection*
Reservation Management
\end_layout
\begin_layout Subsubsection*
Events Handler
\end_layout
\begin_layout Subsubsection*
Interfaces
\end_layout
\begin_layout Standard
\begin_inset Newpage newpage
\end_inset
\end_layout
\begin_layout Section
\series bold
Tools and Test Equipment Required
\end_layout
\begin_layout Standard
This section presents all tools and test equipment needed to accomplish
the integration.
(REMOVE: Refer to the tools presented during the lectures.
Explain why and how you are going to use them.
Note that you may also use manual testing for some part.
Consider manual testing as one of the possible tools you have available)
\end_layout
\begin_layout Standard
\begin_inset Newpage newpage
\end_inset
\end_layout
\begin_layout Section
\series bold
Program Stubs and Test Data Required
\end_layout
\begin_layout Standard
this section aims to identify any program stubs or special test data required
for each integration step, based on the testing strategy and test design.
\end_layout
\begin_layout Standard
\begin_inset Newpage newpage
\end_inset
\end_layout
\begin_layout Section
Appendix [TO UPDATE]
\end_layout
\begin_layout Subsection
Tools used
\end_layout
\begin_layout Standard
We used the following tools to produce this document:
\end_layout
\begin_layout Itemize
\series bold
LaTex
\series default
as typesetting system to write this document
\end_layout
\begin_layout Itemize
\series bold
LyX
\series default
as editor
\end_layout
\begin_layout Itemize
\series bold
Visio Professional
\series default
and
\series bold
draw.io
\series default
to draw all the diagrams
\end_layout
\begin_layout Subsection
Hours of work
\end_layout
\begin_layout Standard
\begin_inset Float figure
wide false
sideways false
status open
\begin_layout Plain Layout
\align center
\begin_inset Graphics
filename res/img/hours.png
width 50text%
height 50theight%
keepAspectRatio
\end_inset
\end_layout
\begin_layout Plain Layout
\begin_inset Newpage pagebreak
\end_inset
\end_layout
\end_inset
\end_layout
\end_body
\end_document