Create an inventory list• Insert the items when they arrive and delete when sold or damaged.• Location (shelf, warehouse, display etc) of the item to be displayed when requested.• For any product/s the inventory to be displayed.
Prepared by: Dr Nandini Sidnal Moderated by: Dr Ghassan Kbar Oct, 2018 Assessment Details and Submission Guidelines Unit Code MN404 – T2 2020 Unit Title Fundamentals of Operating Systems and Programming Assessment Type Individual Assignment Assessment Title Inventory Management Purpose of the assessment (with ULO Mapping) This assignment assesses the following Unit Learning Outcomes; students should be able to demonstrate their achievements in them: a. Describe the role of Operating Systems (OS) and its different subsystems in controlling computer hardware b. Demonstrate competency in the use of a command line interface to operate and perform simple OS administration c. Apply principles of abstraction and problem solving in an object-oriented programming language d. Apply knowledge of programming constructs in developing computer programs e. Create programs based on incremental development processes of designing, coding, testing and debugging. Weight 30% of the total assessments Total Marks 60 marks Due Date Week 10 laboratory class – To submit the video presentation of the algorithm. Week 11 laboratory class – To submit video of the program Demonstration along with the document Submission Guidelines • All work must be submitted on Moodle by the due date along with a title Page. • The assignment must be in MS Word format, 1.5 spacing, 11-pt Calibri (Body) font and 2.54 cm margins on all four sides of your page with appropriate section headings. • Reference sources must be cited in the text of the report, and listed appropriately at the end in a reference list using IEEE referencing style. Extension • If an extension of time to submit work is required, a Special Consideration Application must be submitted directly through AMS. You must submit this application within three working days of the assessment due date. Further information is available at: http://www.mit.edu.au/about-mit/institute-publications/policies-proceduresand-guidelines/specialconsiderationdeferment Academic Misconduct • Academic Misconduct is a serious offence. Depending on the seriousness of the case, penalties can vary from a written warning or zero marks to exclusion from the course or rescinding the degree. Students should make themselves familiar with the full policy and procedure available at: http://www.mit.edu.au/aboutmit/institute-publications/policies-procedures-and-guidelines/PlagiarismAcademic-Misconduct-Policy-Procedure. For further information, please refer to the Academic Integrity Section in your Unit Description. MN404 Fundamentals of Operating Systems and Programming Page 2 of 6 Prepared by: Dr Nandini Sidnal Moderated by: Dr Ajay Sharma July, 2020 Academic Integrity: For assignments, students are encouraged to consult each other, the lecturer, tutor or anyone else for that matter. However, the assistance offered or accepted should not go beyond a discussion of the problem and a sketch of a solution. But in your assignment, do not use any written material from the discussion/website/book. If you can reconstruct the discussion and complete the solution on your own, then you have learned the material (and that is the objective of this course!). Assignment 2 Specification With the development of this application and the course, it makes the students capable of applying knowledge of programming constructs in developing computer programs. The students shall learn to create programs based on incremental development processes of designing, coding, testing and debugging. Assignment description: Control and management of inventory are vital to most types of businesses but especially to supermarkets. In the past, hand-written accounts were kept of inventory coming in and stock being sold. Later, software packages became available to assist in inventory control although all data still needed to be entered manually into a computer. These days, control of inventory in supermarkets has become far more advanced with the use of digital technology integrated with software packages. This effectively and much more accurately manages and controls stock. In this assignment you have to develop a program based on incremental processes of collecting software requirements, designing, coding, testing and debugging to maintain the inventory of a super market for the managers. Inventory control is keeping a record of stock that comes into the store and stock that leaves the store. Following features of the inventory system are to be incorporated in the design and implementation. • The student shall develop the inventory for a grocery shop or any other shop of his/her interest. The number of items in the inventory list may be limited to max 10. • Inventory to account for the stock that is kept in the supermarket warehouse, on the floor, in display, damaged etc. and in other areas of the store. • Your code should also track on returns and update the stock. • Information like where in the supermarket the stock has been placed and the use of the item (is it for sale, display purposes or to replace a returned item?) is also to be recorded. • Every time an item is sold, the sale to be deducted from the inventory list. • In essence, your code should, be able to tell you how much inventory there is for any product at any given time. MN404 Fundamentals of Operating Systems and Programming Page 3 of 6 Prepared by: Dr Nandini Sidnal Moderated by: Dr Ajay Sharma July, 2020 In summary: The program must perform the following: • Create an inventory list • Insert the items when they arrive and delete when sold or damaged. • Location (shelf, warehouse, display etc) of the item to be displayed when requested. • For any product/s the inventory to be displayed. The assignment report has to include the following sections: • User Requirements: o Include all the user (assignment) requirements here. For example: Number of items the item names and existing stock • Analysis Analysis often requires the programmer to learn some things about the problem domain and that information the user will have to provide. Also, it should specify what the program is going to do. In this case the problem domain would be the logic used to maintain the inventory of the super market. • Design: The design phase has to describe how the program is going to do the desired task. This usually involves writing an algorithm or a flow chart in fact, algorithms are more often written in a somewhat stylized version of English called pseudocode. Although there are no precise rules governing the syntax of pseudocode, in your pseudocode you should strive to describe the essential elements of the program in a clear and concise manner. Note that this pseudocode closely resembles Python code, so the transition to the coding step should be straightforward. • Implementation Phase: In this phase the complete code in python without any syntax and semantic errors must be completed. The complete code with proper indentation has to be pasted here along with sample inputs and outputs. • Testing: Only thorough testing can build confidence that a program is working correctly. Testing is a deliberate process that requires some planning and discipline on the programmer’s part. Once all the errors are debugged, set of all possible inputs are to be provided. Even though the range of the input numbers on a computer is finite, testing all of the possible combinations of inputs would be impractical. So, the challenge is to find a smaller set of inputs, called a test suite, from which we can conclude that the program will likely be correct for all inputs. The number and type of input samples have to cover all possible cases of validity checks of the inventory. The difference between the opening and closing balance of the inventory has to match with the items sold on that day or items purchased to stock. MN404 Fundamentals of Operating Systems and Programming Page 4 of 6 Prepared by: Dr Nandini Sidnal Moderated by: Dr Ajay Sharma July, 2020 • A short video to be recorded explaining: o the logic of the algorithm o the code in detail o the test cases Submission Guidelines: Your assignment should be completed according to the General Guidelines for Presentation of academic work. Your submission should contain the following: I. The assignment Word file that will be submitted shall include: a) Link of the video to be included in the word document that has the following details: i) Explanation of the logic used in the algorithm to maintain the inventory on daily basis. ii) Explanation of the code and demonstration of the outputs obtained. iii) The time limit of the video is 5 min. b) Algorithm/flow chart c) Complete program in Python without syntax errors (cut and paste the complete code). d) Must include appropriate and sufficient comments in the source code. e) Screen shots of initial compilation results with syntax errors. f) Troubleshooting the syntax errors g) Sufficient screen shots showing all possible outputs obtained. The file name must have your student ID as part of its name. II. Documentation should follow the standard submission guidelines as below: i) Front page - indicating your name and student ID, teaching staff (Lecturer’s and tutor’s name), a statement of what has been completed and acknowledgement of the names of all assisted you. ii) List of references used (IEEE style) – Reference sources must be cited in the text of the report, and listed appropriately at the end in a reference list. Only IEEE referencing style is acceptable for this assignment. III. The assignment must be submitted using Moodle. The page numbers of the assignment must be clear on each page. The report document must be checked for similarity through Moodle/Turnitin while submitting it. Please refer to the study skills unit staff (CoL)if you need further assistance. MN404 Fundamentals of Operating Systems and Programming Page 5 of 6 Prepared by: Dr Nandini Sidnal Moderated by: Dr Ajay Sharma July, 2020 Marking Guide Sections to be included in the Assignment Description of the sections Marks allocated Submission Part A User requirements Assumptions if any Analysis Phase Design Phase Algorithm or Flowchart To cover all requirements mentioned in the assignment along with any relevant assumptions made 4 Marks 4 Marks 10 Marks Implementation Phase Program Testing Phase Link to 5 Min Video that explains the algorithm, code and demonstrates the program with good test cases Error free, well commented Python program for the algorithm without any discrepancy between the program and the algorithm. 10 Marks 5 Marks (Relevant and critical 5 test cases) 15 Marks References Minimum of 4 references used along with intext citation 2 Marks Total marks 50 Marks MN404 Fundamentals of Operating Systems and Programming Page 6 of 6 Prepared by: Dr Nandini Sidnal Moderated by: Dr Ajay Sharma July, 2020 Rubrics Tasks Excellent (HD) Very Good(D) Good ( C ) Satisfactory (P) Unsatisfactor y(F) User Requirements Has provided complete set of user requirements Has provided all of the user requirements Has provided most of the user requirements Has provided some user requirements Has not provided the requirements Analysis Phase (Analysis of the Problem domain, all possible inputs and outcomes of the program are identified and presented) Analysis is complete and optimal Analysis carried out is very good Analysis carried out is moderate Sufficient analysis is not carried out No analysis is carried out Design Phase (The algorithm /Flowchart) Logic used in the algorithm/flow chart with high degree of clarity. Considered all possible code flows. Optimal algorithm with all possible code flows are considered Very good logic and all required code flows are considered Good logic and some code flows are considered Some logic and few code flows are considered. Relevant Logic not considered. Algorithm/flow char presentation Video Excellent presentation Flawless Good presentation Moderate Ok No presentation Implementation Phase Perfect code with complete solution Good code with complete solution Good code but with not complete solution Poor coding and incomplete solution No solution provided. Testing All possible test cases considered. Unit and integrated test cases considered Most of the test cases considered. Integrated cases only Considered test cases are not adequate Few test cases are considered No test cases Demo Video Exceptional demonstratio n of the complete program logic and test cases Very good Demonstratio n of the complete program logic and test cases Good demonstratio n of the program with some test cases Poor presentation No presentation References Relevant and good references Good references Moderate references Few references No references