-
Notifications
You must be signed in to change notification settings - Fork 2
Meeting 5
Irem Uguz edited this page Mar 12, 2019
·
5 revisions
- Ahmet Gedemenli
- İbrahim Can Kaplan
- Egemen Göl (Today, meeting notes are written by Egemen)
- Gamze Gülbahar
- İrem Uğuz
- Halit Özsoy
- Burhan Akkuş
- Review and improve the accuracy and precision of the requirements.
- Talk about the corrections of the instructor, both Piazza feedback and comments in class.
- Talk about the Use Case Diagram, go over the review about it and decide what to update in Requirements and diagram itself.
- Talk about the Class Diagram, decide when to start, after or before corrections.
- Decide this week's tasks and action items.
- User scenerios are considered containing multiple scenerios, we decided to split the scenerios into multiple smaller scenerios.
- Scenerios are in need of tagging but complex scenerios are hard to be tagged.
- Use Case Review document of Egemen does need to be translated and formatted into github. We need to decide where to upload it, wiki or docs.
- A list needs to be created for customer, to update the Requirements and Use Case Diagram.
- Expert declaration is out, "I want to play a more important role, I can review essays" mentality is in.
- Use Case Diagram is almost over, Class Diagram can start.
- Use Case Diagram and Requirements needs to be updated according to comments from the customers, after asked questions.
- We found out that the Sequence Diagram is harder than we thought, at least one more person cen be added for help.
- Class and Sequence diagrams have been talked about. Team members who attended lectures and problem sessions did explained their understanding and everyone got up to speed.
- User scenerios are to be divided into multiple smaller scenerios by their respective creators.
- Scenerios are to be tagged respective to what they demonstrate.
- Review will be uploaded into github issue system without translation.
- Will create a question list to ask the customer (Teaching assistant). Will update requirements and Use Case Diagram accordingly.
- Class Diagram will start.
- Sequence Diagram team will expand.
No. | Who | What | Deadline | Prerequisite |
---|---|---|---|---|
1 | İrem, Ahmet, Emirhan | Split user scenarios | 20 March 23.59 | |
2 | Halit, Gamze, Arda | Divide mockups and add arrows | 20 March 23.59 | |
3 | Egemen | Upload the "Use Case Review" document and Class Diagram tutorial video | 14 March 23.59 | |
4 | Gamze, İbrahim, Ahmet | Update Requirements and Use Case Diagram, according to review and Q&A | 17 March 23.59 | |
5 | Emirhan, İrem | Start preparing Class Diagram | 14 March 23.59 | |
6 | Ahmet | Will compile questions to be asked to the customer | 17 March 23.59 | |
7 | Burhan | Will join to the Sequence Diagram team | Immediately |