This repository has been archived by the owner on Mar 30, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6
Customer Meeting #1: 15.02.2018
Omer Kirbiyik edited this page Mar 12, 2018
·
3 revisions
- Date: 15th of February, 2018
- Time: 16:10-17:30
- Location: Boğaziçi University, North Campus, Computer Engineering Building, A4 Lab
- Erkam Ağralı
- Atıf Emre Yüksel
- Ömer Kırbıyık
- Fatih Maytalman
- Mert Aközcan
- Zeynep Işık
- Hilal Mente
- Ali Özden
- Abdurrahman Dilmaç
- Making annotation part definite
- Determining the admin's status in platform
- Asking the necessity of language support
- Determining the minimum number of users in platform at the same time
- Discussing restrictions about the types of events
-
We asked about annotation to determine the contents of it clearly. Customer did not give useful recommendations for annotation. He specified that project description contained more details for this part. Also, we can ask questions that are related to annotation to the other customers.
-
We asked whether using the cross platform is allowed or not in project. Customer pointed out that there were no restrictions when project was developed unless users and guests encountered a problem in platform.
-
We determined the limits and features of events in platform by discussing with customer:
- Only one page should be opened by users about a cultural activity including certain time and location. Users can mark their attendance status in this page.
- If pages having the same content are opened, they should be merged by the platform. Otherwise, the event that has more participants must be showed when users and guests search this type of event.
- Events shall not be pulled from the other platforms directly. Events merely create in platform by users.
- Events related to different subjects which are not be involved by cultural events shall be put in the category having others label.
- Every user can attend the events without encountering any blocking by platform.
-
We asked about whether users can block the others or not. Customer expected to use blocking mechanism in the platform.
- Events shall be created merely in the platform. They shall not be pulled from other platforms.
- Admin panel can be added in the next part of the project. It is not necessary at the moment.
- Using cross-platform is allowed in developing project.
- The platform should manage the users' requests as many as possible.
- The language support should be added to the platform.
- Cultural Activities Project
- Communication Plan
- Requirements Analysis
- Project Plan
- User Stories
- Mockups
- User Scenarios
- Class Diagram
- Sequence Diagrams
- Use Cases
- Test Cases
- Android Software Design
- Twitter API Application
- First Term Milestone Report
- Milestone#1 Report
- Milestone#2 Report
- Meeting #1: 8.02.2018
- Meeting #2: 13.02.2018
- Customer Meeting #1: 15.02.2018
- Meeting #3: 19.02.2018
- Meeting #4: 26.02.2018
- Meeting #5: 05.03.2018
- Meeting #6: 12.03.2018
- Meeting #7: 19.03.2018
- Meeting #8: 26.03.2018
- Meeting #9: 02.04.2018
- Meeting #10: 09.04.2018
- Meeting #11: 06.05.2018
- Meeting #12: 19.05.2018
- Meeting #13: 01.10.2018
- Meeting #14: 06.10.2018 - Project Design
- Meeting #15: 08.10.2018 - Android Related
- Meeting #17: 24.10.2018 - Backend Team
- Meeting #18: 29.10.2018 - Before Milestone(Skype)
- Meeting #19: 30.10.2018 - After Milestone(Skype)
- Meeting #20: 06.11.2018 - Backend Team
- Meeting #21: 09.11.2018 - Android Team
- Meeting #23: 19.11.2018 -Android Team(Skype)
- Meeting #24: 27.11.2018 - Backend Team
- Meeting #25: 01.12.2018 - Frontend Team
- Meeting #26: 05.12.2018 - Frontend Team
- Meeting #27: 10.12.2018 - Frontend Team
- Meeting #28: 31.12.2018 - Frontend Team
- Abdurrahman Dilmaç
- Anıl Seyrek
- Atıf Emre Yüksel
- Erkam Ağralı
- Fatih Maytalman
- Mert Aközcan
- Mustafa Alparslan
- Ömer Kırbıyık (Project Manager/Communicator)
- Zeynep Işık