Difference between revisions of "System requirements"
(New page: {| style="width:95%; border="0" |-valign="top" | 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, 2...) |
|||
| (10 intermediate revisions by the same user not shown) | |||
| Line 7: | Line 7: | ||
'''Functional requirements''' | '''Functional requirements''' | ||
| − | What must the | + | What must the application be able to do? |
| + | |||
*[[Functional requirements|Overview / index]] | *[[Functional requirements|Overview / index]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
'''Metadata requirements''' | '''Metadata requirements''' | ||
| − | What data must the | + | What data must the application capture in order to be able to do these things? |
| + | |||
*[[Metadata requirements|Overview / index]] | *[[Metadata requirements|Overview / index]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
'''Quality requirements''' | '''Quality requirements''' | ||
| − | What interface | + | What design and interface features must the application have in order to do these things ''well''? |
| + | |||
| + | *[[Quality requirements|Overview / index]] | ||
| Line 37: | Line 29: | ||
'''Technical requirements''' | '''Technical requirements''' | ||
| − | What architecture, hardware / software configurations, and programming rules must the | + | |
| + | 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''' | ||
| − | |||
| − | |||
| + | [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/wiki/index.php?title=Functional_Requirements Qubit requirements] | |
| − | *[ | ||
|} | |} | ||
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?
What data must the application capture in order to be able to do these things?
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?
What if scenarios describing interactions with the application from the end-user's point of view.
Qubit is the generic open information management toolkit created by the ICA-AtoM project and used to implement the ICA-AtoM application. |