Matt Tempia Chris Thomas Thomas Taylor Jeffrey Tansey

 Project Definition  Project Plan  Project Design  Prototype

 Team Members:  Matthew Tempia  Thomas Taylor  Chris Thomas  Jeffrey Tansey  Client:  Dr. Susan Rieken, Dental Administration

 Reasons for the Project:  Effective Tool for Fair Testing  Preparation for Boards  Objective: Move competency tests for treatment planning from the clinical environment into the classroom.  Purpose of the System: To allow an administrator to create, edit, administer, and grade a competency test for treatment planning.

 Previous Procedure:  Student would be evaluated on “real life” situations with patients. They would perform a clinical examination on a patient and prepare a plan of proposed treatment based upon the findings. The students would then be graded on how they performed.  Online Test:  There are samples of tests online that are guides for how the software will act. Some websites for reference:

1. Admin -> Pool of Questions -> Lock In 2. The multiple choice questions graded by the software 3. Vertical scrolling for large questions 4. Scrambled Questions 5. Timer 6. Mark Questions 7. A question list will be color coded to show status 8. An administrator will have the ability to insert various media

 Must be network connected.  Must have a database.  Interface must be easily manipulated.  A login is necessary.  Measures to prevent cheating

Meet with Client Client Input Website Project Definition Document

Analysis and Design Group  Write problem description.  Write design specification.  Manage changes in the project.  Create and present prototypes.  Write user documentation.  Delivery and installation of the system. Team Member Thomas Taylor Team Member Chris Thomas Lead Analyst Thomas Taylor Team Leader Matthew Tempia Order of Responsibilites

Programming Group  Detailed design of the project. How to actually implement the design made by the analysis and design group.  Code the system. Team Member Chris Thomas Team Member Thomas Taylor Lead Programmer Jeff Tansey Team Leader Matthew Tempia Order of Responsibilites

Testing Group  Write test cases. Acceptance, Unit, Integration, and System tests.  Gather test data.  Schedule test resources.  Execute tests.  Analyze test data.  Document test results. Team Member Jeff Tansey Team Member Thomas Taylor Lead Tester Chris Thomas Team Leader Matthew Tempia Order of Responsibilites

Dr. Rieken (Client) Dr. Rieken (Client) Matt Tempia (Team leader) Matt Tempia (Team leader) Dr. Xudong Yu (Upper management) Dr. Xudong Yu (Upper management) Chris Thomas (Lead Tester) Chris Thomas (Lead Tester) Jeff Tansey (Lead programmer) Jeff Tansey (Lead programmer) Thomas Taylor (Lead analyst) Thomas Taylor (Lead analyst)

 Wide Band Delphi Estimation  1.Kick off meeting  Individual preparations  2.Estimation forms during estimation meeting Database Test taker(User) Interface Admin Interface Testing  Project leader spread sheet of all members data  3.Final meeting

 Security Controls Security Controls  Treatment/Preparation based Risk  Any assumed or current risks will be documented in a Statement of Applicability, which identifies which particular Control Objectives and controls from the standard have been selected, and why.Statement of ApplicabilityControl Objectives  Possibility Risk: (n out of 10)  Damage Risk : (m out of 10)  Security Controls  Terminate (aka elimination, get rid of the problem entirely and forget about it)  Treat(aka mitigation, create a solution to the risk when it arises, adapt)  Tolerate (aka ignore and move on)  Preparation (aka already have a solution in place to automatically fix risk)

 Name of person documenting risk  Date  Time  Risk Description (Possibility and Damage Rating)  Proposed Security Control  Reasoning for Proposed Security Control  In depth description of how to implement the Security Control

 Module Test  To define, design, and choose an outline for a module of the program that is effective in its delivery and understanding for the client and user.  Integration Test  Approved module or part of the program interact effectively according to how users expect it to.  System Test  Retesting the completed software system in as nearly live an environment as possible by personnel other than those who produced the programs.  Acceptance Test  Exercising the software system under conditions agreed to by the customer in order to demonstrate that the system satisfies the customer’s requirements.  Site Test  Test the software in the actual environment it will be used in. Test hardware also.

 Document Plan  Project Definition Document – Objective of this document is stated in the actual document  Project Plan Document– Objective of this document is stated in the actual document  Project Design Document– Objective of this document is stated in the actual document  Training Plan  Understanding Session  Review and Reporting Plan  Statement of Applicability

Interface Logic Database Interface Logic StudentAdmin

 All information necessary directly relating to the students: StudentIDCHARThe unique ID number of a student FirstNameVARCHARStudent’s first name LastNameVARCHARStudent’s last name UserNameCHARStudent’s login name PasswordCHARStudent’s encrypted password

 Each question stored individually in the database: QuestionIDINTEGERThe unique number to identify a given question QuestionTextVARCHARThe question being asked IsMultipleChoice BOOLEANIs the question multiple choice? AnswerAVARCHARFirst possible answer AnswerBVARCHARSecond possible answer AnswerCVARCHARThird possible answer AnswerDVARCHARFourth possible answer AnswerEVARCHARFifth possible answer CorrectAnswerCHARIdentifies possible answer as correct DateAddedDATEDate question was added to the database

 A test that was administered to a student and submitted: StudentIDCHARForeign key to the Student class, identifies what student took this test TestIDINTEGERForeign key to the SavedTest class, identifies what test was taken ScoreINTEGERScore on graded test IsGradedBOOLEANIs the test graded?

 An individual question that was submitted by a student during a test: StudentIDCHARForeign key to the Student class, identifies what student answered this question TestIDINTEGERForeign key to the SavedTest class, identifies on what test this question appeared QuestionIDINTEGERForeign key to the Question class, identifies what question was asked AnswerGivenVARCHARAnswer submitted by student during test IsCorrectBOOLEANTri-state Boolean: True: Correct, False: Incorrect, NULL: Un-graded

 An individual question that appears in a saved test: TestIDINTEGERForeign key to SavedTest class, identifies on what test this question appears QuestionIDINTEGERForeign key to Question class, identifies what question appeared

 A test that has been saved to the database for later use: TestIDINTEGERUnique identity code for a test DateAddedDATEWhen the test was created NameVARCHARUser defined test name

 The currently selected test that will be administered to students. A check will be in place to prevent more than one entry in this class: StartDateDATEDate when test is to be available EndDateDATEDate when test stops being available StartTimeTIMETime when test is available EndTimeTIMETime when test stops being available TestIDINTEGERForeign key to SavedTest to identify what test to make available

 Client Interface: Visual Studios Visual Basic is a visual approach to coding software, it will be implemented with Visual Studios.net  Admin Interface: Visual Studios Visual Basic  Database: The dental data storage is implemented as a MySQL database, a popular open-source relational database management system  Operating system: Windows XP or newer will be used for proper implementation of the Visual Basic Software  Connection: Intranet  Location: Client Interface used on specific lab locations Admin Interface used on admin lab Computers and Office computer  Team programming: Tortoise SVN is a useful program that integrates code effectively from several locations

 Current test The test that is currently set up for students to take at a certain time and place.  Selected test The test that is being edited.  Locked/Unlocked “Locked” questions, are questions that are in the Selected test. “Unlocked” questions, are questions that are not in the Selected test.  Pool List of questions/tests in the database.

 Goals For prototype  Both interfaces will be able to do the basic/most important tasks.  Display the functionality of the admin/student interfaces  Admin Interface:  edit/add questions  edit/create tests  edit students.  Client Interface:  Use all the functions of the student test interface  NOTE: Database will not be interacting with interfaces for this prototype.