Hello! Welcome to the world of Information Studies II: "Information Systems"
Hi everyone! Let's explore the world of "Information Systems" together. When you hear "information system," you might imagine complicated machinery or lines of code. But in reality, things around us like convenience store cash registers, library search terminals, and smartphone booking apps are all information systems.
In this chapter, we will uncover "how these useful mechanisms are built" and "how they stay up and running." It might feel a bit challenging at first, but we'll go through it using familiar, everyday examples, so don't worry!
1. The Big Picture and the System Lifecycle
An information system is a mechanism where "computers," "networks," "data," and "humans" work together to achieve specific goals (such as making shopping smoother or sharing information efficiently).
The Flow of System Development (Lifecycle)
A system isn't just "built and done." Just like building a house, there is a set procedure. This is called the Software Lifecycle.
- Requirements Definition: Discuss and decide "what kind of system we want." This is the most important step!
- Design: Based on the requirements, create the blueprints (design documents).
- Development (Programming): Following the blueprints, write the actual code to build it.
- Testing: Check to see if it works correctly and ensure there are no bugs (errors).
- Operation and Maintenance: Put it into actual use. Fix it if it breaks, or update it with new features.
【Pro Tip】
A common misconception is that "programming takes the longest time," but in reality, "Requirements Definition" and "Operation and Maintenance" often take up the most time. It’s essential to think about the user's perspective!
【Analogy】
It’s similar to planning a school festival booth. "We want to do a haunted house (Requirements Definition)" → "Draw a diagram of where everything goes (Design)" → "Build it (Development)" → "Hold a rehearsal (Testing)" → "Start the show (Operation)."
Summary of this section
System development follows these steps: Requirements Definition → Design → Development → Testing → Operation & Maintenance!
2. System Architecture and Reliability
It is vital that a system "never stops." It would be a disaster if a bank's system went down, right? To prevent this, there are techniques to improve reliability.
Methods of System Configuration
The names change depending on how you combine multiple computers.
- Duplex System: You prepare two units: one is the "primary (live)" unit, and the other is the "standby" unit. If the primary breaks, the standby takes over.
- Dual System: Two units perform the same processing "simultaneously." They compare results to constantly check for errors. This is even more reliable!
Calculating "Availability" to Measure Reliability
The indicator used to show how well a system is running is called Availability. We’ll look at a bit of math here, but it's simple once you understand the logic.
- MTBF (Mean Time Between Failures): The average time spent running without a failure. Think of this as the "healthy period."
- MTTR (Mean Time To Repair): The average time taken to fix the system after a failure. Think of this as the "time spent in the hospital."
The formula to find Availability is as follows:
\( Availability = \frac{MTBF}{MTBF + MTTR} \)
【Memorization Tip】
Remember it as: "The ratio of healthy time out of the total time (healthy time + repair time)."
💡 Fun Fact:
You might hear the term "five nines" (99.999%). This refers to super-high reliability where the system is down for less than 5 minutes in a whole year!
Summary of this section
Prepare backups (Duplex/Dual systems) in case of failure, and use Availability to evaluate the strength of your system!
3. Network Configuration and Data Management
Within a system, tasks are divided among components. The most typical model is the Client-Server System.
Forms of Task Division
- Client: The side requesting services (everyone's smartphones or PCs).
- Server: The side providing services (large computers that store data or perform heavy calculations).
Apart from this, there is also a method called P2P (Peer-to-Peer), where everyone exchanges data as equals. This is often used for online games and file sharing.
UI and UX (The Secrets of Ease-of-Use)
Good systems must be easy to use.
- UI (User Interface): The "visible parts" like screen design, button shapes, and font size.
- UX (User Experience): The "experience" of feeling that the system is "fun" or "convenient" to use.
【Analogy】
Imagine a stylish cafe. The lovely tables and chairs are the UI, while the feeling of being able to "relax" after drinking a delicious coffee there is the UX.
Summary of this section
Systems operate through task division (Client/Server), and their usability is determined by UI/UX!
4. Systems, Society, and Security
Finally, let's learn about our responsibilities when handling information systems.
Protecting Information System Security
To protect systems from malicious attacks, the following measures are necessary:
- Authentication: Verifying identity through IDs, passwords, or fingerprint scans.
- Access Control: Limiting who is allowed to view or access which data.
- Backup: Making copies of data so that if it gets deleted, it isn't lost forever.
⚠️ Common Misconception:
Thinking "if I install security software, it's 100% safe" is a mistake. The biggest weakness is often "human carelessness" (like sticking passwords on sticky notes), so the mindset of the user is incredibly important.
Summary of this section
To use systems safely, you need both technical measures and proper user manners (information ethics)!
In closing...
Information systems are like magic tools that support our daily lives. By understanding how they work, you'll be able to move beyond just using them and start thinking, "Could it be even more convenient if we did it this way?" Start by observing the systems around you (like ticket gates at the station or payments at a convenience store)! I'm rooting for you!