Section 6 tables stubs

This commit is contained in:
Giulio De Pasquale 2017-01-20 19:04:01 +01:00
parent c26a47bcb2
commit fdd84200af

View File

@ -6210,6 +6210,14 @@ Risks have always to be considered in any long term project planning due
\begin_layout Itemize \begin_layout Itemize
\series bold
Business risks
\series default
, involving the company developing the software.
\end_layout
\begin_layout Itemize
\series bold \series bold
Project risks Project risks
\series default \series default
@ -6224,312 +6232,744 @@ Technical risks
, involving the project implementation. , involving the project implementation.
\end_layout \end_layout
\begin_layout Itemize
\series bold
Business risks
\series default
, involving the company developing the software.
\end_layout
\begin_layout Subsection \begin_layout Subsection
Project Risks Project Risks
\end_layout \end_layout
\begin_layout Itemize \begin_layout Standard
Risk: No estimations/schedules have been made before this project. \align center
\begin_inset Tabular
<lyxtabular version="3" rows="6" 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
No estimations/schedules have been made before this project.
A lack of experience in this area can lead to serious errors in evaluating A lack of experience in this area can lead to serious errors in evaluating
development time development time
\end_layout \end_layout
\begin_deeper \end_inset
\begin_layout Itemize </cell>
Probability: High <cell alignment="block" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
High
\end_layout \end_layout
\begin_layout Itemize \end_inset
Damage: Critical </cell>
<cell alignment="block" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Critical
\end_layout \end_layout
\begin_layout Itemize \end_inset
How to deal with it: Studying previous works on a similar subject can be </cell>
very helpful in this. <cell alignment="block" 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
\end_layout \end_layout
\end_deeper \end_inset
\begin_layout Itemize </cell>
Risk: Due to several overlapping tasks the team is involved into, the project </row>
<row topspace="4pt" bottomspace="4pt">
<cell alignment="block" valignment="top" usebox="none">
\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 is very likely to suffer from schedule delays
\end_layout \end_layout
\begin_deeper \end_inset
\begin_layout Itemize </cell>
Probability: High <cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
High
\end_layout \end_layout
\begin_layout Itemize \end_inset
Damage: Critical </cell>
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Critical
\end_layout \end_layout
\begin_layout Itemize \end_inset
How to deal with it: A strict organization among the team components is </cell>
fundamental. <cell alignment="block" valignment="top" usebox="none">
\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 This implies a constant cooperation between developers, in order to squeeze
even the tiniest time slots available for this project. even the tiniest time slots available for this project
\end_layout \end_layout
\end_deeper \end_inset
\begin_layout Itemize </cell>
Risk: A sudden growth in requirements can lead to a rush to meeting deadlines, </row>
jeopardizing the overall quality <row topspace="4pt" bottomspace="4pt">
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
A sudden growth in requirements can lead to a rush to meeting deadlines,
jeopardizing the overall quality
\end_layout \end_layout
\begin_deeper \end_inset
\begin_layout Itemize </cell>
Probability: Medium <cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Medium
\end_layout \end_layout
\begin_layout Itemize \end_inset
Damage: Critical </cell>
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Critical
\end_layout \end_layout
\begin_layout Itemize \end_inset
How to deal with it: Thinking with a broader mind on the first stages can </cell>
be very helpful; however, the team should be care- ful against over-engineering <cell alignment="block" valignment="top" usebox="none">
(which can also paralyze the develop- ment) \begin_inset Text
\begin_layout Plain Layout
Thinking with a broader mind on the first stages can be very helpful; however,
the team should be careful against over-engineering (which can also paralyze
the development)
\end_layout \end_layout
\end_deeper \end_inset
\begin_layout Itemize </cell>
Risk: Collaboration issues can sometimes be crucial, especially when dealing </row>
with task divisions. <row topspace="4pt" bottomspace="4pt">
<cell alignment="center" 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
\end_layout \end_layout
\begin_deeper \end_inset
\begin_layout Itemize </cell>
Probability: Medium <cell alignment="center" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Low
\end_layout \end_layout
\begin_layout Itemize \end_inset
Damage: Medium </cell>
<cell alignment="center" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Critical
\end_layout \end_layout
\begin_layout Itemize \end_inset
How to deal with it: Meeting often can be a solution, other than explicitly </cell>
writing whose responsibility for each task is. <cell alignment="center" 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
\end_layout \end_layout
\end_deeper \end_inset
\begin_layout Itemize </cell>
Risk: The team is very small (3 people) but homogeneous; if someone leaves </row>
or gets ill then the remaining team would have serious repercus- sions. <row topspace="4pt" bottomspace="4pt">
<cell alignment="block" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Collaboration issues can sometimes be crucial, especially when dealing with
task divisions
\end_layout \end_layout
\begin_deeper \end_inset
\begin_layout Itemize </cell>
Probability: Low <cell alignment="block" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Medium
\end_layout \end_layout
\begin_layout Itemize \end_inset
Damage: Catastrophic </cell>
<cell alignment="block" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Medium
\end_layout \end_layout
\begin_layout Itemize \end_inset
How to deal with it: All team members must be able to cover all development </cell>
sections and cooperate effectively. <cell alignment="block" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Meeting often can be a solution, other than explicitly writing whose responsibil
ity for each task is
\end_layout
\end_inset
</cell>
</row>
</lyxtabular>
\end_inset
\end_layout
\begin_layout Standard
\begin_inset Newpage newpage
\end_inset
\end_layout \end_layout
\end_deeper
\begin_layout Subsection \begin_layout Subsection
Technical Risks Technical Risks
\end_layout \end_layout
\begin_layout Itemize \begin_layout Standard
Risk: A lack of previous experience in developing with Java EE can almost \align center
surely slow down the entire team, which has to study these new technologies \begin_inset Tabular
first <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_layout
\begin_deeper \end_inset
\begin_layout Itemize </cell>
Probability: High <cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
\series bold
Probability
\end_layout \end_layout
\begin_layout Itemize \end_inset
Damage: Critical </cell>
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
\series bold
Damage
\end_layout \end_layout
\begin_layout Itemize \end_inset
How to deal with it: This has to be account in the first stages of planning </cell>
and inserted in the project scheduling. <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
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
</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
This has to be account in the first stages of planning and inserted in the
project scheduling
\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
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_layout
\end_deeper \end_inset
\begin_layout Itemize </cell>
Risk: If the servers happen to be unreliable or in the case of more users <cell alignment="block" valignment="top" usebox="none">
than expected, a significant downtime can seriously damage the whole project \begin_inset Text
\begin_layout Plain Layout
Medium
\end_layout \end_layout
\begin_deeper \end_inset
\begin_layout Itemize </cell>
Probability: Medium <cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Critical
\end_layout \end_layout
\begin_layout Itemize \end_inset
Damage: Critical </cell>
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
A scalable design of the overall architec- ture is essential, both in software
and in hardware choices
\end_layout \end_layout
\begin_layout Itemize \end_inset
How to deal with it: A scalable design of the overall architec- ture is </cell>
essential, both in software and in hardware choices. </row>
<row topspace="4pt" bottomspace="4pt">
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
The application may be susceptible to security issues if not well designed
\end_layout \end_layout
\end_deeper \end_inset
\begin_layout Itemize </cell>
Risk: The application may be susceptible to security issues if not well- <cell alignment="block" valignment="top" usebox="none">
designed. \begin_inset Text
\begin_layout Plain Layout
Medium
\end_layout \end_layout
\begin_deeper \end_inset
\begin_layout Itemize </cell>
Probability: Medium <cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Critical
\end_layout \end_layout
\begin_layout Itemize \end_inset
Damage: Critical </cell>
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
All modern standards in computer security guidelines must be followed, especiall
y when dealing with the user input, which has to be correctly verified and
processed
\end_layout \end_layout
\begin_layout Itemize \end_inset
How to deal with it: All modern standards in computer security guidelines </cell>
must be followed, especially when dealing with the user input, which has </row>
to be correctly verified and processed. <row topspace="4pt" bottomspace="4pt">
<cell alignment="center" valignment="top" bottomline="true" usebox="none">
\end_layout \begin_inset Text
\end_deeper \begin_layout Plain Layout
\begin_layout Itemize Testing may prove difficult (for example, if several mocks are necessary)
Risk: Testing may prove difficult (for example, if several mocks are necessary)
or highlight problems which are hard to solve, especially when doing integratio or highlight problems which are hard to solve, especially when doing integratio
n testing or —even worse—validation. n testing or even worse validation
\end_layout \end_layout
\begin_deeper \end_inset
\begin_layout Itemize </cell>
Probability: Medium <cell alignment="center" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Medium
\end_layout \end_layout
\begin_layout Itemize \end_inset
Damage: Critical </cell>
<cell alignment="center" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Critical
\end_layout \end_layout
\begin_layout Itemize \end_inset
How to deal with it: All components must be unit tested as soon as possible, </cell>
to eliminate serious bugs when they first appear; integration testing must <cell alignment="center" valignment="top" bottomline="true" usebox="none">
be done according to the specifications contained in [5]. \begin_inset Text
A periodic check of requirements contained in [2] is also required.
\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 \end_layout
\end_deeper
\begin_layout Subsection \begin_layout Subsection
Business Risks Business Risks
\end_layout \end_layout
\begin_layout Itemize \begin_layout Standard
Risk: Testing devices & infrastructure (PCs, several mobile phones, server \align center
rent) need to be purchased and configured. \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 This is going to increase costs, that may be not sustainable if the company
is too small. is too small
\end_layout \end_layout
\begin_deeper \end_inset
\begin_layout Itemize </cell>
Probability: High <cell alignment="block" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
High
\end_layout \end_layout
\begin_layout Itemize \end_inset
Damage: Catastrophic </cell>
<cell alignment="block" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Critical
\end_layout \end_layout
\begin_layout Itemize \end_inset
How to deal with it: Testing tools are to be clearly defined in [2], in </cell>
order to avoid worthless spendings. <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_layout
\end_deeper \end_inset
\begin_layout Itemize </cell>
Risk: The company may find itself in serious financial trouble. </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_layout
\begin_deeper \end_inset
\begin_layout Itemize </cell>
Probability: Low <cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Low
\end_layout \end_layout
\begin_layout Itemize \end_inset
Damage: Catastrophic </cell>
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Critical
\end_layout \end_layout
\begin_layout Itemize \end_inset
How to deal with it: A feasibility study together with the RASD must highlight </cell>
the impossibility of starting a whole new project. <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_layout
\end_deeper \end_inset
\begin_layout Itemize </cell>
Risk: myTaxiService may violate some (future) laws related to taxi management. </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_layout
\begin_deeper \end_inset
\begin_layout Itemize </cell>
Probability: Low <cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Low
\end_layout \end_layout
\begin_layout Itemize \end_inset
Damage: Critical </cell>
<cell alignment="block" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Critical
\end_layout \end_layout
\begin_layout Itemize \end_inset
How to deal with it: A periodic check must be done in order to avoid legal </cell>
consequences. <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 In the case of drastic changes, the whole team must work in order to adapt
to the new regulations as soon as possible. to the new regulations as soon as possible
\end_layout \end_layout
\end_deeper \end_inset
\begin_layout Itemize </cell>
Risk: Another bigger company could acquire this company. </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_layout
\begin_deeper \end_inset
\begin_layout Itemize </cell>
Probability: Low <cell alignment="center" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Medium
\end_layout \end_layout
\begin_layout Itemize \end_inset
Damage: Marginal </cell>
<cell alignment="center" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Marginal
\end_layout \end_layout
\begin_layout Itemize \end_inset
How to deal with it: No preventive solutions are available. </cell>
Note that this is not necessarily a negative thing. <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
\end_layout
\end_inset
</cell>
</row>
</lyxtabular>
\end_inset
\end_layout \end_layout
\end_deeper
\begin_layout Standard \begin_layout Standard
\begin_inset Newpage newpage \begin_inset Newpage newpage
\end_inset \end_inset