cs361 winter 2013 final exam review software engineering i oregon state university
TRANSCRIPT
![Page 1: CS361 Winter 2013 Final Exam Review Software Engineering I Oregon State University](https://reader036.vdocument.in/reader036/viewer/2022082404/56649e7d5503460f94b7fc13/html5/thumbnails/1.jpg)
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](https://reader036.vdocument.in/reader036/viewer/2022082404/56649e7d5503460f94b7fc13/html5/thumbnails/2.jpg)
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](https://reader036.vdocument.in/reader036/viewer/2022082404/56649e7d5503460f94b7fc13/html5/thumbnails/3.jpg)
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](https://reader036.vdocument.in/reader036/viewer/2022082404/56649e7d5503460f94b7fc13/html5/thumbnails/4.jpg)
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](https://reader036.vdocument.in/reader036/viewer/2022082404/56649e7d5503460f94b7fc13/html5/thumbnails/5.jpg)
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](https://reader036.vdocument.in/reader036/viewer/2022082404/56649e7d5503460f94b7fc13/html5/thumbnails/6.jpg)
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](https://reader036.vdocument.in/reader036/viewer/2022082404/56649e7d5503460f94b7fc13/html5/thumbnails/7.jpg)
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](https://reader036.vdocument.in/reader036/viewer/2022082404/56649e7d5503460f94b7fc13/html5/thumbnails/8.jpg)
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](https://reader036.vdocument.in/reader036/viewer/2022082404/56649e7d5503460f94b7fc13/html5/thumbnails/9.jpg)
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](https://reader036.vdocument.in/reader036/viewer/2022082404/56649e7d5503460f94b7fc13/html5/thumbnails/10.jpg)
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](https://reader036.vdocument.in/reader036/viewer/2022082404/56649e7d5503460f94b7fc13/html5/thumbnails/11.jpg)
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](https://reader036.vdocument.in/reader036/viewer/2022082404/56649e7d5503460f94b7fc13/html5/thumbnails/12.jpg)
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](https://reader036.vdocument.in/reader036/viewer/2022082404/56649e7d5503460f94b7fc13/html5/thumbnails/13.jpg)
Testing and Quality
• Definition of unit testing• Refactoring
![Page 14: CS361 Winter 2013 Final Exam Review Software Engineering I Oregon State University](https://reader036.vdocument.in/reader036/viewer/2022082404/56649e7d5503460f94b7fc13/html5/thumbnails/14.jpg)
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](https://reader036.vdocument.in/reader036/viewer/2022082404/56649e7d5503460f94b7fc13/html5/thumbnails/15.jpg)
Professionalism
• How to behave ethically, morally, and legally• What engineering professionalism is