User Requirement - en
User Requirement - en
User Requirement - en
Versione 1.0
Venerd 15 Luglio 2011
TELEFONO
WEB
Ivano Pezzoli
User Requirement
Riferimenti ..................................................................................................3
Versioni Documento........................................................................................................................3 Definizioni e acronimi......................................................................................................................3 Riferimenti a documenti..................................................................................................................3
Scopo del documento...................................................................................4 Project phase ..............................................................................................5 Schema Progetto..........................................................................................6 Schema Base Dati.........................................................................................7 Back-end Web .............................................................................................8
Description......................................................................................................................................8 Autentication and Users Managemen Module..............................................................................8 Administrators.................................................................................................................................9 Agents.............................................................................................................................................9 Characteristics of Authentication and User management module...............................................9 User interfaces ...............................................................................................................................9 Users reserved area .......................................................................................................................9 The administrative interface protected.........................................................................................10 Content management ..................................................................................................................10 The data relating to contracts ......................................................................................................10 Le conditions.................................................................................................................................11 Kind of offer..................................................................................................................................11 Duration of the royalties...............................................................................................................11 Frequency of payments.................................................................................................................11 Payment........................................................................................................................................11 Administrative costs......................................................................................................................11 Type of property / Producer..........................................................................................................12
User Requirement
Riferimenti
Versioni Documento
Ver. 1.0 Elabora (UO) I. Pezzoli Verifica (UO) Approva (UO) Data emissione 15/07/2011 Descrizione delle modifiche Nascita del documento
Definizioni e acronimi
Definizione/Acronimo WSDL XML ASCII Descrizione Web Services Description Language eXtensible Markup Language American Standard Code for Information Interchange
Riferimenti a documenti
Definizione/Acronimo Descrizione
User Requirement
User Requirement
Project phase
nothing
User Requirement
Schema Progetto
nothing
User Requirement
User Requirement
Back-end Web
The project requires the construction of a website back-end managed by staff Customer, which contains all the contents of the app front-end users and administrators and agents. The back end will be built with web technology and will rely to a relational database. Currently, the strategic choice, given the dynamics of the software world, leads us to think that you will use technology based on HTML5 and jQuery, MySQL database. Key features are the modularity and scalability of the product. The modular design allows you to add features to the product, depending on the demands from specializing. The key points of the project will, in fact: Split the program into individual modules, Independence of the modules together, Minimal interaction of each form with the outside world, Easy testability of modules such as isolated entities, Explicit and simplification of interfaces through which modules communicate with each other.
The scale will give capability, the system developed to "grow" or "decrease" (increase or decrease the scale) depending on needs and availability.
Description
The back-end software will be the real heart of the system and will be developed so that there are two well-defined and different macro-areas: 1- Autentication and User management 2- Content Management Application
User Requirement
Administrators
Are those who have permits management of users. They can access the restricted area and make any necessary changes to the maintenance of content.
Agents
Are those who can only enjoy access to their area and use the content provided by administrators.
User interfaces
Consist of a link, visible in a web pages of the site (page of login), with which users can log in to your area. Registration In order to be activated a restricted area you must be a user with administrative rights to create a "profile" by including data and references in an appropriate form. Once you submit the registration request, the system will check if the customer is already registered or not. In the first case, the super user is notified that his name is already present in the archive and asked to verify or change the user user name. In the second case, the registration is accepted and the user receives an email address given during registration, with the password (generated automatically) that allows you to log in to his private area. This step is important to comply with the law and ensure the utmost respect for privacy and to avoid fraudulent registrations; Login You can access the reserved area by entering the email address during registration and password received at his email address. The email address used during registration is also used to retrieve your password, if it has been forgotten.
Change of personal data Any time the customer can change his entire registry with the exception of your password. For safety reasons and to protect the confidentiality of the user that the password change should be explicitly required to the site manager.
9
User Requirement
The administrative interface protected
Will be developed to allow the use of: an authentication module with username, password and password recovery for protected access; an archive of the User Reserved Area members; two modes of consultation of the archive as "list names" and "Search Names"; This mode is useful to search for specific names or filter a particular category of students.
In addition there is the possibility of: edit the registry manually and delete subscribers; manually add names;
Content management
By accessing the private area with profile management will be able to manage and maintain the entire contents of the app. On the form you can define, for each agent: The data relating to contracts The conditions Kind of offerts Duration of the royalties Frequency of payments Payments Administrative costs Type of asset / Producer
Will be able to manage individual items listed for each individual agent, or to groups of agents.
10
User Requirement
Le conditions
Inserts the list of conditions that can be associated with a contract. Example: 1- Condizioni C.SP 2- Partner
Kind of offer
Inserts the list of offers that the agent may have: 1- New request 2- New offer 3-
Frequency of payments
Inserts the list of the frequency of payments that the agent can offer. You can enter, for example: 1- monthly 2- quarterly 3-
Payment
Inserts the list of payment methods that the agent can offer. You can enter, for example: 1- Bank transfer 2- RID 3-
Administrative costs
Inserts the list of administrative expenses that the agent can offer. You can enter, for example: 1- no cost
11
User Requirement
2- 1,00 3- 2,00 4- 5,00 5-
12
User Requirement
The app will also handle the negotiation with the client. Provide the ability to find information on the conductor, edit or insert. example:
13
User Requirement
The search function operates on data that are present on the local db and helps you locate information on clients already managed by the agent. Pressing the "Next" button beside the correct name, you can work with data of the selected customer. The application will allow you to select and complete the "Conditions of Contract". example:
The application will allow you to select the "Data Base" to complete the offer. example:
14
User Requirement
Entered the "purchase price", you can press the "Calculate". The result of this operation is as follows:
Form will be made in the calculation of the fee by multiplying the purchase price for the coefficients defined above. By following the following formula: Coefficient x purchase price. Any duration (in months) of different coefficients that determine the value of the rent.
There is also a form that allows you to manage the types of property including split the funding requested.
15
User Requirement
The imputing different values for different products. By the APA. You can enter data for new objects that will populate the fields "Type of property" and "Manufacturer".
At the end will be saved on local database, the data for each operation.
The offer will be sent as an attachment to an e-mail with a lot of documentation containing data and the logo of the contract if the agent added.
Archive Area
The area will be available and will allow the agent to be able to read all the information concerning the activities carried out close to its customers. The research will be performed on data in the local database. You will have a search form like this.
16
User Requirement
The agent can also insert its own logo. for example:
17
User Requirement
18
User Requirement
Added Module
nothing
19
User Requirement
20
User Requirement
Definizione tempi
nothing
21