Difference between revisions of "System requirements"

From ICA-AtoM
Jump to navigation Jump to search
 
(8 intermediate revisions by the same user not shown)
Line 5: Line 5:
 
| style="width:500px; border: 1px solid rgb(255, 201, 201); padding: 0.5em 1em 1em; color: rgb(0, 0, 0); background-color: rgb(255, 243, 243);" |  
 
| style="width:500px; border: 1px solid rgb(255, 201, 201); padding: 0.5em 1em 1em; color: rgb(0, 0, 0); background-color: rgb(255, 243, 243);" |  
  
'''[[Functional requirements]]'''
+
'''Functional requirements'''
 +
 
 +
What must the application be able to do?
  
What must the system be able to do?
 
 
*[[Functional requirements|Overview / index]]
 
*[[Functional requirements|Overview / index]]
*[[FNC-1 | FNC-1 Implement a system of control]]
 
*[[FNC-2 | FNC-2 Add / edit content]]
 
*[[FNC-3 | FNC-3 Translate content]]
 
*[[FNC-4 | FNC-4 Access content]]
 
*[[FNC-5 | FNC-5 Import / export content]]
 
*[[FNC-6 | FNC-6 Administer the system]]
 
  
  
 
'''Metadata requirements'''
 
'''Metadata requirements'''
  
What data must the system capture in order to do these things?
+
What data must the application capture in order to be able to do these things?
 +
 
 
*[[Metadata requirements|Overview / index]]
 
*[[Metadata requirements|Overview / index]]
*[[MTD-1 | MTD-1 Record information about archival materials]]
 
*[[MTD-2 | MTD-2 Record information about actors]]
 
*[[MTD-3 | MTD-3 Record information about archival institutions]]
 
*[[MTD-4 | MTD-4 Record information about controlled terms]]
 
*[[MTD-5 | MTD-5 Record information about descriptions]]
 
*[[MTD-6 | MTD-6 Record information about users]]
 
  
  
 
'''Quality requirements'''
 
'''Quality requirements'''
  
What interface and design features must the system have in order to do these things '''well'''?
+
What design and interface features must the application have in order to do these things ''well''?
 +
 
 +
*[[Quality requirements|Overview / index]]
  
  
Line 38: Line 30:
 
'''Technical requirements'''
 
'''Technical requirements'''
  
What architecture, hardware / software configurations, and programming rules must the system implement in order to meet the functional, metadata, and quality requirements?
+
What architecture, hardware / software configurations, and programming rules must the application implement in order to meet the functional, metadata, and quality requirements?
 +
 
 
*[[Technical requirements|Overview / index]]
 
*[[Technical requirements|Overview / index]]
  
  
 
'''Use cases'''
 
'''Use cases'''
 +
 +
''What if'' scenarios describing interactions with the application from the end-user's point of view.
 +
 
*[[Use cases|Overview / index]]
 
*[[Use cases|Overview / index]]
  
  
 
'''Qubit requirements'''
 
'''Qubit requirements'''
* see also: [http://qubit-toolkit.org/wiki/index.php?title=Functional_Requirements Qubit requirements]
 
** [http://qubit-toolkit.org Qubit] is the generic open information management toolkit created by the ICA-AtoM project and used to implement the ICA-AtoM application
 
  
 +
[http://qubit-toolkit.org Qubit] is the generic open information management toolkit created by the ICA-AtoM project and used to implement the ICA-AtoM application.
  
'''Glossary'''
+
*[http://qubit-toolkit.org/wiki/index.php?title=Functional_Requirements Qubit requirements]
*[[Glossary | Glossary of terms used throughout documentation]]
 
  
 
|}
 
|}

Latest revision as of 10:34, 18 August 2008

Please note that ICA-AtoM is no longer actively supported by Artefactual Systems.
Visit https://www.accesstomemory.org for information about AtoM, the currently supported version.

Functional requirements

What must the application be able to do?


Metadata requirements

What data must the application capture in order to be able to do these things?


Quality requirements

What design and interface features must the application have in order to do these things well?


Technical requirements

What architecture, hardware / software configurations, and programming rules must the application implement in order to meet the functional, metadata, and quality requirements?


Use cases

What if scenarios describing interactions with the application from the end-user's point of view.


Qubit requirements

Qubit is the generic open information management toolkit created by the ICA-AtoM project and used to implement the ICA-AtoM application.