System Life Cycle and Integration Quiz

System Life Cycle

• The system life cycle describes the stages involved in developing a new system.
• Systems typically begin with an analysis stage, followed by design, implementation, and evaluation.
• It may be necessary to return to an earlier stage during development.

Systems in Organizations

• New systems are often created to replace outdated, inefficient, or redundant systems.
• The aim of a new system is to improve productivity, quality, and minimize costs.
• System planning should consider potential business issues such as lack of organizational or business strategy, stakeholder participation, end-user ownership, required training, and organizational culture.
• Feasibility studies evaluate a project's potential.
• Change management is essential for successfully integrating new systems.
• Legacy systems may still be used due to data compatibility issues, as well as the existing functionality.
• Merging businesses can decrease costs.

System Integration Strategies

• Systems can be integrated to maintain the same functionality.
• Replacement of the existing systems can increase costs.
• Selective integration of the best aspects of existing systems can decrease costs.
• System language differences create communication problems.
• Software incompatibility can hinder successful system integration.
• Systems can be hosted locally on the client's infrastructure or remotely on the provider's infrastructure.
• SaaS (Software as a Service) involves using cloud-based software and data storage.

Types of Changeovers

• Parallel changeover involves keeping the old system running alongside the new.
• Big bang changeover involves immediately switching to the new system.
• Pilot changeover limits the new system's use to a specific group initially.
• Phased changeover gradually switches to the new system in stages.

Types of Testing

• Functional testing ensures individual commands and functions operate correctly.
• Data testing evaluates handling of normal, abnormal, and extreme data inputs.
• Alpha testing is conducted by the software developers before public release.
• Beta testing involves user feedback on a public version.
• Dry-run testing uses pen and paper to simulate system functionality.
• Unit testing examines individual parts of the system separately.
• Integration testing verifies how system components function together.
• User acceptance testing is done to confirm that the system meets customer needs.
• Debugging is systematic error-finding and fixing.

Importance of User Documentation

• Users need external and internal documentation to understand complex programs or systems.
• External documentation (manuals, guides) explains how to use programs or systems.
• Internal documentation (comments, code structure) assists in understanding the code.

Methods of Delivering User Training

• Self-study allows users to learn at their own pace with manuals, books, or online resources.
• Formal classes provide interaction and discussion between students and instructors.
• Remote/online training offers flexibility and accessibility from anywhere with Internet access.
• Online portals provide updated manuals, support, and FAQs.

Causes of Data Loss

• Accidental deletion, administrative errors, poor data storage, fires, viruses, data corruption, firmware corruption, natural disasters, power outages are common causes of data loss.

Data Migration

• Transferring data between different systems or formats is known as data migration.
• Issues like data incompatibility or differences in data formats often cause issues during data migration.

Importance of User Documentation

• External documentation provides a clear guide on how to use a system.
• Internal documentation offers insights into the program's internal workings and structure.
• Online support, FAQ lists, and email support make systems user-friendly.
• Live chat assistance resolves immediate user problems while on systems.
• User manuals provide comprehensive guidance on the operation aspects of the systems.

Various Types of Testing

• Functional testing checks if commands operate correctly.
• Data testing uses different inputs to evaluate the system's design.
• Alpha testing assesses a system by company staff.
• Beta testing is user feedback before public release.
• Dry-run testing mimics operations using paper.
• Validation ensures the system meets defined specifications.
• Verification ensures the system fulfills required functions according to the design.

Computer Hardware and Software

• Computer hardware are physical components.
• Computer software contains instructions for the CPU.
• Input, processing, output, and storage.
• Peripheral devices include printers and scanners, and are used for auxiliary functions.
• Computer networks are interconnected systems that share resources.

IT Subjects and Ethical Significance

• Reliability is how well a system functions, and it impacts data integrity, time-loss, and money loss
• Issues of data integrity can cause issues such as data incompleteness or errors.
• Issues of data inconsistency can occur when different copies of the same data are not in sync with one another.
• Privacy refers to control over data usage.
• Security safeguards systems from unauthorized access or use.

