Fachhochschule Vorarlberg. GsiOS. University of Applied Sciences Vorarlberg. FH Vorarlberg. Sarah Hofer. Hannes Kappl. Matthias Kathan.

Größe: px

Ab Seite anzeigen:

Download "Fachhochschule Vorarlberg. GsiOS. University of Applied Sciences Vorarlberg. FH Vorarlberg. Sarah Hofer. Hannes Kappl. Matthias Kathan."

Philipp Schäfer
vor 7 Jahren
Abrufe

1 Fachhochschule Vorarlberg University of Applied Sciences Vorarlberg GsiOS Studiengang Informatik FH Vorarlberg Dornbirn, im Jahr 2009 Vorgelegt von: Sarah Hofer Hannes Kappl Matthias Kathan Christian Kuen Christoph Storm

Vorarlberg Dornbirn, im Jahr 2009 Vorgelegt von: Sarah

2 Inhaltsverzeichnis

3 1 Rollen 1.1 Elevator Pitch For the application developer who develops flexible and robust applications in an easy way the GSIOS is an operating system which provides convenient, efficient and evolvable interfaces and unlike Windows we are developing an embedded operating system. 1.2 Rollen Endbenutzer: - Als Endbenutzer möchte ich Stabilität, damit die Anwendung nicht abstürzt. - Als Endbenutzer möchte ich Sicherheit, damit meine Daten geschützt sind. - Als Endbenutzer möchte ich Usability, damit ich das Betriebssystem ohne Probleme installieren kann. - Als Endbenutzer möchte ich Usability, damit ich die Anwendungen einfach starten kann. - Als Endbenutzer möchte ich eine Konsole, damit ich mich einfach durch das Dateisystem navigieren kann. - Als Endbenutzer möchte ich Multitasking, damit ich mehrere Anwendungen gleichzeitig ausführen kann. - Anwendungsentwickler: - Als Anwendungsentwickler möchte ich eine gute API, damit ich ohne Probleme Anwendungen entwickeln kann. - Als Anwendungsentwickler möchte ich eine gute Dokumentation, damit ich ohne Probleme Anwendungen entwickeln kann. - Als Anwendungsentwickler möchte ich, dass sich jeder Entwickler an die Richtlinien hält, damit der Code konsistent bleibt. Coach: - Als Coach möchte ich eine gut strukturierte Planung, damit ich immer auf dem neuesten Stand bin. - Als Coach möchte ich eine gute Dokumentation, damit ich Teamentscheidungen nachvollziehen kann. - Als Coach möchte ich eine gute Dokumentation, damit ich die Spezifikationen verifizieren kann. OS-Entwickler: - Als OS-Entwickler möchte ich klare Richtlinien, damit ich ohne Probleme am OS weiterentwickeln kann. - Als OS-Entwickler möchte ich eine gute Dokumentation, damit ich mich im Code zurechtfinde. - Als OS- Entwickler möchte ich definierte Schnittstellen, damit ich daran anknüpfen 3

interfaces and unlike Windows we are developing an embedded operating system. 1.2 Rollen Endbenutzer: - Als Endbenutzer möchte ich Stabilität, damit die Anwendung nicht abstürzt.

4 kan, um das OS weiterzuentwickeln. - Als OS-Entwickler möchte ich, dass sich jeder Entwickler an die Richtlinien hält, damit der Code konsistent bleibt. Endbenutzer: Das System sollte komfortabel, einfach zu benutzen, leicht zu erlernen, zuverlässig, sicher, schnell sein. Alle, die das System designen, erstellen, warten, bedienen müssen: Das System sollte leicht zu designen, implementieren und warten sein. Es sollte flexibel, zuverlässig, fehlerfrei und effizient sein. Convenience: OS makes a computer more convenient to use Efficiency: OS allows the computer system resources to be used in an efficient manner Ability to evolve: OS should be constructed in such a way as to permit the effective development, testing, and introduction of new system functions without interfering with service 1.3 Rollen im Scrum Team: Sarah Hofer, Hannes Kappl, Matthias Kathan, Christian Kuen, Manuel Oblasser, Christoph Storm Scrum Master: Christoph Storm Product Owner: Sarah Hofer Customer: Fachhochschule Vorarlberg End User: alle, die einen AVR32AP7000 (NGW100) haben Manager: Patrick Ritschel, Thomas Hensler Target Customer für OS: - Anwendungsentwickler - Endanwender (Applikationen ausführen) Target Customer für Gesamtsystem: - Benutzer des Bilderrahmens 4

