1. Main Product Features

---

Introduction Document Goals

According to the use cases we described on the Use Case page before, we'll build a guideline scheme for our project.

This Document will describe the system architecture. The goal of the design page is:

• Preparation for the realization of our software.
• Help us to split the tasks of the implementation between team members.
• Checking correctness of software design.
• Save coding cumbersome
• Realizing preparation clearly code
• Focus on the developments we should think about in advance before we start coding.

2. Architecture Diagrams

---

3. Class Diagrams

---

4. Risk Management

	Description of risk	Owner	Possible impact	Prob %	Impact (L,M,H,VH)	Mitigation plan / Contingency plan
1:	Client lack of confidence in his desires and needs	Project Manager	Customer dissatisfaction	85%	H	start with very clear work plan and write a program as modular as possible to enable future changes easily. Also, we'll create a prototype to present to the client as soon as possible
2:	New Technology	All Programmers	Development problems	70%	VH	Take an online Mean course Build Prototype
3:	The client will want to add some features during the code writing	PO	Depending on the number of requests and their complexity - reasonable requests should not create a problem, and complicated requests may create a tight schedule and may cause a delay	60%	M	Before starting the project we will ask you for all the features that the customer is interested in
4:	Time Shortage		Product quality	Project Manager	40%	H
5:	The project's team will not be able to create communication between the website and the database	All Programmers	Delay or even cancel less important features	25%	VH	Giving maximum attention to solving the problem
6:	Machines Breaking	All Programmers	Delay in schedule	10%	L	Back up all data & progress in GitHub