Abstract Data Types Implementation & Design

_**Abstract data type implementation **__**Problem:**_ abstract data type PrintJob describes a print request in an operating system pmt queue which = PrintQueue. Print requests are generated by system clients & result in the creation of a PrintJob entity which is appended to a single system PrintQueue. Special priority print requests are inserted directly into position two of the print queue if it is not empty, otherwise at the front of the queue. During a normal working day, around 1% of jobs derive from priority requests. Jobs are serviced, & subsequently removed from the print queue by a single printer process which outputs the ftle identified by the print job at the front of the print queue, before deleting the now completed job & proceeding to the next job in the queue. If the queue is empty, the printer process sleeps for 5 seconds before inspecting the queue again. Print queue receives a max. of 10,000 print jobs & inspection of the queue normally reveals between 10 & 30 jobs awaiting service. A re-engineering of the printer accounting system now requires consideration of the implementation approach to be adopted for PrintJob and PrintQueue. **_Required: _**To consider and discuss static & dynamic approaches to the implementation of PrintJob and PrintQueue. Your discussion should address both space & process issues and seek to derive some comparative numerical measures of the differences between two identified approaches to implementation (one static, one dynamic). **_Abstract data type Design Problem: _**A computer-application is being proposed which will allow on-line presentation of programme structures & interactive management of course design. As a prelude to the development of this application a domain analysis of the thematic curriculum model problem space is required, together with an illustration of the way in which data abstraction could support modeling of this problem domain. **_Required: _**i. a domain analysis of the thematic curriculum model problem domain; ii. a short discussion of what you perceive is rewaled by your analysis; iii. specification; for two prime candidate abstract data types which derive from the findings of your domain analysis. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform Printing under any Windows system (95, 98, ME, XP etc...) The way in which the Operating system performs and handles the day to day printing requests.