1 / 15

CS361 Winter 2013 Final Exam Review

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. Materials.

arnon
Download Presentation

CS361 Winter 2013 Final Exam Review

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. 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

  3. Materials • You are allowed one side of one letter-sized piece of paper for notes during the exam • Hand-written crib sheets only

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

  5. 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

  6. Diagram Notations • Know your diagrams • ER Diagrams • Dataflow diagrams • Message sequence charts • UML • Class diagrams • Real-time UML • StateCharts • Structured class diagrams

  7. Evaluating Requirements and Prototyping • Attributes of good requirements • Approaches for evaluating requirements • Paper prototyping • Risk management • Types of prototypes and associated advantages/disadvantages

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

  9. Design Patterns • What design patterns are • What is useful about design patterns • How to apply the various design patterns

  10. Evaluating Architecture • Methods to evaluate an architecture • Looking at an existing architecture and identifying potential problems

  11. Scheduling and Estimation • How to estimate • How to schedule • What activity diagrams and Gantt charts are

  12. Elements of Agile Development • Principles of agile software development • How interactions with the customer are done • Key aspects of XP • Key aspects of SCRUM

  13. Testing and Quality • Definition of unit testing • Refactoring

  14. Agile Collaboration • How to collaborate and communicate with your client • How to collaborate and communicate with your fellow developers

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

More Related