Skip to main content

Currently Skimming:


Pages 39-48

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 39...
... 39 C h a p t e r 4 This chapter defines key system and user requirements that were used to build the Archive. These requirements were captured as user stories and developed on the basis of two workshops, conducted as part of the L13A project, which aimed to collect SME feedback on essential features of the Archive.
From page 40...
... 40 4.2.1 Administrator The administrator role is performed by the project manage­ ment members of the Archive system management team. The administrator's role serves the following functions: • Archive setup.
From page 41...
... 41 registration process. Users may choose to store additional information in their user account.
From page 42...
... 42 allows users to browse available data and discussions. Essentially, this means developing the data archive site in a modern style that is easy to navigate.
From page 43...
... 43 • System backups. System backup formats must follow a documented industry standard.
From page 44...
... 44 Figure 4.3. Map search.
From page 45...
... 45 of any fields in the data set or a subset of a data set. The sys­ tem also has the capability to plot different series on a com­ mon plot.
From page 46...
... 46 function. User stories are employed in agile software develop­ ment methodologies as the basis for defining the functions a business system must provide and to facilitate requirements management.
From page 47...
... 47 US6. The Archive administrator deletes/updates artifacts.
From page 48...
... 48 4.5.1.5 Download US22. The Archive user can download Archive objects.

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.