1.

1 Systems in organisations​ 2
Planning and system installation (1.1.1 - 1.1.7)​ 2
1.1.1 Identify the context for which a new system is planned.​ 2
1.1.2 Describe the need for change management.​ 3
1.1.3 Outline compatibility issues resulting from situations including legacy systems
or business mergers.​ 3
Legacy systems​ 3
1.1.4 Compare the implementation of systems using a client’s hardware with hosting
systems remotely.​ 4
Locally hosted system​ 4
Remote hosted system (SaaS)​ 4
1.1.5 Evaluate alternative installation processes.​ 4
Parallel Running​ 4
Big Bang/Direct Changeover​ 5
Pilot Running​ 5
Phased Conversion​ 5
1.1.6 Discuss problems that may arise as a part of data migration.​ 6
1.1.7 Suggest various types of testing.​ 6
1. Static Testing​ 6
2. Dynamic Testing​ 6
3. Alpha Testing​ 6
4. Beta Testing​ 6
5. Black-box testing​ 7
6. White-box testing​ 7
7. User acceptance testing​ 8
8. Automated testing​ 8
User focus (1.1.8 - 1.1.10)​ 8
1.1.8 Describe the importance of user documentation.​ 8
1.1.9 Evaluate different methods of providing user documentation.​ 8
Help files​ 8
Online documentation​ 9
Community Forums​ 9
1.1.10 Evaluate different methods of delivering user training.​ 9
Self-instruction​ 9
Formal classes​ 10
Remote / online training​ 10
System backup (1.1.11 - 1.1.13)​ 10
1.1.11 Identify a range of causes of data loss.​ 10
1.1.12 Outline the consequences of data loss in a specified situation.​ 10
1.1.13 Describe a range of methods that can be used to prevent data loss.​ 11
Software deployment (1.1.14)​ 11
1.1.14 Describe strategies for managing releases and updates.​ 11
Types of Updates​ 11
Management​ 12
 Deployment Methods​ 12
1.2 System design basics​ 12
Components of a computer system​ 13
1.2.1 Define the terms: hardware, software, peripheral, network, human resources.​13
1.2.2 Describe the roles that a computer can take in a networked world.​ 13
1.2.3 Discuss the social and ethical issues associated with a networked world.​ 14
System design and analysis (1.2.4 - 1.2.11)​ 14
1.2.4 Identify the relevant stakeholders when planning a new system.​ 14
1.2.5 Describe methods of obtaining requirements from stakeholders.​ 15
Questionnaire​ 15
Interviews​ 15
Direct observations​ 15
1.2.6 Describe appropriate techniques for gathering the information needed to arrive
at a workable solution.​ 16
1.2.7 Construct suitable representations to illustrate system requirements.​ 16
1.2.8 Describe the purpose of prototypes to demonstrate the proposed system to the
client.​ 17
1.2.9 Discuss the importance of iteration during the design process.​ 17
1.2.10 Explain the possible consequences of failing to involve the end-user in the
design process.​ 18
1.2.11 Discuss the social and ethical issues associated with the introduction of new
IT systems.​ 18
Human interaction with the system (1.2.12 - 1.2.16)​ 19
1.2.12 Define the term usability.​ 19
Accessibility​ 19
1.2.13 Identify a range of usability problems with commonly used digital devices.​ 19
1.2.14 Identify methods that can be used to improve the accessibility of systems.​ 20
1.2.15 Identify a range of usability problems that can occur in a system.​ 20
1.2.16 Discuss the moral, ethical, social, economic and environmental implications of
the interaction between humans and machines.​ 21

1.1 Systems in organisations

Planning and system installation (1.1.1 - 1.1.7)

1.1.1 Identify the context for which a new system is planned.

The extent and limitations of a new system should be appreciated. Organisational issues
related to the installation of new systems such as user roles, underlying technologies.

●​ Old system is inefficient

●​ Old system is no longer suitable for original purpose or outdated
●​ To increase productivity and quality of output
●​ To increase efficiency and minimise costs
 Bespoke Off-the-self

tailored to your - Very expensive - Cheap - Made for a general

specific needs - May require - Skilled workers audience therefore
special training readily available won't have
everything you need

1.1.2 Describe the need for change management.

Students should understand there are a number of factors that need to be managed to
ensure change is successful. S/E The way that change is managed can have significant
effects on employers and employees

