Unit 1

Hardware

The physical parts of a computer system (e.g., CPU, RAM, keyboard).

Software

A set of instructions that provides functionality (e.g., applications, OS).

Peripheral

An external device that provides input/output (e.g., mouse, keyboard, monitor).

Network

A group of connected computers for data and resource sharing.

Human Resources

The people using or maintaining the computer system.

Client

A device that receives services through a network.

Server

A device that provides services through a network (e.g., email server, DNS server).

Router

A device that routes data between networks.

Firewall

A device or software that filters malicious information in and out of a network.

Usability

The extent to which a system can be used effectively, efficiently, and satisfactorily by users.

Ergonomics

The optimization of human well-being and system performance by examining elements of a system.

Accessibility

The extent to which a system can be used by people with a wide range of user needs.

Prototype

An early sample, model, or release of a product created to test a concept or process.

Iteration

The process of repeating the design cycle to test, adjust, and optimize a product.

Stakeholder

A person, group, or organization with an interest or concern in a system.

End-User

The person who actually uses a particular product or system.

Context for Planning a New System

Includes understanding who (users), where (environment), when (scenario), why (need), what (existing technology), and how (use cases), along with organizational issues like user roles.

Change Management

Important to manage data loss, resources, testing, retraining, and policies to reduce organizational impact.

Legacy System

An old or outdated system that may cause compatibility issues when integrating with new systems.

Compatibility Issues in Business Mergers

Issues like software incompatibility, language encoding, and date/time conventions.

On-Premise Systems

Systems hosted locally on the client's hardware; high management costs but full control.

SaaS (Software-as-a-Service)

Cloud-based systems hosted remotely; minimizes costs but raises security concerns.

Direct Changeover

Replacing the old system entirely with the new; fast but no fallback if issues arise.

Parallel Running

Running both old and new systems simultaneously; offers backup but costly.

Pilot Running

Trialing the new system in a small part of the organization; limits risk but no backup if it fails.

Phased Conversion

Implementing the new system in stages; allows training but risks during failed phases.

Data Migration Problems

Common issues include incompatible file formats, data structures, validation rules, incomplete data transfer, and international conventions.

Static Testing

Testing without executing the code; involves reviewing documentation or code.

Dynamic Testing

Testing by interacting with the system to check functionality.

Alpha Testing

Internal testing done by the development team before release.

Beta Testing

Testing done by selected public users before the final release.

Black Box Testing

Testing without knowledge of the internal code or structure.

White Box Testing

Testing with full knowledge of the internal code and structure.

User Testing

Testing done by end-users to ensure the system meets their needs.

Automated Testing

Using software tools to automate parts of the testing process.

Debugging

The process of finding and resolving bugs or errors in the system.

User Acceptance Testing

Testing to ensure the system meets the users' needs and requirements.