From fdd84200afe78ac41a8d37a62fd8bd244e5f1eae Mon Sep 17 00:00:00 2001 From: Giulio De Pasquale Date: Fri, 20 Jan 2017 19:04:01 +0100 Subject: [PATCH] Section 6 tables stubs --- 4.Project Management/Planning.lyx | 808 +++++++++++++++++++++++------- 1 file changed, 624 insertions(+), 184 deletions(-) diff --git a/4.Project Management/Planning.lyx b/4.Project Management/Planning.lyx index 5831cf1..323ed1f 100644 --- a/4.Project Management/Planning.lyx +++ b/4.Project Management/Planning.lyx @@ -6210,6 +6210,14 @@ Risks have always to be considered in any long term project planning due \begin_layout Itemize +\series bold +Business risks +\series default +, involving the company developing the software. +\end_layout + +\begin_layout Itemize + \series bold Project risks \series default @@ -6224,312 +6232,744 @@ Technical risks , involving the project implementation. \end_layout -\begin_layout Itemize - -\series bold -Business risks -\series default -, involving the company developing the software. -\end_layout - \begin_layout Subsection Project Risks \end_layout -\begin_layout Itemize -Risk: No estimations/schedules have been made before this project. +\begin_layout Standard +\align center +\begin_inset Tabular + + + + + + + + +\begin_inset Text + +\begin_layout Plain Layout + +\series bold +Risk +\end_layout + +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout + +\series bold +Probability +\end_layout + +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout + +\series bold +Damage +\end_layout + +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout + +\series bold +Possible solution +\end_layout + +\end_inset + + + + +\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 – + development time \end_layout -\begin_deeper -\begin_layout Itemize -Probability: High +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +High \end_layout -\begin_layout Itemize -Damage: Critical +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +Critical \end_layout -\begin_layout Itemize -How to deal with it: Studying previous works on a similar subject can be - very helpful in this. +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +Studying previous works on a similar subject can be very helpful in this \end_layout -\end_deeper -\begin_layout Itemize -Risk: Due to several overlapping tasks the team is involved into, the project +\end_inset + + + + +\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 \end_layout -\begin_deeper -\begin_layout Itemize -Probability: High +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +High \end_layout -\begin_layout Itemize -Damage: Critical +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +Critical \end_layout -\begin_layout Itemize -How to deal with it: A strict organization among the team components is - fundamental. +\end_inset + + +\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. - + even the tiniest time slots available for this project \end_layout -\end_deeper -\begin_layout Itemize -Risk: A sudden growth in requirements can lead to a rush to meeting deadlines, - jeopardizing the overall quality +\end_inset + + + + +\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 -\begin_deeper -\begin_layout Itemize -Probability: Medium +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +Medium \end_layout -\begin_layout Itemize -Damage: Critical +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +Critical \end_layout -\begin_layout Itemize -How to deal with it: Thinking with a broader mind on the first stages can - be very helpful; however, the team should be care- ful against over-engineering - (which can also paralyze the develop- ment) +\end_inset + + +\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_deeper -\begin_layout Itemize -Risk: Collaboration issues can sometimes be crucial, especially when dealing - with task divisions. - +\end_inset + + + + +\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 -\begin_deeper -\begin_layout Itemize -Probability: Medium +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +Low \end_layout -\begin_layout Itemize -Damage: Medium +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +Critical \end_layout -\begin_layout Itemize -How to deal with it: Meeting often can be a solution, other than explicitly - writing whose responsibility for each task is. - +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +All team members must be able to cover all development sections and cooperate + effectively \end_layout -\end_deeper -\begin_layout Itemize -Risk: 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_inset + + + + +\begin_inset Text + +\begin_layout Plain Layout +Collaboration issues can sometimes be crucial, especially when dealing with + task divisions \end_layout -\begin_deeper -\begin_layout Itemize -Probability: Low +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +Medium \end_layout -\begin_layout Itemize -Damage: Catastrophic +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +Medium \end_layout -\begin_layout Itemize -How to deal with it: All team members must be able to cover all development - sections and cooperate effectively. +\end_inset + + +\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 + + + + +\end_inset + + +\end_layout + +\begin_layout Standard +\begin_inset Newpage newpage +\end_inset + + \end_layout -\end_deeper \begin_layout Subsection Technical Risks \end_layout -\begin_layout Itemize -Risk: 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 +\begin_layout Standard +\align center +\begin_inset Tabular + + + + + + + + +\begin_inset Text + +\begin_layout Plain Layout + +\series bold +Risk \end_layout -\begin_deeper -\begin_layout Itemize -Probability: High +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout + +\series bold +Probability \end_layout -\begin_layout Itemize -Damage: Critical +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout + +\series bold +Damage \end_layout -\begin_layout Itemize -How to deal with it: This has to be account in the first stages of planning - and inserted in the project scheduling. +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout + +\series bold +Possible solution +\end_layout + +\end_inset + + + + +\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 + + +\begin_inset Text + +\begin_layout Plain Layout +High +\end_layout + +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +Critical +\end_layout + +\end_inset + + +\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 + + + + +\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_deeper -\begin_layout Itemize -Risk: If the servers happen to be unreliable or in the case of more users - than expected, a significant downtime can seriously damage the whole project - – +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +Medium \end_layout -\begin_deeper -\begin_layout Itemize -Probability: Medium +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +Critical \end_layout -\begin_layout Itemize -Damage: Critical +\end_inset + + +\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 -\begin_layout Itemize -How to deal with it: A scalable design of the overall architec- ture is - essential, both in software and in hardware choices. - +\end_inset + + + + +\begin_inset Text + +\begin_layout Plain Layout +The application may be susceptible to security issues if not well designed \end_layout -\end_deeper -\begin_layout Itemize -Risk: The application may be susceptible to security issues if not well- - designed. - +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +Medium \end_layout -\begin_deeper -\begin_layout Itemize -Probability: Medium +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +Critical \end_layout -\begin_layout Itemize -Damage: Critical +\end_inset + + +\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 -\begin_layout Itemize -How to deal with it: All modern standards in computer security guidelines - must be followed, especially when dealing with the user input, which has - to be correctly verified and processed. - -\end_layout +\end_inset + + + + +\begin_inset Text -\end_deeper -\begin_layout Itemize -Risk: Testing may prove difficult (for example, if several mocks are necessary) +\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. - +n testing or even worse validation \end_layout -\begin_deeper -\begin_layout Itemize -Probability: Medium +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +Medium \end_layout -\begin_layout Itemize -Damage: Critical +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +Critical \end_layout -\begin_layout Itemize -How to deal with it: 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_inset + + +\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 + + + + +\end_inset + + +\end_layout + +\begin_layout Standard +\begin_inset Newpage newpage +\end_inset + + \end_layout -\end_deeper \begin_layout Subsection Business Risks \end_layout -\begin_layout Itemize -Risk: Testing devices & infrastructure (PCs, several mobile phones, server - rent) need to be purchased and configured. +\begin_layout Standard +\align center +\begin_inset Tabular + + + + + + + + +\begin_inset Text + +\begin_layout Plain Layout + +\series bold +Risk +\end_layout + +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout + +\series bold +Probability +\end_layout + +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout + +\series bold +Damage +\end_layout + +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout + +\series bold +Possible solution +\end_layout + +\end_inset + + + + +\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. - + is too small \end_layout -\begin_deeper -\begin_layout Itemize -Probability: High +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +High \end_layout -\begin_layout Itemize -Damage: Catastrophic +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +Critical \end_layout -\begin_layout Itemize -How to deal with it: Testing tools are to be clearly defined in [2], in - order to avoid worthless spendings. - +\end_inset + + +\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_deeper -\begin_layout Itemize -Risk: The company may find itself in serious financial trouble. +\end_inset + + + + +\begin_inset Text + +\begin_layout Plain Layout +The company may find itself in serious financial trouble \end_layout -\begin_deeper -\begin_layout Itemize -Probability: Low +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +Low \end_layout -\begin_layout Itemize -Damage: Catastrophic +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +Critical \end_layout -\begin_layout Itemize -How to deal with it: A feasibility study together with the RASD must highlight - the impossibility of starting a whole new project. - +\end_inset + + +\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_deeper -\begin_layout Itemize -Risk: myTaxiService may violate some (future) laws related to taxi management. - +\end_inset + + + + +\begin_inset Text + +\begin_layout Plain Layout +PowerEnjoy may violate some (future) laws related to taxi management \end_layout -\begin_deeper -\begin_layout Itemize -Probability: Low +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +Low \end_layout -\begin_layout Itemize -Damage: Critical +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +Critical \end_layout -\begin_layout Itemize -How to deal with it: A periodic check must be done in order to avoid legal - consequences. +\end_inset + + +\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. - + to the new regulations as soon as possible \end_layout -\end_deeper -\begin_layout Itemize -Risk: Another bigger company could acquire this company. - +\end_inset + + + + +\begin_inset Text + +\begin_layout Plain Layout +Another bigger company could acquire this company \end_layout -\begin_deeper -\begin_layout Itemize -Probability: Low +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +Medium \end_layout -\begin_layout Itemize -Damage: Marginal +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +Marginal \end_layout -\begin_layout Itemize -How to deal with it: No preventive solutions are available. - Note that this is not necessarily a negative thing. +\end_inset + + +\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 + + + + +\end_inset + + \end_layout -\end_deeper \begin_layout Standard \begin_inset Newpage newpage \end_inset