Design Document - sarahbe/-SWE573-SoftwarePractice GitHub Wiki

Introduction:

This document describes the system's component and the relation between them. In order to achieve a full description of the system UML diagrams is used.

Software architecture:

Member

The member is the main user of the system and he can have different roles as the following:

Role	Rights
Member	can add review volunteer and apply for any other role
Administrator	has more authority than member
Super User	Has full permission, and can grant a member an administrative role
Seller	a member with selling right
Stocker	a member with stocking right

The following use-case diagram illustrates each role in detail:

The structure of the users in the system is described in the following class diagram:

A new user to the system should follow these steps to be a member:

Products And Producers:

Adding a new product or producer is done by admins. The following classes are related with the product and producer elements:

Sale:

The following classes are related with sales operations:

and the sales operation is done as the following: