-
Notifications
You must be signed in to change notification settings - Fork 4
Meeting #4 (06.03.2019)
Meltem Suiçmez edited this page Mar 12, 2019
·
6 revisions
- Location: Cmpe Building B5
- Date: 6 March 2019
- Time: 18:00 - 19:30
- Ali Meriç Deşer
- Yusuf Mert Bila
- Furkan Kadıoğlu
- Veli Can Ünal
- Mahmut Uzunpostalcı
- Hasan Öztürk
- Abdullah Yıldız
- Selamettin Dirik
- Meltem Suiçmez
- Abdullah Enes Öncü
- 2.1. Reviewing and understanding our assignment#4 clearly.
- 2.2. Discussing how we are going to do it and dividing the work we are going to do.
- 2.3. Reviewing what is left of the updating of our feedback, assigning members to do them.
- 2.4. Receiving feedbacks about the works we have finished from all group members.
- 2.5. Emphasizing the importance of using commit messages.
- 2.6. Discussing type labels and what to add to enrich them.
- 2.7. Emphasizing and reminding the right usage of labels.
- 2.8. Discussing about the technologies we are going to use in our project.
- 3.1 Use case diagrams, class diagrams and sequence diagrams of previous groups 5 and 7 were examined. We will determine how we distribute jobs to every member in the next 2 days. We talked about the properties of these figures. We decided to specify registered and guest user properties in the use case diagrams and we agreed we will do them according to our user requirements.
- 3.2 We agreed that we should decide which technologies we are going to use nex semester in this week. We mentioned our options which are nodejs, django, and java spring for backend; kotlin, java for android; React.js, Angular.js, Vue.js, and TypeScript for frontend. We will all search which languages are the most suitable for us and continue our discussion on Slack to determine them in the next days.
- 3.3 We decided that our type labels are enough for now. But we are all aware that we will need to add labels like 'bug' in the next weeks. Also the right usage of status labels are reminded to everyone, especially Status:Review needed and Status:Completed.
- 3.4 From now on, everyone will add comments/messages whether it's editing pages or commiting files. These messages should be specific enough to understand the changes/what is committed without opening it up and looking at it. We all agreed that this would be best and we will continue this way.
- 3.5 We planned to look at sequence diagrams more detaily on the next week when we will be finished with use case and class diagrams. On thursday morning a group will start use diagrams and we will have a plan to how we are going to divide the work. We will work on use case diagrams till saturday night and we are going to start class diagrams. It will be finished on tuesday night. Tasks will be distributed after use case diagrams. Then when we meet next wednesday we will determine how to continue with sequence diagrams.
- 3.6 We realized we still have some confusing questions about our project. We opened an issue on questions to our customer. Everyone will add their questions at the comments part of that issue whenever they have any and we will clarify all our questions on the next customer meeting.
ID | Who | What | Deadline |
---|---|---|---|
1. | Enes, Furkan, Hasan | Starting working on use case diagrams and class diagrams | 07.03.2019 at 11 am |
2. | Everyone(Subgroup assignments later) | Finishing use case diagram | 09.03.2019, midnight |
3. | Everyone(Subgroup assignments later) | Finishing class diagram | 12.03.2019, midnight |
4. | Everyone | Doing research on technologies to use at our project(@3.2) | 09.03.2019, midnight |
This project is operated in the context of Cmpe 451
- Ali Meriç Deşer
- Yusuf Mert Bila
- Furkan Kadıoğlu
- Mahmut Uzunpostalcı
- Hasan Öztürk
- Selamettin Dirik
- Meltem Suiçmez (Communicator)
- Abdullah Enes Öncü
- Kartal Kaan Bozdoğan
- Nevzat Ersoy
💻 Project
- Requirements
- User Manual
- User Stories
- Mockups
- Diagrams
- Milestone I Report (CMPE 352)
- Project Plan (CMPE 352)
- API Documentations:
- Milestone 2 Report (CMPE 352)
- Milestone I Report
- Milestone II Report
- Final Report
Meeting 2 (Android) (02.10.19) | Meeting 2 (Frontend) (07.10.19) | Meeting 2 (Backend) |