Term
| Sequential computation |
|
Definition
| idea that instructions should be written and processed in a sequential order |
|
|
Term
|
Definition
| a collection of instructions along with the sequential order in which they should be executed |
|
|
Term
|
Definition
| an algorithm that has been encoded by a programming language to be complete and unambiguous |
|
|
Term
|
Definition
| a representation of the algorithm that can be directly executed by the computer hardware |
|
|
Term
| Application programming interface (API) |
|
Definition
| set of function calls implemented by any given software package |
|
|
Term
|
Definition
| when operating systems only allows one execution engine in each process |
|
|
Term
|
Definition
| multiple execution engines allowed in each process |
|
|
Term
| Thread (lightweight process) |
|
Definition
| each execution engine component |
|
|
Term
|
Definition
| the computational environment that includes the program, data, files, and other resources |
|
|
Term
| Multithreaded computation |
|
Definition
| process defines a program and data, but having two different executions of the program in progress at the same time |
|
|
Term
|
Definition
| all components (physical and logical) of the abstract machine that are needed to execute a program |
|
|
Term
|
Definition
| a named, linear stream of bytes of information that are kept on a device |
|
|
Term
|
Definition
| a named sequential collection of bytes (POSIX file) |
|
|
Term
|
Definition
| associated with each instance of an open file |
|
|
Term
|
Definition
| abstract data structure based on the principles of LIFO |
|
|
Term
|
Definition
| holds all the properties that are unique to the thread |
|
|
Term
|
Definition
| execution instructions stored in memory for boot time |
|
|
Term
|
Definition
| set of machine components mainly memory addresses that could be referenced by the execution engine |
|
|
Term
|
Definition
| system call created processes to execute the child process |
|
|
Term
| Operating system responsibilities |
|
Definition
| create an abstract machine environment with multiple, autonomous abstract components. Coordinate the use of the components according to the policies of the machine’s administrator |
|
|
Term
|
Definition
| implement the aspects of device management that are unique to each device type |
|
|
Term
|
Definition
| cooperates with the process manager to administer allocation and use of the primary memory resource |
|
|
Term
|
Definition
| allows the abstract machines primary memory to appear larger than the physical machines memory |
|
|
Term
|
Definition
| OS is as efficient as possibly is use of machine resources |
|
|
Term
| Exclusive use of resources |
|
Definition
| resource isolation, allowing a process’s resources to save information without fear that the information will be altered or copied |
|
|
Term
|
Definition
| processor hardware mode bit is used to distinguish between instruction execution on behalf of an OS and a User |
|
|
Term
|
Definition
| trusted software module that supports the correct operation of all other software |
|
|
Term
|
Definition
| tools that the OS provide to implement security policies chosen by the administrator |
|
|
Term
|
Definition
| defines the machine-specific strategy for managing access to resources |
|
|
Term
|
Definition
| has been carefully written and debugged at the time the OS is created or updated |
|
|
Term
|
Definition
| has not been subjected to such careful analysis, and the overall protection of the machine should not be dependant on the operation of this software |
|
|
Term
|
Definition
| defines the execution capability of a program on the processor |
|
|
Term
|
Definition
| the processor can execute every instruction in its hardware repertoire; these instructions are referred to as supervisor, privileged, or protected instructions |
|
|
Term
|
Definition
| can only execute a subset of the instruction |
|
|
Term
| Message passing system call approach |
|
Definition
| user process constructs a message (request that is desired) uses OS send() system call to pass the message to a trusted OS process |
|
|
Term
|
Definition
| unless it was absolutely necessary for a function to be trusted, it should be implemented outside the kernel |
|
|
Term
| Dynamically installable module |
|
Definition
| can be compiled and installed on a running version of the kernel |
|
|
Term
|
Definition
| layer of abstraction for function implementation |
|
|
Term
|
Definition
| provides specific mechanisms for general object, memory, process, file, and device management |
|
|
Term
|
Definition
| software module that uses the services implemented in the NT Kernel and Executive to implement more abstract services |
|
|
Term
| Hardware Abstraction Layer (HAL) |
|
Definition
| isolates the NT Kernel from hardware differences |
|
|
