Wednesday, May 17, 2017

The issue of rising prescription drug costs has garnered a significant amount of discourse in recent years

The issue of rising prescription drug costs has garnered a significant amount of discourse in recent years. The Medicare Prescription Drug Improvement and Modernization Act (Medicare Part D) established a prescription drug program for Medicare and provided drug coverage for Medicare enrollees. The Act expressly prohibited Medicare from negotiating drug prices with pharmaceutical companies. The lack of negotiations between Medicare and the pharmaceutical companies has been cited as a major factor in the increased costs of prescription drugs for Medicare enrollees.
Formulate an argument where you either support or challenge the effectiveness of allowing price negotiations between Medicare and drug manufacturers in order to reduce overall costs. Justify your response.
Posted by at No comments:

In 1999, the Institute of Medicine (IOM) published a scathing report on medical errors

In 1999, the Institute of Medicine (IOM) published a scathing report on medical errors, indicating that up to 98,000 people die each year because of preventable errors in hospitals. The IOM’s report has been followed up by subsequent reports with increasing numbers of preventable errors causing deaths in U.S. hospitals.
Go to the Hospital Safety Score website at www.hospitalsafetyscore.org, and select two (2) facilities of your choosing. Next, interpret the results and compare the safety scores between the two (2) facilities. Suggest a strategy for improving one (1) of the facility’s safety scores, and then examine the effect that the safety score has on consumer perception of quality.
Posted by at No comments:

Monday, May 15, 2017

Byrne Limited is an Australian company. Directors have formed a view on a number of issues require clarification

Extra information 
RESEARCH CASE STUDY – BYRNE LIMITED 
Background 
Byrne Limited is an Australian company. Directors have formed a view on a number of issues require clarification. The views of directors may not be in compliance with a specific Australian Accounting Standard (AASB), Corporations Act 2001, and relevant websites. This will mean that the company financial statements will not provide a true and fair view, which is contrary to the Corporations Act 2001. 
CASE STUDY 
This research question consists of a case study: You are a graduate accountant who has completed your Bachelor of Business Studies at the Peter Faber Business School ACU. You are now working for Baxter and Associates a public accounting firm. The address of the firm is 12 Eagle Street, Brisbane Qld 4000. 
The manager of your accounting practice, Ms. Pippa Baxter has asked you to draft a letter in response to an email received from a client – Mr Bastin Byrne, the managing director of Byrne Ltd, raising number of issues regarding his company – see the copy of the email on the following page. 
Thank you for your telephone call this morning, as agreed I am emailing you regarding five (5) accounting issues we briefly discussed. By the way to assist the accounting team in our discussion – making process could you please make sure you reference any relevant sources relating to your advice, for example, AASBs, Corporations Act 2001, and relevant websites. 
Q.1 At our recent board meeting, Ambrose a director of our company suggested that we no longer need to show our non-current assets at their cost value in the balance sheet. Is this correct? Could you please outline our options? Would you advise us to show all our assets at cost value, fair value, or market value or just increase those assets that have appreciated in the market? 
Q.2 The board is also concerned with the frequent variances in the amount of warranty expenses that were initially recognised compared to the actual cost of the warranty the company paid/incurred to fix/replace the faulty products. Therefore at the most recent board meeting it was agreed to stop recognising the warranty expenses before the warranty cost is actually incurred. The directors are wandering why we should complicate a very simple way of calculating warranty expenses – why not “stick with” recognising the expense when we pay for it. This way we won’t have to deal with all these variances. What do you think we should do and why?
Posted by at No comments:

Richard Turpin Managing Director, Company Founder