Purpose → minimise negative impacts of change

Negative Impacts:
●​ resistance,
●​ confusion,
●​ decreased productivity,
●​ project failure.

Managing Factors:
1.​ Communication (of the need for and benefits of change)
2.​ Training and Support
3.​ Recruitment → bring in suitable skill sets

1.1.3 Outline compatibility issues resulting from situations including

legacy systems or business mergers.

State two compatibility issues that may arise when international businesses merge. [M22]
1.​ Language differences
a.​ Communication issues and different interpretations.
2.​ Software incompatibility
a.​ Newer software may not run on old hardware or may not integrate well with
legacy software, limiting functionality and leading to inefficiencies.
3.​ Data Transfer (structure and formats)
a.​ Legacy systems often use outdated data formats that may not be supported
by modern systems, requiring complex data transformation.
4.​ Security
a.​ Legacy systems may lack modern security features, making them more
vulnerable to attacks when connected with newer systems.
Legacy systems
Refers to outdated computer systems that have been superseded by newer technologies

1.​ higher costs for maintaining older systems as the systems may fail more frequently
with age
2.​ no more technical support for these systems
3.​ legacy systems tend to be more vulnerable to security threats due to a lack of
security updates

1.1.4 Compare the implementation of systems using a client’s hardware

with hosting systems remotely.

Locally hosted system

-​ Software is installed and operated on the client's own hardware/ infrastructure.

-​ full control over the hardware and -​ higher initial cost than remote
software, including updates, security -​ harder to predict total cost (maybe
configurations, and backup policies more expensive in long run with
-​ this allows for customisation and maintenance payments)
can tailor the system more easily to -​ have to maintain yourself (hire IT
their specific needs without needing personnel).
to adhere to the limitations of
external providers.
-​ locally hosted systems can offer
high performance with reduced
latency as all data processing
happens on-site.

Remote hosted system (SaaS)

-​ Hardware is elsewhere, updated centrally. Users can access data and operate
software from the cloud and pay for service on a subscription basis.

-​ lower initial cost -​ less control over system’s

-​ can predict overall cost easier infrastructure
-​ best for when organisation doesn't -​ sensitive data is stored off-site,
have necessary hardware already raising concerns about data privacy
-​ you don't have to maintain it yourself and compliance with regulations
-​ data secure in data centre -​ More expensive in the long term as
ongoing subscription fees and
charges add up
1.1.5 Evaluate alternative installation processes.
Parallel Running
-​ Both systems run parallel to each other at first to compare outputs until satisfied
with the new system, terminate old one

-​ low risk + no loss of productivity → if -​ higher cost

new system fails, can revert to old -​ not efficient if systems have different
one input/outputs/ processes.
-​ ideal for critical systems e.g. nuclear -​ workers trained to use new system
power station for nothing
-​ outputs from the two systems can
be compared to see if new one is
running correctly

Big Bang/Direct Changeover

-​ Set up new one and terminate old one at the same time

-​ cheapest -​ higher risk → if new system fails, no

-​ preferred if system not critical backup
-​ minimal time and effort, new system
is available immediately

Pilot Running
-​ New system is introduced in one of the sites (pilot site/group) then introduced to
others if successful, suitable for organisations with multiple sites.

-​ risk limited to the pilot group -​ higher local risk → subset of users
-​ all features are fully trialled; in the pilot group, there is no backup
-​ if the new system fails, only if the new system fails
a small part of the
organisation suffers; staff
who were part of the pilot
can train other staff
-​ cheaper than parallel
-​ less staff and work involved

Phased Conversion
-​ Convert one module of system at a time

-​ risk limited to specific system -​ higher local risk → if the new system
component fails, there is no fall back for that
-​ small change each time part
-​ longer ease in period -​ training period and implementation
takes longer
 -​ allows people to get used to
the new system; training of
staff can be done in stages

1.1.6 Discuss problems that may arise as a part of data migration.

📖 Data migration is the process of transporting data from one system to another, usually
an older system to a newer one.

Issues:
1.​ incompatible with file formats in the new system
a.​ If the new system cannot read or properly interpret the file format from the old
system, data may be corrupted or lost during migration.
2.​ incompatible data structures
a.​ result in a mismatch of data
3.​ different validation rules
a.​ may not meet the validation criteria in the new system, leading to rejected
data
4.​ data misinterpretation
a.​ due to conventions in different countries e.g. date, measurements, currencies

