Internet-speed development: Difference between revisions

Revision as of 07:26, 11 December 2012

Revision as of 07:29, 11 December 2012

Line 581:

''Figure 4: Developing phase process/data model''

<TABLE{| WIDTH=581 BORDER=1>

<TR|- VALIGN=TOP>

<TD| WIDTH=194> | Activity

| Definition (source)

Activity

|-

</TD>

| Develop Features

<TD WIDTH=357>

| Building of solution components (documentation as well as code).”

Definition (source)

</TD>

</TR>

<TR>

<TD>

Develop Features

</TD>

<TD>

Building of solution components (documentation as well as code).”

(MSF Process model) <ref name="ReferenceA"/>

Also includes testing after the daily build, bug fixing and evaluating the features.

|-

</TD>

| Create Daily Build

</TR>

| Creation of a build after a workday.

<TR>

|-

<TD >

| Finalize Scope

Create Daily Build

| At this milestone, all features are complete and the solution is ready for external testing and stabilization.”</span></span></span></SPAN>

</TD>

<TD>

Creation of a build after a workday.

</TD>

</TR>

<TR>

<TD>

Finalize Scope

</TD>

<TD>

At this milestone, all features are complete and the solution is ready for external testing and stabilization.”</span></span></span></SPAN>

(MSF Process model) <ref name="ReferenceA"/>

|-

</TD>

| Develop Infrastructure

</TR>

| The infrastructure is developed.”

<TR>

<TD>

Develop Infrastructure

</TD>

<TD>

The infrastructure is developed.”

(MSF Process model) <ref name="ReferenceA"/>

|}

</TD>

</TR>

</TABLE>

''Table 5: Developing activities''

The most important activity in the developing phase is the development of the features. Besides the implementation of these features the scope is also finalized in this phase. During development new features may be added to the product, but once the scope is finalized the features become frozen and ready for testing and stabilizing. The infrastructure is also developed in this phase which means that network structures are identified and servers like for example a database server are defined.

<TABLE{| WIDTH=580 BORDER=1>

<TR|- VALIGN=TOP>

<TD| WIDTH=194> |

Concept

||

</TD>

<TD WIDTH=356>

Definition (source)

|-

</TD>

| INSTALLATION SCRIPTS AND CONFIGURATION SETTINGS FOR DEPLOYMENT

</TR>

| A collection of scripts and settings needed for the product to install/run.

<TR>

|-

<TD>

| INSTALLATION SCRIPTS AND CONFIGURATION SETTINGS FOR DEPLOYMENT

| The scripts needed to install the product.

</TD>

|-

<TD>

| CONFIGURATION SETTINGS

A collection of scripts and settings needed for the product to install/run.

|

</TD>

</TR>

<TR>

<TD>

INSTALLATION SCRIPTS

</TD>

<TD>

The scripts needed to install the product.

</TD>

</TR>

<TR>

<TD>

CONFIGURATION SETTINGS

</TD>

<TD>

The configuration properties of the product.

|-

</TD>

| PERFORMANCE SUPPORT ELEMENTS

</TR>

| Elements that support the performance of the product (extra databases, servers etc.).

<TR>

|-

<TD>

| TEST SPECIFICATIONS AND TEST CASES

PERFORMANCE SUPPORT ELEMENTS

| Specification of the tests and test cases used to validate the product.

</TD>

|-

<TD>

| FUNCTIONAL SPECIFICATION

Elements that support the performance of the product (extra databases, servers etc.).

| The functional specification describes in detail how each feature is to look and behave. It also describes the architecture and the design for all the features.”

</TD>

</TR>

<TR>

<TD>

TEST SPECIFICATIONS AND TEST CASES

</TD>

<TD>

Specification of the tests and test cases used to validate the product.

</TD>

</TR>

<TR>

<TD>

FUNCTIONAL SPECIFICATION

</TD>

<TD>

The functional specification describes in detail how each feature is to look and behave. It also describes the architecture and the design for all the features.”

(MSF Process model) <ref name="ReferenceA"/>

|-

</TD>

| SOURCE CODE AND EXECUTABLES

</TR>

| The source code/executables combination.

<TR>

|-

<TD>

| SOURCE CODE AND EXECUTABLES

| The source code of the product.

</TD>

|-

<TD>

| EXECUTABLE

The source code/executables combination.

| The executable created by source code.

</TD>

|}

</TR>

<TR>

<TD>

SOURCE CODE

</TD>

<TD>

The source code of the product.

</TD>

</TR>

<TR>

<TD>

EXECUTABLE

</TD>

<TD>

The executable created by source code.

</TD>

</TR>

</TABLE>

''Table 5: Concepts in the developing phase''