1. Develop a Project scope document 
Using the Signed, Sealed, Delivered Case Study provided, develop a system scope document. This document must include a section for each of the following: 
• the business problem, 
• a statement of purpose, 
• the benefits of a new system 
• the system capabilities and what it must achieve as a minimum 
• exclusions – what the proposed system will NOT include 
Ensure you use business language and write in the third person (avoid the use of I or we). This section should comprise four or more paragraphs but should be no longer than a page in length. All bullet lists must be introduced with at least one sentence that provides context for the reader. 
Signed Sealed Delivered Case Study 
Notes from an interview with Richard Turpin Managing Director, Company Founder: 
As an employee of a large international courier and shipping service, I met almost every day with many companies that shipped and received packages. I was frequently asked if the company I worked for could deliver local packages on the same day. Over several months, I observed that there appeared to be a substantial need for courier services in the city I lived in so I decided I would form my own courier delivery company called Signed, Sealed, Delivered to fill this gap in the market. 
I began by listing my mobile telephone number in the Yellow Pages and sending letters to all those companies that had requested same-day courier service that my previous employer had not been able to serve. I hoped that, through good service and word-of-mouth advertising, my own business would grow. I also began other advertising and marketing activities to promote my new services. 
At first, I received delivery requests on his business mobile phone. However, it was not long before my customers were asking if I had a Web site where they could place orders for shipments. I knew that if I could get a Web presence I could increase exposure and help the business grow. 
After I had been in business only a few short months, I discovered I needed to have additional help. I hired another person to help with the delivery and pickup of packages. It was good to see the business grow, but another person added to the complexity of coordinating pickups and deliveries. With the addition of a new person, I could no longer -warehouse- the packages out of his delivery van. I now needed a central warehouse where I could organize and distribute packages for delivery. I thought that if his business grew enough to add one more delivery person I would also need someone at the warehouse to coordinate the arrival and distribution of all the packages. 
. 
The details of the package pickup and delivery process are described on the following pages: 
When I got an order, at first, only on my phone, I recorded when I received the call and when the shipment would be ready for pickup. Sometimes, customers wanted immediate pickup; sometimes, they were calling to schedule a later time in the day for pickup. 
Once I arrived at the pickup location, I collected the packages. It was not uncommon for the customer to have several packages for delivery. In addition to the name and address of the delivery location, I also recorded the time of pickup. I noted the desired delivery time, the location of the delivery, and the weight of the package to determine the courier cost. When I picked up the package, I printed out a label with his portable printer that I kept in the delivery van. 
At first, I required customers to pay at the time of pickup, but I soon discovered that there were some regular customers who preferred to receive a monthly bill for all their shipments. I wanted to be able to accommodate those customers. Bills were due and payable upon receipt. 
To help keep track of all the packages,I decided that I needed to scan each package as it was sorted in the warehouse. This would enable me to keep good control of his packages and avoid loss or delays. 
The delivery of a package was fairly simple. Upon delivery, I would record information about when the delivery was made and who received it. Because some of the packages were valuable, it was necessary in those instances to have someone sign for the package. 
Signed, Sealed, Delivered courier services grew and changed over the years. At first, I received requests for package pickups on my mobile phone, recorded that information in a log, and would then drive around to retrieve all the packages later in the day. 
However, I soon discovered that with another driver, it was difficult to coordinate pickups between the two of us from the van. It was not long before I reorganized the business and turned the warehouse employee into a driver. Then, I stayed in. the warehouse myself, and my two employees made all the pickups and deliveries. 
This worked well because I could control and coordinate the pickups and deliveries better. It was also easiest for me to receive pickup requests working at a desk rather than trying to do it while driving a delivery van. 
As I thought about how the business was growing and the services I provided to my customers, I began to itemize the kinds of information I would need to maintain. Of course, I needed to maintain information about customers. Some customers were businesses; some were individuals. I needed to have basic address and contact information for every customer. 
Also, for corporate customers, I needed to identify a primary contact person. It was mostly corporate customers who wanted to receive monthly statements listing all their shipments during the month and the total cost. I needed to distinguish which customers paid cash and which wanted monthly statements. In fact, for those that paid monthly, I needed to keep a running account of such things as when they were last billed, when they paid, and any outstanding balances. 
Finally, when payments were received, either for individual shipments or from monthly invoices, I needed to record information about the payment: type of payment, date, and amount. Although this was not a sophisticated billing and payment system, I thought it would suffice for our needs. 
Next, I started thinking about his packages and shipments. At the time that a request for a pickup came in, I needed to keep track of it as some type of delivery request or delivery ·order. At that point in time, I mostly needed to know who the customer was, where the pickup location was, and what date and time the package(s) would be ready for pickup. I also recorded the date and time that I received the order. A delivery order was considered -open- until the delivery van arrived at the pickup location and the packages were all retrieved. At that point, the delivery order was satisfied. 
Once the packages were retrieved, each package needed to be uniquely identified; I needed to know when it was picked up and which delivery person picked it up. Other important information was the -deliver to- entity name and the address. I also needed to identify the type of delivery. Some packages were high priority, requiring same-day delivery, others were overnight. Of course, the weight and cost were recorded so the customer could either pay or have it added to the monthly invoice. 
In the courier and delivery business, one of the most important information requirements is the date and time stamp. For each package, it is important to know when it was picked up, when it arrived at the warehouse, when it went back out on the delivery run, and when it was delivered. When possible, it is also important to have names associated with each of these events. 
As Signed, Sealed, Delivered Courier Services continues to grow, I anticipate that I can provide much better services to our customers if I utilize some of the technology that is currently available. For example, it will allow us to maintain frequent communication with the delivery trucks, which could save transportation and labour costs by making the pickup and delivery operations more efficient. This would allow us to serve our customers better. Of course, a more sophisticated system will be needed, but a development consultant has assured me that a straightforward and not too- complex solution can be developed. 
This is how I would like the business to operate. Each truck will have a morning and afternoon delivery and pickup run. Each driver will have a portable digital device with a touch screen. The driver will be able to view his or her scheduled pickups and deliveries for that run. However, because the trucks will maintain frequent contact with the home office via telephony Internet access, the pickup/delivery schedule can be updated in real time-even during a run. Rather than maintain constant contact, I believe it will be sufficient if the digital device synchronizes with the home office whenever a pickup or delivery is made. At those points in time, the route schedule can be updated with appropriate information. 
With the current system, customers have been able to either call the company and request a package pickup or visit the company's Web site to schedule a pickup. Once customers log in, they can go to a Web page that allows them to enter information about each package, including -deliver to- addresses, size and weight category information, and type of service requested. Signed, Sealed, Delivered provided -three hour,- -same day- and 
-overnight- services. To facilitate customer self-service, Signed, Sealed, Delivered haven’t required exact weights and sizes, but there are predefined size and weight categories from which the customer can choose. 
Once the customer has entered the information for all the packages, the system would calculate the cost and then print mailing labels and receipts. Depending on the type of service requested and the proximity of a delivery truck, the system would schedule an immediate pickup or one for later that day. It would display this information so the customer would immediately know when to expect the pickup. 
Picking up packages is a fairly straightforward process, but there was some variation in what would happen depending on what information was in the system and whether the packages were already labelled. Upon arriving at the scheduled pickup location, the driver would have the system display any package information available for this customer. If the system already had information on the packages, the driver would simply verify that the correct information was already in the system for the packages. The driver could also make such changes as correcting the address, deleting packages, or adding new packages. If this were a cash customer, the driver would collect any money and enter that into the system. Using a portable printer from the van, the driver could print a receipt for the customer as necessary. If there were new packages that weren't in the system, the driver would enter the required information and also print mailing labels with his portable printer. 
One other service that customers have required was to be able to track the delivery status of their packages. The system needed to track the status of a package from the first time it -knew- about the package until it was delivered. Such statuses as -ready for pickup,- 
-picked up,- -arrived at warehouse,- -out for delivery,- and -delivered- were important. Usually, a package would follow through all the statuses, but due to the sophistication of the scheduling and delivery algorithm, a package would sometimes be picked up and delivered on the same delivery run. We also decided to add a status of -cancelled- for those packages that were scheduled to be picked up but ended up not being sent. 
Marking Criteria 
ASSESSMENT 1 CRITERIA 
N/A Poor Fair Good Very Good Excellent 
Scope 
Document Statement of Purpose (1) 
Business problem (2) 
Business Benefits (2) 
System capabilities (2) 
Exclusions (1) 
Document Format Document Presentation Good layout, grammar & spelling (2). 
Deduction for late, copied, or plagiarised work (up to total marks earned) 
Total out of 10
Posted by at No comments:

