Topic 1: System Fundamentals Flashcards
Identify the context for which a new system is planned.
Consider the extent and limitations of the new system.
Describe the need for change management.
Need to train users on new system, users might be resistant to change, possible incompatibility, data loss, expenses.
Outline compatibility issues resulting from situations including legacy systems or business mergers.
A legacy system is an older system that may no longer be supported. It may not be compatible with new systems. A merger is when two companies combine into one. There may be issues with system compatibility, especially on an international basis.
Compare the implementation of systems using client’s hardware with hosting systems remotely.
Software-as-a-service (SaaS) is a distribution model in which a third-party provider hosts applications and makes them available to customers over the Internet. SaaS minimizes an organization’s IT responsibilities and costs, if server needs change, an organization can just adjust their SaaS subscription. May have difficulty integrating SaaS with existing on-premise applications. Business using SaaS must trust a third-party with security. Businesses must take into account the government compliance regulations inherent to storing customer data in a remote data center (laws might be different in different countries).
Installation process: Direct changeover (advantages & disadvantages)
The old system is stopped and the new system is started.
Advantages: minimal time and effort, new system available immediately.
Disadvantages: if the new system fails, there is no fallback.
Installation process: Parallel running (advantages & disadvantages)
The new system is started, but the old system is kept running alongside it. Data has to be entered into both systems.
Advantages: if the new system fails, the old system runs a backup, outputs from two systems can be compared to see if new one is running correctly
Disadvantages: Have to run two systems simultaneously simultaneously (costly in terms of time and money)
Installation process: Pilot running (advantages & disadvantages)
The new system is piloted with a small subset of the organization. Once it is running correctly, it is implemented across the whole organization.
Advantages: if the system fails, only a portion of the organization suffers, staff who were part of the pilot can train other staff.
Disadvantages: Have to run two systems (the new and the old) simultaneously, though not as costly as parallel running (since the new system is just running for a portion of the organization).
Installation process: Phased conversion (advantages & disadvantages)
The new system is introduced in phases as parts of the old system are gradually replaced with the new system.
Advantages: allows users to get acclimated with the new system slowly, training can be done in stages.
Disadvantages: Parts of the new system may be incompatible with parts of the old system, it may be difficult to run them together.
What problems might arise as part of data migration?
Incompatible file formats, differences in data structures (how the data is organized), differences in validation rules (which check if data inputs are valid), incomplete data transfers, differences in data/currency/character sets (think of how different countries use different formats for dates).
Why is testing a system important?
To ensure the system is in line with user requirements.
To prevent the end user being dissatisfied with the final system;
Testing is important to enable early discovery of errors;
to reduce time delay/ using more resources / avoid higher cost;
Suggest various types of testing.
Debugging, Beta testing, user acceptance testing
Describe beta testing
Involves sending sample software to the intended audience;
(Selected audience do not pay for this software);
To try/use the software product;
And give the feedback to the authors (which help in correcting bugs);
Describe user acceptance testing
Often the final stage of software testing, end users are asked if the system meets their expectations. A “black-box” test (testers do not have access to the internals of the system).
Describe debugging
Finding and resolving bugs or errors in software by looking inside the software itself (also called “white-box” testing or “structural” testing).
What is user documentation and how can it be delivered?
Any document that explains how to use features and functions of a system to its end users (not developers). It comes in many forms:
Why is user documentation necessary for a system?
User efficiency; To ensure that users know how to use the system correctly;
Support/Troubleshoot; To provide users help when they encounter errors;
Accuracy; To ensure the correct methods are used to enable reliable output;
Improved user experience; the user is aware of all available features, so they can make the most out of the system;
User documentation: Help files (adv/disadv)
Files supplied together with the system, can usually be called up with a button in the software.
Advantages: easily accessible at anytime
Disadvantage: can only be used after a system has been installed, only deal with general errors
User documentation: Online support (adv/disadv)
Special web service hosted by a system’s developer to provide user documentation.
Advantages: more extensive compared to help files, get continuously revised, can provide options for live support, often have search capabilities
Disadvantages: require Internet connection, live support might not always be available.
User documentation: Printed manuals (adv/disadv)
Manuals printed on paper supplied together with the system.
Advantages: they can be read through by the user before starting to work with the new system (can help with installation), always available.
Disadvantages: Not automatically updated, limited in number.
User training: Self-instruction (adv/disadv)
Users can learn how to use a new system on their own, by reading a manual, watching a tutorial.
Adv: Lowest cost, flexible timeline, user can choose exactly what they want to learn.
Disadv: No guidance or feedback, unstructured learning means certain features might be misunderstood or ignored, can feel isolated.