Alle, die das System designen, erstellen, warten, bedienen müssen: Das System sollte leicht zu designen, implementieren und warten sein. Es sollte flexibel, zuverlässig, fehlerfrei und effizient sein.

5 2 Tools 5

6 3 Prozesse Process Management: - Process Concept, Scheduling - Threads - CPU Scheduling - Scheduling Algorithm - Interprocess communication - Process Synchronization - Deadlocks Process needs certain resources - CPU time, memory, files, I/O devices, given to it when created, allocated or while it is running Program by itself is not a process. Program is a passive entity, process is an active entity, with a program counter specifying the next instruction to execute. Execution of a process must be sequential. Operating system is responsible for: - creating and deleting both user and system processes - suspending and resuming processes - providing mechanisms for process synchronization - providing mechanisms for process communication - providing mechanisms for deadlock handling Protection System: Processes must be protected from one another s activities. Controlling the access of programs, processes or users to the resources defined by a computer system. 6

Program is a passive entity, process is an active entity, with a program counter specifying the next instruction to execute. Execution of a process must be sequential.

7 4 Speichermanagement Main-Memory Management: Program to be executed must be mapped to absolute addresses and loaded into memory. We have to keep several programs in memory. Many different memory-management schemes are available. Operating system is responsible for: - keeping track of which parts of memory are currently being used and by whom - deciding which processes are to be loaded into memory when memory space becomes available - allocating and deallocating memory space as needed - Memory Management: Paging - Virtual Memory 7

Operating system is responsible for: - keeping track of which parts of memory are currently being used and by whom - deciding which

8 5 Konsole Command-Interpreter System: Many commands are given to the operating system by control statements. When a new job is started in a batch system, or when a user logs on to a time-shared system, a program that reads and interprets control statements is executed automatically. - Shell 8

When a new job is started in a batch system, or when a user logs on to a

9 6 Treiber I/O-System Management: Operating system is responsible for: - a memorymanagement component that includes buffering, caching and spooling - a general device-driver interface - drivers for specific hardware devices 9

includes buffering, caching and spooling - a general

10 7 Dateisystem File Management: Operating system abstracts from the physical properties of its storage device to define a logical storage unit, the file. Files represent programs and data. Operating system is responsible for: - creating and deleting files - creating and deleting directories - supporting primitives for manipulating files and directories - mapping files onto secondary storage - backing up files on stable (nonvolatile) storage media - File-System - Directory Implementation: Linear list of file names with pointers to the data blocks (files) 10

Operating system is responsible for: - creating and deleting files - creating and deleting directories - supporting primitives for

11 8 System Calls System Calls: Summary of the types of system calls normally provided by an operating system: - Process control: - end, abort - load, execute - create process, terminate process - get process attributes, set process attributes - wait for time - wait event, signal event - allocate and free memory - File management: - create file, delete file - open, close - read, write, reposition - get file attributes, set file attributes - Device management: - request device, release device - read, write, reposition - get device attributes, set device attributes - logically attach or detach devices - Information maintenance: - get time or date, set time or date - get system data, set system data - get process, file, or device attributes - set process, file, or device attributes - Communications: - create, delete communication connection - send, receive messages - transfer status information - attach or detach remote devices 11

- get file attributes, set file attributes - Device management: - request device, release device - read, write, reposition - get device attributes, set device attributes - logically attach or detach

12 9 Kernel Monolithic kernel: - provide the most functionality int he least space (because of the limited hardware on which it runs), so it is not divided into modules carefully) - even in monolithic systems it is possible to have some structure. The services (system calls) provided by the operating system are requested by putting the parameters in a well-defined place (e.g. the stack) and then executing a trap instruction. This instruction switches the machine from user mode to kernel mode and transfers control to the operating system. The OS then fetches the parameters and determines which system call is to be carried out. After that it indexes into a table that contains in slot k a pointer to the procedure that carries out system call k. Basic structure for the operating system: - A main program that invokes the requested service procedure - A set of service procedures that carry out the system calls - A set of utility procedures that help the service procedures 12

This instruction switches the machine from user mode to kernel mode and transfers control to the operating system.

13 10 Sicherheit 13

Ähnliche Dokumente

NEWSLETTER. FileDirector Version 2.5 Novelties. Filing system designer. Filing system in WinClient

NEWSLETTER. FileDirector Version 2.5 Novelties. Filing system designer. Filing system in WinClient Filing system designer FileDirector Version 2.5 Novelties FileDirector offers an easy way to design the filing system in WinClient. The filing system provides an Explorer-like structure in WinClient. The