Skip to content

Inception

David Recanati edited this page Apr 9, 2018 · 29 revisions

Project Inception / Planning Page

Process

We are using Agile method, Scrum:
Seperating the development into iterations, in each iteration we are going to develop one feature, test it and then send it to the client for feedback, using the feedback to synchronize the feature with the client's requirments. We will work and check our product and ask the customer for each step of development, get his opinion and change our product as the expections.

Initial Feature List

  1. The application will get input, as text or click on image and it will write or show the image on the screen.
  2. Output can be with voice and not only shown by image / words.
  3. The application should be able to work on smartphones, tablets and pc.

Initial Planning

  1. Comfortable GUI that easly can be used by everyone.
  2. Usage that solve the misscommunication that Aphasia patients have. The user insert input and the output should be shown to the partner that the user is communicating with.

Risk Management

Risk Severity Response
1 Lack of communication between team members. Medium Use both Face-to-Face meeting, WhatsApp group and online chat to communicate between the group members. Schedule at least three meeting to go over the products of each group member.
2 Project scope extends beyond course limits. High Reach complete understanding between client, project team and course management regarding expectations, abilities and project requirements.
3 Working with new tools in an unfamiliar environment Medium Getting familiar with the software tools used for development by attending classes, hands down experience, and various tutorials.
4 Change requirements Medium The client changes its requirements in such a way that shifts the timetable of the project or defines the project as not meeting client's requirements.
5 Incorrect system size assessment High Because of lack of communication between team members and the client, The system might be more complex and bigger than we thought at first.
6 Communicating with the customer Medium The customer is busy and it can cause delay on development, if the product is as expected or not. the answers can be delayed and it will influence the whole project.
7 Incorrect estimates of response time Medium Incorrect assessment of system response time due to low network performance. If the application will be too slow it will not be useful for the target audience.
8 Too many errors during testing Medium Finding too many bugs during testing can delay the termination of the current iteration in such a way that can delay the termination of the project in time.
9 Use new technology High As a result of the client reiquirements we need to create Text-to-Speech system, for now there is almagu srevice that maybe we can use us

Development

We are going to develop this product with Angular2. This type of technology will work on Smartphones, Tablets and PC's.

Tools

  1. Angular2

  2. Database

  3. Firebase (for deployment and maybe for DB services).

Deployment

We deploy are code using Google Fiarebase

Version Control

We maintain our code using GitHub system.

Coding Convention

We will use the OO coding style like in Java.

Initial Architecture

DeploymentDiagram1.0

Testing Strategy

  1. Every developed step will be tested in automated unit testing scripts.
  2. The team will write tests before writing the modules and check the modules with those tests.