Wednesday, April 1, 2020

cst438 Software Engineering

what does SMART mean in the context of requirements?

 User stories should be specific, measurable, achievable, relevant and timeboxed. Specific, user stories should not be vague. User stories should be measurable so they can be testable using numbers as criteria. They should also be achievable, so the user story should be finished in one implementation. User stories should have business value to one or more stakeholders using the 5 whys to find more stakeholders. Timeboxing means stopping work on a story when the time budget is up, then giving up or dividing the user story into smaller ones and then rescheduling those for the next iteration. One can also go to the customer to find the highest value story and doing that. 
at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)

cst 499 week 8

This week, we finished writing the paper in order to do the best job possible even if it was a little bit late. Now that everything is done,...

  • cst499 capstone week 2
    This week, our group discussed the effective meetings reading from last week. It seemed like we already used a few ideas in the article thro...
  • cst325 w4
    This week, we learned about raytracing and it's similarities and differences from rasterization. We also learned about the CPU and GPUs ...
  • CST 338 M4 Software Design
    Give an example of polymorphism and what what be inherited between classes. After the learning this week, can you identify the difference...