Skip to content

inception

Jump to bottom
sarah-hoter edited this page Apr 3, 2016 · 22 revisions

Project Inception / Planning Page

Process

Scrum is an agile way to manage a project, usually software development. The primary artifact in Scrum development is, of course, the product itself. The Scrum model expects the team to bring the product or system to a potentially shippable state at the end of each Scrum sprint.

Within agile development, Scrum teams are supported by two specific roles:

SCRUM Diagram

The first is a ScrumMaster, who can be thought of as a coach for the team, helping team members use the Scrum process to perform at the highest level.

We will chose the most expert in the technology that we will use.

The product owner (PO) is the other role, and in Scrum software development, represents the business, customers or users, and guides the team toward building the right product.

We will choose the student who is the most frequently customer in resturants to represent the product owner.

Initial Feature List

  1. Chose a restaurant. (nice to have)
  2. Order a table. (mandatory)
  3. order a dose from the menu (mandatory) – enable options: a. First courses b. Middle / Main courses c. Kids courses
  4. Order a dose from business menu
  5. Order deserts (mandatory)
  6. Order drinks (mandatory)
  7. Call a waiter (mandatory)
  8. Checkin (mandatory)

**Note: because our planning can be complex, we won’t do the features that defined as nice to have. If we'll have the time, we will do it at the end. **

Initial Planning

  1. Build a mockup and main processes.
  2. Divide roles
  3. Build application using - 3 design model
  4. Check bugs
  5. Deployments and version control

Note: we need to reorganize the initial planning by scrum methodology

Risk Management

Risk Level of effect Probability Avoidance steps Alternative plan
1 incorrect division
between the developers		 Medium High perform an intelligent division.
(will be the scrum master according
to the scrum methodology)
2 Security payment through the app High High the payment will be made
directly with the waiter
3 Outdated information of a list of
restaurants, menus and prices		 High Medium Frequently updating the list of
restaurants, menus and prices
4 Dynamic and frequently changes in uses tables. High High Get this data by resturant service
5 Lack of time for completing development Medium High Minimized the mandatory capacity.
The features rated as
mandatory / nice to have		 Splitting the work within the group depending on their knowledge
6 Unstable Web Service Low Low Test our software and take good care of exceptions handling

Development

Using css, html ,javascript for client side Using ASP.Net with MVC technology for server side Converting to ios / android.

Tools

Deployment

We used Google App Engine because it's easy to create, easy to maintain, and easy to scale as our traffic and data storage needs change. With App Engine, there are no servers to maintain. We simply upload our application and it’s ready to go.

Version Control

The Git feature that really makes it stand apart from nearly every other SCM out there is its branching model.

Git allows and encourages to have multiple local branches that can be entirely independent of each other. The creation, merging, and deletion of those lines of development takes seconds.

Coding Convention

Naming Conventions

We use the same naming convention for all code:

  • Variable and function names written as camelCase
  • Global variables written in UPPERCASE (We don't, but it's quite common)
  • Constants written in UPPERCASE

Spaces Conventions

  • Always put spaces around operators ( = + - * / ),
  • Don't use spaces in the end of a line

Readability Convention

  • avoid lines longer than 80 characters.

Initial Architecture

Architacture Diagram

Clone this wiki locally