Planing Inception - Nir-Cohen/Bishvil GitHub Wiki
Project Inception / Planning Page
This document serves us as a documentation, and a guideline to the implementation of our product, and supply a snapshot of the intended system from multiple points of view.
In this project, our team are planing to build a mini social-network web application for the lone girls.
The application help to the girls in many issues (communication, night culture, accessories donation).
- First planing with the organization.
- Project Design (features, structure, etc.)
- Division of labor between team members.
- Start Working and testing each step.
- Login & Register system.
- Add/Edit/Delete topics.
- Special design (Working with a designer)
- Admin control system.
- User Profile
| * | Risk's Type | Risk | Probability | Severity | Weight (s * p) | Risk prevention |
|---|---|---|---|---|---|---|
| 1 | Development | We do not know the development and work environment. The language is new to us. | 0.3 | 4 | 1.2 | We will learn the language on the Internet, watch videos and consult with experts in order to get ready for the project and get to know the development environment. |
| 2 | Development | The application doesn't handle with the load. | 0.7 | 2 | 1.4 | We will understand from the client before starting work the number of potential users and the number of entries he thinks the application will have. |
| 3 | Estimation | We did not correctly estimate the development time and time needed for each iteration. | 0.4 | 4 | 1.6 | We will learn the language on the Internet, watch videos and consult with experts in order to get ready for the project and get to know the development environment. |
| 4 | Technology | Lower application performance -Problems and mismatch as a result of the updated versions of operating systems. | 0.2 | 3 | 0.6 | Pushing updates to the application and improvement of the code. |
| 5 | Requirement | Customer requirements do not match the app. | 0.6 | 4 | 2.4 | We'll sit with the client for a long time on the demands for deep understanding. We will present him with an archetype after two weeks of work. |
| 6 | Resources | Financial resources are insufficient. | 0.2 | 5 | 1 | In-depth analysis of requirements and the reduction of costly transparency requirements such as graphic artist or designer. |
| 7 | Requirement | The customer change requirements. | 0.7 | 4 | 2.8 | Showing a prototype to the client for reduction and prevention surprises. |
| 8 | Technology | A complicated user interface to use. | 0.2 | 4 | 0.8 | We will discuss the interface on the interface and try to match it to the client's needs. |
| 9 | Development | We do not know the development and work environment. The language is new to us. | 0.6 | 5 | 3 | We will sit with the customer and explain that changing the requirements may lead to the application falling and that the requirements will be final and planned to the ground. |
| 10 | Development | Lack of knowledge in software that we fail to develop the functions | 0.1 | 4 | 0.4 | We will learn the language well. We will watch many videos that teach it. We will read a lot of materials and consult with experts such as the academic staff of the course. |
| 11 | Development | During the registration process, a confirmation email will be sent to the webmaster so that he will choose who he needs to approve | 0.8 | 4 | 3.2 | We hope to find content about this problem online if we do not refer to the staff of the course that guides us. |
Basic Architecture
In this project, our team are planing to build a mini social-network web application for the lone girls. The application help to the girls in many issues (communication, night culture, accessories donation).
Upload after the meeting with Bishvil organization.
- We are planing to work in Agile software development
- The project is planned to built in TypeScript with Angular2 program - web application.
- The product is explosive with a free cloud service, we choosed to work with FireBase @ google.
- We plan to share our project in GitHub and work synchronized with that tool.
- The code will be written in a predefined format which was agreed by team members.
| * | Type | Date | In Process / Done |
|---|---|---|---|
| 1 | Meeting with Bishvil Manager | 10.3.17 | Done |
| 2 | Requirements | 20.3.17 | Done |
| 3 | Finish the SRS | 10.3.17 | Done |
| 4 | Prototype | 1.4.17 | Done |
| 5 | ZFR | 10.4.17 | Done |
| 6 | Iteration1 | 2.5.17 | Done |
| 7 | Meeting with Bishvil Manager | 15.5.17 | Done |
| 8 | Iteration2 | 1.6.17 | Done |
| 9 | Meeting with Bishvil Manager | 11.6.17 | Done |
| 10 | Iteration 3 | 15.6.17 | Done |
| 11 | Testing System | 15.6.17-20.6.17 | Done |
| 12 | Final Project | 20.6.17 | Done |