Section 4 done. Formatting fixes
This commit is contained in:
parent
0db3108b9f
commit
0bbd835a84
@ -658,6 +658,13 @@ http://www.qsm.com/resources/function-point-languages-table
|
||||
\end_inset
|
||||
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
\begin_inset Newpage newpage
|
||||
\end_inset
|
||||
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Section
|
||||
@ -3532,6 +3539,13 @@ SLOC=46\cdot181=8326
|
||||
\end_inset
|
||||
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
\begin_inset Newpage newpage
|
||||
\end_inset
|
||||
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Section
|
||||
@ -3820,31 +3834,43 @@ Schedule Estimation Now we can estimate the project duration with the following
|
||||
0.31 ⇠ = 9.44 M onths
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
\begin_inset Newpage newpage
|
||||
\end_inset
|
||||
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Section
|
||||
Tasks & Schedule
|
||||
Tasks scheduling
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
The main tasks of this project are the following:
|
||||
The main assignments of our project are:
|
||||
\end_layout
|
||||
|
||||
\begin_layout Enumerate
|
||||
Creation of the Requirement Analysis and Specification Document [2], which
|
||||
explains in detail functional and nonfunctional require- ments, domain
|
||||
assumption and goals of the application to be built.
|
||||
|
||||
Creation of the Requirement Analysis and Specification Document (
|
||||
\series bold
|
||||
RASD
|
||||
\series default
|
||||
).
|
||||
\end_layout
|
||||
|
||||
\begin_layout Enumerate
|
||||
Creation of the Design Document [3], which deals with the architecture and
|
||||
the design shape of the application.
|
||||
|
||||
Creation of the Design Document (
|
||||
\series bold
|
||||
DD
|
||||
\series default
|
||||
).
|
||||
\end_layout
|
||||
|
||||
\begin_layout Enumerate
|
||||
Creation of the Integration Testing Plan Document [5], which con- tains
|
||||
integration testing strategy we intend to apply to the application.
|
||||
|
||||
Creation of the Integration Testing Plan Document (
|
||||
\series bold
|
||||
ITPD
|
||||
\series default
|
||||
).
|
||||
\end_layout
|
||||
|
||||
\begin_layout Enumerate
|
||||
@ -3852,13 +3878,12 @@ Creation of the Project Plan, this document.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Enumerate
|
||||
Preparation of a quick presentation, using slides, (⇠ 10 min) of the previously
|
||||
mentioned documents to our client.
|
||||
Creation of a set of slides to present our work to the client.
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Enumerate
|
||||
Development of the entire application and the preparation of the unit tests.
|
||||
Development of the system and the preparation of the unit tests.
|
||||
|
||||
\end_layout
|
||||
|
||||
@ -3868,23 +3893,46 @@ Running of integration testing on the application.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
For the first tasks the activities were already given along with correspond-
|
||||
ing deadlines for the submission of needed documents.
|
||||
Starting from the im- plementation, instead, no schedule was given so,
|
||||
according to the COCOMO estimation performed and described in 2, we expect
|
||||
the implementation of the application to be complete in 9.5 months, around
|
||||
the 15th of September 2016.
|
||||
Regarding the integration testing, it will take place in the last month
|
||||
of developement.
|
||||
The development of the application started after the creation of the De-
|
||||
sign Document and will be carried on in parallel with the rest of the tasks.
|
||||
Tests will be run on the developing application in order to verify the
|
||||
proper functioning of every new functionality added.
|
||||
In Figure 3 you can find the dependency graph of every task, in Table 20,
|
||||
The first four tasks were already completed within the given submission
|
||||
deadlines.
|
||||
Starting from step 5 onward, according to our COCOMO® estimation
|
||||
\begin_inset Foot
|
||||
status open
|
||||
|
||||
\begin_layout Plain Layout
|
||||
see Section 3 for more details
|
||||
\end_layout
|
||||
|
||||
\end_inset
|
||||
|
||||
, we expect to deliver a working implementation within
|
||||
\series bold
|
||||
TODO
|
||||
\series default
|
||||
months which corresponds to
|
||||
\series bold
|
||||
mid-TODO.
|
||||
|
||||
\series default
|
||||
The development started just after the submission of the Design Document
|
||||
and continued simultaneously with the rest of the tasks; the integration
|
||||
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.
|
||||
|
||||
\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.
|
||||
Also the Gantt chart for the project is provided in Figure 4.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
\begin_inset Newpage newpage
|
||||
\end_inset
|
||||
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Section
|
||||
Resource Allocation
|
||||
\end_layout
|
||||
@ -3912,6 +3960,13 @@ This section is meant to show the way our available resources are allocated
|
||||
24, 25, 26, 27.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
\begin_inset Newpage newpage
|
||||
\end_inset
|
||||
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Section
|
||||
Risks
|
||||
\end_layout
|
||||
@ -4254,6 +4309,13 @@ How to deal with it: No preventive solutions are available.
|
||||
\end_layout
|
||||
|
||||
\end_deeper
|
||||
\begin_layout Standard
|
||||
\begin_inset Newpage newpage
|
||||
\end_inset
|
||||
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Section
|
||||
Appendix
|
||||
\end_layout
|
||||
|
Loading…
Reference in New Issue
Block a user