Implementation

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

Industry-specific definitions[]

Computer science[]

In computer science, an implementation is a realization 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 implementations of programming languages.

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

Information technology[]

In the information technology during industry, implementation 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, customizations, systems integrations, user policies, user training and delivery. These steps are often overseen by a project manager using project management methodologies. Software Implementations involve several professionals that are relatively new to the knowledge based economy such as business analysts, technical analysts, solutions architects, and project managers.

To implement a system successfully, many 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 implementation 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, implementation 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 implementation include the legislative intent, the administrative capacity of the implementing bureaucracy, interest group activity and opposition, and presidential or executive support.

In international relations, implementation refers to a stage of international treaty-making. It represents the stage when international provisions are enacted domestically through legislation and regulation. The implementation stage is different from the ratification of an international treaty.

Social and health sciences[]

Implementation is defined as a specified set of activities designed to put into practice an activity or program of known dimensions.^[1] According to this definition, implementation 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 implemented is described in sufficient detail so that independent observers can detect its presence and strength.

Water and natural resources[]

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

Types[]

Direct changeover
Parallel running, also known as parallel
Phased implementation
, also known as pilot

Role of end users[]

System implementation 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 implementation 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.^[2] 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?^[1]

Designer concerns[]

How much disk 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?^[2]

Critique of the Premise of Implementation[]

Social scientific research on implementation also takes a step away from the project oriented at implementing a plan, and turns the project into an object of study. Lucy Suchman's work has been key, in that respect, showing how the engineering model of plans and their implementation cannot account for the situated action and cognition involved in real-world practices of users relating to plans:^[3] that work shows that a plan cannot be specific enough for detailing everything that successful implementation requires. Instead, implementation draws upon implicit and tacit resources and characteristics of users and of the plan's components.

References[]

^ ^a ^b "Framework 2: Implementation Stages | NIRN". nirn.fpg.unc.edu. National Implementation Research Network.
^ ^a ^b Laudon, K., & Laudon, J. (2010). "Management Information Systems: Managing the Digital Firm." Eleventh Edition (11 ed.). New Jersey: Prentice Hall.
^ Suchman, Lucy (1987). Plans and situated actions: The problem of human-machine communication. Cambridge MA: Cambridge University Press. ISBN 9780521337397.

[NIRN2014-1] "Framework 2: Implementation Stages | NIRN". nirn.fpg.unc.edu. National Implementation Research Network.

[Laudon2010-2] Laudon, K., & Laudon, J. (2010). "Management Information Systems: Managing the Digital Firm." Eleventh Edition (11 ed.). New Jersey: Prentice Hall.

[Suchman1987-3] Suchman, Lucy (1987). Plans and situated actions: The problem of human-machine communication. Cambridge MA: Cambridge University Press. ISBN 9780521337397.

[1]

[2]

[3]