This page is related to the utilization of use cases and how they are build. Also contains examples of use cases and tasks related to them
A UML (Unified Modeling Language) is used in system development to visually represent the structure and behavior of a system. When a customer reaches out to a system developer to create a website, UML diagrams help in:
It ensures clear communication between the customer and developer, reducing misunderstandings and improving project planning.
Primary actor | Admin |
---|---|
Scope | Product Management |
Level | Admin |
Stakeholders and interests: |
Stakeholder 1 – Admin users can create, edit and delete product from the webstore. Stakeholder 2 – Admin users can temporarily hide store products from the webstore if a product is out of stock temporarily or is out of season and expected to return at a later date. | | | Precondition **** | - Admin user needs to be logged in to manage store products. - Admin user needs certain privileges to manage store products | | Main success scenario: - (når alt går godt) 1. Admin user successfully logs into the site and creates a new store product 2. Admin user successfully logs into the site and edits a store product 3. Admin user successfully logs into the site and deletes a store product | | | Extensions: - (Hvad kan gå galt og hvordan vil systemet svare?) 1. Admin user logs into the site but is unable to access admin panel where products can be managed -> user is missing privileges to access the admin panel 2. Site unreachable – server error / client error / code error | | | Non-functional requirements: - (kvalitetsfaktore) NF1 – Site load speed is below 4 seconds on specific example device NF2 – 100 users can browse and use the site simultaneously NF3 – Admin users can make changes to the webstore live | |