1. http://www.flickr.com/photos/bdunnette/184607940/sizes/m/

2. Which of these is not a quality attribute? g)Integrity h)Portability i)Reusability c)Usability d)Maintainability e)Flexibility f)Functionality j)Testability k)Interoperability a)Reliability b)Efficiency

3. a)Spiral is faster and cheaper than waterfall b)Spiral is for winners; waterfall is for losers c)Spiral was invented earlier d)Spiral includes extra steps for managing risk e)Spiral is only used for military contracts; waterfall can be used for anything How does a spiral process differ from a waterfall process?

4. a)Heavy use of unit tests b)Minimalist requirement specifications c)Daily prototyping d)Regular refactoring e)Rapid iteration f)Heavy involvement of customers or users Which of these is not a key trait of agile processes?

5. a)Microsoft PowerPoint b)HTML and JavaScript c)PhotoShop d)Adobe Acrobat e)Paper and pencil Which of these might be a suitable medium for evolutionary prototyping?

6. Paper prototyping Low-fidelity prototyping Stakeholder review Manual analysis Formal analysis Name 1 strength and 1 weakness for each req. evaluation technique

7. A rectangle in a state diagram A rectangle in a UML class diagram A rectangle at the top of a sequence diagram A rectangle with two horizontal bars in a dataflow diagram An oval in a dataflow diagram An oval in a use case diagram A vertical dashed line in a sequence diagram What do these shapes mean?

8. Stakeholder review Process-oriented decomposition Risk exposure Connector Formal analysis Scrum Failure mode Define…

9. Elements of modeling – System boundary – Use case – Entity – Attribute – Quality attributes Reliability Efficiency Integrity Usability Maintainability Testability Flexibility Portability Reusability Interoperability Process – Waterfall vs Spiral vs Agile – Iterative vs Incremental Concepts covered so far Requirements – Definition vs specification – Functional Textual Use cases – Non-functional Textual Fit criteria Diagrams – Use case diagram – UML class diagram – Entity-relationship diagram – Dataflow diagram – Sequence diagram – State diagram Risk – Impact, likelihood, exposure – Management Assessment Control Prototyping – Paper vs Low-Fidelity vs High-Fid. – Throwaway vs Evolutionary Requirements evaluation techniques – Stakeholder review – Manual analysis – Formal analysis Architecture – Components and connectors – Decomposition Function-oriented Data-oriented Object-oriented Feature-oriented Process-oriented Event-oriented – Styles Pipe and filter Client-server Peer-to-peer Publish-subscribe Layering …

10. Architecture – … – Evaluation w.r.t. quality attributes w.r.t. failure modes w.r.t. use cases w.r.t. checklist Object-oriented design – Modularity and concerns – Coupling and cohesion – Interfaces – Usability and polymorphism – Design patterns Schedule, effort, and cost – Activity graph Critical path Slack time – Effort estimation methods PSP Complexity & productivity – Gantt Chart Concepts still to come Agile – Values – Use and role of models – Role of customer – Use and role of tests – DSDM vs XP XP Practices – Whole team – Metaphor – The planning game – Simple design – Small releases – Customer acceptance tests – Pair programming – Test-driven development – Design improvement – Collective code ownership – Continuous integration – Sustainable pace – Coding standards Specific techniques – User stories – Tasks – Agile estimation – Spikes – Communication – Debriefings – Source code control – Refactoring Professionalism – Membership – Constructive role of ego – Vision – Commitment – Planning – Risk management – Character