1.1.7 Suggest various types of testing.

[M22]
Importance → identifies problems to be fixed, areas for improvement and determines
whether system/ software works as intended

Testing is important (at every stage) to make sure the system operates in line with user
requirements/as intended;
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;

Impact → inadequate employee productivity → reduced efficiency and output → increased

costs = end-user dissatisfaction

1.​ Static Testing

a.​ reviews , walkthroughs, or inspections
b.​ like proofreading when the IDEs check source code or syntax.
c.​ spot security flaws, optimising code, quality controls
d.​ involves verification
 2.​ Dynamic Testing
a.​ actually executing programmed code with a given set of test cases
b.​ intentionally trying to crash the software → preparing for unexpected outputs
c.​ involves validation
3.​ Alpha Testing
a.​ 1st stage of testing
b.​ internal employees of the organisation test
c.​ performed at developer’s site
4.​ Beta Testing
a.​ later stages of testing
b.​ external people eg end users or clients
c.​ performed at client location or end user of the product
5.​ Black-box testing

Objective: ensures that the system meets user requirements and

functions as expected by comparing inputs and outputs
against the specified requirements

Methodology: testing what the system is supposed to do, from the point of
view of the user, with no knowledge of how the program does
what it does

Test basis: based on description/specification of software

Example techniques: 1.​ Boundary Value Analysis: Testing at the boundaries of

input ranges.
2.​ Decision Table Testing: Creating a table of conditions
and actions to cover different scenarios.

-​ requires no knowledge of the -​ limited in identifying internal code

internal code, allowing errors or logic issues.
non-developers to perform tests. -​ provides less coverage for hidden
-​ tests whether system meets code paths or edge cases within the
functional requirements implementation.
-​ finds issues related to missing
functionality, UI and performance

6.​ White-box testing

Objective: to verify the internal workings and logic of the code, ensuring
that it behaves correctly at a granular level.

Methodology: testing the system from the point of view of the programmer,
with full knowledge of how it does what it does

Test basis: source code and implementation details

 Example techniques: 1.​ Statement Coverage: Ensuring each line of code is
executed at least once.
2.​ Branch Coverage: Testing all possible branches (e.g.,
“if-else” statements) within the code.

-​ optimises code by highlighting -​ may not identify functionality or

unnecessary or redundant logic usability issues from a user’s
-​ provides thorough testing coverage perspective.
of the code’s internal structure. -​ requires in-depth knowledge of the
code, making it more
time-consuming and generally
requiring developer expertise.

7.​ User acceptance testing

a.​ testing any new/updated system with its ultimate end users to see if it meets
their expectation is very important.
b.​ Happy users = more productive users = good for developers
8.​ Automated testing
a.​ uses of special software tools to control the execution of tests and then
compares actual test results with predicted or expected results.
b.​ all of this is done automatically with little or no intervention from the test
engineer

User focus (1.1.8 - 1.1.10)

1.1.8 Describe the importance of user documentation.

📖 User documentation explains how to use the features and functions of a system to its
end users

Outline one reason why accurate user documentation is necessary for a system [M22]
Importance →

1.​ Improved user experience;

a.​ the user is aware of all available features, so they can make the most out of
the system;
2.​ User efficiency;
a.​ To ensure that users know how to use the system correctly;
3.​ Support/Troubleshoot;
a.​ To provide users help when they encounter errors;
4.​ Accuracy;
a.​ To ensure the correct methods are used to enable reliable output;
1.1.9 Evaluate different methods of providing user documentation.
Help files
-​ integrated, often context-sensitive, files within the software application itself

-​ easy to access -​ limited scope

-​ cheap -​ focuses on specific tasks or
-​ can't be misplaced functions
-​ no internet needed -​ complexity restriction
-​ since stored locally, available -​ not suitable for extensive
without an internet troubleshooting or complex
connection, instructions
-​ beneficial for users in
low-connectivity areas.

Online documentation
-​ web service hosted by the system's developer to provide user documentation

-​ has search capabilities -​ access limited by internet

-​ extensive compared to help files connection
-​ provide live support option -​ live support does not work quite well
-​ can be updated with users unfamiliar with computers