investigate mortality levels of children, infants and babies around the world

Theme: Child Mortality 
Your task is to investigate mortality levels of children, infants and babies around the world. Which countries have a high rate of child deaths and which countries have low rates? Are there connections between child mortality rates and the income levels of the country, or the region where they are situated? Are the child mortality rates improving in recent years or getting worse? Reduction of child mortality was Goal 4 of the United Nations' Millennium Development Goals (2000-2015): 
• http://www.un.org/millenniumgoals/ 
• http://www.un.org/millenniumgoals/childhealth.shtml 
The data you will need is available from WHO: The World Health Organisation. 
The two files you need to download are available from these web pages (or can be downloaded from the ICT702 Blackboard page): 
• child mortality data from: http://apps.who.int/gho/data/view.main.182?lang=en. (Download COMPLETE Data as CSV Dataset). 
• country metadata from: http://apps.who.int/gho/data/node.metadata.COUNTRY?lang=en. (To get all the data you need, you must download the JSON version of this file, or the CSV XMART version). 
Learning Objectives 
In this task you will learn how to: 
• Apply relevant Python programming concepts to a data analysis challenge 
• Read data from real sources and wrangle it into the form you need. 
• Develop creative approaches to solving the wrangling/analysis problems. 
• Adhere to the recommended Python programming styles 
• Write programs that produce correct and useful output 
• Organise and present a data analysis report 
• Give an insightful analysis of the given problem. 
Task 2 is broken into two parts (each worth 20% of the course): 
1. Due Week 9. Use Python to read and analyse the child mortality data and generate various useful graphs that give insight into the trends. 
2. Due Week 12. Use Python to combine the child mortality data and the country metadata, to give higher-level analyses of child mortality in relation to income grouping and regions of the world. 
1 Child Mortality 
In this first part of Task 2, you should write a Python script that reads and analyses the child mortality data file (WHOSIS_MDG_000003.csv) and produce at least FIVE useful graphs that give insight into the data trends. 
For example, here are some suggestions: 
• show the change in child/infant/neonatal mortality over the period 1990 to 2015 for several representative countries. 
• compare the mortality rates of all countries in a given year. 
• compare the improvement in mortality rates over the 1990/2015 period - that is, one divided by the other. 
• compare child mortality against infant mortality and neonatal mortality to see what is the relationship between them. 
Hints: 
1. Some of the columns contain multiple values (a mortality rate, plus a confidence interval), so you will need to split these up into seperate columns. 
2. You can either use standard Python data structures to store and manipulate the data, or use the Pandas library if you prefer. 
3. Use markup and headings to break your Jupyter notebook into sections and give commentary about what you doing, and discussion of your results. This Jupyter notebook will be what you submit. 

