230EA.1 CSE 2102 CSE2102 Exam Advice and Hints Prof. Steven A. Demurjian, Sr. Computer Science & Engineering Department The University of Connecticut 271.

Slides:



Advertisements
Similar presentations
© Andrew IrelandSoftware Design F28SD2 Software Design: Summary Andrew Ireland School of Mathematical & Computer Sciences Heriot-Watt University Edinburgh.
Advertisements

Ossi Taipale, Lappeenranta University of Technology
CS487 Software Engineering Omar Aldawud
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
FE.1 CSE 4701 CSE4701 Final Exam Advice and Hints Prof. Steven A. Demurjian, Sr. Computer Science & Engineering Department The University of Connecticut.
OV-1.1 CSE4701 CSE4701 Introduction to Databases Prof. Steven A. Demurjian Computer Science & Engineering Department The University of Connecticut 371.
OV-1.1 CSE4100 CSE4100 Programming Language Translation Prof. Steven A. Demurjian, Sr. Computer Science & Engineering Department The University of Connecticut.
Software Testing and Quality Assurance
OV-1.1 CSE4939 CSE4939 CS & E Design Laboratory Prof. Steven A. Demurjian, Sr. Computer Science & Engineering Department The University of Connecticut.
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
General information CSE 230 : Introduction to Software Engineering
FE.1 CSE4100 Final Exam Advice and Hints Prof. Steven A. Demurjian, Sr. Computer Science & Engineering Department The University of Connecticut 191 Auditorium.
CSE 322: Software Reliability Engineering Topics covered: Course outline and schedule Introduction, Motivation and Basic Concepts.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Review 1.
333 EA-1 CSE333 Distributed Component Systems Final Exam Advice and Hints Prof. Steven A. Demurjian, Sr. Computer Science & Engineering Department The.
CIS 321—IS Analysis & Design
Chapter 2: Approaches to System Development
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 2- Software Process Models and Project.
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
OV-1.1 CSE2102 CSE2102 Intro to Software Engineering Prof. Steven A. Demurjian, Sr. Director, CS&E Graduate Program Computer Science & Engineering Department.
Information Systems Analysis and Design
Instructor: Peter Clarke
OV-1.1 CSE4939 CSE4940 CSE4939W/4940 CS & E Design Lab I/II Prof. Steven A. Demurjian, Sr. Computer Science & Engineering Department The University of.
CS361 Winter 2013 Final Exam Review Software Engineering I Oregon State University.
Introduction To System Analysis and Design
Software Engineering EKT 420 MOHAMED ELSHAIKH KKF 8A – room 4.
Guiding Principles. Goals First we must agree on the goals. Several (non-exclusive) choices – Want every CS major to be educated in performance including.
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
Chapter 1 Object-Oriented Analysis and Design. Disclaimer Slides come from a variety of sources: –Craig Larman-developed slides; author of this classic.
CS206 System Analysis and Design Note 1 By ChangYu 1 Course Information Lecturer NameCHANG YU Web sitewww.chuhai.edu.hk/changyu/
Systems Analysis and Design 8 th Edition Chapter 6 Object Modeling.
Course Overview Stephen M. Thebaut, Ph.D. University of Florida Software Engineering Foundations.
Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 1 Informatics 43 Introduction to Software Engineering.
Final Exam Review Session 14 LBSC 790 / INFM 718B Building the Human-Computer Interface.
Lecture 2 –Approaches to Systems Development Method 10/9/15 1.
Chapter 13: Software Life Cycle Models Omar Meqdadi SE 273 Lecture 13 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Computer Architecture 2 nd year (computer and Information Sc.)
CSC 354 – System Development Life Cycles & Processes, Spring 2015 March 2015 Dr. Dale Parson.
UML - Development Process 1 Software Development Process Using UML.
Meghe Group of Institutions Department for Technology Enhanced Learning 1.
Software Engineering I. Introduction to Software Engineering Software models Formal Specification using ASML (Abstract State Machines Language) Software.
Your Interactive Guide to the Digital World Discovering Computers 2012 Chapter 12 Exploring Information System Development.
Systems Analysis and Design in a Changing World, 6th Edition
CH4.1 CSE244 Midterm Subjects Aggelos Kiayias Computer Science & Engineering Department The University of Connecticut 371 Fairfield Road, Box U-155 Storrs,
Intrto-1 CSE 5810 Miscellaneous FHIR Slides Prof. Steven A. Demurjian, Sr. Computer Science & Engineering Department The University of Connecticut 371.
AIM : To provide an in-depth knowledge in software engineering paradigms, life cycles and Development processes.
© Chinese University, CSE Dept. Software Engineering / Topic 3: Software Engineering Principles Your Name: _____________________ Computer Science.
OV-1.1 CSE262 CSE293 CSE262 Software Engineering Laboratory CSE293 CS & E Design Laboratory Prof. Steven A. Demurjian, Sr. Computer Science & Engineering.
OV-1.1 CSE230 CSE230 Introduction to Databases Prof. Steven A. Demurjian, Sr. Computer Science & Engineering Department The University of Connecticut 371.
CS 8532: Adv. Software Eng. – Spring 2007 Dr. Hisham Haddad Discussion of Course Syllabus Class will start momentarily. Please Stand By … CS 8532: Advanced.
CS 8532: Adv. Software Eng. – Spring 2009 Dr. Hisham Haddad , Monday Class will start momentarily. Please Stand By … CS 8532: Advanced Software.
DigitalHC-1 CSE 5810 Digital Healthcare Security Prof. Steven A. Demurjian, Sr. Computer Science & Engineering Department The University of Connecticut.
Final Exam Study Guide COP 4331 and EEL4884 OO Processes for Software Development © Dr. David A. Workman School of EE and Computer Science University of.
Advanced Software Engineering Dr. Cheng
CSE784 – Software Studio Jim Fawcett Fall 2002.
Advanced Software Engineering
CSE 219 Final exam review.
Chapter 7: Software Engineering
Lecture 0 Software Engineering Course Introduction
CSE305 Software Engineering
CSE784 – Software Studio Jim Fawcett Fall 2006.
Chapter 1 Object-Oriented Analysis and Design. Disclaimer Slides come from a variety of sources: –Craig Larman-developed slides; author of this classic.
Miscellaneous FHIR Slides
CSE255 Final Exam Advice and Hints
CSE4939W/4940 CS & E Design Lab I/II
Practical Software Engineering
CSC 354 – System Development Life Cycles & Processes, Fall 2013
Software Engineering (Second Year) Dr
CSE4939W/4940 CS & E Design Lab I/II
Presentation transcript:

