This section gives a scope description and overview of everything included in this System Requirements Specifications document. Also, the purpose for this document is described and a list of abbreviations and definitions is provided.

The purpose of this document is to give a detailed description of the requirements for the “ERP & CRM” application as a whole. It will illustrate the purpose and complete declaration for the development of the system. It will also explain system constraints, interface and interactions with other external applications.

This document is primarily intended to be proposed to users for their needs and a reference for developing the different versions of the system for people interested in getting involved in an Open Source project.

We will provide UML & SysML diagrams to illustrate the product.

An ERP system, or Enterprise Resource Planning, will be developed to match general enterprise requirements in terms of resource management and most precisely in this case project managements along with assigned tasks with time consumed and agenda fields. The entire system will be linked to a CRM (Customer Relationship Management) which concentrate more on Customers and also Suppliers, dealing with Invoices, Quotes and orders.

Besides these two systems, will be implemented an accounting management system and the possibility to fill an e-commerce website which main template will also be included in the current project.

The accounting system will be opened to different accounting rules (Europe and US).

The whole system is divided in micro services applications, each one providing API access in order to be linked by Android applications and other tierce parts.

The software will need an Internet connection at all time. Docker images will be configured to deploy the services.

Term | Definition
User	Someone who interacts with the mobile and website application
Admin / Administrator	System administrator who is given specific permission for managing and controlling the system
Owner	The owner of the applications
Web portal	A web application which present special facilities to the owner
Application store	The online store where users can make purchases which will be linked to the CRM system
CRM	Customer Relationship Management system
ERP	Enterprise Resource Planning
Stakeholder	Any person who has interaction with the system who is not a developer.

The remainder of this document includes three chapters and appendixes. The second one provides an overview of the system functionality and system interaction with other systems. This chapter also introduces different types of stakeholders and their interaction with the system. Further, the chapter also mentions the system constraints and assumptions about the product.

The third chapter provides the requirements specification in detailed terms and a description of the different system interfaces. Different specification techniques are used in order to specify the requirements more precisely for different audiences.

The fourth chapter deals with the prioritization of the requirements. It includes a motivation for the chosen prioritization methods and discusses why other alternatives were not chosen.

The Appendixes in the end of the document include the all results of the requirement prioritization and a release plan based on them.