| Abdulkadir Elmacı |
- Attending most weekly and all assistant meetings
- Researching previous years repos
- Discovering GitHub repositories
- Creating personal wiki page
- Learning about Git
- Requirements elicitation
- Creating glossary
- Reviewing requirements after customer meeting
- Creating user scenario
- Creating user mockups
- Taking notes for meeting #5
- Determining class diagram components
- Drawing class diagram components
- Updating class diagrams based on TA’s feedback
- Determining sequence diagram components
- Drawing some of the sequence diagram components
- Creating RAM for the the task done until Milestone #1
- Writing future plans for Backend
|
| Yağız Efe Şabanoğlu |
- Attending most weekly and all assistant meetings
- Writing weekly efforts for my Personal Efforts Page
- Creating a Personal Wiki Page
- Analyzing previous groups' repositories
- Researching platforms similar to our projects and adding them into github
- Creating table and preparing template of research of similar project page
- Review the admin scenario and suggest edits
- Preparing the mockup for the Admin Scenario
- Meeting with the customer
- Researching the class and sequence diagram
- Determining class diagram components and drawing three about controllers
- Determining sequence diagram components and drawing cases 8-11 and 12
- Modifying the class diagram to draw the sequence diagram
- Preparing a project plan for the part of the 352 course covered so far
- Updating the project plan for the prepared future plan
|
| Erencan Uysal |
- Attending all weekly and assistant meetings
- Creating README page
- Examine previous years groups’ repositories
- Creating personal wiki page
- Examine several github repositories and document favorite one
- Doing research about git
- Finding customer questions
- Attending customer meeting
- Documenting meeting notes for meeting #4 and #9
- Create user scenarios
- Create mockups for user scenarios in android
- Determining the Use Case Diagram components
- Drawing the Use Case Diagram
- Modifying Use Case Diagram based on assistant's feedback
- Determining classes for Class Diagram and relationships between classes
- Writing the executive summary for the Milestone Report 1 (contents and description parts)
- Writing a future project plan for frontend part
- Writing weekly efforts to github
|
| Hamza Akyıldız |
- Preparing Communication Plan
- Discovering GitHub repositories
- Creating Slack workspace
- Requirements elicitation
- Creating a glossary
- Creating Admin user scenario
- Taking meeting notes
- Meeting with the customer
- Determining use cases and drawing use case diagram
- Determining sequence diagrams and drawing three of them
- Reviewing and updating the requirements before first milestone report
- Reporting the evaluation of the tools and processes
- Planning the upcoming backend design and implementation
|
| İsmail Ata İnan |
- Attending all our weekly group meetings
- Attending all meetings with the assistant
- Creating the Wiki Home Page, Sidebar and Footer for our Github repository
- Creating a personal Wiki page
- Looking at several Github repositories and explaining one at Wiki
- Doing a research about Git
- Determining the format and the specification of the Requirements and listing them in the repository
- Communicating with the assistant whenever we had questions
- Inviting the assistant to our Slack channel
- Reviewing and modifying the Requirements after feedbacks
- Attending to the customer meeting
- Writing the Guest user scenario
- Preparing the mockup for the Guest user scenario using the mobile application
- Documenting the meeting notes for Week 4
- Determining the Use Case Diagram components
- Drawing the Use Case Diagram
- Modifying Use Case Diagram based on assistant's feedback
- Determining the key use cases for Sequence Diagrams
- Drawing 4 Sequence Diagrams
- Writing the executive summary for the Milestone Report 1
- Writing a project plan for the rest of the 352 course
|
| Merve Rabia Barın |
- Attending all weekly and assistant meetings
- Preparing a Meeting Notes Template
- Discovering a Github repository and summarize it
- Research about Git
- Creating a Personal Wiki page
- Contributing to the specification of requirements
- Modifying requirements based on the assistant's feedback
- Contributing to the creation of User Scenario including persona, story, goals and acceptance criteria
- Creating Web Mockups for Sharing and Editing Story pages
- Editing User Scenarios page in Wiki & dividing scenarios into three
- Attending Customer Meeting
- Determining use cases for Use Case Diagram
- Drawing Use Case Diagram
- Modifying Use Case Diagram based on assistant's feedback
- Determining classes for Class Diagram and relationships between classes
- Listing deliverables and their status, also evaluating the status of each deliverable for the first Milestone Report
- Writing a project plan for the rest of the 352 course
|
| Onurcan Avcı |
- Attending all weekly and assistant meetings
- Attending all meetings with the assistant
- Examining previous groups' repositories
- Connect Github Repo with Slack
- Creating a personal wiki page
- Discovering a Github repository and summarize it
- Creating table and prepare template of research of related project page
- Creating a team in Figma for simultaneously develop
- Writing the Guest user scenario
- Making research about mockups
- Preparing the mockup for the Guest user scenario using the mobile application
- Determining the Use Case Diagram components
- Drawing the Use Case Diagram
- Modifying Use Case Diagram based on assistant's feedback
- Determining the key use cases for Sequence Diagrams
- Drawing 3 Sequence Diagrams
- Reviewing listing deliverables and status
- Filling project plan
- Creating future plan for mobile and front-end
|
| Ramazan Bulut |
- Attending our weekly meetings
- Attending meetings with the responsible assistant
- Examining old repositories prepared by previous years’ groups
- Wiki Page designing
- Creating personal Wiki Page
- Git Version Control System research and documenting it as a cheatsheet
- Discovering Git repositories
- Documenting personal effort weekly
- Making pre-meeting research about week’s task
- Communicating with group members about implementation process
- Documenting and clarifying question to be asked to the customer
- Research on how mockups should be according to requirements and scenario
- Preparing a admin web page template and creating some pages
- Determining classes by checking their requirements
- Creating 2 classes on diagram and attending a connection meeting
- Reviewing other class diagrams created by other members
- Determining and creating sequence diagrams
- Facilitating communication between class and sequence diagram groups
- Creating RAM table and filling it
- Creating future plan for mobile and front-end
|
| Umut Kocasarı |
- Attending all our weekly and review meetings
- Attending all the meetings done with the assistant
- Examining previous years' repositories
- Creating a personal wiki page
- Creating a template for personal efforts
- Making git research and summarizing it with explanations and images
- Discovering Github repositories and summarizing one of them
- Communicating with the team about what I have done and how the progress is
- Understanding the project and preparing questions
- Asking questions to the assistant during meeting and saving the answers
- Updating the questions page according to the answers
- Making research about mockups
- Creating a scenario for guest in website
- Preparing the mockup for guest at website
- Helping the team in use case diagram preparation
- Modifying Use Case Diagram based on assistant's feedback
- Determining classes for Class Diagram and dividing them between each other
- Doing my personal part of Class Diagram
- Combining classes with appropriate relationships
- Reviewing what other team members have done about Sequence Diagram
- Creating title page of milestone report
- Combining all the markdown files in an appropriate format for milestone report with the table of content and title page and doing this in an automatic way
- Planning the backend for future work with the backend team
|
