Fixes here and there

This commit is contained in:
Giulio De Pasquale 2017-01-13 22:56:59 +01:00
parent 6984c7d243
commit aaba835a99

View File

@ -693,13 +693,13 @@ 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.
) describes how integration tests are to be performed.
The tests here described focus on the information's flow between every
module as a whole.
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.
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.
@ -766,81 +766,6 @@ RMSS: Request Management Subsystem
ITPD: Integration Test Plan Document
\end_layout
\begin_layout Subsubsection*
Abbreviations
\end_layout
\begin_layout Description
Req.
as for Requirement
\end_layout
\begin_layout Description
Web
\begin_inset space ~
\end_inset
app as for Web Application
\end_layout
\begin_layout Subsection
Reference documents
\end_layout
\begin_layout Itemize
Requirements Analysis and Specification Document produced before
\end_layout
\begin_layout Itemize
Design Document produced before
\end_layout
\begin_layout Itemize
Specification Document
\end_layout
\begin_layout Itemize
JUnit
\begin_inset Foot
status open
\begin_layout Plain Layout
http://junit.org/junit4/javadoc/latest/
\end_layout
\end_inset
\end_layout
\begin_layout Itemize
JMockit
\begin_inset Foot
status open
\begin_layout Plain Layout
http://jmockit.org/api1x/overview-summary.html
\end_layout
\end_inset
\end_layout
\begin_layout Itemize
Arquillian
\begin_inset Foot
status open
\begin_layout Plain Layout
http://arquillian.org/guides/
\end_layout
\end_inset
\end_layout
\begin_layout Subsection
Document Structure
\end_layout
@ -1044,6 +969,106 @@ Integration Testing Plan Document of PowerEnjoy
Elements to be Integrated
\end_layout
\begin_layout Standard
The following list represents every component grouped into several subsystems:
\end_layout
\begin_layout Itemize
\series bold
Core Data
\end_layout
\begin_deeper
\begin_layout Itemize
Data Manager
\end_layout
\begin_layout Itemize
Database Management System
\end_layout
\end_deeper
\begin_layout Itemize
\series bold
Account Management
\end_layout
\begin_deeper
\begin_layout Itemize
Authentication Manager
\end_layout
\begin_layout Itemize
AccountInformation Manager
\end_layout
\end_deeper
\begin_layout Itemize
\series bold
Car Management
\end_layout
\begin_deeper
\begin_layout Itemize
ADS_Application Manager
\end_layout
\begin_layout Itemize
Car Manager
\end_layout
\end_deeper
\begin_layout Itemize
\series bold
Request Management
\end_layout
\begin_deeper
\begin_layout Itemize
CheckAvailability Manager
\end_layout
\begin_layout Itemize
Reservation Manager
\end_layout
\end_deeper
\begin_layout Itemize
\series bold
Events Handler
\end_layout
\begin_deeper
\begin_layout Itemize
Payment Manager
\end_layout
\begin_layout Itemize
Notification Manager
\end_layout
\end_deeper
\begin_layout Itemize
\series bold
Interfaces
\end_layout
\begin_deeper
\begin_layout Itemize
Web GUI
\end_layout
\begin_layout Itemize
App (Mobile) GUI
\end_layout
\end_deeper
\begin_layout Standard
For a detailed description of each components function and interaction refer
to the
@ -1051,7 +1076,6 @@ For a detailed description of each components function and interaction refer
Design Document
\series default
, section 2.3.
\end_layout
\begin_layout Subsection
@ -1119,8 +1143,8 @@ Data Manager
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.
We start from here because every other component relies on Data Manager
to perform queries on the underlying data structure.
\end_layout
\begin_layout Standard
@ -1294,7 +1318,7 @@ Car Manager
Car Manager
\series default
handles the status of each car by communicating the ADS installed on each
car.
car through the ADS_Application Manager.
\end_layout
\begin_layout Standard
@ -8761,7 +8785,7 @@ iOS
\begin_layout Standard
• Android phones will run
\series bold
Nougat
Kitkat
\series default
or superior
\end_layout
@ -8769,7 +8793,7 @@ Nougat
\begin_layout Standard
• iOS phones will run
\series bold
iOS 10
iOS 8
\series default
or superior
\end_layout
@ -8927,6 +8951,64 @@ draw.io
to draw all the diagrams
\end_layout
\begin_layout Subsection
Reference documents
\end_layout
\begin_layout Itemize
Requirements Analysis and Specification Document produced before
\end_layout
\begin_layout Itemize
Design Document produced before
\end_layout
\begin_layout Itemize
Specification Document
\end_layout
\begin_layout Itemize
JUnit
\begin_inset Foot
status open
\begin_layout Plain Layout
http://junit.org/junit4/javadoc/latest/
\end_layout
\end_inset
\end_layout
\begin_layout Itemize
JMockit
\begin_inset Foot
status open
\begin_layout Plain Layout
http://jmockit.org/api1x/overview-summary.html
\end_layout
\end_inset
\end_layout
\begin_layout Itemize
Arquillian
\begin_inset Foot
status open
\begin_layout Plain Layout
http://arquillian.org/guides/
\end_layout
\end_inset
\end_layout
\begin_layout Subsection
Hours of work
\end_layout