CSE784 – Software Studio Fall 2001
Project #1 – Requirements Database
B-Specification due Sep 17, C-Specification and code due Sep 24
Purpose:
This program captures and saves customer requirements1, development requirements2, and requirements issues. It
provides capability to:
Number each customer requirment, and each development requirement.
Attach an issue statement with each requirement, above. Provide a status for each issue which has one of
the two values: current, or closed.
Provide a title for each requirement.
Stamp each requirement with a creation time and date and a last modified time and date.
Edit requirements and issues already entered.
Add new or delete existing requirements and issues at any time.
Associate a priority (levels High, Normal, or Low) with any requirement’s issue.
Display any requirement by number or title. Provide two view – one with requirements only, one with both
requirements and issues.
Sort requirements by creation date, last modified date, or priority.
Save and restore the database in a file3.
You may assume that the entire database can fit into memory so your design can read the entire file contents at one
time.
Requirements:
Your Reqdata program:
1. Shall read from a database file at startup if one is defined. On process termination, it shall save any entered
data to the specified database or to a default name if none is specified4.
2. Shall accept from the user a definition of a new item in one of the two categories (1) customer specification, or
(2) development specification.
3. Each item shall consist of a number, title, time-date stamps, a text description, and priority setting.
4. Shall support addition of a new requirement, modification of an existing requirement, or addition or
modification of a requirements issue, at any time.
5. Shall display, on command, any requirement by number or title. If no title matches, shall return the closest
matching title5.
6. Shall provide two views, one displaying requirements, the other displaying both requirements and their
associated issues. This display shall be sorted as described above.
7. Shall read, from a specified or default file, all requirements and issue items at program startup.
8. Shall save all requirements and issues at program termination, using an XML-based format.
1 From A-Level Requirments Specification.
2 For B-Level Requirements Specification.
3 To keep things simple please do not use a commercial database – simply save the program’s data in a flat ASCII
file, using an XML-based format.
4 You may, optionally save at the time of entry or modification, if you wish.
5 This requirement is ambiguous. You will have to elaborate on the meaning of the requirement in your B
Specification.
