Unit 1

Flashcard 1: Hardware
Front: What is hardware?
Back: The physical parts of a computer system (e.g., CPU, RAM, keyboard).

Flashcard 2: Software
Front: What is software?
Back: A set of instructions that provides functionality (e.g., applications, OS).

Flashcard 3: Peripheral
Front: What is a peripheral?
Back: An external device that provides input/output (e.g., mouse, keyboard, monitor).

Flashcard 4: Network
Front: What is a network?
Back: A group of connected computers for data and resource sharing.

Flashcard 5: Human Resources
Front: What are human resources in computing?
Back: The people using or maintaining the computer system.

Flashcard 6: Client
Front: What is a client?
Back: A device that receives services through a network.

Flashcard 7: Server
Front: What is a server?
Back: A device that provides services through a network (e.g., email server, DNS server).

Flashcard 8: Router
Front: What is a router?
Back: A device that routes data between networks.

Flashcard 9: Firewall
Front: What is a firewall?
Back: A device or software that filters malicious information in and out of a network.

Flashcard 10: Usability
Front: What is usability?
Back: The extent to which a system can be used effectively, efficiently, and satisfactorily by users.

Flashcard 11: Ergonomics
Front: What is ergonomics?
Back: The optimization of human well-being and system performance by examining elements of a system.

Flashcard 12: Accessibility
Front: What is accessibility?
Back: The extent to which a system can be used by people with a wide range of user needs.

Flashcard 13: Prototype
Front: What is a prototype?
Back: An early sample, model, or release of a product created to test a concept or process.

Flashcard 14: Iteration
Front: What is iteration?
Back: The process of repeating the design cycle to test, adjust, and optimize a product.

Flashcard 15: Stakeholder
Front: What is a stakeholder?
Back: A person, group, or organization with an interest or concern in a system.

Flashcard 16: End-User
Front: What is an end-user?
Back: The person who actually uses a particular product or system.

1.1.1 Context for a New System

Flashcard 1: Context for a New System
Front: What is the context for planning a new system?
Back: It includes understanding who (users), where (environment), when (scenario), why (need), what (existing technology), and how (use cases). Also, consider organizational issues like user roles and underlying technologies.

1.1.2 Change Management

Flashcard 2: Change Management
Front: Why is change management important?
Back: To manage factors like data loss, time/money/resources, testing, employee retraining, installation processes, and policies. Proper change management reduces organizational impact and improves employee experience.

1.1.3 Compatibility Issues

Flashcard 3: Legacy Systems
Front: What is a legacy system?
Back: An old or outdated system that may cause compatibility issues when integrating with new systems.

Flashcard 4: Business Mergers
Front: What are compatibility issues in business mergers?
Back: Issues like software/OS incompatibility (e.g., Mac/Windows), language encoding (e.g., Unicode for Asian characters), and date/time conventions (e.g., MM/DD/YYYY vs. DD/MM/YYYY).

1.1.4 On-Premise vs. SaaS

Flashcard 5: On-Premise Systems
Front: What are on-premise systems?
Back: Systems hosted locally on the client’s hardware.

• Pros: Available anytime, full control, self-managed security/data.

• Cons: High management costs and hardware requirements.

Flashcard 6: SaaS (Software-as-a-Service)
Front: What is SaaS?
Back: Cloud-based systems hosted remotely by a provider.

• Pros: Minimizes maintenance/development costs, easy to start, scalable, remote backups.

• Cons: Dependent on the provider and raises security concerns with third-party data sharing.

1.1.5 Installation Processes

Flashcard 7: Direct Changeover
Front: What is direct changeover?
Back: Replacing the old system entirely with the new system at once.

• Pros: Fast and least additional cost.

• Cons: No turning back if issues arise.

Flashcard 8: Parallel Running
Front: What is parallel running?
Back: Running both the old and new systems simultaneously for a period.

• Pros: Provides a backup and allows comparison between systems.

• Cons: Costly due to double resource usage.

Flashcard 9: Pilot Running
Front: What is pilot running?
Back: Trialing the new system in a small part of the organization.

• Pros: Limits risk to a small group and allows for comparison.

• Cons: No backup for the pilot group if the system fails.

Flashcard 10: Phased Conversion
Front: What is phased conversion?
Back: Implementing the new system in stages or phases.

• Pros: Allows steady acclimation and training.

• Cons: No backup for failed phases, and the process takes longer.

1.1.6 Data Migration Problems

Flashcard 11: Data Migration Problems
Front: What are common problems during data migration?
Back:

1. Incompatible file formats: Different versions of software may cause data to be unreadable.

2. Data structures: Differences in how data is organized between old and new systems.

3. Validation rules: Data might be lost if it doesn’t fit the new system’s validation rules.

4. Incomplete data transfer: Data may be lost or corrupted during migration.

5. International conventions: Differences in date formats, currencies, and character encoding (e.g., Unicode).

1.1.7 Types of Testing

Flashcard 12: Static Testing
Front: What is static testing?
Back: Testing without executing the code (e.g., reviewing documentation or code).

Flashcard 13: Dynamic Testing
Front: What is dynamic testing?
Back: Testing by interacting with the system to check its functionality.

Flashcard 14: Alpha Testing
Front: What is alpha testing?
Back: Testing done internally by the development team before release.

Flashcard 15: Beta Testing
Front: What is beta testing?
Back: Testing done by selected users from the public before the final release.

Flashcard 16: Black Box Testing
Front: What is black box testing?
Back: Testing without knowledge of the internal code or structure.

Flashcard 17: White Box Testing
Front: What is white box testing?
Back: Testing with full knowledge of the internal code and structure.

Flashcard 18: User Testing
Front: What is user testing?
Back: Testing done by end-users to ensure the system meets their needs.

Flashcard 19: Automated Testing
Front: What is automated testing?
Back: Using software tools to automate parts of the testing process, reducing costs and time.

Flashcard 20: Debugging
Front: What is debugging?
Back: The process of finding and resolving bugs or errors in the system.

Flashcard 21: User Acceptance Testing
Front: What is user acceptance testing?
Back: Testing to ensure the system meets the users' needs and requirements.