Community Forums
-​ Community forums allow users to ask questions, share insights, and access a
library of articles, often moderated by support staff or user community members.

-​ find solutions for specific scenarios, -​ information may be inconsistent or

often learning from others' incomplete without moderation.
experiences. -​ responses can vary in quality, which
-​ crowdsourced support can reduce may confuse users looking for
pressure on the official support team reliable answers.

1.1.10 Evaluate different methods of delivering user training.

Examples should include self instruction, formal classes, remote/ online training. S/E The
quality of the delivery of user training can affect the rate of implementation of the new
system.

Importance → Training end-users in using a new system is very important as productivity

greatly depend on how familiar a system.
Self-instruction
-​ learn on their own

-​ easiest and cheapest -​ usually only used for easy/ common

-​ with more flexible time for user use programs with sufficient
documentation
-​ depends on user motivation and
ability to work on their own
-​ with no guidance, user might feel
lost/overwhelmed
-​ unstructured learning means certain
features might be
misunderstood/ignored

Formal classes
-​ classroom setting, free discussion

-​ cheap option for large amounts of -​ class sizes may be too big
staff -​ cant deal with individual
-​ structured learning environment problems and questions
-​ expert on hand to answer questions -​ resource intensive
-​ curriculum designed to teach all -​ Time, teachers, facilities
aspects, including ones that might -​ rigid schedule and curriculum
be misunderstood or difficult to
grasp

Remote / online training

-​ an instructor training one user or a small group of users by some kind of remote
connection

-​ larger variety of courses online, can -​ those without infrastructure/internet

access any time, easier to set up or IT skills to use it, might not be as
and include new members = effective
cheaper
-​ flexible locations

System backup (1.1.11 - 1.1.13)

1.1.11 Identify a range of causes of data loss.

1.​ Human error
a.​ accidental deletion,
 b.​ closing before saving
2.​ Natural disasters
a.​ Fire, flood, earthquake
3.​ Malicious activities
a.​ Hacks
4.​ Computer viruses
a.​ Viruses, ransomware, and other malware can corrupt, delete, or encrypt data,
making it inaccessible or permanently lost.
5.​ Power failure

1.1.12 Outline the consequences of data loss in a specified situation.

Consequence Impact

Operational Disruption Reduced productivity, delayed projects,

compromised decision-making, loss of
records

Financial Loss Recovery costs, lost revenue, legal fines

Reputation Damage Loss of customer trust, negative public

perception, potential customer attrition

1.1.13 Describe a range of methods that can be used to prevent data

loss.
1.​ Regular backups
a.​ On hard disks/ magnetic tape, online or on removable media (e.g. USB, CDs)
for fast backup and storage
2.​ Offsite storage
a.​ Data backups stored in different geographical location
3.​ Firewall and antivirus
a.​ Prevent virus infections
4.​ Failover systems
a.​ Computer system that system can switch to in case of hardware/ software/
network failure. Often switches automatically to reduce time
5.​ Access Controls
a.​ Limit access to sensitive data to minimise the risk of accidental or intentional
deletion.
Software deployment (1.1.14)

1.1.14 Describe strategies for managing releases and updates.

Types of Updates

1.​ Patches
a.​ small pieces of software designed to fix specific problems or security
vulnerabilities in existing programs. Patches are typically released more
frequently than updates and are used to quickly address issues that have
been discovered in the software.
2.​ Updates
a.​ periodic release of software that typically includes new features, add minor
functionalities, and bug fixes. Updates are usually released to improve the
overall user experience and bring new functionality to the software
b.​ free
3.​ Upgrades
a.​ new version of software that replaces an older version. Upgrades typically
include significant changes to the software and may involve the addition of
new features, enhancements, and bug fixes. Upgrades are usually released
to bring the software up to date with the latest technology and to address
compatibility issues with other software or hardware
b.​ paid
4.​ Releases
a.​ final, working applications gone through testing

Management

1.​ Continuous Integration and Continuous Deployment (CI/CD)

a.​ This approach involves automating the build, test, and deployment process,
allowing new releases to be deployed quickly and consistently. This helps to
minimise the risk of errors and ensures that releases are tested thoroughly
before they are deployed to production.
2.​ Rollback Strategies
a.​ This involves having a plan in place for rolling back to a previous version of
the software in the event of a failed release. This helps to minimise the impact
of any issues that may arise during the release process, and ensures that end
users are not impacted by any problems with the software.
3.​ Staging Environments
a.​ This involves testing new releases in a controlled environment before they are
deployed to production. This allows for thorough testing and helps to identify
any issues that may arise before they impact end users.

