1. The Gordian Atlas Elaboration Phase #3

2. Vision Unchanged. Vision Restated: To take a new look at our past by presenting historical information in a novel new way – an online collaborative tool featuring world class multimedia tools and user interactivity. Think Wikipedia meets Google Earth!

3. Scope Has been modified to fit the realities of deadlines, skill sets, and manpower. The following have been declared out of scope for the first product release: Multiple timelines: Instead, the system is operating with a single compulsory timeline. Multiliple languages: The infrastructure was developed with international use in mind, allowing it to deal with other language options; however it is currently fixed to English. Full Search, Tagging and combining elements in soft timelines: Will not be used at this time.

4. Domain Model Unchanged.

5. Data Model / Schema Gordian Config has been replaced by Gordian State, a custom library. Otherwise, no real changes to the database schema or Domain model at this time. Permissions will be revisited. Currently working with a single group.

6. Use Cases this iteration Over the course of iteration 3, the following use cases have been implemented using Code Igniter models login: is functional. This was a big deal and influenced the course of the project. Edit User: functional Gordian Setup in progress for next iteration.

7. Additional Use Cases The “Donate to Atlas Site” use case is conceived and ready for development in the next iteration. Some necessary groundwork has been laid and mockups of donations payed through PayPal have been drawn up. The “System Setup” use case is well underway, if not functional by this time.

8. Donate to Atlas Main Success Scenario: 1. Client donates the Gordian Website 2. Client select the payment method 3. Client enter personal information 4. PayPal confirmation (Thank to client)

9. Donate to Atlas (SD) Client/PeopleGordianAtlas System-PayPal Use credit card/PayPal/ Select Amount Enter Billing Information Confirmation/Thank you Donation

10. Donate to Atlas (SSD) ClientGordian Admin-PayPal Donation Select payment method Confirmation/Thank you Client’s billing information

11. System Setup Name Setup the Gordian Atlas [SETUP01] Scope Initial Administrative Function Level User Goal Primary Actor Administrator Stakeholders and Interests n/a Preconditions 1.A web accessible URL via HTTP has been made available via some hosting method. a.optionally but strongly encouraged, relevant user accounts for mySQL and HTTPD access have been setup if desired. b.optionally but strongly encouraged,.htaccess or equivalent technology has been enabled to allow for URL rewriting. 2.The source code for the Gordian Atlas has been extracted to a web accessible directory. 3.The database schema has been setup via phpMyAdmin, console access, so forth. 4.Appropriate configuration changes have been made to the /application/config/database.php and /application/config/config.php files to properly point to all appropriate files for the CodeIgniter framework. 5.The gordian atlas setup routine has not been run previously before.. Postconditions 1.The initial administrative user has been created. 2.The initial group and timeline have been created. 3.The administrative user created in #1 is the owner of the elements in #2 4.The website is ready for normal usage. Main Success Scenario 1.The site administrator access any URL mapped to the goridan atlas. (e.g. http://testatlas.com/) 2.The system hook detects lack of configuration and forwards the user to http://www.testatlas.com/setup/ 3.Admin agrees to license and welcome message 4.The Atlas responds with account setup UI 5.Admin fills in default login information for account. 6.The Atlas responds with default Timeline setup UI 7.Admin fills in default timeline information 8.The Atlas sets up supporting group and timeline information. 9.The Atlas stores essential configuration details 10.Admin is forwarded to Admin control Panel 11.Admin toggles system activation

12. System Setup Extensions 1.Admin rejects license a.Setup fails to proceed with user notice. 2.Admin provides invalid account information a.Atlas re-affords setup UI and requires acceptable information. 3.Admin provides invalid timeline information a.Atlas re-affords setup UI and requires acceptable information. Special Requirements n/a Variations in Technology and Data 1.The configuration details described in #9 of the success scenario may eventually be moved to a flat file rather than a database, as one off information technically doesn ’ t belong there. Frequency of Occurrence Once and only once. Miscellaneous

13. System Setup (SD)

14. System Setup (SSD)

15. Glossary Additional terms Gordian Auth The custom authentication component backing the functionality of the user / view / group / timeline quadrinity. Godian Assets A custom HTML asset management engine that loads CSS, Javascript and assorted linked components on the fly, also underpins some essential UI features in development. Most current version always available via the project wiki.project wiki

16. Domain Rules Unchanged.

17. Software Architecture CodeIgniter, as our project’s framework, has been working much better than CakePHP, and the Software Architecture Document has reflected these changes since the decision to drop CakePHP was made. We continue to work our way up the learning curve in using this new framework and feel that it will suit this projects needs for development beyond the first product release!

18. Discussion Thank you for your time. If you have any questions, please feel free to ask. Or see the project wiki and repository for additional information.project wikirepository The currently developed Gordian Atlas is live at gordianatlas.com