Skip to content
elile edited this page Jan 22, 2013 · 46 revisions

Frequent Buyer.

Welcome to Frequent Buyer wiki page!

Project

FREQUENT BUYER Vision

Our vision is to give every business owner the opportunity to publish and promote the business with the most modern tools, and to give the client the chance to join and enjoy an interactive membership card.

Frequent Buyer - Project Stages

Frequent Buyer - Documents Project

Frequent Buyer - Project Team

  • Mr. Yuval Zargari
  • Mr. Eli Levi
  • Mr. Eitan Nosraty
  • Mr. Yoav Fuchs

Team Values

אנו כיחידים וכקבוצה שואפים ללמידה, התפתחות, ומצוינות ביצועית. אמונים על ערכי תקשורת, הוגנות, ושיתוף פעולה פורה בין חברי הקבוצה שיובילו להשגת המטרות המשותפות לאורך כל שלבי הפרויקט.

Frequent Buyer - Sponsors and Customers

Our product may interest restaurant business owners such as: Bars, Coffee shops and Restaurants.

Our client is : Nir Levi

Planned Way Of Work

The way of work between the team members is going to be through e-mails and setting up group meetings as needed. In any sort of question we will contact and ask questions through "piazza" and "github".

Frequent Buyer - Technical Solution

The application will develope by the team with compatible to Android OS and suit tools.

The application uses the Internet.

שיטת הפיתוח

תכנון והערכה ראשוניים

• Decide about prefer project, give a name and write the offer.

• Decide about prefer develope process in the team.

• Define base classes and extra classes.

• Define Architecture for the system.

• Define seperate modules in the code.

• Devide the mission based on the modules to the team members.

• Cooperate in the integration and coding between the modules.

• Execution the modules after the integration and build the system.

• Test the system and install on different devices.

Risk Management

Risk 1: Write in unknown environment.

Solution 1: Start coding ASAP.

Risk 2: Implement remote control, enable HW devices without previous experience.

Solution 2: Check the coding as first step, before writing the specific imlement as require in the system.

Risk 3: Missed the time allocation of the course because project too big.

Solution 3: Define base classes and extra classes that will implement in the project based on the available time.

רשימת מאפיינים

מאפייני האפליקצייה מתחלקים ל2 - בעל עסק ולקוח ואלו המאפיינים של שתיהם:

• כרטיסיית הנחות - זמן עד להנחה הבאה

• אירועים

• הודעות מהמנהל

• מבצעים

בעל העסק יוכל לעדכן מאפיינים אלו הלקוח צופה במאפיינים אלו

Clone this wiki locally