Skip to content

inception

Jump to bottom
Avia Cheriker edited this page Apr 20, 2017 · 27 revisions

Project Inception / Planning Page

Process

Our developing method is a combination between the waterfall-model and scrum.

The project's steps will be executed by the waterfall method while the implementation will be executed by scrum. In the first step we gather and understand exactly what the customer wants from the system and make requirements document. In the second step we plan the system and its performance by creating a prototype. The development process itself consists of sprints. Duration of each sprint is two-three weeks. All sprint incluses mini product development so every sprint do a little from the beginning to the end. Every sprint includes: requirements, planning, implementation, tests, launching of the product to the customer. Every two-three weeks we should show something. Detail about this in "Main assignments".

The reasons for this development method are:

  1. Customer requirements are clear in advance.
  2. People and the communication are more important to us than processes and tools.
  3. Working software is more important to us than full documentation.
  4. Cooperation with the customer is more important to us than contracts and negotiations.
  5. Rapid response to change is more important to us than following a detailed plan.
  6. Our team is diverse.
  7. Our team work teamwork so that everyone will do anything.

Initial Feature List

  1. Design form of requests for certain events for the Jewish community.

  2. Creating chat for every 10 Jewish community contributors by a certain event.

  3. Data retention of every 10 Jewish community contributors in every city in database.

  4. Data retention of certain events for the Jewish community in database.

  5. Time management for a particular event- The amount of time budgeted to close the event should be determined

  6. Setting up a staff member that takes responsibility on the event as director of the event.

Initial Planning

Our Calendar - A common calendar updated by any staff member.

Main assignments:

  1. Requirements- This step includes a meeting with the client and writing a primary detailed requirements' document and test cases. Estimated Duration: 1 week.

  2. Prototype- This step includes producing a prototype, afterwards a meeting with the client and if required- writing an updated requirements' document. Estimated Duration: 2-3 weeks.

  3. Planning- This step includes breaking the whole project into small tasks and planning the schedule, including setting deadlines for each task. Estimated Duration: 1-2 weeks.

  4. Implementation- This step will be divided to 2-3 sprints, while in the end of a sprint we have a working application. Every sprint starts by creating tasks and dividing them among the staff members, continues by working on the task and testing the application, and is ended with a meeting with the client (if necessary). Estimated Duration: 7-8 weeks.

  5. Testings - This step includes testing the application, perhaps also letting people to try it. Estimated Duration: 1-2 weeks.

  6. Changes - If necessary, this step includes making some changes in the application according to the conclusions of the testing step, and also new testings. Estimated Duration: 1-2 weeks.

  • During each step, we make tests.
  • There might be some unexpected meetings with the client.
  • Updates will be added to the common calendar and to the following table.
  • The time that we estimate for finishing the project is shorter than the time that we got for it.

Working Status

# Type Date In Process / Done
1 Meeting with Ben 16.3.17 Done
2 Requirements 24.3.17 Done
3 Meeting with Ben 26.3.17 Done
4 Presenting the SRS to Yaakov 28.3.17 Done
5 Fixing the SRS 30.3.17
6 SDS 2.4.17 In process
7 Prototype 9.4.17 In process
8 ZFR 22.4.17 In process

Risk Management

# Risk's type Risk Probability (P) Severity (S) Weight (P*S) Treatment / Prevention plan
1 Resources project's budgeted resources (like money) are not enough. 2 5 10 Making a ballpark for the project and preparing contingency plans in case that it reduced.
2 Requirement The application doesn't meet the customer's requirements. 4 5 20 Showing a prototype to the client for reduction and prevention surprises.
3 Requirement The customer change requirements. 1 4 4 Showing a prototype to the client for reduction and prevention surprises.
4 Technology Lower application performance –Problems and mismatch as a result of the updated versions of operating systems. 2 3 6 Pushing updates to the application and improvement of the code.
5 Technology A complicated user interface to use. 2 4 8 Feedback and discussion group about the interface.
6 Estimation Development time estimates were wrong. 4 5 20 Setting properties and basic features to the Publish of the application and adding the missing after the exit.
7 Development The customer change requirements 1 4 4 Division of roles for couples so that, if one leaves will be who replaces him.
8 Development The application doesn't handle with the load. 3 4 12 Finding out the maximum number of users that the client wants to be online simultaneously and taking a large measure of expected.
9 Development Lack of knowledge in software so that we can't implement features. 5 5 25 Reading online materials and consultations with experienced people.
10 Development Unfamiliarity with the development environment. 3 3 9 Reading online materials and consultations with experienced people.

A main risk that does not depend on us:

Platform that does not support the app - If we turn the project into an application, IOS may not support the application because it is intended for a closed group (10 people) and not open to the entire population.

Development

Tools

Angular2

Deployment

This project will by distributed via:

  1. Firebase
  2. https://www.heroku.com/

Code Sharing

We are going to use GitHub hosted git repository in order to share our application code.

Coding Convention

https://github.com/airbnb/javascript

Basic Architecture

  1. General Use-Case: General Use-Case
  2. state diagram 1: http://www.siz.co.il/my.php?i=3dqe2n5m5yyy.png
  3. state diagram 2: https://srv214.gif.co.il/images/4570622.png
  4. state diagram 3: https://srv214.gif.co.il/images/997543.png
  5. state diagram 4: https://srv214.gif.co.il/images/2574914.png
  6. state diagram 5: https://srv214.gif.co.il/images/502935.png
  7. state diagram 6: https://srv214.gif.co.il/images/3863846.png
  8. state diagram 7: https://srv214.gif.co.il/images/2962997.png
  9. state diagrams 8+9: https://srv214.gif.co.il/images/2345828_9.png

Development

We are going to develop the application using HTML for the structure, CSS for the design of the app, JavaScript for the functionality, use Angular an MVC JavaScript library for Client Side and Firebase a web application platform with tools and infrastructure designed that will help us build high-quality app. Also we need to keep the data of the application in a database.

Testing Strategy

e.g., we will write a manual acceptance test script for every major use case and automated unit tests for core functionality.

Clone this wiki locally