Examining Current Systems

• Examine current systems, including documents and procedures.
• Identify stakeholders, end-users, and documentation about functions.
• Information retrieval from various sources is known as literature search.

Iteration

• Iteration means repeating a series of instruction or a block of instructions.

System Usability

• Accessibility means being able to use the system for as many people as possible.
• Usability determines how easily a system accomplishes user tasks.
• Problems in ease of use may arise from impairment, disability or other qualities.

Moral, Ethical, and Social Issues

• How technology is used (surveillance, social divides, and cybersecurity risks).
• The impact of technology on society, business, and the environment.

System Flowcharts

• System flowcharts represent a system, including data flow.
• They display processing steps and data stores.

Data Flow Diagrams (DFD)

• Show data flow throughout a system.
• Include processes, data stores, and entities.

Structure Charts

• Show functions and sub-functions of a system.
• Display relationships between modules.
• Can be used for modular design.

Modular Design

• Divides a problem of significant complexity into smaller parts.
• Allows sub-problems to be solved independently.
• Enables code reuse and facilitates maintenance.
• Reusable modules can be used as building blocks for larger systems.

Programming Languages and Translation

• Machine language describes instructions to a CPU, and is expressed in 1s and Os.
• Assembly language uses mnemonics instead of 1s and Os.
• High-level languages contain instructions closer to natural language.
• Compilers translate high-level language programs into machine language.
• Interpreters translate each instruction in high-level languages line by line into machine instructions.

Variables and Data Types

• A variable is a place to store a value.
• Data types like strings, integers, Booleans, and arrays are used.
• Variable scope must also be considered and the different types of scope are global and local.
• Arrays store multiple elements of the same type.
• One-dimensional arrays are organized linearly.

Data Structures(Arrays, Linked Lists, Stacks, Queues, Binary trees)

• Linear data structures such as arrays process elements one after another.
• Arrays store items of a specific type/data in an arranged order.
• Stacks process element in Last-in, First-out (LIFO) order.
• Queues process element in First-in, First-out (FIFO) order.
• Linked lists are non-linear (or non-sequential) data structures made up of nodes.
• Binary trees are hierarchical data structures made up of nodes.
• Data structures aid in organizing and storing data efficiently.

Operating Systems (OS)

• Manages hardware resources, peripheral devices, and memory utilization, allowing concurrent or multitasking operation.

Computer Networks

• Computer networks consist of two or more interconnected computer systems.
• Nodes connect to a network through cables or wireless technologies.
• Clients request services (e.g., printing, data access).
• Servers supply services to clients.
• Ethernet cables, Wi-Fi, and PANs are network types.
• Hubs, switches, and routers are network devices and are interconnected to create a network.
• WLANs use radio waves for communication, while LANs use cables.
• WANs span larger geographical areas.

Wireless Networking

• All wireless devices communicate via radio transmissions.
• Wireless technologies include cell phones, keyboards, and mice.
• Wireless networks can be more convenient but at the cost of security risks.
• Interference, low bandwidth, and security are potential drawbacks.
• Technologies such as Wi-Fi and Bluetooth facilitate wireless communications.

System Components

• Input devices, processor, output devices, storage and memory.
• The way these components interact with each other.

Analogue-to-Digital Converters (ADCs)

• Devices that convert analogue signals into digital signals.
• Accuracy, range and resolution are essential sensor properties.
• Sensors are used to measure physical quantities and convert them into electrical signals, aiding in control systems.

Processors and Microprocessors

• Microprocessors are integrated circuits.
• They perform arithmetic and logic operations.
• They control other systems and devices.
• Processors can be general-purpose or specialized.
• Graphic processing units (GPUs) are processors for handling graphic-related tasks.

Algorithms and Data Structures

• A procedure or a set of rules to solve problems.
• Data Structures are techniques for organizing and storing data.
• Common data structures include arrays, stacks, queues, and linked lists.
• Algorithm characteristics include efficiency (e.g., time and resources needed to complete a task), correctness (e.g., producing expected results), and reliability (e.g., dependability and consistency).