AAPP006-4-2-SDP

Project Specification

Page 1 of 4

Scenario
Online Dental Appointment Management System
Ora-Care is a dental clinic which is located at Bukit Jalil, Malaysia. Dr.Simmons is the owner
of the clinic, he provides various services such as cleaning, extracting, filling, crowning and so
on. Patients would nornally walked-in and wait for their turn to be served. Sometimes patients
would complain after waited for hours. This had irritated Dr.Simmons and he felt that
something should be done to solve the issue. He approaches you for your help to build an
online appointment system. The system would enable patients to schedule an appointment
before coming to the clinic. The staff working in Ora-Care clinic could also use the system to
help walked-in / called-in patients to schedule their appointments. By doing so, patients could
reduce waiting time inside the clinic. The system also provides other functions such as viewing
dentist profile, clinic location, services and pricing, sending request or feedback.
The following are the minimum functions for respective end-users (but not limited to):
Staff options:
1. Register/sign-in
2. Edit own profile
3. Schedule/view/cancel patients appointment
4. View/reply patients request/feedback
5. Update services and pricing
6. Generate appointment list
Patients options:
1. Register/sign-in
2. Edit own profile
3. Schedule/view/cancel an appointment
4. Send request/feedback
5. Search/view services and pricing
*Note: You are not only limited to the above requirements. Any other relevant
requirements to ease the process of managing the operations in the system can be added if
you think they are viable. The system is assumed to run online on the web.
Other Requirements
1. For security purposes, you should have a password protected log-in page to verify the
user type
2. You should include appropriate validations and error handling within your application
3. You may define other business rules or constraints after discussing them with your
lecturer.

The project process

Diploma

Asia Pacific University of Technology & Innovation

AAPP006-4-2-SDP

Project Specification

Page 2 of 4

You will be assigned a project supervisor who will be responsible for managing the project
activity as well as the occasional guidance as necessary.
i)

The duration of the entire project is fourteen weeks:Planning system design and implementation
4 weeks
System development and implementation
7 weeks
System presentation
2 weeks
Documentation development
1 week

ii) You will be doing the project in a group and this will be finalised by your project
supervisor.
iii) You and your group are responsible for reporting to your project supervisor once a week
through a weekly progress report. This report will act as the minutes of meetings held
during the week. Your progress report must include the progress of your project work
and any issues relating to your project. Any issues, which are uncovered in the project,
must be addressed immediately.
iv) Any missed deadlines must be supported by an EC1.
v) All communication with the project supervisor must be through the group project leader.
Project assessment
The project is assessed on the following four deliverables:
Deliverable

Proportion of total marks

Design presentation
Partial documentation
Program presentation
Final documentation

10%
25%
50%
15%

Documentation assessment criteria

1.
2.
3.
4.

Overall documented standard.

Compliance to specifications of documentation.
The level of consistency throughout your documentation.
The selection and use of appropriate techniques of analysis, design and implementation.

Partial documentation requirements

1. Introduction to the project. This section should be used to provide the reader with a brief
introduction to what the whole project is all about.
2. Gantt Charts (schedule of activities). This chart should clearly outline the major activities
involved in the project.
3. Workload matrix (outline of responsible individuals). This chart should clearly outline the
activities being carried out by every individual of the project team.
1

EC: Extenuating circumstance.

Diploma

Asia Pacific University of Technology & Innovation

AAPP006-4-2-SDP

Project Specification

Page 3 of 4

4. Hierarchy Chart (outline of system modules). This chart should clearly outline the
modules, which the system is to contain.
5. Context Diagram & data flow diagrams & Data Dictionary & ERD
6. Pseudocode or program flowcharts (optional). This section will contain the algorithm of
every program or module within each program.
7. Screens design. This section must contain the design of the screens used by the system.
This should contain input screens as well as menus used within.
8. Report design. This section should contain the designs of the reports used by the system.
9. Test plan. This section should outline the test plan used to ensure that the design is
correct. Data sets should also be provided to check the correctness of the design.
10. Perceived limitations. This section should outline issues, which the system is unable to
address. This section should also address the issue of future enhancements.
11. Perceived assumptions. Under this section, you are required to state any assumptions,
which you have identified.
Final documentation contents (recommended)
(There is a deliberate overlap of the final documentation with partial documentation. The
partial documentation is meant to be a subset of the final documentation).
The submitted documentation should include the following sections:
1. A table of contents, which outlines the topics of the document together with the relevant
page, numbers where topics are located.
2. An acknowledgement section.
3. An introduction to the project. This section should be used to provide the reader with a
brief introduction to what the whole project is all about. It should also include the
complete program specification provided by the project supervisor.
4. Gantt Charts (schedule of activities). This chart should clearly outline the major activities
involved in the project.
5. Workload matrix (outline of individual responsibilities). This chart should clearly outline
the activities being carried out by every individual of the project team.
6. Hierarchy Chart (outline of system modules). This chart should clearly outline the module
which the system is to contain.
7. System charts or data flow diagrams and Data Dictionary (updated version if corrections
needed)
8. Pseudocode or program flowcharts. This section contains the details of the design of the
system. The design should not be ambiguous but detailed.
9. Screen designs. This section must contain the design of the screens used by the system.
This should contain input screens as well as menus used within.
10. Report designs. This section should contain the designs of the reports used by the system.
11. Test plans. This section should outline the test plan used to ensure that the design is
correct. Data sets should also be provided to check the correctness of the design. It should
also include results of tests and the conclusions.

Diploma

Asia Pacific University of Technology & Innovation

AAPP006-4-2-SDP

Project Specification

Page 4 of 4

12. Limitations and enhancements. This section should outline the issues, which the system is
unable to address. It can also include the difficulty the group might have faced. This
section should also address the issue of future enhancements.
13. Assumptions. Under this section, you are required to state any assumptions, which you
have identified.
i.

Reference section. This must use the Harvard system of referencing system.

14. Conclusion
15. References
16. Appendix (hard copy listings of programs)
17. Minutes of all meetings which have been conducted to date.

Diploma

Asia Pacific University of Technology & Innovation