Grade Distribution

1. Grade Distribution Worry Worry a Lot

2. Fall 13 - Problem 1 – SW Qualities • 1a: Top 6 any order • User Friendliness, Performance, Robustness • Reliability, Repairability, Portability • - 1 pt if either of other two listed • Why is User Friendliness Most Important? • 1b: Discuss FOUR Qualities of HCA with Specific Example • User Friendliness: Computer Skills of RNs, MDs, and Time/Safety Critical areas (OR, ER) • Reparability: Quickly fix which is critical for OR, ER, etc. Systems can’t be down long • Performance: People can Die is Treatments, Drugs, etc., Not carefully Tracked • 3 pts/quality - Typical Deductions: -1 to -2/Quality for Too General (No example from HCA – can apply to any Appl.) • Deciphering my writing: Too G (too general), what can happen to the patient? What does the provider need? What can go wrong if perf, robus, relia, repai bad? Relate to HCA.

3. Fall 13 - Problem 2 – SW Principles • Top 4 are: Took any order • Separation of Concerns, Anticipation of Change • Generality, Incrementality • If Mod/Abstr is 3rd or 4th : -1; 1st or 2ndis -2 • Why not Mod/Abs 1st? If don’t have others, M/A won’t matter!! • Discuss THREE Principles of HCA with Specific Example • Separation of Concerns: Performance vs. DB vs. GUI vs. Security • Anticipation of Change: New Meds, New Treatments, New Equipment (MRI, etc.), new Computing Dev (mobile) • Incrementality: Can’t Build Such a Large System all at Once – must Deliver in Parts, Add Features, Sys of Sys • Generality: Patient UI customized for MD, RN, etc. Similar interfaces regardless of Surgery, Pediatrics, etc. • Important to HCA vs. Impact on HCA – different! • Typical Deductions: -1 to -2/Principle for Too General (No example from HCA – can apply to any Appl.)

4. Fall 13 - Problem 3 - Client/Server • 3a: Pure Server (Export) and Pure Client (Import) • Both Yes – 1pt position, 2 pts disc, 2 pts example • Purse Server: Formulary Database with API to Access Meds; Drug Interaction Module, etc. • Pure Client: Any Read-Only GUI for Patient DB, Formulary DB, etc. • Again – Deductions for Generality • 6/12 min attempt; 8/12 a ex; 10/12 two so soexs • 3b: Differentiate OO vs. ADT/Modules: Accept either • 3pts: Inheritance – 1pt Quality Evolution/Reuse; 1pt Prin. Anticipation of Change, Incrementality • Instantiation – Multiple Instances of “Same” Class • Not True for ADT/Module • Independent Instance Behavior

5. Fall 13 - Problem 4 - DFD • Deductions for • No labels of inputs/data on arrows • Using incorrect symbols for Input/Output/Function/Database • Missing Inputs/outputs/labels • Multiple Inputs/Function • Making Incorrect Connections (DB to Output) • Too connected and too linked • More like state-chart than DFD • Should have used DBs from HCA Info Section • 6/15 minimum attempt • 9/15 an attempt – but missing multiple above • 12/15 knows DFD concepts – but incomplete

6. Fall 13 - Problem 4 – DFD for HCA Triage Patient Examine Patient Decision Diagnosis Pat History PatientID LabTest DB Med DB Patient DB Get Med History PatientID Patient History Test Results Treatment Pat History Decision PatientID, Test List LT Results Order & Perform Tests PatientID Outcome Disc/ Admit LT Results Assess New Rx PatientID Curr Rx

7. Fall 13 - Problem 5 – State-Chart Diagram • Overall – Generally Best performance of all problems • 34 students out of 52 who did problem received 12/15 or higher • 9/15 if missed point or didn’t do a state-chart – some more like activity diagram and mixing in DFD and ER concepts • 6/15 and lower for bare or minimal attempt • Some took too detailed approach • No need to have picking patient and going through displays or screens • Not the purpose of state-chart • Meant to model behavior

8. Fall 13 - Problem 5 – State-Chart Diagram Waiting Room Triage New Patient Examine Patient Alert Comatose Order Tests More Tests? Still waiting Further Examine Order Tests Perform Tests No Done Tests No Diagnosis ER Visit Complete? Assess Patient Have Diagnosis Yes Discharge Final Decision Patient Released Admit Patient To Room