Difference between revisions of "System requirements"
| Line 31: | Line 31: | ||
What architecture, hardware / software configurations, and programming rules must the application 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]] | ||
| Line 44: | Line 48: | ||
'''Glossary''' | '''Glossary''' | ||
| − | *[[Glossary | Glossary of terms used throughout documentation]] | + | *[[Glossary|Glossary of terms used throughout documentation]] |
|} | |} | ||
Revision as of 15:26, 10 July 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.
|