2 Child Mortality and Country Types 
In this second part of Task 2, you should write another Python script that reads and analyses the country metadata (COUNTRY.json) and merges it with the child mortality data from Part 1, to allow you to do some higher-level analysis of child mortality trends. 
Your report should include at least two graphs that display or compare child/infant/neonatal mortality in different regions of the world (using the 'WHO_REGION' string to group the countries). 
You report should include at least two graphs that compare child/infant/neonatal mortality across different income groupings (using the 'WORLD_BANK_INCOME_GROUP' string to classify the countries). 
Hints: 
1. You can use the 'json' library to read the .json file. The resulting object is quite deeply nested, so you will need to explore which substructures contain the data that you want, and then extract that substructure into a dictionary or list that is easier to use. Or write a function that extracts the data that you need. 
2. You can either use standard Python data structures to store and manipulate the data, or use the Pandas library if you prefer. 
3. Use markup and headings to break your Jupyter notebook into sections and give commentary about what you doing, and discussion of your results. This Jupyter notebook will be what you submit. 
3 Marking Criteria 
Your submission for each part of this task will be assessed according to the following criteria: 
• Presentation and organisation of your report [25%] 
• Program output [25%] 
o Correctness of the program output 
o Insightful analysis and discussion of the given problem 
• Programming style [50%] 
o Creative approaches to solving the problem 
o Good use of relevant programming concepts, especially good use of functions 
o Good use of appropriate Python data structures, such as lists and dictionaries 
o Adherence to the recommended Python programming styles (indentation, documentation, naming conventions, etc.)
Posted by at No comments:

Specification of a System - Wheat Truck Control System (WTC)

