cs361 winter 2013 final exam review software engineering i oregon state university

15
CS361 Winter 2013 Final Exam Review Software Engineering I Oregon State University

Upload: kathlyn-bryant

Post on 12-Jan-2016

229 views

Category:

Documents


4 download

TRANSCRIPT

Page 1: CS361 Winter 2013 Final Exam Review Software Engineering I Oregon State University

CS361 Winter 2013 Final Exam Review

Software Engineering IOregon State University

Page 2: CS361 Winter 2013 Final Exam Review Software Engineering I Oregon State University

Comprehensive Exam

• The exam will cover the entire set of course material

• Contents will not be limited to this set of slides: please look at all of the slides

Page 3: CS361 Winter 2013 Final Exam Review Software Engineering I Oregon State University

Materials

• You are allowed one side of one letter-sized piece of paper for notes during the exam

• Hand-written crib sheets only

Page 4: CS361 Winter 2013 Final Exam Review Software Engineering I Oregon State University

Software Processes

• Waterfall vs. Spiral vs. Agile processes• Incremental vs. Iterative• When to use them

Page 5: CS361 Winter 2013 Final Exam Review Software Engineering I Oregon State University

Requirements

• Functional requirements• Non-functional requirements• Eliciting requirements• Use cases and attributes of use cases• How do you write a good use case?– Main success scenario– Pay attention to good style and practices

Page 6: CS361 Winter 2013 Final Exam Review Software Engineering I Oregon State University

Diagram Notations

• Know your diagrams– ER Diagrams– Dataflow diagrams– Message sequence charts– UML• Class diagrams

– Real-time UML• StateCharts• Structured class diagrams

Page 7: CS361 Winter 2013 Final Exam Review Software Engineering I Oregon State University

Evaluating Requirements and Prototyping

• Attributes of good requirements• Approaches for evaluating requirements• Paper prototyping• Risk management• Types of prototypes and associated

advantages/disadvantages

Page 8: CS361 Winter 2013 Final Exam Review Software Engineering I Oregon State University

Architecture

• Different types of decomposition• Patterns and their usefulness• Coupling and cohesion• Assignment of responsibilities• Usefulness of diagramming

Page 9: CS361 Winter 2013 Final Exam Review Software Engineering I Oregon State University

Design Patterns

• What design patterns are• What is useful about design patterns• How to apply the various design patterns

Page 10: CS361 Winter 2013 Final Exam Review Software Engineering I Oregon State University

Evaluating Architecture

• Methods to evaluate an architecture• Looking at an existing architecture and

identifying potential problems

Page 11: CS361 Winter 2013 Final Exam Review Software Engineering I Oregon State University

Scheduling and Estimation

• How to estimate• How to schedule• What activity diagrams and Gantt charts are

Page 12: CS361 Winter 2013 Final Exam Review Software Engineering I Oregon State University

Elements of Agile Development

• Principles of agile software development• How interactions with the customer are done• Key aspects of XP• Key aspects of SCRUM

Page 13: CS361 Winter 2013 Final Exam Review Software Engineering I Oregon State University

Testing and Quality

• Definition of unit testing• Refactoring

Page 14: CS361 Winter 2013 Final Exam Review Software Engineering I Oregon State University

Agile Collaboration

• How to collaborate and communicate with your client

• How to collaborate and communicate with your fellow developers

Page 15: CS361 Winter 2013 Final Exam Review Software Engineering I Oregon State University

Professionalism

• How to behave ethically, morally, and legally• What engineering professionalism is