Project Part 2 Feedback

Requirements Specification: Good 3/3

Overall, team 3 demonstrates understanding of core material of requirement specification. The specifications are clear and mostly consistent. However, the following points should be noticed:

• Use case 1: server should also be an actor.
• There is no use case 100 or 104.
• Use case 3: Reader proceeds to interact with the story as in use case 1, use case 1 is browsing story(while expecting to be reading story)
• Use case test 4: number issue

Also, I would argue about the following:

• User should be able to download a story, edit it and publish it as his/her own.
• Users being able to get stories from other users and authors means they can somehow request stories from another user/author.

---

User Interface Mockups and Storyboard: Excellent 3/3

Consistent, fancy, covers important use cases.

---

OOA: Excellent 2/2

Clear understanding of MVC design. Clear model class separation from data class. Clear separation of concern, important classes are modelled well.

---

Release Planning: Excellent 1/1

Consistent and realistic.

---

Glossary: Good 1/1

Clear glossary but seems missing something, e.g. continue, browse, develop, choice.

---

Summary: 10/10

This is based on rubric of part 2. Feel free to contact me were there any concerns. haiming1[at]ualberta.ca