CSE2102 Exam Advice and Hints

11
230EA.1 CSE 2102 CSE2102 Exam Advice and Hints CSE2102 Exam Advice and Hints Prof. Steven A. Demurjian, Sr. Computer Science & Engineering Department The University of Connecticut 271 Fairfield Road, Box U-2155 Storrs, CT 06269-2155 [email protected] http://www.engr.uconn.edu/~steve (860) 486 - 4818

description

CSE2102 Exam Advice and Hints. Prof. Steven A. Demurjian, Sr. Computer Science & Engineering Department The University of Connecticut 271 Fairfield Road, Box U-2155 Storrs, CT 06269-2155. [email protected] http://www.engr.uconn.edu/~steve (860) 486 - 4818. - PowerPoint PPT Presentation

Transcript of CSE2102 Exam Advice and Hints

Page 1: CSE2102 Exam Advice and Hints

230EA.1

CSE2102

CSE2102 Exam Advice and HintsCSE2102 Exam Advice and Hints

Prof. Steven A. Demurjian, Sr. Computer Science & Engineering Department

The University of Connecticut271 Fairfield Road, Box U-2155

Storrs, CT [email protected]

http://www.engr.uconn.edu/~steve(860) 486 - 4818

Page 2: CSE2102 Exam Advice and Hints

230EA.2

CSE2102

Final Exam - Material and AdviceFinal Exam - Material and Advice Material: Material:

Ghezzi - Chapters 2, 3, 6, 7, 8 Web Page Slides

Agile Process (including PDF) Software Architectures UML

Note Read Book and Review Slides: Slides have more material than Book Chapters

Coverage: Coverage: Software Qualities, Principles (Chapters 2 + 3)

Verification, Testing, Validation (Chapter 6) Software Process Models (Chapter 7) Management and Team Issues (Chapter 8) Role of OO/UML in SW Process, Testing, etc.

Page 3: CSE2102 Exam Advice and Hints

230EA.3

CSE2102

Final Exam - Material and AdviceFinal Exam - Material and Advice Examine and Review HCA/PHA as it Relates to Course Examine and Review HCA/PHA as it Relates to Course

Material from Second Half of SemesterMaterial from Second Half of Semester Chapter 6: Chapter 6:

Testing in the Small White-Box Testing

Black-Box Testing Testing in the Large Strategies

Big-Bang vs. Incremental vs. Bottom Up/Top Down Formulating Test Case at Code Level SWQ and Principles re. Testing

Chapter 7: Software Process ModelsChapter 7: Software Process Models Alternative Models (Spiral, Waterfall, Agile, etc.) Relationship to Testing and Teams(Chapter 8) Appropriateness of Current Models for Mobile

Computing

Page 4: CSE2102 Exam Advice and Hints

230EA.4

CSE2102

Final Exam - Material and AdviceFinal Exam - Material and Advice Chapter 8: Chapter 8:

Estimation, Teams, Team Structures, Implementation Strategies

SW Quality Assurance, Acquisition, Re-Engineering, etc.

Interplay of Teams with Testing OO/UML – Impact of UML on HCA/PHA and Role OO/UML – Impact of UML on HCA/PHA and Role

of UML in Various Second Semester Topicsof UML in Various Second Semester Topics No Explicit Questions Assume Know OO and Core UML (Use-Case,

Class, Sequence, State-Chart, Activity Diagrams) No Security, No Open Source No Security, No Open Source Overall: 5 Multiple-Part Questions on these TopicsOverall: 5 Multiple-Part Questions on these Topics 120 pts vs. 120 Minutes120 pts vs. 120 Minutes Open Book/Notes/WebOpen Book/Notes/Web

Page 5: CSE2102 Exam Advice and Hints

230EA.5

CSE2102

Key Final Exam ConceptsKey Final Exam Concepts Components and Problem DecompositionComponents and Problem Decomposition

Ability to Identify and Specific Components when Given Problem Statement/Description

