Pride Case Study
ISM 3013
7-4. There are many advantages to locating the PRIDE database to the cloud. Dr. Flores and his partners could benefit from the increased accessibility, operating costs, minimal investment, superior security and disaster preparations, speedy development, automated on-the-go scaling and better performance. By locating the database internally, they could face cost uncertainties, significant capital investment, annual maintenance costs, ongoing support costs, difficulty in accommodating demand and the need to train staff and personnel.
7-5. Figure 7-15 shows the query that is used to create the Workout table from the PRIDE database. Here the developer is using the SQL Azure thin-client application that is used manage databases from within the Windows Azure Platform. Figure 7-16 shows three diagrams that represent and describes the relationships between tables: Person, Workout and Performance from the PRIDE database. The diagrams were created by Microsoft Visual Studio, which is also a thin-client application used to manage and create databases. The data from the tables were created from metadata that was read from the PRIDE V1 database. The relationship between the Person and Workout table can be defined by referencing the PersonID from the Person table. And the “Constraint WorkoutPersonFK foreign key (PersonID) References Person(PersonID) On Delete No Action” ensures that every row from Workout table will correspond to some row in the Person table.
7-6. The Store Exercise prescription application uses the data from the tables in figure 7-17 to display information to a client application that can be accessed and used by healthcare professionals to help them prescribe the appropriate workout for particular patients.
7-7. The Store Exercise Data application uses the data from the tables in figure 7-17 to display performance information to a client application that can be accessed and used by healthcare professionals to help them monitor and track a patient’s
7-4. There are many advantages to locating the PRIDE database to the cloud. Dr. Flores and his partners could benefit from the increased accessibility, operating costs, minimal investment, superior security and disaster preparations, speedy development, automated on-the-go scaling and better performance. By locating the database internally, they could face cost uncertainties, significant capital investment, annual maintenance costs, ongoing support costs, difficulty in accommodating demand and the need to train staff and personnel.
7-5. Figure 7-15 shows the query that is used to create the Workout table from the PRIDE database. Here the developer is using the SQL Azure thin-client application that is used manage databases from within the Windows Azure Platform. Figure 7-16 shows three diagrams that represent and describes the relationships between tables: Person, Workout and Performance from the PRIDE database. The diagrams were created by Microsoft Visual Studio, which is also a thin-client application used to manage and create databases. The data from the tables were created from metadata that was read from the PRIDE V1 database. The relationship between the Person and Workout table can be defined by referencing the PersonID from the Person table. And the “Constraint WorkoutPersonFK foreign key (PersonID) References Person(PersonID) On Delete No Action” ensures that every row from Workout table will correspond to some row in the Person table.
7-6. The Store Exercise prescription application uses the data from the tables in figure 7-17 to display information to a client application that can be accessed and used by healthcare professionals to help them prescribe the appropriate workout for particular patients.
7-7. The Store Exercise Data application uses the data from the tables in figure 7-17 to display performance information to a client application that can be accessed and used by healthcare professionals to help them monitor and track a patient’s
References: Person(PersonID) On Delete No Action” ensures that every row from Workout table will correspond to some row in the Person table. 7-6. The Store Exercise prescription application uses the data from the tables in figure 7-17 to display information to a client application that can be accessed and used by healthcare professionals to help them prescribe the appropriate workout for particular patients. 7-7. The Store Exercise Data application uses the data from the tables in figure 7-17 to display performance information to a client application that can be accessed and used by healthcare professionals to help them monitor and track a patient’s prescribed workout. 7-8. The Report Patient Exercise application uses the data from the tables in figure 7-17 to produce patient exercise reports for healthcare professionals and personal trainers. 7-9. Yes, the duplicate data in the Person table could create problems for the health clubs, healthcare providers and the PRIDE users. Data duplication can cause data inconsistencies and inefficiencies. Combining separate isolated databases and revising applications can help alleviate the inconsistencies that arise from data integrity problems. And if combining isolated databases isn’t possible, better management can also help to avoid problems. 7-10. The PRIDE database eliminates information silos by storing all relevant patient data as tables in the database that can be accessed by client applications. And as result of locating the database to the cloud, users’ of the PRIDE database may display frustration and distress from learning to use the new system. 7-11. I believe moving the PRIDE database to the cloud will be successful, because of the infrastructure set in place with the Windows Azure platform.