Please enable JavaScript.
Coggle requires JavaScript to display documents.
Unit 3: Operating Systems - Coggle Diagram
Unit 3: Operating Systems
OS Overview
a collection of applications that work together to coordinate all of a computer's activities
2 objectives:
Convenience: an OS makes a computer more convenient to use
Efficiency: an OS allows the computer resources to be used in an efficient manner
OS services: Program creation, Program execution, Access to I/O devices, Controlled access to file, System access, Error detection and response, Accounting
OS as a resource manager
master program
OS Types
Mobile OS
For example: iOS, Android
and Windows (Mobile Edition)
Server OS
For examples: Windows Server, macOS Server,
UNIX, Linux
Desktop OS
For examples: Windows, macOS, UNIX,
Linux
OS Components
Device Manager
Keeps track of all devices, channels, and control units.
File Manager
It keeps track of all of the files in the system.
Processor Manager
Determines how the CPU will be allocated.
Network Manager
All networking chores are my responsibility.
Memory Manager
In charge of main memory (RAM)
User Interface
The user interface was made out of command lines.
OS Functions
Updating OS
software
Managing
memory
Managing programs and processes
Providing file and
disk management tools
Establishing internet connection
Coordinating tasks
Providing a user
interface
Controlling
network
Monitoring
performances
Configuring
devices
Starting and
shutting down
Administering
security
Cooperation
The File Manager (FM) must compute its precise disc position and transmit this information to the Disk Manager (DM), who obtains the programme and transfers it to Memory Manager (MM).
Once in memory, the MM must keep track of the program's position and progress as the PM runs it.
PMs checked to see if it needs to be fetched from storage or if it is already in memory, and then the relevant manager is notified.
When the programme is done, it must transmit a completed message to the PM so that the processor may be assigned to the next programme in line.
The PM provides a screen acknowledgement message to let the user know that the command has been received.
Finally, the PM must send the completed message to the DM so that the user may be notified and the screen can be refreshed.
The Device Manager (DM) takes electrical impulses and transmits it to the user interface, where the Process Manager (PM) confirms it.