INF2144H Chap.4 Time-Sharing and Information Networks
Time-Sharing and Information Networks
Trace architecture into interaction
Time-sharing allowed multiple people to interact with a shared computer through terminals, changing the delay and continuity of computing work. Explain which resource was shared, how sessions were scheduled and what the user could do differently from a prior workflow.
Connection alone does not establish collaboration.
Separate augmentation and automation
Augmentation extends human reasoning or coordination through a feedback loop, while automation delegates a defined operation. A system may combine both.
Identify the human judgment retained, the machine operation performed and the interface through which results return to the person or group.
Keep institutions in the process
Terminals, accounts, expertise and organizational purpose shaped who could use early networked systems. Qualify claims of democratization by naming which delay or cost decreased and which access condition remained.
Compare visionary texts with implemented systems so aspiration does not become evidence of adoption.
Establish the prior workflow
Interactive computing is meaningful only against a comparison. Batch processing may require users to prepare jobs and wait for later output, while a terminal session supports repeated input and response. State the task, delay and feedback available in both arrangements.
This keeps responsiveness from becoming an anachronistic judgment based on contemporary networks and shows why a historical system felt different to its users.
Describe the shared resource
Time-sharing divides processor attention and other resources among sessions through scheduling.
The user experiences an interactive environment, yet that experience depends on system load, terminal connection, software and institutional priorities. Explain which parts are shared and which appear personal.
The distinction matters because a private-feeling session can still be governed by a central allocation system.
Show how coordination is produced
Remote terminals do not create collaborative work on their own. Participants need shared records, naming conventions, permissions and a way to interpret one another's changes.
Trace how a document, message or link persists between sessions and how users learn its meaning. If the evidence establishes connection but not common practice, stop at interaction rather than claiming collaboration.
Read visionary texts against implementation
Visions of human-computer symbiosis and augmentation specify ambitions for a future relationship.
Analyse the division of labour they propose, the task assigned to human judgment and the operation assigned to machines. Then compare those claims with a working system.
Differences in scale, access or interface are valuable evidence about how a vision was translated, narrowed or redirected.
Qualify the reach
A research system can introduce a powerful interaction model while remaining available only within an institution. Name terminals, accounts, expertise, cost and organizational purpose when evaluating access.
The conclusion can state which delay or barrier decreased without claiming universal democratization. End by identifying the later platform feature that shares the principle and the governance or business conditions that make the two systems historically distinct.
What this chapter covers
- 01
Time-sharing
- 02
Interactive computing
- 03
Augmentation
- 04
Networked information
- 05
Institutional access
Worked example · free
Explain networked collaboration
- 2Describe the shared architecture and access.
- 4Trace interaction and coordination practices.
- 2Qualify the institutional reach.
Key terms
- Time-Sharing
- Time-Sharing allocates a shared computer across multiple interactive user sessions.
- Augmentation
- Augmentation uses computing operations and feedback to extend human reasoning or coordinated work.
- Interactive Computing
- Interactive Computing supports continuing input and response during a user session rather than delayed batch processing.
Time-Sharing and Information Networks FAQ
Why does network connection not prove collaboration?
Collaboration also needs shared objects, conventions, permissions, communication and coordinated practice. A technical link creates a condition for interaction, while institutions and participants determine what that interaction becomes. Trace a persistent record and the next participant action to show whether information is merely transmitted or incorporated into joint work.
Qualify the claim with the actual access conditions.
Assessment move
Put prior workflow, shared resource, access condition, interactive operation and collaborative practice in causal order, then test the weakest transition. Write a process trace with resource, account, input, response, stored record and next human decision. Attach evidence to every link.
A technical source may establish scheduling or terminal behaviour, an institutional history may establish who received access and a participant account may establish how rapid feedback changed work. Mark any unsupported connection as an inference rather than borrowing certainty from another layer. Run the trace against a failure such as heavy system load, lost connection or incompatible naming conventions.
Identify which part of interaction stops and which social practice compensates. This reveals whether the significant innovation lies in resource sharing, interface feedback, persistence or organizational coordination. Compare a visionary text with an implemented system by listing the division of labour each proposes between person and machine.
Preserve differences in scale and access instead of treating them as incomplete versions of the present. Close by stating which delay or barrier decreased, which institutional condition remained and which later platform feature shares the principle without sharing the same governance or business arrangement.
