Section 6.3 done

4.Project Management/Planning.lyx

@@ -9034,11 +9034,50 @@ In the meantime, tests will be run all along the entire development process
 \begin_layout Standard
 
 \series bold
-In Figure 3 you can find the dependency graph of every task, in Table 20,
- instead, you can find the schedule of every task.
+In Figure 1 you can find the dependency graph of every task.
  Also the Gantt chart for the project is provided in Figure 4.
 \end_layout
 
+\begin_layout Standard
+\begin_inset Float figure
+wide false
+sideways false
+status open
+
+\begin_layout Plain Layout
+
+\end_layout
+
+\begin_layout Plain Layout
+\align center
+\begin_inset Graphics
+	filename res/Dependencies.png
+	lyxscale 10
+	scale 45
+
+\end_inset
+
+
+\begin_inset Caption Standard
+
+\begin_layout Plain Layout
+Dependency graph
+\end_layout
+
+\end_inset
+
+
+\end_layout
+
+\begin_layout Plain Layout
+
+\end_layout
+
+\end_inset
+
+
+\end_layout
+
 \begin_layout Standard
 \begin_inset Newpage newpage
 \end_inset
@@ -9095,7 +9134,7 @@ The following tables explain further the work division throughout the whole
 \begin_inset Float table
 wide false
 sideways false
-status open
+status collapsed
 
 \begin_layout Plain Layout
 \begin_inset Tabular
@@ -9357,7 +9396,7 @@ RASD:
 \begin_inset Float table
 wide false
 sideways false
-status open
+status collapsed
 
 \begin_layout Plain Layout
 \begin_inset Tabular
@@ -9619,7 +9658,7 @@ Design Document:
 \begin_inset Float table
 wide false
 sideways false
-status open
+status collapsed
 
 \begin_layout Plain Layout
 \begin_inset Tabular
@@ -9885,7 +9924,7 @@ ITPD:
 \begin_inset Float table
 wide false
 sideways false
-status open
+status collapsed
 
 \begin_layout Plain Layout
 \align center
@@ -10638,9 +10677,8 @@ Possible solution
 \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
+The testing phase may be harder than expected and / or highlight bugs that
+ are hard to solve.
 \end_layout
 
 \end_inset
@@ -10667,10 +10705,9 @@ Critical
 \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
+Every component has to be tested as soon as possible in order to solve critical
+ bugs and integration testing has to be executed as defined in the ITPD.
+ A requirements check has to be done periodically.
 \end_layout
 
 \end_inset
@@ -10681,8 +10718,8 @@ All components must be unit tested as soon as possible, to eliminate serious
 \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
+Lack of experience in the new environment (e.g JavaEE) may slow down the
+ development or other experienced team members.
 \end_layout
 
 \end_inset
@@ -10709,8 +10746,8 @@ Critical
 \begin_inset Text
 
 \begin_layout Plain Layout
-This has to be account in the first stages of planning and inserted in the
- project scheduling
+This has to be taken into account in the first stages of planning and put
+ into the project scheduling.
 \end_layout
 
 \end_inset
@@ -10721,7 +10758,8 @@ This has to be account in the first stages of planning and inserted in the
 \begin_inset Text
 
 \begin_layout Plain Layout
-The application may be susceptible to security issues if not well designed
+Security bugs may be suddenly discovered if the application is not well
+ designed.
 \end_layout
 
 \end_inset
@@ -10748,9 +10786,10 @@ Critical
 \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
+Computer security guidelines have to be followed in order to minimize the
+ number of incidents; when dealing with user inputs, each field has to be
+ sanitized.
+ 
 \end_layout
 
 \end_inset
@@ -10761,8 +10800,8 @@ y when dealing with the user input, which has to be correctly verified and
 \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 significant downtime can critically damage the whole project if the servers
+ are unreliable or more than the expected number of users use the service.
  
 \end_layout
 
@@ -10790,8 +10829,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
+The architecture has to adopt a fully scalable design, both software and
+ hardware side.
 \end_layout
 
 \end_inset