Technical student analysis of an operating system project

IT 600 Final Project Milestone One Guidelines and Rubric Overview: For the final project, you will evaluate a fictitious organization and develop a set of operating system requirements and a comprehensive recommendation for that organization. The goal is to leverage the cumulative knowledge you acquire in each module of this course to map operating system components to organizational challenges. Each module will have a conceptual base. You will then complete a hands-on lab by leveraging the workstation you are using to take this course. Later, you can apply the knowledge of the specific operating system commands in those labs to write about how the commands would be applied in a real-world analysis of an operating system’s capabilities. Review the Top Secret, Inc. scenario below carefully to understand the nature of the problem. They make a fine product, yet they cannot use it effectively to run their own operation. Consider the differences between a simple single-purpose operating system and a general-purpose operating system and how the concepts you are learning in this course can help Top Secret, Inc. find a solution. Scenario: Top Secret, Inc. (TSI) is a successful operating system company whose customers include Fortune 500 companies, governments throughout the world, and major U.S. contractors. TSI makes embedded operating systems for secure terminals that control ingress/egress control systems for Wall Street firms, camera systems for drone aircraft for government contractors, and alarm systems for top-secret government installations. TSI operating systems are worldrenowned for their quick response to sensor input, highly reliable operation, limited memory utilization, small size on disk, and low power consumption. The TSI Operating System (TSI OS) works exceptionally well on the devices owned by TSI customers, but it does not work well in the TSI back office. Like many startup companies, TSI had to cut costs when it launched a few years ago. To save money, the company decided not to use enterprise-class operating systems for its own workstations and servers. Instead, it chose to use a single-purpose TSI OS, reasoning that TSI OS was good enough for TSI customers, so it should be good enough for TSI. Unfortunately, TSI OS lacks many features of a modern operating system and does not take advantage of the architectural optimizations present in the latest hardware. Below is a matrix of general purpose operating system (GPOS) features and how they map to TSI OS: GPOS Feature TSI OS Support for GPOS Feature Multiprogramming TSI OS does not support more than one program running at a time. TSI customers need one program resident, and that is the program that handles sensor input and (e.g., from cameras and motion sensors). A backoffice operating system requires preemptive multitasking and advanced scheduling features. Multiprocessing TSI OS does not support more than one processor on a physical device. The operating system locks up when interrupts are generated by a second processor. Since most processors on the market are multicore, TSI has to purchase old, decommissioned hardware with single-core processors for its data center.