Software Engineering Methodologies 
Assignment 2 Group Assignment - (Groups of 2- 3) 
Specification of a System - Wheat Truck Control System (WTC) 
Overview 
As a Software Engineering consultant, your task is to develop a formal specification in Z for the proposed system described below. You will present your work to show that your system does work and answer questions about the system specification your group has developed. 
Timelines and Expectations 
Percentage Value of Task: 20% 
Minimum time expectation: 10 hours 
Learning Outcomes Assessed 
S1. Critically analyse and use complex decision making to research and determine the appropriate Software Engineering tools and methodologies to utilize in a given situation. 
S2. Apply professional communication skills to support and manage the engineering of a large software system. 
S3. Review, critically analyse and develop artefacts to define processes for quality assurance, risk management and communication in large software development projects. 
S4. Implement quality assurance activities in order to verify user requirements and validate design decisions. 
A1. Analysis of a large system development problem to decide upon the best methodological approach. 
A2. Development of appropriate artefacts to support and manage the software engineering process such as change control and configuration management. 
H7410 Assig 2 Sem 1 2017 
Assessment Details 
A new computerized system is to be developed for the storage and handling of accounts for wheat farmers and truck deliveries to Mahsroh Wheat Board silos. Detailed below are the major objects to be considered in the system: silos, ships, trucks and farmers. This system could be quite complicated. However, to simplify the system for this assignment we will be content to include the following in our proposed system: 
Silos 
The Board currently has ten (10) wheat silos around the country but the system must be written to seamlessly handle at least twice that number. Each silo has a unique name and storage capacity (in tonnes) that must be stored in the proposed system. In addition the system must maintain the current amount of wheat stored in the silo. Obviously when the silo is full no further deliveries of wheat can be made to that silo before some is offloaded onto a ship for export overseas. Similarly a silo cannot off-load more wheat onto a ship than is currently stored. We will assume that when off-loading to a ship, no trucks can unload due to operational and safety considerations. Only one ship can be handled at a time at each silo. 
We will assume that only one truck can unload into a particular silo at any one time. 
Therefore during busy times each silo also maintains a queue of trucks waiting to unload. Trucks should only be entered into the waiting queue when there is sufficient room for the wheat that the truck holds, i.e. you need to know that the current storage plus all the loads currently in the queue will not exceed the silos capacity. 
Ships 
The system will keep a record of all ships that have been registered to transport wheat overseas for the Wheat Board. The ships name, nationality and capacity (in tonnes) will be stored. The ship's captain can specify the amount of wheat to be off-loaded into the ship as long as it is less than the ships capacity and also the silos current amount in storage. The system will keep a record of the amount of wheat off-loaded to the ship and adjust the current storage appropriately. 
Trucks 
As each loaded truck arrives at the silo, it is weighed to ascertain the amount of wheat in the truck. The system maintains a list of registered trucks and their empty weight (in tonnes). Therefore, a single weighing is sufficient to determine the wheat load. If there is sufficient room in the silo then the wheat is off-loaded into the silo and a record is kept of the amount off-loaded against both the truck registration number and the farmer providing the wheat. 
Date and Time 
Normally we would maintain the date and time of each operation (truck delivery or ship offloading) however to simplify this assignment we will ignore those aspects. Instead, we will keep a sequential count of each operation for each silo. Therefore, we will have a history of the order of truck unloading and ship off-loading operations that take place for each silo. 
The system would be able to say for example, that silo HORSHAM_1, operation number 999 involved 25 tonne of wheat delivered by the truck registered TONKA owned by Jack Black from farmer Bob Smith. Then operation 1000 was an off-loading operation of 125,000 tonnes to the ship -Southern Aurora-. 
There is also a need to keep track of the operation order between silos, therefore we will keep a global sequential count of the operations at silos as well. Refer to the table below as an example: 
You will need to decide how to demonstrate that your system specification works and satisfies the client requirements. (You might wish to discuss your approach with your tutor.) 
General Comments 
The submission must be presented in a professional, clear and concise manner. If you need further system information please use your initiative and make reasonable and logical assumptions. Questions of a general nature (for example to clarify some part of the assignment requirements) can also be sent to the discussion forums, note these should not in any way give solutions or parts thereof. Similarly you are encouraged to ask questions about the Z specification language, it is not simple and no students will have encountered it before. 
Requirements: 
Z Schema Operations 
You are to create a Z schema that adequately describes the WTC system. It should include at least one state space and the following operations: 
• An initialization operation called Init. 
• An operation Enter_new_silo that an operator uses to enter the details of a new silo into the system. Assume the new silo is currently empty. 
• An operation Accept_delivery that an operator uses to signal the system to begin offloading x tonne of wheat from a truck. Note that the system must do a check to see if that storage capacity is available in the silo, if not then an error message must be output and no truck unloading done. Additional information needed by this routine is the truck registration and the farmer’s name. If successful this operation stores all necessary details into the system for that delivery. If a truck is already unloading then this new truck will be placed in a queue waiting for its turn to unload. 
• An operation Leave_queue. This operation is run by the system operator each time there is a queue for a silo and the driver of a specified truck decides that the anticipated waiting time is too long and leaves the queue. The operation outputs to the operator the list of trucks in the queue after the specified truck is removed or if none in the queue a reasonable error message. 
• An operation Silo_account that outputs the total amount of wheat in tonnes delivered to a particular silo by ALL farmers in a specified time period (note that means between two global operations numbers in our simplified system). In other words between global operations 10000 and 10500 for example. 
• An operation Ships_total_account that outputs the total amount of wheat that a particular ship has taken from ALL silos in the total history of the system. 
• An operation Farmers_account that outputs the total amount of wheat delivered to ALL silos in between two specified global operation numbers (e.g. 10000 and 10500). 
You should provide robust versions of each operation that are capable of handling any possible error conditions. For example, if the ship or truck is not correctly registered in the system an appropriate error message must be given. 
The submissions will be considered for presentation, conciseness and correctness (both logically and notationally). Versions of the operations that are developed using the Z Schema Calculus will be more highly considered than monolithic versions that account for all conditions within a single schema. 
You should also add a narrative in the report to explain any schemas or logic that you have used. Schemas should be annotated. Authorship should be made clear. 
You will be asked to explain and answer questions about your work in a presentation - which will be scheduled at a suitable time – in either labs or lecture. 
Submission 
Your assignment should be completed according to the Guides to your assessments 
https://federation.edu.au/__data/assets/pdf_file/0018/190044/General-Guide-to-Writing-and-Study-Skills.pdf 
Using the link provided in Moodle, please upload the following in one zip file as directed by your lecturer. 
Name your zip file in the following manner: 
GivenName_FAMILY-NAME _ ID .zip e.g. Aravind_ADIGA_30301234.zip 
The assignment must be submitted electronically through the Moodle assignment system in Microsoft Word document format, rtf format or as a pdf document. If you are unable to provide one of these formats please contact your lecturer/tutor by email prior to submission to ensure that they will be able to handle the alternative format. 
To alleviate any problems with fonts and symbols for the Z specification all students must use the 
Zed true type font that is available on Moodle. Note this zip file has both true type and Adobe Type Manager files for both Windows and Macintosh machines. Please make sure you use the true type font. The archive contains a Readme.txt file that explains how to install the font. 
Feedback 
Assessment marks will be made available in fdlMarks, feedback to individual students will be provided via Moodle or as direct feedback during your tutorial class 
Plagiarism: 
Plagiarism is the presentation of the expressed thought or work of another person as though it is one's own without properly acknowledging that person. You must not allow other students to copy your work and must take care to safeguard against this happening. More information about the plagiarism policy and procedure for the university can be found at: 
http://federation.edu.au/students/learning-and-study/online-help-with/plagiarism 
Your support material must be compiled from reliable sources such as the academic resources in 
Federation University library which might include, but not limited to: the main library collection, library databases and the BONUS+ collection as well as any reputable online resources (you should confirm this with your tutor). 
Federation University General Guide to Referencing: 
The University has published a style guide to help students correctly reference and cite information they use in assignments. A copy of the University’s citation guides can be found on the university’s web site. It is imperative that students cite all sources of information. The General Guide to Referencing can be purchased from the University bookshop or accessed online at: 
http://federation.edu.au/library/resources/referencing 
Suggested References: 
Weeks 4 and 5 study materials and Section 4 of study Guide 3 
The Z Notation: A Reference Manual http://www.rose-hulman.edu/class/cs/cs415/zrm.pdf 
Using Z http://www.comlab.ox.ac.uk/igdp/usingz 
Sections 21.5, 21.6 and 21.7 from Pressman 7th Ed. 
Solutions for Problem 2 of Week 6 tutorial problems 
Introduction to Z Notation - http://www.youtube.com/watch?v=qfEe9luJmVE 
Marking Criteria 
Group Name: __________________ 
Student ID: Student name: 
other members in the group 
Student ID: Student name: 
Student ID: Student name: 
Task Mark 
Z Schema Operations Init 
Enter_new_silo_account 
Schema = 4 marks 
Concise & correct Accept_delivery 
Notation & logic correct 
Leave_queue 
Schema Annotations = 4 marks Silo_account 
Relevant, concise & clear 
Ships_total_account 
Farmers_account 8 
8 
8 
8 
8 
8 
8 
1. Evidence that system works correctly – included in report 14 
2. Report – adheres to the FedUni guidelines for the presentation of academic work 10 
3. Presentation – discuss your contribution – development & testing, answer questions about the system 20 
Total 100 
Final /20 
Comments
Posted by at No comments:
Subscribe to: Posts (Atom)