APOLLOMergedArchitectureRequirementsAnalysis


 * Acronym Soup
 * FRR: Further Research Required
 * NTB: Need To Build
 * ADT: APOLLO Does This
 * DNM: Does Not Meet
 * NAI: Not an APOLLO Issue
 * System Requirements
 * 3.1.1.1 Persistent User Accounts
 * set up standalone LDAP server?
 * Needs investigation
 * *FRR*
 * 3.1.1.2 Admin Accounts
 * *FRR*
 * Tie into LDAP group or flags?
 * Should open up different functionality (create workflows, etc...)
 * Create an interface to LDAP administration as an optional module NTB
 * 3.1.1.3 Automated password retrieval
 * FRR -- how do LDAP servers handle this?
 * 3.1.1.4 Listing digital assets
 * ADT. Including thumbnails
 * 3.1.1.5 persistent archive of assets
 * ADT. Assets can be stored on server.
 * 3.1.1.6 Database to store XML
 * ADT -- native XML database support
 * NTB: finish XStreamDB EOAdaptor
 * 3.1.1.7 Online Accessibility
 * ADT -- it's a web app
 * 3.1.1.8 Internet Delivery
 * ADT -- web based content
 * NTB -- templates and finished presentations need to be internet friendly
 * 3.1.1.9 Performance
 * ADT
 * 3.1.1.10 Easy to install authoring environment
 * NTB -- installers for APOLLO and WO
 * Planning on doing this anyway for APOLLO by October
 * 3,1,1,11 Authoring envionment should be platform independent
 * FRR -- investigate database options and connections with existing systems on various platforms
 * 3.1.1.12 Open Source
 * ADT
 * 3.1.1.13 Authoring env. will be implemented in free, open source platform
 * May be mitigated by deploying on Tomcat/JBoss with embedded "free" WebObjects license
 * Perhaps this requirement is overstated -- modify this to "can be" or "at low cost"
 * DNM
 * 3.1.1.14 Robust
 * ADT -- needs more testing
 * 3.1.1.15 Delivery in multi*modes
 * NTD -- keep in mind for publishing model
 * 3.1.1.16 Can return to saved work-in-progress
 * ADT
 * NTD: how to handle simultaneous access of project? Lock? Check in? Live sharing?
 * 3.1.1.17 Sequence of Pachyderm Screens
 * FRR -- how to define constraints on which screens can be first and which can be linked from which other screens.
 * 3.1.1.18 Publish multiple projects simultaneously
 * FRR, but minimal risk.
 * how to handle esoteric collisions -- publishing presentation A that has bits from Presentation B that is being edited at the time of publishing Presentation A...
 * 3.1.1.19 Asset regeneration -- optimize
 * NTB -- not apollo specific
 * APOLLO can handle on-the-fly generation of needed sizes etc... Part of the publishing process.
 * 3.1.1.20 Batch importing of metadata
 * this is being built into APOLLO for BC work, will be done by October
 * will be XML based
 * 3.1.1.21 Database holds rights info
 * APOLLO can hold any metadata we specify
 * 3.1.2.1 User friendly interface design
 * APOLLO supports any possible interface, html, flash, etc
 * 3.1.2.2 KISS
 * NAI -- this is a design issue
 * 3.1.2.3 Accessibility of Authoring (for disabilities)
 * javascript is not required for APOLLO, except for FUSION
 * can have two interface "faces" --- a forms based and a more "GUI" one
 * FRR
 * 3.1.2.4 Accessibility of created presentations
 * NAI -- this will be handled in publishing component
 * 3.1.2.5 Easy start of new project
 * APOLLO workflow could make this very easy & flexible
 * 3.1.2.6 Easy to enter new assets
 * APOLLO functionality not finished, in progress (?)
 * in "resource" section can pull assets from a client machine or another collection
 * FRR
 * 3.1.2.7 Metadata added and edited manually
 * ADT
 * 3.1.2.8 Transparence of asset existence
 * ADT
 * 3.1.2.9 Placeholder image for missing asset
 * NAI
 * 3.1.2.10
 * NAI
 * 3.1.2.11
 * NAI
 * 3.1.2.12
 * NAI
 * 3.1.2.13
 * NAI
 * 3.1.2.14 View a list of projects
 * NTD
 * 3.1.2.15
 * NAI
 * 3.1.2.16 Adding author information into asset metadata
 * Requirement for BC, will be done by October
 * 3.1.2.17
 * NAI
 * 3.1.2.18
 * NAI
 * 3.1.3.1 Standards based learning objects
 * ADT
 * 3.1.3.2 Use of Dublin Core metadata
 * no problem, APOLLO will support any type of metadata
 * 3.1.3.3
 * NAI -- this will be handled in publishing
 * 3.1.3.4
 * NAI -- this will be handled in publishing
 * 3.1.3.5 Standardize technical metadata
 * ADT
 * 3.1.5.1 Context sensitive help
 * NTB