Deployment management

Deployment is the realisation of an application, or execution of a plan, idea, model, design, specification, standard, algorithm, or policy.

Computer science
In computer science, a deployment is a realisation of a technical specification or algorithm as a program, software component, or other computer system through computer programming and deployment. Many implementations may exist for a given specification or standard. For example, web browsers contain implementations of World Wide Web Consortium-recommended specifications, and software development tools contain deployment of programming languages.

A special case occurs in object-oriented programming, when a concrete class deploys an interface; in this case the concrete class is an deployment of the interface and it includes methods which are deployments of those methods specified by the interface.

Information technology (IT)
In the IT Industry, deployment refers to post-sales process of guiding a client from purchase to use of the software or hardware that was purchased. This includes requirements analysis, scope analysis, customisations, systems integrations, user policies, user training and delivery. These steps are often overseen by a project manager using project management methodologies. Software Deployment involves several professionals that are relatively new to the knowledge based economy such as business analysts, software implementation specialists, solutions architects, and project managers.

To deploy a system successfully, a large number of inter-related tasks need to be carried out in an appropriate sequence. Utilising a well-proven implementation methodology and enlisting professional advice can help but often it is the number of tasks, poor planning and inadequate resourcing that causes problems with an deployment project, rather than any of the tasks being particularly difficult. Similarly with the cultural issues it is often the lack of adequate consultation and two-way communication that inhibits achievement of the desired results.

Political science
In political science, deployment refers to the carrying out of public policy. Legislatures pass laws that are then carried out by public servants working in bureaucratic agencies. This process consists of rule-making, rule-administration and rule-adjudication. Factors impacting deployment include the legislative intent, the administrative capacity of the deploying bureaucracy, interest group activity and opposition, and executive support.

Social and health sciences
"Deployment is defined as a specified set of activities designed to put into practice an activity or program of known dimensions. According to this definition, deployment processes are purposeful and are described in sufficient detail such that independent observers can detect the presence and strength of the "specific set of activities" related to implementation. In addition, the activity or program being deployed is described in sufficient detail so that independent observers can detect its presence and strength."

Water and natural resources
In water and natural resources, deployment refers to the actualisation of best management practices with the ultimate goals of conserving natural resources and improving the quality of water bodies.

Types:
 * Direct changeover
 * Parallel running or as known as parallel
 * Pilot introduction or as known as pilot
 * Well-trade
 * Phased Deployment

Role of end users
System deployment generally benefits from high levels of user involvement and management support. User participation in the design and operation of information systems has several positive results. First, if users are heavily involved in systems design, they move opportunities to mold the system according to their priorities and business requirements, and more opportunities to control the outcome. Second, they are more likely to react positively to the change process. Incorporating user knowledge and expertise leads to better solutions.

The relationship between users and information systems specialists has traditionally been a problem area for information systems deployment efforts. Users and information systems specialists tend to have different backgrounds, interests, and priorities. This is referred to as the user-designer communications gap. These differences lead to divergent organizational loyalties, approaches to problem solving, and vocabularies. Examples of these differences or concerns are below:

User concerns

 * Will the system deliver the information I need for my work?
 * How quickly can I access the data?
 * How easily can I retrieve the data?
 * How much clerical support will I need to enter data into the system?
 * How will the operation of the system fit into my daily business schedule?

Designer concerns

 * How much storage space will the master file consume?
 * How many lines of program code will it take to perform this function?
 * How can we cut down on CPU time when we run the system?
 * What are the most efficient ways of storing this data?
 * What database management system should we use?