Framework for a Pavement-Maintenance Database System (2016) / Chapter Skim
Currently Skimming:
Pages 98-102
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 98... ...
98 The following section describes the functional and non-functional requirements that were identified to guide the development of PMDb. Functional Requirements In software engineering, a functional requirement defines a function of a system or its component.
|
From page 99... ...
Pavement-Maintenance Database System Requirements 99 Append data Contributor users will be able to append additional data to existing pavement sections over time. For example, it is anticipated that condition data will be collected on a periodic basis and will be appended to the existing pavement section.
|
From page 100... ...
100 Framework for a pavement-Maintenance database System Non-Functional Requirements A non-functional requirement is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviors. This should be contrasted with functional requirements that define specific behavior or functions.
|
From page 101... ...
pavement-Maintenance database System Requirements 101 • Encryption strength: no encryption will be used for this project at this time as the data is all public domain. User Account Requirements • Username will be the email address registered to the user account.
|
From page 102... ...
102 Framework for a pavement-Maintenance database System • Integrated help tool tips for users (included within application) • Localization: The system will not support localization.
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.