Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Personal Training System
Transcript of Personal Training System
Personal Information e.g height
Heart rate monitor
Target Weight loss - Actual Weight loss
Heart rate compared to average heart rate
Weight left to lose graph / stats
Heart rate monitor
The numerical data that is recorderd is put into a database.
The customer will be required to fill out a form with their personal information and goals
Every week an email will be sent to the client entailing their progress over the week and how far they have to go to get to their targets. Some of this could be displayed graphicaly.
Is Heart rate near the average?
Is the client achieving their targets?
Is the client keeping up a healthy diet?
Has the client changed any personal information?
Are the data entry processes functioning correctly and efficiently?
Are the outputs correct?
By Michael and Harvey
Does the program function properly? (opening, closing, saving, printing, running without errors)
If something does not pass the testing, then you have to go back to the previous steps to fix these areas
Direct would be used
Design Validation checks
1.Direct changeover – the old system is stopped completely. The new system is started
Reduces change over time.
The new system is up and running immediately
If the system fails there is no back-up system. This may mean loss of data
2.Parallel Running – both systems run for a short time. When the new system has been proven to work, the old system is stopped
The old system acts as a backup
The outputs from the old and new systems can be compared to check that the new system is running correctly
Entering data into two systems, and running two systems together, takes a lot of extra time and effort
3.Phased implementation – the new system is introduced gradually, replacing parts of the old system until it is fully replaced.
Users can slowly get used to the new system
Staff can be trained in stages
There is no back-up system. Data may be lost if the system fails
4.Pilot Running – the new system is trialled (piloted) in one part of the business organisation adopt the system
All features of the system can be trialled.
Reduced harm from any server faults
Pilot staff can train other staff
No back-up system if the pilot system fails