1 / 15

Final Exam

Final Exam. Material from first half, but not a lot Design Dataflow State machines Modularity, abstraction, information hiding Refinement, topdown design Quality Assurance User interface design RUP and XP Bazaar and Crystal Clear. Read the papers!. Parnas, Berard, Wirth JoelOnSoftware

brick
Télécharger la présentation

Final Exam

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. Final Exam • Material from first half, but not a lot • Design • Dataflow • State machines • Modularity, abstraction, information hiding • Refinement, topdown design • Quality Assurance • User interface design • RUP and XP • Bazaar and Crystal Clear CS427

  2. Read the papers! • Parnas, Berard, Wirth • JoelOnSoftware • Tidwell – UI patterns • Raymond - Cathedral and the Bazaar • Crystal Clear CS427

  3. Software engineering • 327 – process • Modeling, management, requirements and design • 329 – tools • Software configuration management • Testing • Metrics • Maintenance and reverse engineering • Client-server, web systems, component software • CASE tools CS427

  4. Grade curve from 2001 • A+ 7 • A 15 • A- 27 • B+ 19 • B 13 • B- 11 • C+ 4 • C 1 CS427

  5. Project Problems • Takes too long to learn technology • Don’t know how to divide up work • A few people do all the work • Spend more effort on teaching, less on building • Pair for learning • All work in the same room at the same time • Fire those who are holding you back CS427

  6. RUP and XP • What are the main differences? • What different assumptions do they make? • How are their goals different? CS427

  7. Scheduling • How are the goals of scheduling different in RUP and XP? • How do the techniques differ? • Who makes schedules? Does it matter? CS427

  8. Requirements • How do use cases differ from user stories? • Who does the work? Does it matter? CS427

  9. Analysis • What happens during the RUP workflow called “analysis”? • XP doesn’t have anybody called an “analyst” or a phase called “analysis”. • Where does the work get done? • What are the advantages and disadvantages of each approach? CS427

  10. Architecture • What is “Architecture” in RUP? • What does an “architect” do? • XP doesn’t have an architect and never mentions architecture. • Does this work get done anyway? CS427

  11. Design • What happens during the RUP workflow called “design”? • XP doesn’t have anybody called a “designer” or a phase called “design”. • Where does the work get done? • What are the advantages and disadvantages of each approach? CS427

  12. Evaluation • How do people on an RUP project know whether they are building the right system? • How do people on an XP project know whether they are building the right system? CS427

  13. Quality • Do RUP and XP have different ideas of software quality? If so, how? CS427

  14. Manager • What does an RUP manager do? • What does an XP manager do? • Which job is harder? CS427

  15. Developer • What things does a RUP developer need to know that an XP developer doesn’t? • What things does an XP developer need to know that an RUP developer doesn’t? • Which job is harder? CS427

More Related