Course Central > CMPT 275 > assignment schedule > UAT

This is the schedule of UAT meeting times for the 2015 spring semester.

• It is your responsibility to assure that the instructor has received an email from your team containing an ordered list (in order highest preference to lowest preference) of five meeting times selected from the available times in the schedule below by Friday May 15 at 5:30PM
• Appointments will be assigned based on the information provided by each team.
• Appointments will be placed in the timetable below before 8:30AM May 17 2015
• Appointments will be changed only in cases of conflict with another class (scheduled lecture or lab), conflicts with an academic, medical, or employment commitment made prior to scheduling of appointments, or other exceptional reasons. It is your responsibility to request such changes as soon as possible after the schedule is posted.
• No changes to the schedule will be considered after week 7 of the term.
• It is your responsibility to update the instructor if your course schedule changes so that rescheduling of your out of class meetings is needed. Such updates must be completed before the end of week 7 of the term.
• Meetings will be held in CSIL,

NOTE: Slots marked -------- are not available

User Acceptance Test

During the User Acceptance test you will meet with the "client" (the instructor in disguise), and a technical (computing science) expert from the clients company (Your TA in disguise). Your team will have a chance to present your final product to the client and the technical expert. The user acceptance test will last up to 65 minutes and will have the following phases:

• Installation and initialization of your system from your submitted code (you will need to compile and build the submitted code for the technical expert and use the compiled code for your demonstration). The steps taken to compile and build the code and prepare the application for demonstration should be clearly documented in your getting started instructions (submitted with your final project)
• Step through examples, to demonstrate various requirements have been met. The client will specify which requirements are to be illustrated.
• Demonstrate any features you wish to highlight that have not previously been viewed by the client during the UAT

The following are a few pointers to help your UAT be a success:

• Remember your audience; your client is not a computing science professional. Your client is an expert in a non-computing field who has contracted to have you build an application to fulfil their needs. Do be prepared for technical questions too, remember the client is bringing a technical expert to help assure the quality of the product
• Prepare for the UAT. This preparation needs to be complete before you submit your final project. You will need to include data and installation instructions that will be used in the UAT with the code submitted for the final project. Your preparation should include the following:
  • Practice the installation from your submitted code using the instructions you provided in the getting started section. This will help you to assure that your instructions are correct and complete and that all necessary components have been submitted with your project.
  • Make sure your installation works in the CSIL windows environment where the UAT will take place
  • Plan ways to demonstrate that each of the requirements of the system have been met
  • Make sure you have submitted all the necessary data to demonstrate that each of the requirements of the system have been met
• Be honest with the client; indicate which features are not implemented early in the UAT.
• Be thorough in your system testing, you will lose fewer points for missing features than for a system that crashes and needs to be restarted during the UAT

Some Rules for the User Acceptance Test

• All members of your team must be present at the User Acceptance Test. If you miss your team's user acceptance test you will receive a grade of 0 for the user acceptance test
• All members of the team must participate by demonstrating features and / or installation of the system.
• The duration of the meeting will be up to 65 minutes. Your teams mark is not dependent on the length of your meeting. A better planned meeting with more concise demonstrations, not a longer meeting, will result in a higher grade

Marking Scheme - out of 50

The instructor and TA will evaluate each User Acceptance test according to the criteria listed below.

• Level of client satisfaction: how closely your software system satisfies the client's requirements.
• Stability and robustness of the system,
  It would be wise not to cut corners during testing since a crashing software system may lose up to 3% of your final grade
• Completeness, number of requirements met
• Ease of use of the system, Ease of access to important features
• Consistency of the user interface to the system
• All team members demonstrated features and / or installation and initialization of the system
• Clarity and conciseness of explanations and demonstrations