Topic 1 - Systems Fundamentals PDF

Summary

This document provides an overview of systems fundamentals, covering topics such as systems in organizations, change management, and compatibility issues. The document explores various aspects of IT systems and their design to help users understand the concepts.

Full Transcript

**Topic 1.1 - Systems in Organizations** ======================================== ### **1.1.1 Identify the context for which a new system is planned.** **Exit Skills** - - - - - New Systems can be created in order to - - - **Context** = background, environment, framework, set...

**Topic 1.1 - Systems in Organizations** ======================================== ### **1.1.1 Identify the context for which a new system is planned.** **Exit Skills** - - - - - New Systems can be created in order to - - - **Context** = background, environment, framework, setting or situation surrounding a system Context of problem can include: - - - - - - **The context will affect the problem, which will affect the solution** E.g. a delivery driver should be equipped with a mobile phone, as they need to carry around packages and move around often; whereas airplane pilots can use tablets as they have more space and move around less **New systems rarely come in a vacuum** - you cannot ignore the context surrounding the problem Considerations when considering a new system's context - - - - - - **Potential Organizational Issues** - - - - - - **Feasibility Report (TELOS)** - - - - - Example: A bookstore uses door to door salesmen to collect orders from customers, these orders are then taken to the company's offices and are input by a secretary. The bookstore has decided to change this department and will ask their salesmen to input the orders at home using their personal computers. Discuss the effects of these changes. - - - - - - ### **1.1.2 Describe the need for change management.** **Exit Skills** - - - Describe the need for change management Examples: - - - **Changing a system can be difficult for a variety of reasons:** -- Users don't like change (too often/at all) -- New systems might omit old features -- Old systems might be faster in certain circumstances -- People find change complex -- From a technology perspective, change might lead to incompatibility -- There might be data loss during migration -- It might be expensive (either in terms of money or time) --... the list goes on! Before any change is applied, the following steps might make the process easier: Successful Change Management relies on factors such as - - - - - The need for Change Management - - - - - ### **1.1.3 Outline compatibility issues resulting from situations including legacy systems or business mergers.** **Exit Skills** - - - - Legacy system : Old system or device, no longer supported by the provider. (Eg. old car, cant find replacement parts) dongle Merger: Combination of two or more entities into one, mergers can be very tricky ![](media/image10.png) Issues when replacing legacy system: - - - Strategies when integrating legacy systems & methods of business merging - - - - ### **1.1.4 Compare the implementation of systems using a client's hardware with hosting systems remotely** **Exit Skills** - - - ![](media/image5.png) **Common SaaS examples** - - - - ![](media/image2.png) ### **1.1.5 Evaluate alternative installation processes** **Exit Skills** - - - 4 alternatives to changing the system - - - - - - - - - - - - ### **1.1.6 Discuss problems that may arise as a part of data migration** **Exit Skills** - - - Possible problems that may arise - - - - - - - - - - - - ### **1.1.7 Suggest various types of testing** **Exit Skills** - - - Static(without execution of software) vs Dynamic Testing(with execution of software) - - - - - - **Static - In the developing stage \*** **Dynamic - In all stages** **Alpha - First stage/phase of software testing** **Beta - Second stage/phase of software testing** **Black box - during all phases of software testing** **White box - In the first stage of software testing** **Dry run testing - Prior to any development** **Data testing -** **Automated testing -** **Unit testing -** **Integration testing -** Alpha vs Beta testing +-----------------------------------+-----------------------------------+ | Alpha Testing | Beta Testing | +===================================+===================================+ | - - | - - | +-----------------------------------+-----------------------------------+ Black Box vs White Box Testing - - User Acceptance Testing - Testing any new/updated system with its ultimate end users to see if it meets their expectation is very important Automated Testing - - - **Data Testing** - when normal, abnormal and extreme data is put into the system for testing - - - - - **Dry run testing** is when the programmer mentally runs the algorithm with pen and paper. They examine the source code and decide the output should be **Unit Testing** is when individual parts of the system are tested separately **Integration testing** is when the whole system is tested together to verify if it all works together **Debugging** is the systematic process of finding and correcting errors in a computer program - **Validation and Verification** - - - - - - ### **1.1.8 Describe the importance of user documentation** **Exit Skills** - - User Documentation is any document that explains how to use the features and functions of a system to its end-users. It comes in many forms: books, PDFs, websites, videos, etc. Reasons why proper user documentation is important - - - - - - - Proper documentation includes - - - - - - - - - ### **1.1.9 Evaluate different methods of providing user documentation** **Exit Skills** - - - +-----------------+-----------------+-----------------+-----------------+ | Methods | Features | Advantages | Disadvantages | +=================+=================+=================+=================+ | Help Files | Offline, | - - - | - - - - | | | supplied with | | | | | the system | | | +-----------------+-----------------+-----------------+-----------------+ | Online Support | Active Support | - - - - | - - | | | | | | +-----------------+-----------------+-----------------+-----------------+ | Printed Manuals | Offline booklet | - - - | - - - | +-----------------+-----------------+-----------------+-----------------+ | | | | | +-----------------+-----------------+-----------------+-----------------+ ### **1.1.10 Evaluate different methods of delivering user training** **Exit Skills:** - - - Importance of user training: - - - +-----------------+-----------------+-----------------+-----------------+ | Methods | Description | Advantages | Disadvantages | +=================+=================+=================+=================+ | Self | Self teach | Low cost | No guidance, | | instruction | | | user feel | | | | Flexible | lost/overwhelme | | | | timeline | d | | | | | | | | | User only | Features | | | | learns the | misunderstood/i | | | | training they | gnored | | | | want | | +-----------------+-----------------+-----------------+-----------------+ | Formal Classes | Learn in a | High quality | High cost | | | class | training | | | | | | Inflexible | +-----------------+-----------------+-----------------+-----------------+ | Remote/Online | Online class | - - - - | - - - | | Training | | | | +-----------------+-----------------+-----------------+-----------------+ ### **1.1.11 - Identify a range of causes of data loss** **Exit Skills** - - +-----------------------------------+-----------------------------------+ | Cause | Examples | +===================================+===================================+ | Hardware/System malfunctions | Physical damage | +-----------------------------------+-----------------------------------+ | Software malfunction | Data corruption | +-----------------------------------+-----------------------------------+ | Human error | - - - - | +-----------------------------------+-----------------------------------+ | Malicious softwares | Trojan, Virus, Worm | +-----------------------------------+-----------------------------------+ | Natural disasters | Sinkhole **smash,** Me when the | | | earth just opens up and eats my | | | laptop | +-----------------------------------+-----------------------------------+ ### **1.1.12 - Outline the consequences of data loss in a specified situation** **Exit Skills** - - Top 5 reasons for data loss: - - - - - Examples: - - - - - - Consequences vary in severity: - - - - - - ![](media/image13.png) ### **1.1.13 Describe a range of methods that can be used to prevent data loss** **Exit Skills** - - Key data loss prevention methods - - - - Security tactics - - ### **1.1.14 Describe strategies for managing releases and updates** **Exit Skills** - - - Patch: quick & temporary small fixes or changes Update: more significant changes, new features, permanent additions and bug fixes Release: a completely new version of the system Upgrade: when a user already has the old version of the system, they upgrade to the new version on top of the old version Patch: - - - - - - Update: - - - DOUG best brawler in bs ye fax [[https://x.com/AshClashYT/status/1761951084283670702?s=20]](https://x.com/AshClashYT/status/1761951084283670702?s=20) - Upgrade: - - Release: - **Downgrade** - **How to get updates** - - - - - - - - Release Management: - - - - - - - - **Topic 1.2 - Systems Design Basics (SL & HL)** =============================================== ### **1.2.1 Define the terms: hardware, software, peripheral, network, human resources** **Exit Skills** - **5 components of a computer system** Hardware: - Peripheral devices: - - - Software: - - - Networking: - - Human Resources: - - - User acceptance testing: - - - ### **1.2.2 Describe the roles that a computer can take in a networked world** **Exit Skills** - - **Client** - - - **Dumb Terminal** - - - **Thin Client** - - **Server** - - - - - - - - **Client-Server Model** - - - **Router** - - **Domain Name System (DNS)** - - - - - **Email Server** - **Router** - - - - **Firewall** - - - ### **1.2.3 Describe the roles that a computer can take in a networked world** **Exit Skills** - - - **Social Issue -** A **social issue** is a problem that **influences** a **considerable number** of the individuals within a **society** Examples of **social issues:** Crime, Health, Education, Media & Propaganda, Poverty, Terrorism **Ethical issue -** A problem or situation that requires a person or organization to **choose** between **alternatives** that must be **evaluated as right (ethical) or wrong (unethical)** Examples of **ethical issues:** Computer crime, Responsibility for computer failure, Protection of computer property, records and software, Privacy IT subjects of **social** and **ethical** significance - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ### **1.2.4 Identify the relevant stakeholders when planning a new system** **Stakeholder** - - - - - - - - - - - - - - ![](media/image7.png) ### **1.2.5 Describe methods of obtaining requirements from stakeholders** **Methods of Obtaining Requirements:** - - - - +-----------------------+-----------------------+-----------------------+ | | Pro | Cons | +=======================+=======================+=======================+ | Survey | - - - - - - | - - - | | | | | +-----------------------+-----------------------+-----------------------+ | Interviews | - - - | - - - - - - | | | | - - | | | - - - - | | | | | TAKES A LONG TIME TO | | | | PROCESS | +-----------------------+-----------------------+-----------------------+ | Direct Observation | - - - - - | - - - - | | | | | | | | - - | +-----------------------+-----------------------+-----------------------+ | Collecting Documents | - | - - | +-----------------------+-----------------------+-----------------------+ Dumb Terminal Thin Client Client ---------------- --------------- ---------------- ---------------- Without Server No Functions Some Functions Most Functions ### ### **1.2.6 Describe appropriate techniques for gathering the information needed to arrive at a workable solution** Before you start making a system you need to make sure you know exactly what's going on at the moment and what other information you might need. Methods of gathering information: - - - - ### **1.2.8 Describe the purpose of prototypes to demonstrate the proposed system to the client** [[1.2.8]](https://docs.google.com/presentation/d/118VXtyQHe2onoFZlS7CW3_ihowPOwqV9D0vcDXibf9M/edit?usp=sharing) **Purpose of prototype:** - - - - - - - - - - - ### **1.2.9 - Discuss the importance of iteration during the design process** [[1.2.9]](https://docs.google.com/presentation/d/1dPzIEvyZD9BIwWVJOZsODfk00_ZsefQuA5Cechof6po/edit#slide=id.g2c0cd55b7b8_0_387) Iteration - a procedure in which repetition of a sequence of operations yields results successively closer to a desired result - - - - - **What is the definition of iteration?** *Repetition with the goal of yielding a desired results.* The process of building on existing prototypes in order to reverse progress. Iteration refers to the iteration of iteration iterating iteration of iteration of iterating the iteration of iterations. Repeat until the operations yield an undesired results. **What is the goal of iteration?** All of the above; resolve bugs; satisfying users; new release of the system **Which is not a part of iteration?** Starting from scratch; user acceptance testing; designing a prototype; creating the perfect product first try. ### **1.2.10 - Explain the possible consequences of failing to involve the end-user in the design process.** [[1.2.10 Explain the possible consequences of failing to involve the end-user in the design process.]](https://docs.google.com/presentation/d/1Ttf1JO3iU-gYhrtpHhEUxpyxpUzhjZQGlG1nvYX6x5o/edit#slide=id.g2c0d410f84b_0_32) User dissatisfaction: - - - ### **1.2.11 Discuss the social and ethical issues associated with the introduction of new IT systems** **Exit Skills** - - - Ways new IT systems have changed the way humans live - - - - ### **1.2.12 Define the term usability** **Exit Skills** - **Accessibility ≠ Usability** **Usability** - the potential of a product, application or website to **accomplish user goals** **Accessibility** - the potential of a service, product, device or environment to serve and meet the demands of **as many users as possible** **Components of Usability** - - - - - **Ergonomics** - ergonomics or human engineering refers to the design of safe and comfortable products, systems or processes, specifically for people (examples include keyboard shaped to consider human comfort) ### **1.2.13 Identify a range of usability problems with commonly used digital devices** **Devices:** - - - ### **1.2.14 Identify methods that can be used to improve the accessibility of systems** **Usability ≠ Accessibility** **Usability** - the potential of a product, application or website to **accomplish user goals** **Accessibility** - the potential of a service, product, device or environment to serve and meet the demands of **as many users as possible** Peripherals can increase accessibility For example: - - - - - - **Types of disabilities** - - - - 4 specific ways to improve accessibility of a system: 1. ### **1.2.15 Identify a range of usability problems that can occur in a system** +-----------------------------------+-----------------------------------+ | | Usability Problems | +===================================+===================================+ | Ticketing System | - - - | +-----------------------------------+-----------------------------------+ | Online Payroll (paying | - - | | salaries/wages) | | +-----------------------------------+-----------------------------------+ | Scheduling | - - - | | | | | | - | | | | | | - - | +-----------------------------------+-----------------------------------+ | Voice recognition | - - - | +-----------------------------------+-----------------------------------+ | Systems that provide feedback | - - - | +-----------------------------------+-----------------------------------+