Lecture and Tutorial 6

The steps involved for prioritising the build are:

1. List all functions or features contained in the requirements
2. Associate each with a priority category
3. Sort the list into descending order of importance (ie. High to Low)
4. Agree final list with client
5. Group features into versions (ie. High = version 1, Medium = version 2)

A Few pointers on creating the documentation:

Requirements Document

• purpose = explain the purpose of the system you will create
• scope and description = describe application by listing function points
• user, entities and attributes = include your use case here
• entity list = include the entities and attributes you will use for the system
• functionality and processing = include your activity diagram here
• security policy = write any security issues you may encounter

Design Document

• purpose = copy from requirements document
• data model = include your ERD here
• data processing = any queries for editing, creating and deleting
• functional specification = include the table for high/medium/low priorities
• development method = include a Gantt Chart here
• user interface = include wire frames for your forms in the proposed system

Hope this helps!

Sam x