Section 6 scrambling

This commit is contained in:
Giulio De Pasquale 2017-01-20 19:25:13 +01:00
parent d3395aa7d0
commit 327f88604e

View File

@ -10067,6 +10067,239 @@ Technical risks
, involving the project implementation.
\end_layout
\begin_layout Subsection
Business Risks
\end_layout
\begin_layout Standard
\align center
\begin_inset Tabular
<lyxtabular version="3" rows="5" columns="4">
<features tabularvalignment="middle" tabularwidth="78page%">
<column alignment="block" valignment="middle" width="33col%">
<column alignment="block" valignment="middle" width="7line%">
<column alignment="block" valignment="middle" width="7line%">
<column alignment="block" valignment="middle" width="33col%">
<row topspace="2pt" bottomspace="2pt">
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
\series bold
Risk
\end_layout
\end_inset
</cell>
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
\series bold
Probability
\end_layout
\end_inset
</cell>
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
\series bold
Damage
\end_layout
\end_inset
</cell>
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
\series bold
Possible solution
\end_layout
\end_inset
</cell>
</row>
<row topspace="4pt" bottomspace="4pt">
<cell alignment="block" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
PowerEnjoy may violate some (future) laws related to taxi management
\end_layout
\end_inset
</cell>
<cell alignment="block" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Low
\end_layout
\end_inset
</cell>
<cell alignment="block" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Critical
\end_layout
\end_inset
</cell>
<cell alignment="block" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
A periodic check must be done in order to avoid legal consequences.
In the case of drastic changes, the whole team must work in order to adapt
to the new regulations as soon as possible
\end_layout
\end_inset
</cell>
</row>
<row topspace="4pt" bottomspace="4pt">
<cell alignment="center" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Another bigger company could acquire this company
\end_layout
\end_inset
</cell>
<cell alignment="center" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Medium
\end_layout
\end_inset
</cell>
<cell alignment="center" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Marginal
\end_layout
\end_inset
</cell>
<cell alignment="center" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
No preventive solutions are available.
Note that this is not necessarily a negative thing
\end_layout
\end_inset
</cell>
</row>
<row topspace="4pt" bottomspace="4pt">
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
The company may find itself in serious financial trouble
\end_layout
\end_inset
</cell>
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Low
\end_layout
\end_inset
</cell>
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Critical
\end_layout
\end_inset
</cell>
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
A feasibility study together with the RASD must highlight the impossibility
of starting a whole new project
\end_layout
\end_inset
</cell>
</row>
<row topspace="4pt" bottomspace="4pt">
<cell alignment="block" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Testing devices & infrastructure (PCs, several mobile phones, server rent)
need to be purchased and configured.
This is going to increase costs, that may be not sustainable if the company
is too small
\end_layout
\end_inset
</cell>
<cell alignment="block" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
High
\end_layout
\end_inset
</cell>
<cell alignment="block" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Critical
\end_layout
\end_inset
</cell>
<cell alignment="block" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Testing tools are to be clearly defined in [2], in order to avoid worthless
spendings
\end_layout
\end_inset
</cell>
</row>
</lyxtabular>
\end_inset
\end_layout
\begin_layout Standard
\begin_inset Newpage newpage
\end_inset
\end_layout
\begin_layout Subsection
Project Risks
\end_layout
@ -10127,27 +10360,26 @@ Possible solution
</cell>
</row>
<row topspace="4pt" bottomspace="4pt">
<cell alignment="block" valignment="top" topline="true" usebox="none">
<cell alignment="center" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
No estimations/schedules have been made before this project.
A lack of experience in this area can lead to serious errors in evaluating
development time
The team is very small (3 people) but homogeneous; if someone leaves or
gets ill then the remaining team would have serious repercussions
\end_layout
\end_inset
</cell>
<cell alignment="block" valignment="top" topline="true" usebox="none">
<cell alignment="center" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
High
Low
\end_layout
\end_inset
</cell>
<cell alignment="block" valignment="top" topline="true" usebox="none">
<cell alignment="center" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
@ -10156,11 +10388,12 @@ Critical
\end_inset
</cell>
<cell alignment="block" valignment="top" topline="true" usebox="none">
<cell alignment="center" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Studying previous works on a similar subject can be very helpful in this
All team members must be able to cover all development sections and cooperate
effectively
\end_layout
\end_inset
@ -10171,8 +10404,9 @@ Studying previous works on a similar subject can be very helpful in this
\begin_inset Text
\begin_layout Plain Layout
Due to several overlapping tasks the team is involved into, the project
is very likely to suffer from schedule delays
No estimations/schedules have been made before this project.
A lack of experience in this area can lead to serious errors in evaluating
development time
\end_layout
\end_inset
@ -10199,9 +10433,7 @@ Critical
\begin_inset Text
\begin_layout Plain Layout
A strict organization among the team components is fundamental.
This implies a constant cooperation between developers, in order to squeeze
even the tiniest time slots available for this project
Studying previous works on a similar subject can be very helpful in this
\end_layout
\end_inset
@ -10249,40 +10481,40 @@ Thinking with a broader mind on the first stages can be very helpful; however,
</cell>
</row>
<row topspace="4pt" bottomspace="4pt">
<cell alignment="center" valignment="top" usebox="none">
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
The team is very small (3 people) but homogeneous; if someone leaves or
gets ill then the remaining team would have serious repercus- sions
Collaboration issues can sometimes be crucial, especially when dealing with
task divisions
\end_layout
\end_inset
</cell>
<cell alignment="center" valignment="top" usebox="none">
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Low
Medium
\end_layout
\end_inset
</cell>
<cell alignment="center" valignment="top" usebox="none">
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Critical
Medium
\end_layout
\end_inset
</cell>
<cell alignment="center" valignment="top" usebox="none">
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
All team members must be able to cover all development sections and cooperate
effectively
Meeting often can be a solution, other than explicitly writing whose responsibil
ity for each task is
\end_layout
\end_inset
@ -10293,8 +10525,8 @@ All team members must be able to cover all development sections and cooperate
\begin_inset Text
\begin_layout Plain Layout
Collaboration issues can sometimes be crucial, especially when dealing with
task divisions
Due to several overlapping tasks the team is involved into, the project
is very likely to suffer from schedule delays
\end_layout
\end_inset
@ -10303,7 +10535,7 @@ Collaboration issues can sometimes be crucial, especially when dealing with
\begin_inset Text
\begin_layout Plain Layout
Medium
High
\end_layout
\end_inset
@ -10312,7 +10544,7 @@ Medium
\begin_inset Text
\begin_layout Plain Layout
Medium
Critical
\end_layout
\end_inset
@ -10321,8 +10553,9 @@ Medium
\begin_inset Text
\begin_layout Plain Layout
Meeting often can be a solution, other than explicitly writing whose responsibil
ity for each task is
A strict organization among the team components is fundamental.
This implies a constant cooperation between developers, in order to squeeze
even the tiniest time slots available for this project
\end_layout
\end_inset
@ -10402,26 +10635,27 @@ Possible solution
</cell>
</row>
<row topspace="4pt" bottomspace="4pt">
<cell alignment="block" valignment="top" topline="true" usebox="none">
<cell alignment="center" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
A lack of previous experience in developing with Java EE can almost surely
slow down the entire team, which has to study these new technologies first
Testing may prove difficult (for example, if several mocks are necessary)
or highlight problems which are hard to solve, especially when doing integratio
n testing or even worse validation
\end_layout
\end_inset
</cell>
<cell alignment="block" valignment="top" topline="true" usebox="none">
<cell alignment="center" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
High
Medium
\end_layout
\end_inset
</cell>
<cell alignment="block" valignment="top" topline="true" usebox="none">
<cell alignment="center" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
@ -10430,12 +10664,14 @@ Critical
\end_inset
</cell>
<cell alignment="block" valignment="top" topline="true" usebox="none">
<cell alignment="center" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
This has to be account in the first stages of planning and inserted in the
project scheduling
All components must be unit tested as soon as possible, to eliminate serious
bugs when they first appear; integration testing must be done according
to the specifications contained in [5].
A periodic check of requirements contained in [2] is also required
\end_layout
\end_inset
@ -10446,9 +10682,8 @@ This has to be account in the first stages of planning and inserted in the
\begin_inset Text
\begin_layout Plain Layout
If the servers happen to be unreliable or in the case of more users than
expected, a significant downtime can seriously damage the whole projects
A lack of previous experience in developing with Java EE can almost surely
slow down the entire team, which has to study these new technologies first
\end_layout
\end_inset
@ -10457,7 +10692,7 @@ If the servers happen to be unreliable or in the case of more users than
\begin_inset Text
\begin_layout Plain Layout
Medium
High
\end_layout
\end_inset
@ -10475,8 +10710,8 @@ Critical
\begin_inset Text
\begin_layout Plain Layout
A scalable design of the overall architec- ture is essential, both in software
and in hardware choices
This has to be account in the first stages of planning and inserted in the
project scheduling
\end_layout
\end_inset
@ -10523,18 +10758,18 @@ y when dealing with the user input, which has to be correctly verified and
</cell>
</row>
<row topspace="4pt" bottomspace="4pt">
<cell alignment="center" valignment="top" bottomline="true" usebox="none">
<cell alignment="block" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Testing may prove difficult (for example, if several mocks are necessary)
or highlight problems which are hard to solve, especially when doing integratio
n testing or even worse validation
If the servers happen to be unreliable or in the case of more users than
expected, a significant downtime can seriously damage the whole projects
\end_layout
\end_inset
</cell>
<cell alignment="center" valignment="top" bottomline="true" usebox="none">
<cell alignment="block" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
@ -10543,7 +10778,7 @@ Medium
\end_inset
</cell>
<cell alignment="center" valignment="top" bottomline="true" usebox="none">
<cell alignment="block" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
@ -10552,247 +10787,12 @@ Critical
\end_inset
</cell>
<cell alignment="center" valignment="top" bottomline="true" usebox="none">
<cell alignment="block" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
All components must be unit tested as soon as possible, to eliminate serious
bugs when they first appear; integration testing must be done according
to the specifications contained in [5].
A periodic check of requirements contained in [2] is also required
\end_layout
\end_inset
</cell>
</row>
</lyxtabular>
\end_inset
\end_layout
\begin_layout Standard
\begin_inset Newpage newpage
\end_inset
\end_layout
\begin_layout Subsection
Business Risks
\end_layout
\begin_layout Standard
\align center
\begin_inset Tabular
<lyxtabular version="3" rows="5" columns="4">
<features tabularvalignment="middle" tabularwidth="78page%">
<column alignment="block" valignment="middle" width="33col%">
<column alignment="block" valignment="middle" width="7line%">
<column alignment="block" valignment="middle" width="7line%">
<column alignment="block" valignment="middle" width="33col%">
<row topspace="2pt" bottomspace="2pt">
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
\series bold
Risk
\end_layout
\end_inset
</cell>
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
\series bold
Probability
\end_layout
\end_inset
</cell>
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
\series bold
Damage
\end_layout
\end_inset
</cell>
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
\series bold
Possible solution
\end_layout
\end_inset
</cell>
</row>
<row topspace="4pt" bottomspace="4pt">
<cell alignment="block" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Testing devices & infrastructure (PCs, several mobile phones, server rent)
need to be purchased and configured.
This is going to increase costs, that may be not sustainable if the company
is too small
\end_layout
\end_inset
</cell>
<cell alignment="block" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
High
\end_layout
\end_inset
</cell>
<cell alignment="block" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Critical
\end_layout
\end_inset
</cell>
<cell alignment="block" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Testing tools are to be clearly defined in [2], in order to avoid worthless
spendings
\end_layout
\end_inset
</cell>
</row>
<row topspace="4pt" bottomspace="4pt">
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
The company may find itself in serious financial trouble
\end_layout
\end_inset
</cell>
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Low
\end_layout
\end_inset
</cell>
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Critical
\end_layout
\end_inset
</cell>
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
A feasibility study together with the RASD must highlight the impossibility
of starting a whole new project
\end_layout
\end_inset
</cell>
</row>
<row topspace="4pt" bottomspace="4pt">
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
PowerEnjoy may violate some (future) laws related to taxi management
\end_layout
\end_inset
</cell>
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Low
\end_layout
\end_inset
</cell>
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Critical
\end_layout
\end_inset
</cell>
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
A periodic check must be done in order to avoid legal consequences.
In the case of drastic changes, the whole team must work in order to adapt
to the new regulations as soon as possible
\end_layout
\end_inset
</cell>
</row>
<row topspace="4pt" bottomspace="4pt">
<cell alignment="center" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Another bigger company could acquire this company
\end_layout
\end_inset
</cell>
<cell alignment="center" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Medium
\end_layout
\end_inset
</cell>
<cell alignment="center" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Marginal
\end_layout
\end_inset
</cell>
<cell alignment="center" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
No preventive solutions are available.
Note that this is not necessarily a negative thing
A scalable design of the overall architec- ture is essential, both in software
and in hardware choices
\end_layout
\end_inset