Inception Planing

The working team is of six students going for computer programming. At the beginning of the development process we will work as a full team. In addition we will plan the timetable.From then on, the rest of the development process will be carried out singly or in pairs.

Risk Management:

The risks which could arise are: 1. Misunderstanding of the customer requirements. 2. Change of customer requirements - additions and last minute changes. 3. Security issues. 4. Display compatibility issues. 5. Failure in meeting the timetable.

How can reduce/deal with them?

First, we will sit down with the customer and make sure that we fully understand what his requirements. We will verify with him the requirements and in addition, explain to him that our time is short and changes / additions during the project can be a problem and he may have to be flexible about his requirements. We will build a primary product (prototype bases) to get the costumer's feedback . In order to deal with the risk of not meeting deadlines - we will plan the schedule in advance with providing small extra time for each task - to enable a small delay in time without changing the deadline. We will set meetings of the team members to assess the progress of the project and to avoid integrating small parts problems. We will solve the problem of security through secure purchase so that the customer can buy without fear of exposing their personal information.

Built of product:

The product is designed as a web application.

we need more specific information from the customer for this part.

Technologies: Client-side: HTML, CSS, JS, ANGULAR, JQ, BOOTSTRAP Server Side: NODE.JS data base: SQL SERVER

Work Environment:

Distribution of application: using heroku.com

Code sharing through github.com

Planning and preliminary evaluation: 1.Characterization of the system according to customer requirements 2.Dividing project into tasks and dividing it within the team 3.Building the data-base 4.Preliminary design of system 5.Building system functionality 6.Validation of the application 7.Correction of issues found during testing. 8.Meeting with the customer and the final corrections of the project. 9.web application is ready to use!!!!:)