Deployment Methods
1.​ Manual Downloads
 a.​ 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.
b.​ or email sent to the registered user with a link to download the update
2.​ Automatic Updates
a.​ Cookie is placed on the machine which communicates with the developer
automatically when software is started up. If an update is available, updates
and patches are automatically downloaded and installed on the end user's
device.
3.​ System Center Configuration Manager (SCCM)
a.​ This is a centralised management tool used by organisations to manage
updates and patches across their entire infrastructure. SCCM allows
administrators to deploy updates and patches to specific groups of devices,
such as those in a particular geographic location or those used by a specific
department

1.2 System design basics

Components of a computer system

1.2.1 Define the terms: hardware, software, peripheral, network, human

resources.
1.​ Hardware
a.​ Physical, tangible elements of a computer system e.g. CPU, HDD
2.​ Software
a.​ The instructions for the CPU and data that can be stored electronically in a
computer system. e.g. programs or data
3.​ Peripheral
a.​ Auxiliary device that is not part of the main computer but which is added to
provide some extra function.e.g. keyboards, microphones, speakers, printers
4.​ Network
a.​ A group of two or more computers linked via a wired or wireless
communication medium.
5.​ Human resources
a.​ The personnel or workers of a business or organisation
b.​ regarded as a significant asset

1.2.2 Describe the roles that a computer can take in a networked world.

Role of computer Definition and description

Client Piece of computer hardware/software that accesses services

made available by server, by sending requests to server
Server Program/host computer that fulfils requests from client programs
or computers across network and shares info to clients

Email server Message transfer agent that transfers electronic messages from
one computer to another in a network

DNS (Domain Name Server that translates web addresses written in letters (more
Server) memorable for humans) to the numeric IP (Internet Protocol)
address

Router Connects networks together to forward data packets between

networks, deciding where to send information so it is received by
one network and then sent to another until it reaches its
destination

Firewall Controls incoming and outgoing network traffic, determining what

data packets should be allowed through, based on a rule set.
1. Ports - id number for a process
2. Source Address - block traffic by where it came from

1.2.3 Discuss the social and ethical issues associated with a networked
world.
Issue Description Social and Ethical Implications

Privacy and Extensive data collection Users face compromised privacy, raising
Surveillance and tracking reduce user concerns about rights and trust in digital
privacy. spaces.

Cybersecurity and Increased risks of Responsibility lies with individuals and

Cybercrime cyber attacks, identity organizations to protect data, yet
theft, and fraud. breaches harm affected individuals.

Digital Divide and Unequal access to Exacerbates socioeconomic inequalities,

Access Inequality technology creates raising questions of fair technology
disparities. access and equity.
System design and analysis (1.2.4 - 1.2.11)

1.2.4 Identify the relevant stakeholders when planning a new system.

Importance → By engaging with stakeholders and understanding their needs, the project
team can ensure that the goals of the project align with the goals of the stakeholders. This
can help to build support for the project and increase the chances of its success.

●​ End-users
○​ have specific requirements for the system's functionality, usability, and
performance.
●​ IT department
○​ responsible for implementing, maintaining, and supporting the new system.
They will have concerns about the technical requirements of the system and
the resources needed to deploy and maintain it.
●​ Regulators
○​ responsible for ensuring that the new system complies with relevant
regulations and standards. They will have concerns about the security and
privacy of the system and the protection of sensitive data.

1.2.5 Describe methods of obtaining requirements from stakeholders.

Questionnaire
-​ Can be closed/restricted (yes/no, box checking) or open/unrestricted (free
response questions)

-​ gathering information from a large -​ Level of detail depends on type of

number of stakeholders in a questions- closed questions don’t
relatively short amount of time allow for clarifications,
-​ conducted online or in person -​ elaborations, more details
-​ Time-saving and cost-efficient- can -​ Stakeholder could interpret question
get info from a large group of people wrong= invalid answers
easily and cheaply -​
-​ Closed/restricted questions= data is
easier to compare
-​ Open questions= more detailed
reports

