LSRE-ReleasePlanningProject

Requirements for a Course Management System. Please check the issue tracker.

Week 47-48

TODO

• Decide on an area of responsibility for each of you (use the course discussion forum for this).
• Assign responsibles for each issue according to what you have decided.
• Link the requirements to each other, along with comments on how they are linked.
• I notice a lot of duplicate requirements. Find them, link them, and close the newest.
• Tag Requirements (assign labels) so we know whether they are bugfixes, feature requests, or whether we should not be working with them.

Next Step

By the second half of week 48, we should have discussed on the course discussion forum what prioritisation method to use, how to apply it in this particular case, and how to do release planning based on this.

Don't forget:

Your reflective logs on this assignment are still empty. How does what you do here connect to research literature?

TODO (week 44-45)

Requirements Quality

As you notice, the quality of these requirements vary quite a bit. Your first job is to -- by adding comments to the issues -- clarify them so that they can be understood.

Dependencies

The next part is to identify any dependencies between requirements. There are quite a number of dependencies here. Comment on the issues and relate them to each other (using #issue-number to link them)

Requirements abstraction level

Some requirements are huge, others are small. Make sure that you break down the huge ones into smaller requirements (into features and components of those features). Make sure that the small requirements are linked to larger requirements.

More Features

Invent more features, add corresponding issues.