Weekly Meeting Report - SWE-574-Spring-2018/LinkyWay GitHub Wiki
Each meeting during project should be documented according to a regular template decided. Meeting notes should cover the information below.
- Date
- Time Interval: The time interval meeting took place.
- Location
- Meeting Objective: A brief description of the objective of the meeting.
- Decisions: Brief descriptions of the desicions made on the meeting.
- Determined Tasks: After each meeting specific tasks should be determined and these tasks should be assigned to specific contributors.
The information related with the specific meetings can be found below.
Week 1
General Information
| Item | Information |
|---|---|
| Date | 11.02.2018 |
| Time Interval | 12:30 - 14:30 |
| Location | Simit Sarayı Hisarüstü |
Meeting Objectives
- Determining weekly meeting date and time
- Determining tasks and assignees
- Discussing briefly about the tools and project management
Decisions
- Every Saturday at 13:00 group meeting should took place.
- If there is someone who cannot attend on Saturday, he could inform the group members one week before the meeting and the meeting for that week should take place on Tuesday.
- On the meeting the tasks should be determined and assigned to specific contributors.
- The project should be divided into 5 main topics like backend or mobile. Each member should be responsible for one of these topics. He should manage the development of the topic by assigning and following tasks, integrating these tasks to project.
Determined Tasks
| Task | Assignee |
|---|---|
| Organization & Repository Creation | Hüseyin Kılıç |
| Github Project Page & Issue Creation & Tag Customization | Duran Serkan Kılıç |
| Detailed Readme Preparation | Nedim Azgari |
| Research on Twitter API & Wikidata API | All |
| Wiki Home Page Creation | Hüseyin Kılıç |
| Wiki Page for Time Tracking and Effort | Salih Demir |
| Wiki Page for Project Technical Stack (Technologies to be Used e.g java8, android5, intellij idea) | Nedim Azgari |
| Wiki Page for Guidelines and Policies (Conventions & Code Review & Pr Merge Policy etc) | Salih Demir |
| Wiki Page for Issue Management Policy & Definition of Done | Duran Serkan Kılıç |
| Wiki Page for Weekly Meeting Notes and Weekly Status Report | Ahmet Can Ersöz |
| Wiki Page for Research Tasks | Hüseyin Kılıç |
Week 2
General Information
| Item | Information |
|---|---|
| Date | 17.02.2018 |
| Time Interval | 14:00 - 17:00 |
| Location | Aptullah Kuran Library |
Meeting Objectives
- Requirements elicitation
- Discussing briefly about the project scope
- Determining tasks and assignees
Decisions
- Every week lecture notes should be added to repository.
- A glossary should be defined to make the documentation and discussions about the project more clear.
Determined Tasks
| Task | Assignee | Deadline |
|---|---|---|
| Coding Standarts | Salih Demir | 19.02.2018 19:00 |
| Repository Standarts | Hüseyin Kılıç | 19.02.2018 19:00 |
| Read Me | Nedim Azgari | 19.02.2018 19:00 |
| Issue Management | Duran Serkan Kılıç | 19.02.2018 19:00 |
| Project Plan | Hüseyin Kılıç | 19.02.2018 19:00 |
| Requirements | Nedim Azgari, Ahmet Can Ersöz | 19.02.2018 19:00 |
| Weekly Meeting&Status Report | Ahmet Can Ersöz | 19.02.2018 19:00 |
Week 3
General Information
| Item | Information |
|---|---|
| Date | 20.02.2018 |
| Time Interval | 19:30 - 21:30 |
| Location | Simit Sarayı Hisarüstü |
Meeting Objectives
- Discussion on W3 Web Annotations
- Discussing user scenarios
- Determining tasks and assignees
Decisions
- Discussed user scenarios should be documented well.
- Documented user scenarios shoud be discussed with the customer.
- User scenarios should be divided into two parts as adding data to system(adding annotation, node, edge) and getting data from the system(data visualization, different structures of the queries that the user would be able to make).
- Further research should be conducted.
Determined Tasks
| Task | Assignee | Deadline |
|---|---|---|
| User Scenarios(Getting Data From the System) | Salih Demir | 26.02.2018 19:00 |
| Detailed Project Plan | Hüseyin Kılıç | 26.02.2018 19:00 |
| W3 Web Annotations(Research and Documentation) | Nedim Azgari | 26.02.2018 19:00 |
| Research on SPARQL | Duran Serkan Kılıç | 26.02.2018 19:00 |
| User Scenarios(Adding Data to System) | Ahmet Can Ersöz | 26.02.2018 19:00 |
| Weekly Meeting&Status Report | Ahmet Can Ersöz | 26.02.2018 19:00 |
Week 4
General Information
| Item | Information |
|---|---|
| Date | 03.03.2018 |
| Time Interval | 14:30 - 17:30 |
| Location | Poğaçacı Hisarüstü |
Meeting Objectives
- Discussion on prototype
- Discussing user scenarios
- Determining tasks and assignees
Decisions
- The backend implementation should be started.
- A wireframe to be more informative about the UI design should be created.
- A prototype of HTML to be more informative about annotations should be created.
- Resulting JSONs of different use cases should be created.
Determined Tasks
| Task | Assignee | Deadline |
|---|---|---|
| Interface of Annotation Creation | Salih Demir | 04.03.2018 19:00 |
| Back End Environment Setup | Hüseyin Kılıç | 04.03.2018 19:00 |
| Interface of Annotation Creation | Nedim Azgari | 04.03.2018 19:00 |
| UI Wireframe | Duran Serkan Kılıç | 04.03.2018 19:00 |
| Resulting Use Case JSONs | Ahmet Can Ersöz | 04.03.2018 19:00 |
| Weekly Meeting&Status Report | Ahmet Can Ersöz | 04.03.2018 19:00 |
Week 5
General Information
| Item | Information |
|---|---|
| Date | 10.03.2018 |
| Time Interval | 14:30 - 17:30 |
| Location | Poğaçacı Hisarüstü |
Meeting Objectives
- Discussion on implementation
- Determining tasks and assignees
Decisions
- The determined 3 user scenarios should be implemented in the first place.
- User interface should be developed with its basic features.
- Twitter API should be integrated to project.
- Application database(PostgreSQL) should be replaced with Neo4j.
- A research about annotation database should be conducted and the integration of the project with annotation database should be implemented.
Determined Tasks
| Task | Assignee | Deadline |
|---|---|---|
| Web UI | Salih Demir | 11.03.2018 19:00 |
| Twitter API Integration | Hüseyin Kılıç | 11.03.2018 19:00 |
| Neo4j Integration | Hüseyin Kılıç | 11.03.2018 19:00 |
| User Scenarios | Nedim Azgari | 11.03.2018 19:00 |
| ? | Duran Serkan Kılıç | 11.03.2018 19:00 |
| Research and Implementation of Annotation Database | Ahmet Can Ersöz | 11.03.2018 19:00 |
| Weekly Meeting&Status Report | Ahmet Can Ersöz | 11.03.2018 19:00 |
Week 6
General Information
| Item | Information |
|---|---|
| Date | 17.03.2018 |
| Time Interval | 14:30 - 17:30 |
| Location | Poğaçacı Hisarüstü |
Meeting Objectives
- Discussion on implementation
- Determining tasks and assignees
Decisions
- Whether an annotation server should be found and used or MongoDB should be integrated to project and annotations should be saved on this database using anno4j should be determined.
Determined Tasks
| Task | Assignee | Deadline |
|---|---|---|
| Web UI | Salih Demir | 18.03.2018 19:00 |
| Twitter API | Hüseyin Kılıç | 18.03.2018 19:00 |
| User Scenarios | Nedim Azgari | 18.03.2018 19:00 |
| Annotation Server | Duran Serkan Kılıç | 18.03.2018 19:00 |
| MongoDB | Ahmet Can Ersöz | 18.03.2018 19:00 |
| Weekly Meeting&Status Report | Ahmet Can Ersöz | 18.03.2018 19:00 |
Week 7
General Information
| Item | Information |
|---|---|
| Date | 24.03.2018 |
| Time Interval | 14:30 - 17:30 |
| Location | Miligram Hisarüstü |
Meeting Objectives
- Discussion on implementation
- Determining tasks and assignees
- Discussion on architecture
Decisions
- The architecture is designed.
- It is decided that RDF4J should be used for annotation.
Determined Tasks
| Task | Assignee | Deadline |
|---|---|---|
| Web UI | Salih Demir | 25.03.2018 19:00 |
| Twitter Login | Hüseyin Kılıç | 25.03.2018 19:00 |
| ? | Nedim Azgari | 25.03.2018 19:00 |
| Annotation Server | Duran Serkan Kılıç | 25.03.2018 19:00 |
| Twitter API | Ahmet Can Ersöz | 25.03.2018 19:00 |
| Weekly Meeting&Status Report | Ahmet Can Ersöz | 25.03.2018 19:00 |