Interviews
-​ Face-to-face with verbal responses
 -​ can observe non-verbal behaviour -​ data is hard to summarise/ evaluate/
-​ more reliable, valid data analyse
-​ unstructured interviews can reveal -​ time-consuming to get detailed
more questions that otherwise results
wouldn’t have been addressed
-​ more detail, depth

Direct observations
-​ On-site observation of different departments to see where things can be more
efficient

-​ aspects not detected in -​ time-consuming/expensive

questionnaires/interviews -​ might need to observe a
-​ produce more detailed complete business/system
reports cycle
-​ habits of workflows and processes -​ people act differently when they
-​ more reliable know they are being watched
-​ unreliable observations

1.2.6 Describe appropriate techniques for gathering the information

needed to arrive at a workable solution.

1.​ Examining current systems

a.​ (using interviews/ surveys/direct observation);
b.​ To compare the existing system against possible requirements to identify
missing features, areas for improvement
c.​ information can be used to inform the design of the new system and ensure
that it meets the needs of the stakeholders.
2.​ Examining competing products
a.​ To compare own system with competitors to identify best practices and
innovative features to add
3.​ Organisational capabilities
a.​ Examining the organisational capabilities of the business is important to
ensure that the new system will be able to integrate effectively with existing
systems and processes. This examination can help to identify any limitations
or constraints that may impact the deployment and adoption of the new
system, and can inform the design and development of the new system to
ensure that it is well-suited to the needs of the organisation.

1.2.7 Construct suitable representations to illustrate system

requirements.
Eg:
-​ system flow charts,
 -​ data flow diagrams,
-​ structure chart

Introduction to Process Flow Charts (Lean Six Sigma) - YouTube

1.2.8 Describe the purpose of prototypes to demonstrate the proposed

system to the client.

📖 process of creating a preliminary version of a proposed system to demonstrate its

functionality and design to the client

Accelerate development: Prototyping can help to accelerate the development process by

allowing the project team to test and refine the system before investing significant resources
in full-scale development.
-​ solicit feedback -​ not useful when
-​ make changes or -​ it's a simple project
improvements to ensure it -​ no end users (dev is the end
meets the needs of end user)
users
-​ save wasting time at later == no need to waste time and
stage money on prototype
-​ improve communication
-​ allows end users to visualise
final solution
-​ clarify any
misunderstandings
-​ ensures both client and
developer are on same page

1.2.9 Discuss the importance of iteration during the design process.

1.​ Reducing risk
 a.​ Iteration can help to reduce the risk of failure by allowing the project team to
test and refine their design before committing to full-scale development. This
can help to identify and resolve any potential issues early in the development
process and prevent costly mistakes down the line.
2.​ Responding to feedback
a.​ Iteration allows the project team to respond to feedback from stakeholders
and make changes to the design based on that feedback. This can help to
ensure that the design meets the needs of the stakeholders and has the best
chance of success.
3.​

1.2.10 Explain the possible consequences of failing to involve the

end-user in the design process.
[M22]
BECAUSE OF lack of feedback:
1.​ User dissatisfaction poor usability
a.​ system does not meet user requirements and needs
b.​ poor usability
c.​ negatively impact user productivity
2.​ resistance to change
a.​ end users may feel that their needs and concerns have been ignored, leading
to resistance to change and a lack of buy-in from the end-users, which can
make it more difficult to implement and support the new system.
3.​ Developers not being paid for the final product;
a.​ as the business owner requests are not evident in the final product/ or outside
of the project's scope;

1.2.11 Discuss the social and ethical issues associated with the
introduction of new IT systems.

Same as 1.2.3
Issue Description Social and Ethical Implications

Privacy and Extensive data collection Users face compromised privacy, raising
Surveillance and tracking reduce user concerns about rights and trust in digital
privacy. spaces.

Cybersecurity Increased risks of cyber Responsibility lies with individuals and

and attacks, identity theft, and organisations to protect data, yet
Cybercrime fraud. breaches harm affected individuals.

Digital Divide Unequal access to Exacerbates socioeconomic inequalities,

and Access technology creates raising questions of fair technology
Inequality disparities. access and equity.
 +​ Employment and job displacement
+​ Automated systems and artificial intelligence technologies can replace human
workers, leading to job losses and a decline in the demand for certain types of
work.

Human interaction with the system (1.2.12 - 1.2.16)

