The non-functional requirements for the Rolodex Tool are organized into three major categories:
In general, the non-functional requirements for the Rolodex Tool are limited, given the simplicity of tool's functionality and the fact that it is public domain non-commercial software.System-related non-functional requirements cover performance, operational environment, and general system characteristics.
Given the limited functionality of the Rolodex Tool and its limited user community, performance is not a significant issue. In general, the speed of all operations must be comparable to similar tools, such as those cited in Section 1.5 on related systems. "Comparable to" means that the Rolodex Tool operations must execute at a speed that is in the same order of magnitude as similar tools under similar computer load conditions.
There are no specific requirements for the allowable size of a rolodex in terms of the number of cards. A Rolodex on the order of thousands of cards is the likely maximum size during normal use. However, there is no specific reason that the size of the Rolodex be limited.
There are no specific requirements for the hardware or software platform on which the Rolodex Tool must operate. As discussed in Section 2.10 , specific elements of the graphical user interface may differ per the conventions of a specific operating environment.
There are no specific requirements for interoperability with external software, such as other database programs.
The functionality of the Rolodex tool is sufficiently straightforward that the tool must be 100% reliable, accurate, and correct. "Reliable" means that the system must not fail due to a software fault that is traceable to one of its functional software components. "Accurate" means that the system must not loose or corrupt data due to a software fault that is traceable to one of its functional software components. "Correct" means that in the absence of external hardware or external software failures, the system performs all operations as defined in the Rolodex Tool formal specification.
The system must be robust in the face of hardware power failures in terms of data loss. "Robust" means that when computer power fails or is interrupted, the Rolodex Tool performs a Save operation on the currently open rolodex file, if the workspace is modified.
There are no specific requirements for security, privacy, safety, portability, modifiability, or extensibility.
The system is to be developed using the software process employed by Gene Fisher in his software engineering classes at Cal Poly university. The process is currently described in lecture notes for the graduate course in software engineering.
The development is to be conducted by a single individual (Gene Fisher) who is
assumed to have the necessary knowledge and skills to complete the project.
There are no specific requirements for the end users of the Rolodex Tool.
Given its simple functionality, it is intended to be usable by end users with
only basic computer literacy skills.