-
Notifications
You must be signed in to change notification settings - Fork 1
Lab 2 Report
Meeting Notes of Lab 2 can be found here.
In this section, the details of the design of the project is included.
As Group 8, our topic is to build a forum-like platform on a specific domain, such as football, chess, racing, etc. We decided our domain as 3D models, including from 3D animation videos to 3D printing blueprints.
Our platform will have 2 kinds of posts in it.
Visual posts define all types of posts that has a data file, other than the text. These posts will build the ideas shared by the community.
This kind of posts will be used especially for discussions. People also should be able to ask questions to the community, which are not expected to have data files attached.
Users should be able to create an account, using an email address.
Users should be able to login to the forum, so that they can be a part of the community.
Posts can be shared by users of the community. The posts might be visual posts (by which the users share their ideas or productions to the community) or text-only posts (that helps users to navigate through, find or create ideas).
Users should be able to like or dislike posts, so that the posts can be rated with the number of likes and dislikes.
The posts will have comments section, where the users can share their opinions about the post.
Since the objective of the platform is to receive and share ideas, the users might not utilize the idea that is shared on a post whenever they see. So, a user should be able to bookmark a post in order to utilize later.
Users might want to search an idea on the platform. So we want to implement a searching mechanism in the system so that a user shall find the ideas of specific things, such as toy cars.
Users should be able to follow other users
Users might find some ideas insufficient or unsatisfactory. So if they have a brighter idea than the one they did not like, they can challenge them with another visual post, by sharing their own idea.
In the lab, we discussed about the W3C Standard and decided to talk about it in another meeting. We postponed this decision for now.
We noticed that we have to find a name that represents our platform to name the application. We mentioned names like "3Design" and "3Discussed".
We wanted to manage tournaments in the platform, in order to satisfy users' ambition. For now, we talked about organizing tournaments each week, where the posts will be ranked by likes and dislikes. We also want to build a reward system for the winners of the tournaments.
Users with high number of likes, dislikes, shared posts, comments, and rewards from the tournaments will get score based on these attributes. So the platform will be a little ambitious place to get higher scores.
The posts will have tags, based on the context of the details of it. The user is supposed to add these tags. More details about the tags will be discussed in the future.
The posts will reside under specific categories, such as "3D Animation" category, or "3D Printing" category. We want to hold more than 10 categories.
The platform is supposed to have the features of semantic search, just like CMPE352 project of Group 8 in Spring 2024. So, the users might navigate through the platform easily, find ideas they are asking for.
Github Roadmap remains as our choice for project planning & tracking. We have been adding new items to our schedule on a regular basis and we will keep updating it once we proceed to implementation phase.
We have prepared a draft for requirements and we are planning to deliver the final list in the following week.
We are constantly creating new issues based on our efforts and labeling them when necessary to sustain an organized environment. Furthermore, we associate those issues with our roadmap and milestones have a more precise plan. However, we could not make sure whether we should create issues that are assigned to multiple people or let everyone have their personal issues.
We are also planning to finalize our elicitaiton questions list after our meeting with the TA.
We have decided to use Spring Boot for Backend and React for Frontend and Mobile platforms. Furthermore, we are planning to use Online 3D Viewer library for 3D file displaying purposes
🏠Home
- First Customer Milestone Report
- RAM
- Requirements
- Mockups
- Sequence Diagrams
- Scenarios
- Use Case Diagram
- Class Diagram
- Milestone1 Presentation Scenarios
- Meeting Notes 7 - Nov 12
- Meeting Notes 6 - Nov 5
- Optional Meeting Notes 1 ‐ Oct 21
- Meeting Notes 5 - Oct 15
- Meeting Notes 4 - Oct 8
- Meeting Notes 3 - Oct 3
- Meeting Notes 2 - Oct 1
- Meeting Notes 1 - Sep 24
- Deniz Ulaş Poyraz
- Eren Donmez
- Ersel Çanakçılı
- Oğuz Kağnıcı
- Onur Çerli
- Yekta Ercul
- Ali Alperen Sönmez
- Huseyin Turker Erdem
- Mehmet Tuluyhan Sozen
352 Material
- Final Milestone Report
- Milestone 2 Report
- RAM
- Use Case Diagram
- Sequence Diagrams
- Class Diagrams
- Requirements
- Elicitation Questions
- Mockups
- Scenarios
- Milestone 1 Report
- Our Favourite Repositories
- Linked Data and SPARQL
- Web Application Development
- API Development and Utilization
- Wikidata and Wikidata API
- Mobile Application Development
- Android Studio
- Git
- Meeting Notes 10 ‐ May 10th
- Meeting Notes 9 ‐ Apr 25th
- Meeting Notes 8 ‐ Apr 21st
- Meeting Notes 7 ‐ Apr 12th
- Meeting Notes 6 ‐ Mar 14th
- Meeting Notes 5 ‐ Mar 11th
- Meeting Notes 4 - Mar 7th
- Meeting Notes 3 - Mar 3rd
- Meeting Notes 2 - Feb 22nd
- Meeting Notes 1 - Feb 18th