peperunas/swing2
1
0
Fork 0
Code Issues 3 Pull Requests Releases Wiki Activity

Section 6.1, section 4 layout

Browse Source
This commit is contained in:
Giulio De Pasquale 2017-01-20 18:36:48 +01:00
parent 5ca0f810f3
commit c26a47bcb2
1 changed files with 23 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

51
4.Project Management/Planning.lyx
View File

@ -5166,7 +5166,11 @@ Running of integration testing on the application.
\begin_layout Standard \begin_layout Standard
The first four tasks were already completed within the given submission The first four tasks were already completed within the given submission
deadlines. deadlines.
Starting from step 5 onward, according to our COCOMO® estimation
\end_layout
\begin_layout Standard
Starting from step 5 onward, according to our COCOMO® estimation
\begin_inset Foot \begin_inset Foot
status open status open
@ -5188,9 +5192,16 @@ mid-TODO.
The development started just after the submission of the Design Document The development started just after the submission of the Design Document
and continued simultaneously with the rest of the tasks; the integration and continued simultaneously with the rest of the tasks; the integration
testing will take place in the last month. testing will take place in the last month.
In the meantime, tests will be run all along the entire development process
to verify the proper functioning of every added feature.
\end_layout
\begin_layout Standard
In the meantime, tests will be run all along the entire development process
to verify the proper functioning of every added feature.
\end_layout
\begin_layout Standard
\series bold \series bold
In Figure 3 you can find the dependency graph of every task, in Table 20, In Figure 3 you can find the dependency graph of every task, in Table 20,
instead, you can find the schedule of every task. instead, you can find the schedule of every task.
@ -6191,50 +6202,34 @@ Risks
\begin_layout Standard \begin_layout Standard
Risks have always to be considered in any long term project planning due Risks have always to be considered in any long term project planning due
to their uncertain nature. to their uncertain nature.
The whole development could fail suddenly due to external actions, economical
\begin_inset Note Note situations or architectural changes; this is the reason why they are here
status open analyzed.
\begin_layout Plain Layout
A sudden change in mind, actions, economi- cal situations and alike could
drift the project development into failure
\end_layout
\end_inset
; this is the reason why they are here analyzed.
Three main risk categories will be later described: Three main risk categories will be later described:
\end_layout \end_layout
\begin_layout Itemize \begin_layout Itemize
\series bold \series bold
Project risks: Project risks
\series default \series default
involving the project plan (described in these pages). , involving the project plan.
Project schedule and overall costs may be subject to (worse) changes due
to these risks.
\end_layout \end_layout
\begin_layout Itemize \begin_layout Itemize
\series bold \series bold
Technical risks: Technical risks
\series default \series default
involving the actual implementation of the project. , involving the project implementation.
They may affect the quality of the software being developed.
\end_layout \end_layout
\begin_layout Itemize \begin_layout Itemize
\series bold \series bold
Business risks: Business risks
\series default \series default
involving the company developing the software. , involving the company developing the software.
This may cause trouble to the project (e.g.
if the business cannot subsidize the software being developed anymore).
\end_layout \end_layout
\begin_layout Subsection \begin_layout Subsection