Vision Statement
To create an online database that showcases the collection of artifacts at the Rock Hall Museum, providing a unique opportunity for people all around the world to experience the wonders of history from the comfort of their own homes. Our platform will allow people to browse through a wide range of artifacts, each with its unique story, and learn about their historical significance. We aim to create a space that is not only informative but also interactive, allowing users to engage with the collection in a way that brings history to life. By leveraging technology, we strive to make the rich history of the Rock Hall Museum accessible to everyone, regardless of their location or ability to visit the physical museum.
Motivation/Opportunity
The motivation behind this database is to share the beauty and history of the Rock Hall Museum’s collection with the world and make it accessible to all. The database is being created to solve the problem of any limited access to the collection. The platform will provide an opportunity for people all over the world to explore the museum’s collection, learn about history and culture, and appreciate the artifacts from the comfort of their own homes. Although off-the-shelf or open-source products may be available, our product will be unique in that it is designed specifically for the Rock Hall Museum and its collection.
Problem Statement
| The problem of… | Any limited access to the Rock Hall Museum’s collection of artifacts due to geographical or other constraints. |
| affects… | a wide range of individuals, including Stony Brook University students and faculty who may be interested in the museum’s collection but are unable to visit due to scheduling conflicts or distance as well as individuals outside of SBU that are interested. |
| The impact of which is… | An increased access and engagement, leading to a greater appreciation for the value of history and culture. |
| A successful solution would be… | An online database through the use of Figma and Filemaker Pro |
| For… | anyone interested in history, culture, and art, including students, faculty, researchers, and individuals who cannot physically visit the museum. |
| Who… | May be tourists, archeologists, or just individuals interested in the broad history of 18th and19th century Rock Hall Museum |
| Our System… | The envisioned system is an online database that showcases the Rock Hall Museum’s collection of artifacts, providing an immersive and interactive experience for users to explore and learn about the historical and cultural significance of each artifact. |
| That | Allows users to search for any particular artifact, as well as view the year, type, condition, as well as a description of said artifact. It also allows for faculty of the Rock Hall Museum to log in, add, or delete artifacts of their choosing on the database. |
| Unlike | The British Museum’s online database, the Metropolitan Museum of Art’s online collection, and the Louvre’s online collections. |
| Our Product | is specifically designed for the Rock Hall Museum’s collection,offering a focus on the historical and cultural assets of the Rock Hall Museum |
Users: Rock Hall Museum faculty as well as anyone interested in history, culture, and art, including students, faculty, researchers
Feature List: A user-friendly interface for easy navigation and exploration, quality images of each artifact with information about their historical and cultural significance, and the ability to search and filter the database by name, year, or type. In addition to Rock Hall Museum staff members being able to add or delete any artifacts they please.
Constraints: The constraints in creating a solution to the limited access to the Rock Hall Museum’s collection of artifacts include the need for a secure and reliable platform, and sufficient resources for the development and maintenance of the online database. The product used FIlemaker Pro, which allowed for a 45 day free trial.
Use cases
Use Case 1: Searching for an artifact
Identification: Users of the online database for the Rock Hall Museum’s collection of artifacts will have the ability to search for specific artifacts by filtering their search results based on what they’re looking for. This feature will allow users to easily and accurately find the artifacts they are looking for based on their specific interests and criteria, making the search process more efficient and user-friendly.
Primary Actor: This feature of searching for artifacts would be available to all users of the online database for the Rock Hall Museum’s collection of artifacts, including students, faculty, researchers, and individuals who are interested in exploring and learning about the collection.
Stakeholders and Interests: The users should be able to search for an artifact based on preference of what they’re looking for with any particular name, year, or type.
Preconditions: The user needs to be sure of what they’re looking for, specifically inputting the correct name, year, or type otherwise the database output would come out as null.
Postconditions: Once preconditions are met successfully, the user will be displayed a list of artifacts based on their search criteria and will then select the artifact of their choosing.
Main success scenario: If the user meets the preconditions they will be able to select the artifact of their choice.
Extensions and alternative flows: If the user fails to input the correct preconditions, they will be met with an error message displaying “No results found”.
Open Issues: If any issues arise from the search function, the steps taken to correct it would be to delete said artifact and readd it
Use Case 1.1: Administrator login
Identification: For the purposes of adding an artifact to the database, that option will be allowed specifically for Rock Hall Museum staff members. In that case, faculty will be allowed to do so under the pretense that they create an administrative login. Once this login is created, the admin will be able to add an asset to the database
Primary Actor: The primary actor in this case would be the administrator.
Stakeholders and Interests: The administrator should be able to input and save artifact information into the system.
Preconditions: The admin should input all necessary information into the database
Postconditions: Once stated preconditions are fulfilled, a message will display on the console stating that the asset is successfully added
Main success scenario: If the admin follows all conditions, the artifact should be added to the system
Extensions and alternative flows: If the admin fails to accurately input the information or misses something, a message stating “There was a problem adding the asset, please try again” will display on the console.
Open Issues: If the admin enters wrong inputs then the system will simply not accept it
Use Case 1.1.1: Deleting an artifact
Identification: Upon completing the steps discussed in use case 1.1, the user will be given the option to either delete or edit an artifact. In this case, deletion will be discussed and the feature allows for admin users to select and delete in artifact of their choice
Primary Actor: The primary actor in this case would be the administrator.
Stakeholders and Interests: The user will be able to select and delete an asset in the system.
Preconditions: The admin should input all necessary information into the database so they can accurately select and delete the selected artifact as well as make sure the selected asset is indeed the correct selection
Postconditions: Once stated preconditions are fulfilled, a prompt will display on the console asking the user if they are sure they wish to delete the artifact to which they will then confirm that the selected asset is the one to delete
Main success scenario: If the admin follows all conditions, the artifact should be deleted in the system
Extensions and alternative flows: If the admin fails to confirm that the selected asset is the correct one then the system will not delete the asset
Open Issues: If any issues arise, the database will not update it and the selected artifact will not be deleted