CSE230 Exam Advice and Hints

1. CSE230 Exam Advice and Hints

3. Hints for Taking CSE230 Exam Role During Exam Software engineer doing design and analysis to solve problems and critique approaches - read and assimilate Exam open book/notes/web Possible Questions Similar to home works, initial design, past exams Evaluative questions vs. qualities, principles, modularization, etc. Constructive questions - Design using FSM, ER, DFD, PN, UML Diagram, etc. Relationship between concepts - Qualities vs. Specification vs. etc... Decisions regarding Design, Algorithms, etc.

4. Hints for Taking CSE230 Exam Read the Questions Carefully! Ask Questions if you are Confused! Answer Questions in Any Order Organized to fit on minimum number of pages Answer �Easiest� questions for you! Assess Points per Time Unit 75 minutes = 75 points 15 points = 15 minutes For Essay/Short Answer Questions - Length Answer Matches Points 5 points = 1/4 page = 3 or 4 sentences 30 points - if 1/4 page - likely few points! Exam Designed to be Longer than 75 Minutes!

5. Hints for Taking CSE230 Exam Don't Define Concepts E.G., Ask About Concept X, Don't Explain Concept X, Just Answer the Question and I'll Know If You Know Concept X Don't Panic, Read and Review Course Materials Prior to Exam! Don't Be Afraid to Not Answer a Question 60% Correct for 100 Points = 60 Points 90% Correct F0r 80 Points = 72 Points Partial Credit Is the Norm If I Ask You to Pick and Analyze a Concept - for a 5 Pt Problem You Get 1 for the Concept and 4 for the Analysis.

6. Midterm Exam - Possible Questions Open Notes and Open Book (Open Web) 5-7 Total Questions Possibilities� Diagrams Analysis of HDIS w.r.t. Principles/Qualities OO/Modular/ADT Concepts Spec Techniques (ER, DFD, etc.) + UML Design/Analysis Questions Software Architectures Show All Work to Receive Partial (Any) Credit Do Not Jump to Final Answer Avoid Run-on Explanations

7. Final Exam - Material and Advice Material: Ghezzi - Chapters 2, 3, 6, 7, 8 Web Page Slides - Security, AOP, UML Note Read Book and Review Slides: Slides have more material than Book Chapters No-Silver Bullet Article Coverage: Software Qualities and Principles (Chapters 2 + 3)No direct questions � review for completeness Verification, Testing, Validation (Chapter 6) Software Process Models (Chapter 7) Management Issues (Chapter 8) Security � Background, MAC, DAC, RBAC AOP � Concepts of AOP and its Relevance Role of UML in SW Process, Testing, etc.

8. Final Exam - Material and Advice Examine and Review HDIS as it Relates to Course Material from Second Half of Semester Chapter 6: Testing in the Small/Large White-Box and Black-Box Testing Chapter 7: Software Models (Spiral, Evolutionary) Chapter 8: Estimation, Teams, Team Structures, SW Quality Assurance, Acquisition, Re-Engineering, etc. UML � Impact of UML on HDIS and Role of UML in Various Second Semester Topics Security, AOP � How can both Impact HDIS ? No Silver Bullet Articles (web page) Overall: 5 Multiple-Part Questions on these Topics

9. CSE230 Midterm Exam Results � Fa06

10. Fa06 - Problem 1 1a: SW Qualities related to Performance Reliability, Correctness, Interoperability � Key Others perhaps Full Credit � Based on Answer Otherwise -1 and -2 Depending on Answer Need to discuss Why and not just Explain Quality -1.5 per Quality if no WHY 1b: Usage of Queueing/Simulation in HDIS 3 points for Feature, 3 for Why, 3 for Resources 7/9 � One of three above Lacking 5/9 � Two or Three Lacking 3/9 � Bare Attempt Typical Deductions: -1 to -2/Quality for Too General (No example from HCA � can apply to any Appl.)

11. Fa06 - Problem 2 Pip and Filter Software Architecture Points Allocated as: 9 for Diagram, 3 for Filter Doc, 3 for Flow Doc For Diagram 6 pts for Filter 1 pt for Fork, 1 for Join, 1 for Feedback Other Deductions -6 if FSM (clearly not Pipe and Filter Architecture) -3 if some Aspects of P&F � other missing pieces -3 Too Low Level � this is an Architecture after all Typical Grading 9/15 � Some OK ideas � basically off track Higher Scores � closer to answer Lower � totally missed point

12. Fa06 - Problem 3 DFD � Structure is: Grading Issues Not using the DB from Project 2A, Not Labeling Arrows with Data, Incorrect Use of I/F/O/DB, too FSM/State Oriented, Incorrect Connections Among I/F/O/DB, etc. 13/15 � Very Close � minor problems 11/15 � 4 to 5 small problems 9/15 � Major problems � missing features 7/15 � Not DFD � Missed the point

13. Fa06 - Problems 4 and 5 Problem 4: State Chart Diagram Overall � Most students did quite Well (12.6/15) Average 13.7 if Take out 3 students that Didn�t Do the Problem Overall � Minor Deductions here and there Problem 5: Sequence Diagrams Part a: Focus on Interchange between Bank and two Credit Agencies Also � Self Reference for Bank to do Assessment & Evaluation Prior to returning to Person Part b: Again � in General very good Slightly lower than Part a �Last Problem of Exam

14. CSE230 Midterm Exam Results � Sp06

15. Sp06 - Problem 1 1a: Top 3 out of: (-1 if portability, -1 if repairability) User Friendliness, Interoperability Verifiability, Maintainability 1b: Discuss Qualities of HCA with Specific Example User Friendliness: Computer Skills of RNs, MDs, and Time/Safety Critical areas (OR, ER) Interop: Multiple Interacting Apps � external DB, Legacy, COTS, Lab Equipment, MRI, etc. Reparability: Quickly fix which is critical for OR, ER, etc. Systems can�t be down long Verifiability: People can Die is Treatments, Drugs, etc., Not carefully Tracked Typical Deductions: -1 to -2/Quality for Too General (No example from HCA � can apply to any Appl.)

16. Sp06 - Problem 2 Did not differentiate between Top 3 � Graded the three that you gave me Focus on Design/Implementation Many User Focused � not issue Discuss 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.) Incrementality: Can�t Build Such a Large System all at Once � must Deliver in Parts, Add Features Typical Deductions: -1 to -2/Principle for Too General (No example from HCA � can apply to any Appl.)

17. Sp06 - Problem 3 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 3b: Differentiate OO vs. ADT/Modules: Accept either Inheritance � Quality � Evolution/Reuse; Principle Anticipation of Change, Incrementality Instantiation � Multiple Instances of �Same� Class Not True for ADT/Module Independent Instance Behavior

18. Sp06 - Problem 4 4a: First Thing to do� Talk to Customers, Identify their Needs, Learn the Domain, Get Input from all Types of Users, etc. Almost everyone received 3/3 4b: Program Family � Same Tool Tweaked for Users Everyone received 0/2 4c: Specification Techniques for GUI Most Relevant are: UCD, DFD, ER, FSM, AD, SC If only 1 diagram cited/discussed � max 7/10 Two or more diagrams discussed � max 10/10 Deductions for generality from -1 to -3 (don�t cite examples from HCA � just talk about GUI)

19. Sp06 - Problem 5 Overall � Generally OK Deductions for No labels of inputs/data on arrows Using incorrect symbols for Input/Output/Function/Database Missing Inputs Multiple Inputs/Function Making Incorrect Connections (DB to Output) etc. Range from -1 to -3 -3 if Missing a function