Topic_1_IB CS
Topic_1_IB CS
FUNDAMENTALS
PLANNING & SYSTEM INSTALLATION
SDLC(SYSTEM DEVELOPMENT LIFE CYCLE)
Research Waterfall Model of system development
Collecting information about the present system works
Analysis
Examining out how the present system works and identifying problems with it
Design
Coming up with a new system that will fix the present systems problems
Development/coding
Creating the new system from the design.
Testing
Checking if the newly created system works as expected
Documentation
Creating documents that describe how to use the new systems, and how it
works
Implementation
Replacing the present system with the new system
Evaluation
Checking that the new system meets all expectations
STAGES OF SDLC
Analysis
• state the need for recording and analysing information about the current system;
Design
• understand that the system is created from the designs and then tested;
• Observation
• Interviews
• Questionnaires
• Collecting Documents
ANALYSIS
Having collected as much information about the present system as possible, the systems analyst
now looks though it all to understand
how the system works, and to try and identify problems that need to be fixed. This process is
called analysis.
This is because any new system that is designed will have to deal with similar inputs and
outputs as the present system.
EXAMPLE OF A REAL-LIFE SCENARIO
ANALYZING(UNDERSTANDING THE CURRENT SYSTEM)
Now the problems with present system are understood, the system analyst can begin to
plan how the new system will fix those problems.
The systems analyst specifies a list of requirements for the new system (‘requirements’
simply means targets or aims).
WHAT HARDWARE AND SOFTWARE WILL software that is created for use
by a large range of customers -
•Custom-written software:
Software Very expensive
•Provides exactly what the
• Is ready-made, off-the-shelf software available? customer needs (a ‘perfect fit’)
•Only has one user, so little
• Is custom-written software required? help is available
FEASIBILITY REPORT
• candidates often lost marks by not stating the aspect of change management
that needed to be considered, before giving an expansion. In this case,
appropriate issues could be, for example, issues with personnel, time needed, or
costs involved. Some candidates did correctly identify these issues, or others,
and achieved marks. However, many did not. Some candidates also discussed
file incompatibility, which was covered in part (a)(ii).
•
COMPATIBILITY ISSUES WITH LEGACY SYSTEMS
• Candidates were generally able to state at least one compatibility issue related to
the merging of international business systems. Some candidates lost out by
naming two issues that were too similar, so therefore covering the same marking
point.
COMPARE THE IMPLEMENTATION OF SYSTEMS USING A CLIENT’S HARDWARE WITH
HOSTING SYSTEMS REMOTELY.
• Students who were able to give a brief answer stating the benefit of SaaS scored
a mark.
• State one drawback of using software-as-a-service (SaaS).[1] • Confidentiality concerns if data related to the customer is also stored on the
supplier’s hardware;
• If the service goes bankrupt / shuts down you can lose your applications
and data;
• Limited customization;
Issues with interoperability and data exchange between different platforms
due to incompatible / limited API.
Security concerns as higher risk of failure / attack / interception;
Time Delay in contacting / receiving response from the supplier / customer
support if there is an issue / different time zone;
Can turn out to be costly in the long run;
FACT FINDING TECHNIQUES
• Observation
• Questionnaires
• Interviews
IB QUESTION
• Parallel running: In this method, both the old and new computer systems are run
in parallel for a specified period of time.
• This allows organizations to compare the performance of the new system with the
old system, and identify any issues that need to be addressed before the new
system is fully implemented.
• Pilot running: In this method, the new computer system is introduced on a small
scale, typically in a specific department or location, before being rolled out to the
entire organization. This allows organizations to test the new system in a
controlled environment and make any necessary adjustments before full
implementation.
IMPLEMENTATION METHODS…
• Direct changeover: In this method, the old computer system is shut down, and
the new system is introduced immediately. This method is typically used when the
old system is no longer viable, or when the new system is a significant
improvement over the old system.
• Phased conversion: In this method, the new computer system is introduced
gradually, over a series of phases. This allows organizations to test and
implement the new system in stages, reducing the risk of disruption to business
operations.
IB QUESTIONS
• Candidates were usually able to identify at least one organizational issue related
to user roles or technology, when implementing a new system. In many cases,
candidates got both.
IB QUESTION
• The management considered phased conversion and direct changeover as • Award [5 max]
methods of implementation. Direct changeover:
is the cheapest and quickest/the old system is completely switched for the
• (b) Evaluate these two methods of implementation. [5] new one;
this is straight forward but also the most risky / nothing to fall back on;
no need to keep data duplicates;
it allows the organization to change the system when most convenient;
the employees have very little time in order get use to the new system as
the change is instantaneous;
there is a period of time when neither systems are operational;
• Phased conversion:
method where the old system is still in use but parts of the new system or
modules are introduced, involves bringing in the new system one step at a
time;
less risky than direct changeover; less risky that the whole system will go
wrong/if something happens, it will only affect the specific part;
takes a lot of time;
employees have enough time for training/to get use to the new system / are
introduced to the changes in small stages;
Employees/users could ask for changes which then hold up the installation
of the next phase which helps improving the system;
EXAMINER REPORT
• The vast majority of candidates were able to correctly evaluate the two given
methods of implementation, direct changeover and phased conversion, with very
comprehensive contextual responses seen. In some cases, it wasn't quite clear
whether the candidate was describing phased conversion or pilot implementation.
However, these cases were rare.
• Describe the pilot running method for • Award [1] for the description and
the implementation of a new system. award [1] for the extension of its
[2] purpose
• Answer
• Examiner’s Report for this question
• Examples:
• One area/branch of the business is selected to try the new computer system;
Once the new system is fully tested and able to function correctly / without errors / as
per the user requirements, it is implemented for everyone;
• The system is introduced only to a small group of users;
It reduces the risks of failure or malfunction before introducing to the full group;
• Pilot running is a small-scale implementation of the system for a limited number of
users;
It allows the developers make improvements in the system based on users’ feedback
before its full release / roll out;
EXAMINER’S REPORT
• Data migration, the process of transferring data from one computer system to
another, can be complex and challenging, and several problems can arise during
this process. Some common problems include:
PROBLEMS THAT MIGHT ARISE AS A PART OF DATA
MIGRATION.
• Data loss or corruption: Data migration can result in data loss or corruption due
to issues such as file format incompatibility, data transfer errors, or data mapping
problems.
• Incomplete data: Data migration can result in incomplete data if not all relevant
data is transferred or if data is not transferred in its entirety.
• Data accuracy: Data migration can result in inaccuracies if data is not accurately
mapped from the old system to the new system. This can lead to issues with data
integrity and the accuracy of business processes.
• Data security: Data migration can result in security risks if sensitive data is not
properly protected during the transfer process.
• Time and cost: Data migration can be time-consuming and expensive,
particularly if the data is large or complex, or if the old and new systems are
significantly different.
• System downtime: Data migration can result in system downtime, which can
impact business operations and productivity.
IB QUESTION
• A large hotel chain runs hotels in many locations around • Award [2 max]
the world. Data is kept locally at each property, and Award [1] for the problem and award [1] for a suitable
centrally, so that the hotel chain can be managed. extension.
• The hotel chain has implemented a significant upgrade to • Data not being stored / not transferred correctly /data
its computer system that requires the data to be migrated loss/data corruption;
from the legacy system to the new system. due to incompatible software/ hardware/ file formats /
data structures / database formats/ Validation rules/data
• (d)Outline one problem that may arise during the data integrity issues/power failure;
migration process.
• Data inconsistencies/incompatibility;
due to incompatible conventions of dates / currencies /
time/ character sets;
• Potential security risks;
due to breach of sensitive information, data leakage and
unauthorised access during data transfer;
EXAMINER REPORT
• User acceptance testing (UAT): User acceptance testing involves testing the
new system by end-users to ensure that it meets their requirements and functions
as expected. UAT helps to identify any issues with the system from the user's
perspective, and can be used to refine the system before full implementation.
• Debugging: Debugging is the process of identifying and fixing errors or defects in
the new system. Debugging can help to ensure that the system is functioning as
intended, and can prevent issues from arising after implementation.
• Beta testing: Beta testing is a form of user acceptance testing that involves
testing the new system by a select group of users before full implementation. Beta
testing can provide valuable feedback on the system and can help to identify any
issues that need to be addressed before full implementation.
IB QUESTION
Define
Draw Explain
Identify
IMPORTANCE OF DOCUMENTATION
• The quality of user documentation is critical to the success of any new system
implementation.
• Poorly written or outdated documentation can lead to confusion, frustration, and a
low rate of adoption, while well-written and up-to-date documentation can help
ensure a smooth and successful implementation.
TYPES OF DOCUMENTATION
• SL:
• A wide range of possible training methods were seen, with the vast majority of
candidates achieving this mark.
• HL:
• All candidates attempted it and many got it right.
• Evaluate the advantages and disadvantages for the end user of the • Award [3 max]
method of training identified Award up to [2] for any advantage to end-user (trainee) evaluated,
and up to [2] for any disadvantage evaluated. Note: The response
should match the method of training identified in (i).
• SL:
• Candidates who identified a correct method of training also achieved some or all
of the marks for identifying advantages and disadvantages of their chosen
method. Some candidates only gave either advantages or disadvantages, but
those who gave both, generally achieved high marks.
• HL:
• All candidates attempted it and many got it right.
CAUSES OF DATA LOSS
• Malicious activities
• Virus or malware attacks: Malware can infect your computer, causing data loss or
corruption.
• Ransomware attacks: Ransomware is a type of malware that encrypts your data and
demands a ransom payment to restore access.
• Human error: Accidentally deleting files or formatting a drive can cause permanent
data loss.
• Hardware failure: Hard drive crashes, overheating, and other hardware issues can
cause data loss.
• Natural Disasters
• Floods, fires, earthquakes, and other natural disasters can cause physical damage to
your computer and storage devices, leading to data loss.
Power surges and outages: Sudden power disruptions can cause corruption of data or
even physical damage to your hardware.
CONSEQUENCES OF DATA LOSS
• Financial loss: Companies may incur significant expenses to recover lost data or to
recreate it. In some cases, data loss can also result in lost revenue and reduced
productivity.
• Reputation damage: Data loss can harm a company's reputation and customer trust,
especially if sensitive information is involved.
• Legal consequences: If personal or confidential information is lost, companies may
face legal action and fines.
• Loss of intellectual property: Data loss can result in the loss of valuable intellectual
property, such as trade secrets and proprietary information.
• Loss of productivity: In the case of data loss, employees may spend significant
time and resources trying to recover lost data, reducing productivity and
efficiency.
• Emotional stress: Data loss can be a traumatic experience, especially for
individuals who have lost personal and sentimental files.
CONSEQUENCES OF DATA LOSS IN MEDICAL
RECORDS
• Patient safety: If medical records are lost or become inaccessible, healthcare
providers may not have access to critical information about a patient's health
history and current medications, putting the patient at risk of receiving incorrect
treatments or diagnoses.
• Legal liability: Inaccurate or missing medical records can result in medical
malpractice lawsuits, as well as fines for violating patient privacy laws.
• Loss of trust: Patients may lose trust in a healthcare provider if their medical
records are lost or compromised, which can result in a loss of business for the
provider.
• Duplication of tests and treatments: If medical records are lost, healthcare
providers may need to repeat tests and treatments that have already been
performed, leading to increased healthcare costs and patient inconvenience.
• Delays in treatment: Data loss can lead to delays in treatment, as healthcare
providers may need to spend time gathering information from other sources or
recreating records.
HOW TO PREVENT DATA LOSS
• Manual Downloads: In this method, updates and patches are made available for
download on a vendor's website or a software repository, such as the Microsoft
Update Catalog. The end user must manually download and install the updates
on their own.
• Automatic Updates: In this method, updates and patches are automatically
downloaded and installed on the end user's device. This is often done in the
background and does not require any user intervention. Automatic updates are
often delivered on a regular basis, such as weekly or monthly, and can be set to
occur at specific times or when the device is idle.
• Cloud-Based Updates: With cloud-based software, updates and patches are
often automatically deployed by the vendor, eliminating the need for end users to
manually install them. This allows for a more seamless and consistent update
process, and helps to minimise the risk of issues arising from manual updates.
• • Award [2 max]
Identify two reasons why patches Allows bugs/error in operating system
may be necessary for an operating to be repaired;
system. [2] Allows new features to be added to
operating system (such as security
updates, improving functionality,
improving usability, etc.);
Allows compatibility issues to be
improved;
EXAMINER’S REPORT
• Most candidates were able to identify at least one reason why patches may be
necessary for an operating system, with a large proportion correctly naming two
reasons.