SWEN-261 Lecture Notes - Lecture 18: User Story, Planning Poker, Code Coverage

35 views3 pages

Document Summary

Make sure that your user stories are thin slices of work, not class based. A person working on a user story should be completing everything related to that story, not just a single class from that story. Even if a story has dependencies, you can still test it by creating unit tests and inject dependencies. Coming up we will have a bunch of documents due for tuesday: Communicates why a certain architecture was chosen and how certain design decisions were chosen. It should generally be a top down style of documentation. Should be simple and easy to understand. An overview of your system and design. What is needed for the current project. Summary of the architecture and why it was chosen. Explain what is in the system, and what is static or dynamic. Design documents usually will use uml standards to display the design (can use visio, lucidchart, etc)

Get access

Grade+20% off
$8 USD/m$10 USD/m
Billed $96 USD annually
Grade+
Homework Help
Study Guides
Textbook Solutions
Class Notes
Textbook Notes
Booster Class
40 Verified Answers
Class+
$8 USD/m
Billed $96 USD annually
Class+
Homework Help
Study Guides
Textbook Solutions
Class Notes
Textbook Notes
Booster Class
30 Verified Answers

Related Documents