Project

Project-Based Software Engineering, Requirements Document Instructions

Requirement Document Instructions

Check the Instructions for the Project Plan

Basically the requirements document follows the same principles as the Project Plan. Thus you should check it for the general instructions.

Topics to Cover in the Requirements Document

Some new requirements have emerged since the start of the project. One of the new requirements is that the software must fit in a 1152 * 864 pixel screen so that the usage is possible without extensive scrolling all the time.

In general you should check the project plan instructions and requirements document templates.

Templates for Requirements Document

As earlier, there is a Standard Requirements Document Template and you can also choose to use any other requirements document template. Check the instructions for the project plan for further details on these templates. The template is SWE-RD.dot

NEW! Comments to RD template

For different kind of requirement documents/templates you can take a look at the references below.

Returning the Requirements Document

The requirements document must be returned by Wednesday 30.10.2002 at 12:00 by noon to email k010752000@kurssit.lut.fi . Do not include in the email anything but the single document as an attachment. The name of the file and other instructions are as before just add RD to the file name (0123456AbC_RD.doc, for examlpe). Make sure that you send the email to the right address. Paper version on the document is expected during this Wednesday to the room 6731.

Questions and Results

If you have any questions about developing the requirements document, about the results/points contact me by email. The results for the requirements documents will be published on Project Homepage in few weeks after submission.

Information Sources

If you need some help on completing the requirements document you can try the following sources:

Descriptions: ConOps-doucument.

Viewpoints: See the Sommerville article below.

Scenarios: See the use case/scenario articles/web sites below.

Requirements Table: The table is based on the information in Volere-cards, check Volere requirements shell.

References

You can access the IEEE papers here: IEEE Xplore.
Software Engineering books: Pressman, Sommerville, Pfleeger, etc.
IEEE Guide for Information Technology - System Definition - Concept of Operations (ConOps) Document, IEEE Std 1362-1998.
IEEE Recommended Practice for Software Requirements Specifications, IEEE Std 830-1998.
Volere Requirements Specification Template, Suzanne Robertson and James Robertson, The Atlantic Systems Guild, here, accessed 16.10.2002.
Viewpoints for requirements elicitation: a practical approach, I. Sommerville, P. Sawyer and S. Viller, ICRE 98, in here, accessed 16.10.2002.
Structuring Use Cases with Goals, Alistair Cockburn, here, accessed 16.10.2002.
Use Case Zone, here, check the "Papers", accessed 16.10.2002.
My requirements engineering links (hopefully, some of them work)

Last updated 17.10.2002