Skip to content

Milestone 1 Report

Yigit Sekerci edited this page Apr 9, 2023 · 38 revisions

CMPE 352 Group 4 Milestone 1 Report

Contributors

  • Selin Işık
  • Ahmet Emre Şafak
  • Ali Nasra
  • Emre Batuhan Göç
  • Ali Alperen Sönmez
  • Enes Furkan Arslan
  • Yusuf Suat Polat
  • Halil Özkan
  • Yiğit Şekerci

Table of contents

1. Executive Summary

1.1 Introduction

Introducing Prediction Polls, a sophisticated platform designed to enable users predict future events, share their opinions and insights with the world! As a part of our milestone report, we are pleased to present our innovative platform that empowers our users to participate in a diverse range of polls on topics ranging from politics to pop culture, and gauge how their views compare to those of other members.

You can quickly look for polls and profiles utilizing our user-friendly, intuitive interface's keyword, category, and username search functionality. Furthermore, our cutting-edge privacy settings provide you total control over your profile and behavior, guaranteeing that your privacy is safeguarded.

As a valued member of our community, you have the opportunity to connect with other users by adding friends, sharing accomplishments, and engaging in the comment section of polls. Furthermore, our poll creation feature allows you to initiate conversations and gain valuable insights on topics that are of significance to you.

1.2 Project Status

As of right now, our project has gone through a preliminary setup phase during which several important tasks have been finished. The team has taken the required actions to set up templates and a wiki for documentation reasons as well as putting in place a meeting structure to speed up project development. Additionally, the project's logistics, comprising requirements, software design documents, and a project plan, have been developed.

The team members initially established individual wiki pages describing their educational and professional backgrounds, skill sets, and interests. The next step was for each team member to construct their ideal repository page in order to learn more about what makes an excellent repository. The team also chose to use Discord and WhatsApp as their major communication platforms, further information is available in sections 4.1 and 4.2 of our project documentation.

Upon completion of the initial setup, we commenced research on project requirements, collaborating closely with our customer to ensure that their needs were fully understood and incorporated into the project plan. In light of our customer's requests, we prepared mock-ups and commenced the diagramming process. It is important to note that feedback from our customer was critical in the decision-making process, and we took great care to adapt our design documents and requirements based on their feedback.

In summary, we have successfully completed the essential design process and necessary tasks, taking into account feedback from our customer at every stage of the project.

1.3 Future Plans

As we move on to the implementation phase, the steps we have already taken will still be of great value to us in creating team cohesion. The project's implementation is currently our main goal, albeit the exacts of how we'll do so are still to be worked out. It is critical to understand that the project's specifications and design papers are inherently subject to change because particular design decisions could change with time. However, we believe that the current documents do the best job possible of capturing our needs.

As we move forward, it may be prudent to consider dividing our team into specialized sub-teams, such as an Android team, to streamline the implementation process. By doing so, we can leverage the expertise of each team member to ensure that each component of the project is executed with the utmost precision and efficiency.

2. List and Status of Deliverables

2.1 Deliverable 1 (Project Repository)

2.2 Deliverable 2 (Requirements)

2.3 Deliverable 3 (Software Design Documents in UML)

2.4 Deliverable 4 (Project Plan, RAM)

2.5 Deliverable 5 (Milestone Report)

3. Evaluation of the status of deliverables

4. Evaluation of tools and processes

4.1 Discord

  • We have used discord for mostly project related stuff for example sharing draft diagrams.
  • We conducted our meetings in discord.
  • Discord's text channels allowed us to categorize our conversations.
  • Discord's talk priority feature helped moderator in our meetings to resolve heated discussion more easily.

4.2 WhatsApp

  • We talked in WhatsApp for mainly timing related issues for example determining time for next meeting.
  • Its poll system helped us to find right time slots for our meetings in asynchronous manner.
  • Some of us made brainstorming in this area but they were more likely to be forgotten than being considered for project because of the informal nature of the platform.

4.3 Github

  • We have used GitHub as version management system for our project.
  • We have used GitHub's document system wiki to store our researches and milestones.
  • GitHub allowed us to make our work asynchronously.
  • Its version control system allowed us to revert unwanted changes.
  • Its issue system allowed us to follow what need is to be done and what is being done more easily.
  • Flag system helped us to categorize our issues to help non-assignee viewer navigation in issues.
  • Issue template feature helped us to create our issues in a same pattern.

4.4 Figma

  • Figma is a special tool for designer to make their design more easily and better looking.
  • We have used Figma to design our Mock Ups in a modern way.

4.5 Diagrams.net

  • Diagrams.net is a tool for designing diagrams.
  • We have used diagrams.net for designing use cases, sequence diagrams, class diagrams.
  • Its easy to understand UI and drag&drop mentality in elements helped us to create our diagrams very fast.

5. Individual Contribution Reports

Clone this wiki locally