1 / 15

Team Spannabe srs / hci presentation

Team Spannabe srs / hci presentation. Presented By: Nathan Folkert, Benjamin Fagin, Anthony Marley, Spencer Border. basis. The International Etruscan Sigla Project is attempting to modernize data archival and retrieval system.

kacia
Download Presentation

Team Spannabe srs / hci presentation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Team Spannabesrs/hci presentation Presented By: Nathan Folkert, Benjamin Fagin, Anthony Marley, Spencer Border

  2. basis • The International Etruscan Sigla Project is attempting to modernize data archival and retrieval system. • Based on the requirements presented to us, we have created a Software Requirements Specification and HCI prototype.

  3. Needs • The previous system was inadequate to handle the large amounts of incoming data on Etruscan sigla. • Additional features such as online access and the ability to cross-search sigla were desired.

  4. Functionality • To facilitate the researchers in their various tasks including: • Searching • Comparing • Storing • Citing • To provide an efficient way for the researchers involved in the IESP to research and communicate data

  5. Preliminary definitions

  6. User characteristics • The primary users of the system will include: • Contributors • Researchers • Students • Secondary users include: • Public Users

  7. Functional Requirements 3.1 The system shall store text data. 3.2 The system shall store images and drawings. 3.3 The system shall store epigraphs. 3.4 The system shall allow researchers to create entries. 3.5 The system shall allow researchers to modify their own non published entries. 3.6 The system shall number entries with unique key.

  8. Functional Requirements 3.7 The system shall make researchers log in to the system for authorized access. 3.8 The system shall allow researchers to create comments. 3.9 The system shall allow the public to view the collection. 3.10 The system shall allow researchers to mark entries as: private(incomplete), protected(under peer review), public(published). 3.11 The system shall enable a researcher to provide protected access to ones data for other researchers.

  9. Functional Requirements 3.12 The system shall allow researchers to tag an entry with a keyword. 3.13 The system shall generate citations for entries. 3.14 The system shall allow only the system administrator to modify entries after publishing. 3.15 The system shall allow researchers to create collects of entries. 3.15.1 The system shall allow researchers to modify their collections.

  10. Functional Requirements 3.16 The system shall allow the administrator to modify contributors accounts. 3.17 The system shall provide graphical annotation for artifact images. 3.18 The system shall provide detail data for the entries.

  11. Nonfunctional Requirements 4.1 The system shall allow for secure log in for researchers and system administrators. 4.2 The system shall provide an intuitive user interface. 4.2.1 The system shall provide an easy to use data entry form for researchers. 4.3 The system shall provide persistent storage of all data. 4.4 The system shall provide support for multiple languages.

  12. Nonfunctional Requirements 4.5 The site shall have a consistent format. 4.6 The site shall be coded in a uniform software language. 4.7 The site shall be usable in multiple browsers.

  13. use case diagram

  14. Class diagram

  15. for the future: • Design the system in SE 2 • Design machine learning algorithm for siglum identification. • Pass ownership to the IESP group • Begin populating with existing sigla data • Discover new relations between sigla!

More Related