Transcript Dataverse_presentation_slides

Dataverse
Software Engineering
for Better Universe
Data Management
Designed by:
Tim Cook
Gloria DeMartelaere
Andrew Yurovchak
Jeff Malone
Aron Ritchie
SRS: Tools
• Front-End : Web Site / User Interface
– CSS
– HTML
– JavaScript
• Back-End : Database / Integration
– PHP
– SQL
SRS : Group Dynamics
• Design dynamics around functionality not tool sets
– Artifact Design / Integration
• Jeff aka “Code Wrangler” or “Compiler Jockey”
• Aron
– Map Design / Integration
• Tim
• Andrew
– User Interface / General Support
• Gloria
SRS : Docs, Deployment, Risk
•
Documentation
– Help and Tutorial pages
– FAQ
•
Deployment
– Web Site
– Users must create an account
– Multiple access levels: “Super-Authority”, “Authority”, “User”
•
Risk
– Map functionality (JavaScript, Icon rollovers, Artifact integration)
– Artifact functionality (Dynamic text boxes, Search)
SRS : Use Cases
User wants to access specific Artifact information
Primary Actor: User
Scope: Searching the Dataverse
Level: User Goal
Stakeholders and Interests:
User: Wants to find a specific artifact instance and retrieve all related data.
Company: Wants multiple ways for the user to be able to find and retrieve what they are
looking for.
Precondition: User is logged into the system
Minimal Guarantee: Zero results are returned and the user is allowed to continue his
search
Success Guarantee: The user is able to find and access the specific artifact information
that they were looking for.
Main Success Scenario:
1. User: Enters topic in the search field.
2. Server: Queries the database for the topic given the users access level and their
search terms.
3. Server: Responds with a list of the closest matching artifacts.
4. User: Selects the desired data.
5. Server: Responds with the artifact page that the user requested.
SRS : Use Cases
Extensions:
1a. User doesn't know the name of a specific artifact object
The search should go through artifact descriptions as well as titles.
1b. User wants to search via a map instead of a text field.
Maps should be available via a domain home page for each specific Dataverse. These
maps will have nodes on them that link to artifact pages.
2a. The database is down, so the query will fail to return anything
This is an error on the company's end and it will need to be addressed.
2b. Illegal or invalid search terms detected in the query
User should be notified and asked to correct their query. Protection against SQL
injection should be handled on the server side
3a. No matching results are found
Prompt the user to search again. Redirect them to the map pages to attempt a visual
search.
3b. No results were found for the given access level
Respond as if nothing were found, the users don't need to know something is hidden.
4a. The user can't find the results they want under the results that were returned
The user will have to modify their query and search again or try a different approach,
such as Using a Map.
SRS : UI
Mock Ups
• Rollover
description
• Various
filters
• Map
locations
link to
Artifacts
SRS : UI
Mock Ups
• Admin
Artifact
View
• Universal
Toolbar
• closable
text boxes
SRS : UI Admin Artifact View
SRS : UI User Map View