Components as Services Web and Cloud Services/Computing JSON, REST, etc.

Software ArchitecturesSoftware Architectures Understand Alternatives and High-Level View Able to Define and/or Modify Architecture

Software Process Methodology/ModelsSoftware Process Methodology/Models Waterfall, Evolutionary, Transformation, Spiral UML Unified Process, Agile Development Phases and Activities of Process Models

Page 6: CSE2102 Exam Advice and Hints

230EA.6

CSE2102

Key Final Exam ConceptsKey Final Exam Concepts Personnel OrganizationPersonnel Organization

Centralized, Decentralized, Mixed and Chief Programmer Teams

Reporting Structure, Interactions Choose Approach Best Suited to Domain/Problem

Implementation StrategiesImplementation Strategies Build-it-Twice Full Prototype Level-by-Level Top Down Incremental Development Advancemanship Agile Scrums

Page 7: CSE2102 Exam Advice and Hints

230EA.7

CSE2102

Midterm Exam - Material and AdviceMidterm Exam - Material and Advice MaterialMaterial

Ghezzi - Chapters 1 to 5 - use class notes and course web content for coverage

Material on UML Key ConceptsKey Concepts

Software qualities (Chapter 2) Software principles (Chapter 3) SW Design, Modularization, OO, Inheritance

(Chapter 4) SW Specification (Chapter 5)- DFDs, FSMs, ERs UML – Use Case, Class, Sequence, and State-

Chart Diagrams

Page 8: CSE2102 Exam Advice and Hints

230EA.8

CSE2102

Hints for Taking Hints for Taking CSE2102 CSE2102 ExamExam Role During ExamRole During Exam

Software engineer doing design and analysis to solve problems and critique approaches - read and assimilate

Exam open book/notes/web Possible QuestionsPossible Questions

Similar to home works, initial design, past exams Evaluative questions vs. qualities, principles,

modularization, etc. Constructive questions - Design using FSM, ER,

DFD, UML Diagram, etc. Relationship between concepts - Qualities vs.

Specification vs. etc... Decisions regarding Design, Algorithms, etc.

Page 9: CSE2102 Exam Advice and Hints

230EA.9

CSE2102

Hints for Taking Hints for Taking CSE2102 CSE2102 ExamExam Read the Questions Carefully!Read the Questions Carefully! Ask Questions if you are Confused!Ask Questions if you are Confused! Answer Questions in Any OrderAnswer Questions in Any Order

Organized to fit on minimum number of pages Answer “Easiest” questions for you!

Assess Points per Time UnitAssess Points per Time Unit 75 minutes = 75 points 15 points = 15 minutes

For Essay/Short Answer Questions - Length Answer For Essay/Short Answer Questions - Length Answer Matches PointsMatches 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!Exam Designed to be Longer than 75 Minutes!

Page 10: CSE2102 Exam Advice and Hints

230EA.10

CSE2102

Hints for Taking CSE230 ExamHints for Taking CSE230 Exam Don't Define ConceptsDon'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 Don't Panic, Read and Review Course Materials Prior to Exam!to Exam!

Don't Be Afraid to Not Answer a QuestionDon'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 NormPartial 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.

Page 11: CSE2102 Exam Advice and Hints

230EA.11

CSE2102

Midterm Exam - Possible QuestionsMidterm Exam - Possible Questions Open Notes and Open Book (Open Web)Open Notes and Open Book (Open Web) 5-7 Total Questions5-7 Total Questions Possibilities… Possibilities…

Diagrams Analysis of HCA/PHA w.r.t. Principles/Qualities OO/Modular/ADT Concepts Spec Techniques (ER, DFD, etc.) + UML Design/Analysis Questions

Show All Work to Receive Partial (Any) CreditShow All Work to Receive Partial (Any) Credit Do Not Jump to Final AnswerDo Not Jump to Final Answer Avoid Run-on ExplanationsAvoid Run-on Explanations