1.2.12 Define the term usability.

W4W [M22]
📕The extent to which a device can be used by specific/its users;
To achieve specific goals effectively/efficiently/satisfactorily;

Factors:
complexity / simplicity / amount of effort to get a result / number of errors with the time taken
to move past them;
readability / comprehensibility / reading or writing speed;
learnability / time to accomplish tasks on the first use;
effectiveness ( user performance);
efficiency (time needed to complete a task);

Accessibility

📕Refers to ability of system to meet needs of as many individuals as possible.

Low accessibility = barriers to certain groups e.g. disabled

1.2.13 Identify a range of usability problems with commonly used digital

devices.

1.​ Complex user interfaces

a.​ Digital devices often have complex user interfaces that are difficult for users
to navigate and understand. This can result in confusion, frustration, and
decreased efficiency.
2.​ Poor accessibility
a.​ Many digital devices are not designed with accessibility in mind, making them
difficult or impossible for users with disabilities to use.
3.​ Unintuitive design
a.​ Some digital devices have user interfaces that are not intuitive and do not
follow established design conventions, making it difficult for users to
understand how to interact with them.
4.​ learnability → inadequate documentation
a.​ making it difficult for users to learn how to use them effectively.

Device​ Specific:
 -​ PCs, digital cameras, cell phones, games consoles, MP3 players and other
commonly used digital devices.
-​ Mobile Phone
-​ Size of screen
-​ Difficult to accurately select the correct character on the virtual
keyboard;
-​ difficult to see/use especially in poor light
-​ Battery life- may need to recharge regularly, inconvenient

-​ (CBA)

1.2.14 Identify methods that can be used to improve the accessibility of

systems.
S/E Examples include touch screen, voice recognition, text-to-speech, Braille keyboard.

Target Group Accessibility Method

visually impaired → colour or fully blind -​ Text-to-Speech (TTS)

-​ braille displays and keyboards
-​ screen magnifiers
-​ high contrast

deaf people -​ subtitles

-​ visual alerts

cognitive problems → dyslexic -​ predictive text

-​ spell check

1.2.15 Identify a range of usability problems that can occur in a system.

(straight from CS Cafe) (Basically 1.2.3 and 1.2.11 but contextualised)

Summary:
-​ shitty UI → confusing, difficult to find stuff
-​ slow performance → difficult to do stuff in a timely manner
-​ security

1.​ e-Ticketing
a.​ Difficult navigation: The process of purchasing tickets online can be
confusing, with a poorly designed website or a confusing layout that makes it
difficult for users to find what they are looking for.
b.​ Slow performance: The website may be slow to load or slow to process
transactions, making it difficult for users to complete their ticket purchase in a
timely manner.
c.​ Security concerns: Users may be concerned about the security of their
personal and financial information when making purchases online.
 2.​ Online Payroll
a.​ Complex user interface: The online payroll system may have a complex user
interface that is difficult for users to navigate and understand, leading to
confusion and frustration.
b.​ Inadequate feedback: The system may not provide adequate feedback to
users, making it difficult for them to know what is happening and whether their
actions are having the desired effect.
c.​ Data accuracy: Users may be concerned about the accuracy of the data that
is being entered into the system, as errors can lead to incorrect paychecks or
other problems.

3.​ Scheduling
a.​ Unreliable software: The scheduling software may be unreliable, leading to
crashes or other problems that can be difficult for users to recover from.
b.​ Limited customization options: The scheduling software may have limited
customization options, making it difficult for users to personalize their
schedules and meet their specific needs.
c.​ Inadequate documentation: The scheduling software may come with
inadequate documentation, making it difficult for users to learn how to use it
effectively.

4.​ Voice Recognition

a.​ Recognition errors: The voice recognition system may have difficulty
recognizing certain words or accents, leading to errors and frustration for
users.
b.​ Poor feedback: The system may not provide adequate feedback to users,
making it difficult for them to know what is happening and whether their
actions are having the desired effect.
c.​ Security concerns: Users may be concerned about the security of their
personal information when using voice recognition technology, as it may store
or transmit sensitive information.

1.2.16 Discuss the moral, ethical, social, economic and environmental

implications of the interaction between humans and machines.
AIM 8 Raise awareness of the moral, ethical, social, economic and environmental
implications of using science and technology

No one fucking cares lmao