Académique Documents
Professionnel Documents
Culture Documents
1.0
Page 1 of 5
COURSEWORK TITLE
DELIVERY MANAGEMENT SYSTEM (DMS)
2.0
3.0
4.0
5.0
LEARNING OUTCOMES
At the end of this coursework, you should be able to:
-
TYPE
-
Level 2
Individual Assignment
2015
6.0
Page 2 of 5
COURSEWORK DESCRIPTION
DMS supports primarily package delivery services. Delivery package shall be selected by
the customers (usually members), assuming that there are several delivery packages at
different rates and delivery loads (Basic, Premium and Gold). In addition to delivery
package, customers or walk-in customers can also send the parcels at standard rate.
The delivery orders will be placed by the members or walk-in customers so that the delivery
management takes place. These orders can be known as standing orders will then be
managed by the end-users. Furthermore, the standing orders can be modified or place onhold from time to time or ready to deliver in accordance to destination addresses. In this
process, an invoice will be generated and stored in storage space.
In respect of payment, the customers can make payment periodically to the delivery
company and the payment is recorded. The customers information are maintainable
whereby personal contacts, billing information, current standing orders and delivery history
including modified or skipped deliveries. The DMS is expected to produce useful reports
for future decision making.
There are THREE (3) user roles: administrator, end-users and general manager.
Administrator is the system user which has full access control throughout the DMS
including administrative control panel, the control panel is an administrative page which
provides general settings before the program is in-use. End-users can be of clerk,
receptionist, operator, etc whoever the program designed for. These users are having
privilege access to the Standing Order Delivery, Customer Management, Payment, and
Invoice Generation features only. General Manager has full access control throughout the
DMS excluding administrative control panel.
Note: You are required to implement an access control for authentication and authorisation
of the system functions according to the user roles.
Level 2
2015
7.0
Page 3 of 5
GENERAL REQUIREMENTS
The program you submitted should be executed without errors and validation should be
done for each entry from the users to avoid logical errors. The implementation code must
highlight the use of object oriented programming concepts as required by the solution.
Besides, all the data that is added and edited must be saved in a data storage facility (either
textfile or database system). This is to make sure that the information can be retrieved when
the system is exited.
8.0
DELIVERABLES:
-
The Delivery Management System with completed source code must be submitted in the
form of a CD-ROM.
8.1
The completed application of the system as well as the softcopy of the report
must be saved in a CD-ROM.
8.2
As part of the assessment, you must submit the project report in printed and
softcopy form, which should follow the following format:
A) Cover Page:
All reports must be prepared with a front cover. A protective transparent
plastic sheet can be placed in front of the report to protect the front cover.
The front cover should be printed with the following details:
Module
Coursework Title
Intake
Student name and id
Date Assigned (the date the assignment details were handed out).
Date Completed (the date the report is due to be handed in).
Level 2
2015
Page 4 of 5
B) Contents:
Description and justification of the design involving use case modeling,
activity diagram, analysis and design class diagram;
The implementation codes which illustrate the object oriented
programming concepts incorporated into the solution.
Any additional functions.
C) Conclusion
The font used in the report must be 12pt Times New Roman. Do not include
full source code in the report. The report must be typed and clearly printed.
D) References
You may look for algorithms and information from the Internet or books.
Proper referencing of the resources should be provided.
All references must be made using the Harvard Naming Convention as
shown below:
The theory was first propounded in 1970 (Larsen, A.E. 1971), but since
then has been refuted; M.K. Larsen (1983) is among those most
energetic in their opposition.
/**
* Following source code obtained from (Danang, S.N. 2002)
*/
int noshape=2;
noshape=GetShape();
Level 2
2015
9.0
Page 5 of 5
ASSESSMENT CRITERIA
The assignment assessment consists of three components: Program Solution &
Documentation (60%), Research Report (30%), and Presentation (10%). Details are as
follows:
Criteria
Marks
Allocated
Criteria:
Marks
Allocated
Requirement Analysis:
- Use case diagram
- Activity diagram
- Class diagram
30%
Report Structure:
Professional Report Format
References
10%
Implementation:
- Standing order delivery
and report
- Customer management
- Invoice and payment
30%
Program Documentation:
Object oriented implementation codes
and any additional functions
20%
Presentation (10%)
10.0
10%
DEVELOPMENT TOOLS
The program must be written in Java language. You can use any Java development IDE as a
tool.
11.0
ACADEMIC INTEGRITY
-
You are expected to maintain the utmost level of academic integrity during the duration
of the course.
Plagiarism is a serious offence and will be dealt with according to APU and
Staffordshire University regulations.
Level 2
2015