230EA.1 CSE 2102 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 (860)

230EA.2 CSE 2102 Final Exam - Material and Advice  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:  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.

230EA.3 CSE 2102 Final Exam - Material and Advice  Examine and Review HCA/PHA as it Relates to Course Material from Second Half of Semester  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 Models  Alternative Models (Spiral, Waterfall, Agile, etc.)  Relationship to Testing and Teams(Chapter 8)  Appropriateness of Current Models for Mobile Computing

230EA.4 CSE 2102 Final Exam - Material and Advice  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 of 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  Overall: 5 Multiple-Part Questions on these Topics  120 pts vs. 120 Minutes  Open Book/Notes/Web

230EA.5 CSE 2102 Key Final Exam Concepts  Components 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 Architectures  Understand Alternatives and High-Level View  Able to Define and/or Modify Architecture  Software Process Methodology/Models  Waterfall, Evolutionary, Transformation, Spiral  UML Unified Process, Agile Development  Phases and Activities of Process Models

230EA.6 CSE 2102 Key Final Exam Concepts  Personnel Organization  Centralized, Decentralized, Mixed and Chief Programmer Teams  Reporting Structure, Interactions  Choose Approach Best Suited to Domain/Problem  Implementation Strategies  Build-it-Twice Full Prototype  Level-by-Level Top Down  Incremental Development  Advancemanship  Agile Scrums

230EA.7 CSE 2102 Midterm Exam - Material and Advice  Material  Ghezzi - Chapters 1 to 5 - use class notes and course web content for coverage  Material on UML  Key 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

230EA.8 CSE 2102 Hints for Taking CSE2102 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, UML Diagram, etc.  Relationship between concepts - Qualities vs. Specification vs. etc...  Decisions regarding Design, Algorithms, etc.

230EA.9 CSE 2102 Hints for Taking CSE2102 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!

230EA.10 CSE 2102 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.

230EA.11 CSE 2102 Midterm Exam - Possible Questions  Open Notes and Open Book (Open Web)  5-7 Total Questions  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) Credit  Do Not Jump to Final Answer  Avoid Run-on Explanations