Editing Implementation

{{Short description|Realization concept}}
{{more citations needed|date=December 2009}}
{{Wiktionary}}
'''Implementation''' is the realization of an application, execution of a [[plan]], idea, [[scientific modelling|model]], [[design]], [[specification]], [[Standardization|standard]], [[algorithm]], [[policy]], or the [[Management|administration]] or [[management]] of a [[process]] or [[Goal|objective]]. 

==Industry-specific definitions==

===Information technology===
In the information technology industry, implementation refers to the 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 analysis|business analysts]], software implementation specialists, [[solutions architect]]s, 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.

===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.<ref name="NIRN2014">{{cite web |title=Framework 2: Implementation Stages {{!}} NIRN |url=https://nirn.fpg.unc.edu/module-1/implementation-stages |website=nirn.fpg.unc.edu |publisher=National Implementation Research Network |access-date=2022-01-26 |archive-date=2022-05-23 |archive-url=https://web.archive.org/web/20220523182349/https://nirn.fpg.unc.edu/module-1/implementation-stages |url-status=dead }}</ref> 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.

In computer science, implementation results in software, while in social and health sciences, implementation science studies how the software can be put into practice or routine use.<ref>{{cite journal
| last1      = Chomutare
| first1     = T
| last2      = Tejedor
| first2     = M
| last3      = Svenning
| first3     = TO
| last4      = Marco-Ruiz
| first4     = L
| last5      = Tayefi
| first5     = M
| last6      = Lind
| first6     = K
| last7      = Godtliebsen
| first7     = F
| last8      = Moen
| first8     = A
| last9      = Ismail
| first9     = L
| last10     = Makhlysheva
| first10    = A
| last11     = Ngo 
| first11    = PD
| date       = 2022
| title      = Artificial Intelligence Implementation in Healthcare: A Theory-Based Scoping Review of Barriers and Facilitators.
| journal    = International Journal of Environmental Research and Public Health
| volume     = 19
| issue      = 23
| page = 16359
| doi        = 10.3390/ijerph192316359
| pmid = 36498432
| pmc = 9738234
| doi-access = free
}}
</ref>

==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.<ref name="Laudon2010">Laudon, K., & Laudon, J. (2010). "Management Information Systems: Managing the Digital Firm." Eleventh Edition (11 ed.). New Jersey: Prentice Hall.</ref> Examples of these differences or concerns are below:

===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?<ref name="Laudon2010"/>

==Critique of the Premise of Implementation==
[[Social Science|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 cognition|situated action and cognition]] involved in real-world practices of users relating to plans:<ref name="Suchman1987">{{Cite book|title=Plans and situated actions: The problem of human-machine communication|last=Suchman|first=Lucy|publisher=Cambridge University Press|year=1987|isbn=9780521337397|location=Cambridge MA}}</ref> 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.

==See also==
* [[Application software]]
* [[Situated cognition]]

==References==
{{Reflist}}

[[Category:Implementation| ]]
[[Category:Computing terminology]]
[[Category:Political science terminology]]
[[Category:Design]]