COMP 1531 Group Project, 18s2 -
Milestone 3
Due-date: Week 12, 9:00 am
1. All working software will need to be pushed to final_release branch GitHub
by Week 12, Monday, 9:59 am
2. Software must also be submitted using GIVE by the due-date
3. All other artifacts (outlined below) will need to be submitted by Friday, 11:59
pm
Deliverable
For this presentation, your tutors will play the role of the customer. Your task
is to “sell” your design and application to them.
(1) Presentation ( In your lab session )
At the start of the presentation, provide a list of core user-stories that you will
be demonstrating.
Marks will be awarded for this presentation based on the (i) quality of your
presentation (ii) demonstration of the key features of your system (iii) how well
you can sell your design to the customer.
(2) Working Software and test-cases (Due: Monday, week 12,
10:00 am)**
All features of the system as outlined in the user-stories must be implemented
To test your working software, tutors will perform. two types of testing as
described below:
o User Acceptance Testing:
Your tutor will log into the system (using the credentials supplied in the csv file)
and test the list of user-stories and their associated acceptance criteria as
enclosed in your report.
o Unit Test Cases:
A comprehensive set of test-cases must be submitted for the acceptance
criteria defined above. Please adhere to the following guide-lines in
implementing the test-cases.
Test-cases must be written for three core user-stories: (1) book an
appointment (2) view a patient history (3) manage a patient history. The test-
cases must be implemented with PyTest.
Each user-story must have multiple test-cases defined. For example, if you
are writing test-cases for “book an appointment with a health-care provider”,
you will be testing for (i) making a successful appointment and getting a
confirmation of the appointment (ii)l booking an appointment in the past (ii)
book multiple appointments in the same day/time-slot (ii) test that a provider
cannot make an appointment with themselves etc.
(Note: these test-cases must match the acceptance criteria that you have
defined for the chosen user-story.)
The test-cases must be in a file “tests.py”. They will be run by your tutor.
Hence, make sure that the test-cases execute successfully.
(3) Report (Friday, Week 12, 11:59 pm):
A final report is to be submitted that includes the following artifacts:
A front-sheet that lists (1) your group-name (2) name and zID of each group
member
A final, updated list of user-stories along with clearly-defined acceptance
criteria to comply with the revised project specification. The list of user-stories
must include all the features of your system
Final class diagram clearly defining all the attributes and methods. Your class
diagram may have changed since your week 10 submission based on tutor
feedback or to accommodate for more flexible design choices that you might
have thought of during implementation
(Note: we will look for appropriate use of OO principles in both your design
and code-base and your implementation must correlate to your class diagram
e.g., if you have modelled inheritance or an aggregation in your class diagram,
this needs to be reflected in your implementation as well. You will be marked
for right use of design principles (inheritance, composition and OCP)
An entity-relationship (ER) design for the EMS system as the clients anticipate
that in the future they might implement a persistence layer based on
databases (only ER is needed, relational model and implementation of
persistence based on databases is not needed)
A log that records the responsibilities allocated to each team member,
progress of tasks using a velocity chart (scanned copy of hand-drawing will
suffice, no sophisticated tool needed) and summary of decisions made in
stand-up meetings
(4) Moodle Peer Assessment (Sunday, Week 12, 11:59 pm)