Internet-speed development: Difference between revisions

Content deleted Content added
deployment phase: Remove <font face> per WP:FONTFAMILY and clean up the mess
m deployment phase: convert wikicode to html
Line 903:
 
===deployment phase===
 
[[Image:Deploying.jpg]]
 
''Figure 6: Deployment phase process/data model''
<TABLE{| WIDTH=581 BORDER=1>
<TR|- VALIGN=TOP>
<TD| WIDTH=194> |
Activity
| Definition (source)
</TD>
|-
<TD WIDTH=357>
| Deploy the Core Components
Definition (source)
| Deployment of all components needed by the product (such as database servers, mail servers etc.)
</TD>
|-
</TR>
| Deploy the solution on site
<TR>
| For tailor-made systems deployment of the product occurs here (can be skipped for software products).
<TD>
|-
Deploy the Core Components
| Stabilize the deployment
</TD>
| Tacking, monitoring and improving the deployed components.
<TD>
|-
Deployment of all components needed by the product (such as database servers, mail servers etc.)
| Transfer the project to operations and support
</TD>
| Transferring all documents and code to the operations and support team.
</TR>
|-
<TR>
| Obtain final approval from customer
<TD>
| The customer must agree that the team has met its objectives before it can declare the solution to be in production and close out the project. This requires a stable solution, as well as clearly stated success criteria. In order for the solution to be considered stable, appropriate operations and support systems must be in place.”
Deploy the solution on site
</TD>
<TD>
For tailor-made systems deployment of the product occurs here (can be skipped for software products).
</TD>
</TR>
<TR>
<TD>
Stabilize the deployment
</TD>
<TD>
Tacking, monitoring and improving the deployed components.
</TD>
</TR>
<TR>
<TD>
Transfer the project to operations and support
</TD>
<TD>
Transferring all documents and code to the operations and support team.
</TD>
</TR>
<TR >
<TD >
Obtain final approval from customer
</TD>
<TD>
The customer must agree that the team has met its objectives before it can declare the solution to be in production and close out the project. This requires a stable solution, as well as clearly stated success criteria. In order for the solution to be considered stable, appropriate operations and support systems must be in place.”
 
(MSF Process model)<ref name="ReferenceA"/>
|-
</TD>
| Review the project
</TR>
| Final review of the project.
<TR>
|}
<TD>
Review the project
</TD>
<TD>
Final review of the project.
</TD>
</TR>
</TABLE>
''Table 8: Deploying activities''
 
The main activity in the deploying phase is the installation of the infrastructure needed to run the product (deployment of servers etc.). Also the documents are finalized and transferred to the operations and support department, a knowledge base is created and the product and project are reviewed by the customer (if applicable) and the project team.
<TABLE{| WIDTH=579 BORDER=1>
<TR|- VALIGN=TOP>
<TD| WIDTH=194> | Concept
| WIDTH=356 | Definition (source)
Concept
|-
</TD>
| PROCEDURES AND PROCESSES
<TD WIDTH=356>
| Collection of procedures and processes.
Definition (source)
|-
</TD>
| PROCEDURES
</TR>
| Collection of procedures to be used for installation and operation of the product.
<TR>
|-
<TD>
PROCEDURES AND| PROCESSES
| Collection of processes to be used for installation and operation of the product.
</TD>
|-
<TD>
| KNOWLEDGE BASE, REPORTS, LOGBOOKS
Collection of procedures and processes.
| Collection of the knowledge base, reports and logbooks.
</TD>
|-
</TR>
| KNOWLEDGE BASE
<TR>
| The knowledge base associated with the product.
<TD>
|-
PROCEDURES
| REPORTS
</TD>
| The reports associated with the product.
<TD>
|-
Collection of procedures to be used for installation and operation of the product.
| LOGBOOKS
</TD>
| Logbooks associated with the product.
</TR>
|-
<TR>
| DOCUMENT REPOSITORY
<TD>
| A repository of all documents.
PROCESSES
|-
</TD>
| FINAL VERSIONS OF ALL PROJECT DOCUMENTS
<TD>
| The final versions of the project documents.
Collection of processes to be used for installation and operation of the product.
|-
</TD>
| OPERATION AND SUPPORT INFORMATION SYSTEMS
</TR>
| Systems used by the operation and support teams associated with the product.
<TR>
|-
<TD>
| CUSTOMER/USER SATISFACTION DATA
KNOWLEDGE BASE, REPORTS, LOGBOOKS
| Collection of data from the customer/user about his satisfaction with the product.
</TD>
|-
<TD>
| DEFINITION OF NEXT STEPS
Collection of the knowledge base, reports and logbooks.
| Description of next steps to take for evolving the product.
</TD>
|-
</TR>
| PROJECT CLOSE-OUT REPORT
<TR>
|
<TD>
KNOWLEDGE BASE
</TD>
<TD>
The knowledge base associated with the product.
</TD>
</TR>
<TR>
<TD>
REPORTS
</TD>
<TD>
The reports associated with the product.
</TD>
</TR>
<TR>
<TD>
LOGBOOKS
</TD>
<TD>
Logbooks associated with the product.
</TD>
</TR>
<TR>
<TD>
DOCUMENT REPOSITORY
</TD>
<TD>
A repository of all documents.
</TD>
</TR>
<TR>
<TD>
FINAL VERSIONS OF ALL PROJECT DOCUMENTS
</TD>
<TD>
The final versions of the project documents.
</TD>
</TR>
<TR>
<TD >
OPERATION AND SUPPORT INFORMATION SYSTEMS
</TD>
<TD>
Systems used by the operation and support teams associated with the product.
</TD>
</TR>
<TR>
<TD>
CUSTOMER/USER SATISFACTION DATA
</TD>
<TD>
Collection of data from the customer/user about his satisfaction with the product.
</TD>
</TR>
<TR>
<TD>
DEFINITION OF NEXT STEPS
</TD>
<TD>
Description of next steps to take for evolving the product.
</TD>
</TR>
<TR>
<TD>
PROJECT CLOSE-OUT REPORT
</TD>
<TD>
Final report on the product, project and the transfer to operations and support.
|}
</TD>
</TR>
</TABLE>
''Table 9: Concepts in Deploying phase''