CS6004ES –Application Development

Individual Coursework –Main-Sit 2019

Introduction
This individual coursework requires developing and documenting a small application in C# using
an object-oriented approach and Visual Studio. Your software artifact must be submitted as a
Visual Studio project. It will be assessed using Visual Studio 2017 or any higher version and any
features not working with the standard installation of Visual Studio 2017 or any higher version
will not be assessed. The coursework carries 30% of the module mark.

Set:
Submission Deadlines: 11.55pm on 17th of February 2020
Coursework Submission in-class Demo: This individual coursework has 2 parts, both of the
soft copies which are to be submitted before 11.55pm on the 23rd of February 2020.
(1) The software application to be developed in C#
(2) The documentation in MS Word format.

Please note the rules on plagiarism.

The application should be implemented individually. This is not a group/team effort. Any
material which is a direct copy from someone else (student or other source) or a close
paraphrase/code must be indicated where it is quoted i.e. it must be made clear what material is a
quotation or close paraphrase e.g. by showing the text in italics or in quotation marks. It is not
sufficient to show the source in a list of references or bibliography. If you are unclear, please
discuss your examples with your seminar tutor or the module leader. Plagiarism is a serious
offence and conviction for plagiarism may lead to suspension from the University, even for a
first offence (please see the section on Academic Misconduct in the Student Handbook).
An inventory is basically a detailed list of all the items in stock. Inventory consists of raw
materials, work-in-process and finished goods. In today’s highly competitive market, businesses
need to maintain an appropriate level of stock to meet the customer demands at any time.
Inventory management is part of the supply chain management.

XYZ is a company who purchase and sell laptops and accessories across Sri Lanka. They decide
to develop centralized inventory management system based on OOP to handle their day-to-day
activities.

Task
1. Admin Login.
2. Only admin can be able to manage admin accounts (Add/Edit/Delete)
3. Manage product and categories.
4. Admin can able to manage the purchase of laptops and accessories.
5. Admin can able to manage sales of laptops and accessories.
6. Admin can be able to adjust the inventory.
7. All the activities should be recorded.
8. The system can able to generate multiple reports such as, purchase order, sales order and
top selling products.
9. Should include search options for the above tasks.
10. Dashboard (Total stock amount, Total purchase, Total sales and Total Profit

Marking Scheme for the CS6004ES Individual Coursework

This individual coursework is worth 30% of the module mark. The following are guidelines for
marking. Mark each item listed below on a scale of 0 to 5. Then multiply the mark by the
weighting indicated, sum it up and divide by 2 to get the final mark.
Mark Characterized By
0 No work or work totally irrelevant
1 Work started on right lines but no result
2 Some result, with major lack and/or errors
3 Acceptable result but incomplete, or some good result with minor
errors
4 Good result but can be further polished
5 Excellent result

Weight X
Item Weight Marks
Marks
IMPLIMENTATION
1 The application user interface 2 5 10
2 Data entry of class list from the database 2 5 10
3 Task 1 : Admin Login 2 5 10
4 Task 2 : Managing admin accounts 3 5 15
5 Task 3 : Managing products and categories. 4 5 20
6 Task 4 : Purchase management 2 5 10
7 Task 5 : Sales management 3 5 15
8 Task 6 : Adjust inventory 2 5 10
9 Task 7 : History of user activities 2 5 10
10 Task 8 : Reports 4 5 20
11 Task 9 : Search functions 2 5 10
12 Task 10 : Dashboard 2 5 10

DOCUMENTATION
1 Detailed instructions to run the program 1 5 5
2 Software architecture diagram 1 5 5
3 UML diagrams – A Use Case Diagram and a 1 5 5
comprehensive Class Diagram
4 Detailed testing evidence of your proposed 1 5 5
system
5 Reflection of your own experience 1 5 5
PROGRAMMING STYLE
1 Clarity of code which shows the underlying 1 5 5
algorithm
2 Sensible naming of programmer-defined 1 5 5
variables, classes, properties and methods
3 Useful comments in code 1 5 5
4 Data validation and exception handling 1 5 5
5 Interface design and usability of the system 1 5 5
Total 200/2