Non-functional Goal | Use Cases / Details |
---|
Easy to install / deploy | |
Easy to upgrade | - "auto-upgrader" option? (script to upgrade, or it auto-upgrades data/configs when you load the new WAR, similar to Atlassian tools)
- Store configuration properties/options in database
|
Scalability / Performance | (needs better definition) Suggestions: - Uploading/Processing content in DSpace should not be bound to size of content
- DSpace should strive to operate in with constant memory usage footprint during all operations.
- DSpace user experience should not be performance limited by number of Communities, Collection, Items and/or Bitstreams
- Support Alternative Assetstore Technologies
- Support Many Database Vendors
|
Attractive to new developers | - Opportunities to learn / contribute
- Adopt Current and Industry Standard Technologies
- Good dev/tech documentation
- Supportive community
|
Attractive to new Repository/Content Managers | - Good user documentation
- Supportive community
- Usage best practices / guidelines?
- More UI Driven Admin Functionality
|
Avoid centrally maintaining duplicative codebases/functions | - Standardize on a single out-of-the-box UI? (other third-party UIs may be offered, but would not be centrally maintained)
- Centralize common UI Actions / Commands and consolidate into Business Tier.
|