-
Notifications
You must be signed in to change notification settings - Fork 8
Meeting #5 (31.03.2022)
📅 Date: 31/03/2022
📍 Location: Discord
🕐 Duration: 20:00 - 22:15
📝 Note Taker: Ahmet Yiğit Özdoğan
👥 Attendees: (10/10)
- Ahmet Yiğit Özdoğan
- Altay Acar
- Bahrican Yeşil
- Ecenur Sezer
- Egemen Atik
- Ezgi Aysel Batı
- Hasan Can Erol
- Mehmet Batuhan Çelik
- Muhammed Enes Sürmeli
- Onur Kömürcü
- Going over the software design assignment pdf, talking about it in general
- Review of the previous week's feedbacks about the requirements, scenarios, and mockups pages
- Deciding the use-case diagram parts to create, and sub-sections to work on
- Deciding the tool with the help of which we will create the diagrams
- Assigning the tasks and determining the assignees for the use-case diagram
1. We went over the software design assignment pdf and ordered the given diagrams according to the most logical completion order as use-case diagram, class diagram, and sequence diagram.
2. Iterated over the software design assignment pdf to create a task list for the use-case diagram, and assigned people on a volunteering or random basis.
3. For common tasks that affect others' work or requires a review of another person (such as the revision, requirements, scenarios), the deadline was decided to be 02.04.2022 - Saturday - 14.00.
4. For the reviewers and documenters, the deadline was decided to be 02.04.2022 - Saturday - 15.00.
5. To have an objective review process, we also decided to select the reviewer among the people who are not assigned to an issue. This both will help us to complete each other and track what's going around in the other issues.
6. It was decided that we should create separate titles and subtitles for the use-case diagram and then assign different people to determine these specified diagram parts. We have separated the use-case diagram as:
- Enrolled Course Actions
- Note Actions (Creating, editing, viewing them)
- Annotation Actions
- Reviewing a Course
- Attending and Viewing Events
- Viewing Content
- Lecturer and Admin Actions
- Course Creation
- Admin Operations
- Non-Lecture Related Sections
- Authentication
- Viewing Profiles
- Chat
- Viewing Homepage
- Searching - Browsing
7. We went over the requirements one last time and discussed about improper parts and definitions that our TA was indicated in the last P.S.. It is decided that the parts which should be revised will be issued to whom prepared these requirements in the previous weeks. We will re-open the issues that were related to corresponding requirements and continue from these issues. These can be seen from Meeting #2 notes from here.
8. We went over the scenarios and mockups and discussed about improper parts and definitions that our TA was indicated in the last P.S.. It is decided that the parts which should be revised will be issued to whom prepared these scenarios and mockups in the previous weeks. We will create new revision issues for this purpose if there are no previous issues, or re-open the issues that were related to corresponding scenarios and mockups and continue from these issues. These can be seen from Meeting #3 notes from here.
9. Previous years' repos were analyzed to understand the concept of the diagrams. It was discussed that which diagrams have more priority and which diagrams are depending each other. From these discussions, it was decided that use case should be started to be done. Class diagram and Sequence diagram will be done later on in the given order because they were considered to have strict connections to the use-case diagram.
10. Our main weekly task is creating the diagrams according to the software design rules. We picked a very convenient free basic drawing tool for creating the use-case diagram, class diagram, and sequence diagram, namely Lucidchart App.
Action items are listed in the order they were discussed during the meeting.
# | Details | Assignee(s) | Due Date | Issue |
---|---|---|---|---|
1 | Document the meeting notes #5 on the wiki | Muhammed Enes Sürmeli | 05.04.2022 Tuesday @ 23:59 | #101 |
2 | Update the annotation requirements according to the received feedback | Ahmet Yiğit Özdoğan | 05.04.2022 Tuesday @ 23:59 | #68 |
3 | Update the events requirements according to the received feedback | Ecenur Sezer | 02.04.2022 Saturday @ 14:00 | #66 |
4 | Revise the Registered Lecturer Scenario according to the feedback received in P.S. | Bahrican Yeşil | 02.04.2022 Saturday @ 15:00 | #83 |
5 | Revise the Mockups For Registered Lecturer Scenario according to the feedback received in P.S. | Ahmet Yiğit Özdoğan | 02.04.2022 Saturday @ 15:00 | #58 |
6 | Open the main issue for the Enrolled Course Actions part of the use-case diagram | Ezgi Aysel Batı | 02.04.2022 Saturday @ 14:00 | #69 |
7 | Create the note actions part of the use-case diagram | Bahrican Yeşil | 02.04.2022 Saturday @ 14:00 | #80 |
8 | Create the reviewing course part of the use-case diagram | Bahrican Yeşil | 02.04.2022 Saturday @ 14:00 | #81 |
9 | Create the event related parts of the use-case diagram | Onur Kömürcü | 02.04.2022 Saturday @ 14:00 | #82 |
10 | Create the View Course Content part of the use-case diagram | Onur Kömürcü | 02.04.2022 Saturday @ 14:00 | #85 |
11 | Create the Annotations part of the use-case diagram | Hasan Can Erol | 02.04.2022 Saturday @ 14:00 | #84 |
12 | Open the main issue for the Admin User and Course Creation Sections of the Use-Case Diagram | Altay Acar | 02.04.2022 Saturday @ 14:30 | #75 |
13 | Create the course creation part of the use-case diagram | Altay Acar | 02.04.2022 Saturday @ 14:30 | #77 |
14 | Create the admin operations part of the use-case diagram | Altay Acar | 02.04.2022 Saturday @ 14:30 | #79 |
15 | Open the main issue for the Non Lecture related Sections of the Use-Case Diagram | Mehmet Batuhan Çelik | 02.04.2022 Saturday @ 14:00 | #70 |
16 | Create the Authentication part of the use-case diagram | Mehmet Batuhan Çelik | 02.04.2022 Saturday @ 14:00 | #72 |
17 | Create the Viewing Profiles part of the use-case diagram | Muhammed Enes Sürmeli | 02.04.2022 Saturday @ 14:00 | #73 |
18 | Create the Searching, Browsing and Viewing Homepage parts of the use-case diagram | Ecenur Sezer | 02.04.2022 Saturday @ 14:00 | #74 |
19 | Create the chat related parts of the use-case diagram | Egemen Atik | 02.04.2022 Saturday @ 14:00 | #76 |
20 | Open the main issue for all the Use-Case Diagrams to ensure integrity | Muhammed Enes Sürmeli | 02.04.2022 Saturday @ 15:00 | #71 |
Group Members
Meeting Notes of 451
Mobile Team Meeting Notes
Back-End Team Meeting Notes
Front-End Team Meeting Notes
Meeting Notes of 352
- Meeting #1 (04.03.2022)
- Meeting #2 (10.03.2022)
- Meeting #3 (17.03.2022)
- Meeting #4 (24.03.2022)
- Meeting #5 (31.03.2022)
- Meeting #5.1 (02.04.2022)
- Meeting #5.2 (05.04.2022)
- Meeting #6 (07.04.2022)
- Meeting #6.1 (12.04.2022)
- Meeting #7 (14.04.2022)
- Meeting #8 (21.04.2022)
- Meeting #9 (01.05.2022)
- Meeting #10 (12.05.2022)
- Practice App Requirements
- Practice App Use Case Diagram
- Practice App Sequence Diagram
- Practice App API Documentation
CMPE451 Milestones
- Will be added when ready