-
Notifications
You must be signed in to change notification settings - Fork 1
Customer Meeting 3
Utkan Gezer edited this page Oct 7, 2016
·
5 revisions
06 October 2016
14:20 - 15:00
BM A2
- Utkan Gezer
- Furkan Erdem Perşembe
- Kayahan Taşyaran
- Ahmet Ercan Tekden
- Ezgi Tekdemir
- Esma Özelbaş
- İsmail Enes Yılmaz
- Reconsider the requirements with the customer, Alp Kındıroğlu:
- Reconsider
1.9.3.2.
, on whether a user should really label tags in both direction. Shouldn't the user be able to make a relation in just one direction without its counterpart? - Discuss about what a "tag" is within the context of our project.
- Reconsider
- We shall modify the requirements according to the following redefinitions:
- Change the
1.9.3.2.
to allow users to define relations in just one direction without another coming back. - Allow the users to rate a relation as a requirement.
- From now on, a "tag" is a label (in the form of a string) for a topic.
- A "semantic tag" is a label with its semantic context attached to it, allowing it to be disambiguated from the other semantic tags that share the same label.
- Change the
- [Communication Plan] (Communication-Plan)
- Database Schema
- API Documentation
- [Description] (Project-Description)
- [Diagrams] (Diagrams)
- [Domain Analysis] (Domain-Analysis)
- [Features, Themes] (Features,-Themes)
- Mockups
- [Personas] (Personas)
- Plan
- Responsibility Assignment Matrix
- Requirements
- [Use Cases] (Use-Cases)
- [User Stories] (User-Stories)
- Peer Reviews
- Project Tutorial
- Repository Usage Manual
- [Test Plan] (Test-Plans)
- Ahmet Ercan Tekden
- Esma Özelbaş
- Ezgi Tekdemir
- Furkan Erdem Perşembe
- İsmail Enes Yılmaz
- İrem Zöğ
- Kayahan Taşyaran
- Mehmet Utkan Gezer
Preliminary Meetings:
- Meeting 1 (Feb 16)
- Meeting 2 (Feb 23)
- Meeting 3 (Mar 03)
- Meeting 4 (Mar 08)
- Meeting 5 (Mar 14)
- Meeting 6 (Mar 28)
- Customer Meeting 1 (Mar 31)
- Meeting 7 (Apr 05)
Meetings In-production:
- Meeting 8 (Sep 27)
- Meeting 9 (Oct 03)
- Meeting 10 (Oct 10)
- Git Meeting (Oct 14)
- Meeting 11 (Oct 17)
- Meeting 12 (Oct 24, expected)
- Meeting 13 (Oct 31)
- [Meeting 14 (Nov 7)] (Meeting-14)
- Meeting 15 (Nov 14)
- [Meeting 16 (Nov 21)] (Meeting-16)
- [Meeting 17 (Dec 5)] (Meeting-17)
- Meeting 18 (Dec 12)
- [Meeting 19 (Dec 19)] (Meeting-19)
within Sub-groups:
- Database Meeting (Oct 11)
- Android Meeting 1 (Oct 14)
- [Frontend Meeting 1 (Oct 14)](Frontend Meeting 1)
with Customer: