Implementation methods: Difference between revisions

Revision as of 14:16, 11 July 2016

System Fundamentals^[1]

Implementing can be defined as putting (a decision, plan, agreement, etc.) into effect^[2].

Once you have carefully planned a system, you must implement the system. You wouldn't just plan a new system and throw it at a new user, would you?

A common point of failure is

Typical activities will include: installing new hardware installing software across the company setting up data sets ready for use training everyone on the new system backing up existing data in case of a problem

There are 4 common methods to implement a new system:

Parallel
Phased
Pilot
Direct

All about Implementation methods[edit]

Real-world practical advice[edit]

Do you understand this material?[edit]

Standards[edit]

Evaluate alternative installation processes Level 3

References[edit]

Students should be aware of the methods of implementation/ conversion. Parallel running, pilot running, direct changeover and phased conversion. S/E Training issues may require organizations to restructure their workforce.

[1] ttp://www.flaticon.com/

[2] ttps://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=define%3Aimplement

[1]

[2]

@@ Line 1: / Line 1: @@
 [[file:system_fund.png|right|frame|System Fundamentals<ref>http://www.flaticon.com/</ref>]]
-In computing, a legacy system is an old method, technology, computer system, or application program, "of, relating to, or being a previous or outdated computer system."Often a pejorative term, referencing a system as "legacy" often implies that the system is out of date or in need of replacement.<ref>https://en.wikipedia.org/wiki/Legacy_system</ref>
+'''Implementing''' can be defined as putting (a decision, plan, agreement, etc.) into effect<ref>https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=define%3Aimplement</ref>.
-Legacy systems are usually '''still in use''' as opposed to retired (or archived) systems, which are no longer in use. Please remember this distinction.
+Once you have carefully planned a system, you must implement the system. You wouldn't just plan a new system and throw it at a new user, would you?
-=== All about legacy systems ===
+A common point of failure is
-Systems must be compatible with other systems if they are going to be useful. Legacy systems are not always compatible with newer systems. Compatibility is a state in which two things are able to exist or occur together without problems or conflict. When you are planning a new system, you should be aware of compatibility issues with older systems. Frequently, the way a legacy system stores data is the most frequent source of compatibility issues.
-A few hypothetical examples may help you understand this:
+Typical activities will include:
+installing new hardware
+installing software across the company
+setting up data sets ready for use
+training everyone on the new system
+backing up existing data in case of a problem
-# A new system accepts input for a date as 11 November 2017, but the legacy system only accept input as 11 November 17
+There are 4 common methods to implement a new system:
-# A new system is web-based, but an older system is not web-based
-# A new system allows [https://en.wikipedia.org/wiki/UTF-8 UTF-8] (Unicode Transformation Format-8) characters but the legacy system does not.
-# A new system assumes all currencies are in US dollars, while the legacy system does not.
-# A new system stores time as HH:MM:SS:MS (HH: hour, MM: minute, SS: second, MS: millisecond) but the legacy system stores time as HH:MM:SS.
-# A new system assumes all numbers can have 4 decimal places, while a legacy system assumes all numbers only have 2 decimal places.
-# A new system stores data in XML while a legacy system stores data in plain text.
-== Real-world practical advice ==
+* Parallel
+* Phased
+* Pilot
+* Direct
-When you are planning a new system '''you should include compatibility planning as part of your new system'''. If you are a system administrator, programmer, network administrator, much of your work will involve getting different systems to be compatible.  It's always nice when you have a new system, new company, and a new process, but this isn't the norm.
+=== All about Implementation methods  ===
-There is a lot more to say about this, but my advice is to assume any system you are involved with needs to be compatible with other systems and legacy systems.
-== Do you understand this material? ==
-This is a simple example:
+== Real-world practical advice ==
-Jana has a small business that buys and sells flowers. Her business is successful. She uses different systems to manage her inventory, point-of-sale, employees, and of course her business finances. Jana also has a website for her flower store where customers can learn about her business.
-Jana is '''so''' successful she decides to expand her business, and buys an older company that buys and sells [https://www.google.com/search?q=cute+stuffed+animals&safe=strict&espv=2&biw=1380&bih=667&tbm=isch&tbo=u&source=univ&sa=X&ved=0ahUKEwimhYC1ouHNAhWJez4KHVzPBvQQsAQIGg cute little stuffed animals].
-Jana wants to merge the two companies together, expecting to benefit with increased sales.
+== Do you understand this material? ==
-Question 1: Outline possible compatibility issues resulting from our example above.
-Question 2: List at least 5 questions would you ask to understand compatibility issues between the two businesses.
 == Standards ==