Search4Yummy
Final Project Report
Version 1.0
Revision History
Date
|
Version
|
Description
|
Author
|
2011-12-03
|
0.1
|
Initial Draft
|
Muhammad Sulyman
|
2011-12-20
|
0.2
|
Introduction, Requirements and Financials Added
|
Muhammad Sulyman
|
2011-12-27
|
0.3
|
Experiences Added
|
Muhammad Sulyman
|
2012-01-03
|
0.4
|
Requirements Updated
|
Muhammad Sulyman
|
2012-01-10
|
0.5
|
Milestones Added
|
Muhammad Sulyman
|
2012-01-11
|
1.0
|
Work Hours added, Review
|
Muhammad Sulyman
|
Table of Contents
1. Introduction 4
1.1 Purpose of this document 4
1.2 Intended Audience 4
1.3 Scope 4
1.4 Definitions and acronyms 4
1.4.1 Acronyms and abbreviations 4
1.5 References 4
2. Organization 4
2.1 Project Management 4
2.2 Project Group 5
2.3 Steering Group 5
2.4 Customer 5
3. Milestones 6
4. Project Results 6
4.1 Requirements 6
4.1.1 Requirement Compliance Matrix 6
4.1.2 Requirements Compliance Summary 8
4.1.3 Remarks 8
4.2 Work Products and Deliverables 8
5. Project Experiences 9
5.1 Positive Experiences 9
5.2 Improvement Possibilities 9
6. Financials 9
6.1 Project Cost Summary 9
6.2 Work per Member 10
6.3 Work hours per week 10
6.4 Work hours per member 10
1.Introduction
1.1Purpose of this document
Purpose of this document is to provide the conclusive remarks about the whole project for all the stake holders to provide them an insight about how the project worked out.
1.2Intended Audience
Following stake holders are the intended audience for this document
-
Team members
-
Supervisor
-
Customer
-
Future developers
1.3Scope
This document will cover the following areas about the project
-
Project management
-
Project results
-
List of all the artifacts produced
-
Requirement compliance
-
Requirement changes
-
Experiences during this project
-
Future improvement that can be done in this project
-
Project financial information
-
Contribution of each team member in the project
-
Milestones achieved during this project
1.4Definitions and acronyms
1.4.1Acronyms and abbreviations
-
Acronym or
abbreviation
|
Definitions
|
FER
|
Faculty of Electrical Engineering and Computing, Zagreb, Croatia
|
MDH
|
Mälardalen University, Vasteras, Sweden
|
IDT
|
School of Innovation, Design and Engineering
|
SVN
|
Subversion: Revision Control System for Documents and Code
|
|
|
|
|
|
|
1.5References
http://www.fer.unizg.hr/rasip/dsd/projects/search4yummy/documents
2.Organization
Muhammad Sulyman is the Project Leader and Jan Čustović is the Team Leader for this project. Project Leader and Team Leader are responsible for project management, directing the project in right direction, assigning work to all team members, keep the project going and deliver all the work according to deadlines.
2.2Project Group
-
Name
|
Initials
|
Responsibility (roles)
|
Muhammad Sulyman
|
MS
|
Project Leader, Documentation Manager
|
Jan Čustović
|
JC
|
Team Leader, Server Side Developer & System Architect
|
Andrej Garić
|
AG
|
Mobile Application Developer
|
Ivan Bandalo
|
IB
|
Web Application Developer, Designer
|
Lovro Maričić
|
LM
|
Tester, Data population in DB
|
Petar Paar
|
PP
|
Mobile Application Developer, Requirement Engineer
|
Ronald Wolvers
|
RW
|
Web Application Developer
|
Yehui Wang
|
YW
|
Tester, Requirement Engineer
|
|
|
|
2.3Steering Group
Prof. Ivica Crnković (MDH), Prof.dr.sc. Mario Zagreb (FER)
Project Supervisor: Aneta Vulgarakis (MDH)
2.4Customer
Project Supervisor: Aneta Vulgarakis (MDH)
Prof. Ivica Crnković (MDH), Prof.dr.sc. Mario Zagreb (FER)
3.Milestones
Id
|
Milestone
Description
|
Responsible Dept./Initials
|
Finished week
|
Metr
|
Rem
|
Plan
|
Forecast
|
Actual
|
Week
|
+/-
|
M-001
|
Project Vision Presentation
|
MS, JC, RW, LM
|
41
|
41
|
0
|
41
|
|
|
M-002
|
Project Plan
|
MS, JC, AG, IB, LM, RW
|
42
|
42
|
0
|
42
|
|
|
M-003
|
Requirement Engineering
|
PP, YW
|
42
|
42
|
0
|
42
|
|
|
M-004
|
Project Plan Presentation
|
MS, JC, RW
|
42
|
42
|
0
|
42
|
|
|
M-005
|
Requirement and Architecture presentation
|
PP, RW, YW, JC
|
43
|
43
|
0
|
43
|
|
|
M-006
|
Database design
|
JC
|
43
|
43
|
0
|
43
|
|
|
M-007
|
Design Document
|
All
|
43
|
43
|
0
|
43
|
|
|
M-008
|
Acceptance Test Plan
|
YW, MS
|
45
|
45
|
0
|
45
|
|
|
M-009
|
Server Side Development for Alpha
|
JC
|
45
|
45
|
0
|
45
|
|
|
M-010
|
Web Application for Alpha
|
IB, RW, LM
|
46
|
46
|
0
|
46
|
|
|
M-011
|
Mobile Application for Alpha
|
AG, PP
|
46
|
46
|
0
|
46
|
|
|
M-012
|
Alpha Prototype Presentation
|
MS, IB, AG, RW
|
47
|
47
|
0
|
47
|
|
|
M-013
|
Server Side Development for Beta
|
JC
|
49
|
49
|
0
|
49
|
|
|
M-014
|
Web Application for Beta
|
IB, RW, LM
|
49
|
49
|
0
|
49
|
|
|
M-015
|
Mobile Application for Beta
|
AG, PP
|
49
|
49
|
0
|
49
|
|
|
M-016
|
Beta Prototype presentation
|
MS, PP, RW
|
50
|
50
|
0
|
50
|
|
|
M-017
|
Server Side Development for Final product
|
JC
|
01
|
01
|
0
|
01
|
|
|
M-018
|
Final Web Application
|
IB, RW
|
01
|
01
|
0
|
01
|
|
|
M-019
|
Final Mobile Application
|
AG, PP
|
01
|
01
|
0
|
01
|
|
|
M-020
|
Testing – Testing report
|
YW, RW
|
01
|
01
|
0
|
01
|
|
|
M-021
|
User Manual
|
YW, RW
|
02
|
02
|
0
|
02
|
|
|
M-022
|
Final Documentation
|
ALL
|
02
|
02
|
0
|
02
|
|
|
M-023
|
Final Project Report
|
MS
|
02
|
02
|
0
|
02
|
|
|
M-024
|
Final product/documentation
|
MS, JC
|
02
|
02
|
0
|
02
|
|
|
|
|
|
|
|
|
|
|
|
4.Project Results
4.1Requirements
4.1.1Requirement Compliance Matrix
Id
|
Requirement
Description
|
completed
|
Rem
|
User interaction via mobile application
|
UC1
|
User registration
|
Yes
|
|
UC2
|
User login
|
Yes
|
|
UC3
|
Restaurant search
|
Yes
|
|
UC4
|
View restaurant
|
Yes
|
|
UC32
|
Menu view
|
Yes
|
|
UC5
|
Dish search
|
Yes
|
|
UC6
|
View dish
|
Yes
|
|
UC7
|
Grade a Dish
|
Yes
|
|
UC9
|
Save a Dish
|
Yes
|
|
UC8
|
Comment a dish
|
Yes
|
|
UC35
|
Grade a restaurant
|
Yes
|
|
UC10
|
Comment a restaurant
|
Yes
|
|
UC11
|
Add photo from restaurant
|
Yes
|
|
UC12
|
Check-in
|
Yes
|
|
UC13
|
View news
|
Yes
|
|
UC14
|
Restaurant news registration
|
Yes
|
|
UC15
|
News registration for restaurant type
|
Yes
|
|
UC36
|
Unsubscribe from news
|
Yes
|
|
UC37
|
Edit user account information
|
Yes
|
|
UC38
|
View Dishes wish list
|
Yes
|
|
User interaction via web application
|
UC33
|
Web restaurant search
|
Yes
|
|
UC1
|
User registration
|
Yes
|
|
UC2
|
User login
|
Yes
|
|
UC3
|
Restaurant search
|
Yes
|
|
UC4
|
View restaurant
|
Yes
|
|
UC32
|
Menu view
|
Yes
|
|
UC5
|
Dish search
|
Yes
|
|
UC6
|
View dish
|
Yes
|
|
UC7
|
Grade a Dish
|
Yes
|
|
UC9
|
Save a Dish
|
Yes
|
|
UC8
|
Comment a dish
|
Yes
|
|
UC35
|
Grade a restaurant
|
Yes
|
|
UC10
|
Comment a restaurant
|
Yes
|
|
UC11
|
Add photo from restaurant
|
Yes
|
|
UC12
|
Check-in
|
Yes
|
|
UC13
|
View news
|
Yes
|
|
UC14
|
Restaurant news registration
|
Yes
|
|
UC15
|
News registration for restaurant type
|
Yes
|
|
UC36
|
Unsubscribe from news
|
Yes
|
|
UC37
|
Edit user account information
|
Yes
|
|
UC38
|
View Dishes wish list
|
Yes
|
|
Interaction with restaurant staff member via web application
|
UC16
|
Update seat availability
|
Yes
|
|
UC17
|
View restaurant menu
|
Yes
|
|
UC18
|
Add dish/menu
|
Yes
|
|
UC19
|
Remove dish/menu
|
Yes
|
|
UC20
|
Update dish/menu
|
Yes
|
|
UC21
|
Update news
|
Yes
|
|
UC34
|
Update restaurant info
|
Yes
|
|
UC25
|
View restaurants
|
Yes
|
|
UC26
|
Add restaurant
|
Yes
|
|
UC27
|
Remove restaurant
|
Yes
|
|
UC28
|
Update restaurant
|
Yes
|
|
System administration
|
UC22
|
View users
|
Yes
|
|
UC23
|
Add user
|
Yes
|
|
UC24
|
Delete user
|
Yes
|
|
UC40
|
Update User
|
Yes
|
|
UC29
|
View restaurant staff members
|
Yes
|
|
UC30
|
Add staff member
|
Yes
|
|
UC31
|
Delete staff member
|
Yes
|
|
UC41
|
Update staff member
|
Yes
|
|
UC39
|
Update restaurant types
|
Yes
|
|
|
|
|
|
Completed: Yes (completely implemented)
No (not implemented at all)
Partially (partially implemented, more description under Remarks subsection)
Unknown (completion status not known)
Dropped (requirement was dropped during the course of the project)
4.1.2Requirements Compliance Summary
-
Total number of requirements
|
61
|
Number of requirements implemented
|
61
|
Requirements partially fulfilled
|
0
|
Requirements not fulfilled
|
0
|
Requirements dropped
|
0
|
4.1.3Remarks
Remark Id
|
Description
|
1
|
Requirement updated: Like a dish, Recommend a dish --> Dish Grading (1-5
|
2
|
Requirement added: Restaurant Grading and Comment Grading
|
3
|
Requirement added: Dish Comment
|
|
|
4.2Work Products and Deliverables -
To
|
Output
|
Planned week
|
Promised week
|
Late +/-
|
Delivered week
|
Rem
|
All Stakeholders
|
Project Plan Document
|
42
|
42
|
0
|
42
|
|
All Stakeholders
|
Requirements Definition document
|
42
|
42
|
0
|
42
|
|
Team Members, Supervisor
|
Project Policies, Coding Policies, SVN Policies
|
42
|
42
|
0
|
42
|
|
All Stakeholders
|
Design Description document
|
43
|
43
|
0
|
43
|
|
All Stakeholders
|
Acceptance test plan
|
50
|
50
|
0
|
50
|
|
All Stakeholders
|
Test Report
|
1
|
1
|
0
|
1
|
|
All Stakeholders
|
Final Project Report
|
2
|
2
|
0
|
2
|
|
All Stakeholders
|
Final Version of all Documents
|
2
|
2
|
0
|
2
|
|
All Stakeholders
|
User Manual for web and android application
|
1
|
1
|
0
|
1
|
|
All Stakeholders
|
Installation Manual
|
1
|
1
|
0
|
1
|
|
All Stakeholders
|
Final Product
|
2
|
2
|
0
|
2
|
|
All Stakeholders
|
Summary Week Report and Happiness Poll
|
Every Monday 23:59
|
|
|
|
|
|
|
|
|
|
|
|
5.Project Experiences
5.1Positive Experiences
Implementation
-
Developing an actual application is fun and a lot of work!
-
Eclipse w/ Android Plug-In is buggy and slow
-
Learning new technologies is fun, but challenging
-
Unbalanced knowledge of technologies, leads to unbalanced work load during implementation
-
Process selection was wise J
Communication
-
New Friends J
-
Luckily!!! No noticeable cultural clashes
-
Different views/backgrounds lead to interesting discussions
Process used in this project was a combination of two types of processes; top level process low level process. In top level process waterfall model is used because the requirements were very stable. In low level process XP (Extreme Programming) model is used to implement the services on demand, fixing the bugs on demand and updating the document on demand. Eventually it turned out that the selection of the process was very wise and it really helped make the project a success.
5.2Improvement Possibilities
In the future system could be expanded with functionality for restaurant owners. This functionality would show structured information about restaurant their owners, e.g. what the people like in their restaurants (foods, environment or something else), how often same costumers returns, how many new customers do they have per day and other similar information. There can also be top user of the month or week or day feature. This will show which user interacted with the application most in a period of time based upon the pictures uploaded, comments given and recommendation about different restaurants and dishes. This project can also be linked with facebook and other social networking sites.
6.Financials
6.1Project Cost Summary
Planned Cost
|
22800 €
|
Actual Cost
|
22800 €
|
6.2Work per Member
6.3
Members
|
W40
|
W41
|
W42
|
W43
|
W44
|
W45
|
W46
|
W47
|
W48
|
W49
|
W50
|
W51
|
W52
|
W01
|
W02
|
Total
|
Andrej Garić
|
5
|
8
|
10
|
17
|
13
|
17
|
21
|
10
|
9
|
25
|
8
|
14
|
13
|
10
|
6
|
186
|
Ivan Bandalo
|
5
|
9
|
8
|
7
|
15
|
30
|
21
|
4
|
15
|
20
|
20
|
13
|
3
|
10
|
1
|
181
|
Jan Čustović
|
11
|
17
|
21
|
28
|
17
|
14
|
14
|
10
|
21
|
21
|
3
|
14
|
0
|
7
|
1
|
199
|
Lovro Maričić
|
2
|
4
|
3
|
7
|
8
|
5
|
0
|
4
|
0
|
10
|
12
|
9
|
10
|
12
|
5
|
91
|
Muhammad Sulyman
|
11
|
16
|
18
|
22
|
15
|
12
|
15
|
15
|
11
|
14
|
15
|
10
|
12
|
12
|
6
|
204
|
Petar Paar
|
7
|
10
|
14
|
23
|
14
|
21
|
16
|
8
|
8
|
9
|
11
|
9
|
0
|
10
|
8
|
168
|
Ronald Wolvers
|
2
|
5
|
8
|
10
|
8
|
9
|
19
|
16
|
18
|
15
|
7
|
8
|
9
|
18
|
5
|
157
|
Yehui Wang
|
3
|
6
|
5
|
11
|
8
|
8
|
6
|
17
|
16
|
22
|
17
|
0
|
8
|
27
|
7
|
161
|
Total
|
46
|
75
|
87
|
125
|
98
|
116
|
112
|
84
|
98
|
136
|
93
|
77
|
55
|
106
|
39
|
1347
| Work hours per week
6.4W ork hours per member
Share with your friends: |
