Legacy system: Difference between revisions

Revision as of 12:47, 7 July 2016

System Fundamentals^[1]

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.^[2]

Legacy systems are usually still in use as opposed to retired (or archived) systems, which are no longer in use. Please remember this distinction.

All about legacy systems[edit]

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:

A new system accepts input for a date as 11 November 2017, but the legacy system only accept input as 11 November 17
A new system is web-based, but an older system is not web-based
A new system allows 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[edit]

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.

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?[edit]

This is a simple example:

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 systems, 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 cute little stuffed animals.

Jana wants to merge the two companies together, expecting to benefit with increased sales.

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[edit]

Outline compatibility issues resulting from situations including legacy systems or business mergers. Level 1

References[edit]

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

[2] ttps://en.wikipedia.org/wiki/Legacy_system

[1]

[2]

@@ Line 38: / Line 38: @@
 Question 2: List at least 5 questions would you ask to understand compatibility issues between the two businesses.
-== Do you have an advanced understanding of this material? ==
-A school of 900 students has a secure web-based application which manages attendance data. The school administrators carefully track attendance for the students so it can identify when students have been absent for a customizable threshold. For example, the school might set a threshold of 5 absences within 30 days, which then automatically notifies the student, parent, and teacher there is a problem with attendance. The threshold might be 3 times within 10 days, or something like that. The system keeps track of attendance and tardies. The system has customizable attendance codes. For example, "absence for school trip", "excused absence", "medical absence" are all allowed absence codes.
-School administrators expect to benefit by having data about attendance so they can support students and parents to be in school. School administrators also expect to benefit by giving parents and students information about attendance (so parents can support their children to be in school). Finally, school administrators expect to benefit by using attendance data to apply for government funding (as they can prove how many students were in class on a specific day).
-Parents expect to benefit by knowing when their children are in school or miss school. This way parents can support their children to be in school. Being in school is a '''shared value''' between the school and the parent.
-Students expect to benefit by understanding how many days of school of they have missed. The school expects students to have a strong "ownership of learning" and manage their attendance.
-'''Change request:''' a school administrator asks for a card-system, so students touch their id card to a reader and be automatically counted as present. There will be a card reader and camera in every classroom. Students must touch their id card to the card reader and then smile for a camera picture. the picture and information embedded in the card is stored in a database and used to provide evidence the student is present in class.
-Question 1: Describe '''why''' we should carefully manage this change process.
-Question 2:  List the steps you would take to make this change (what would you do first, then next, then next).
 == Standards ==