The bounswe2023group8 from bounswe

Meriç Keskin Research Page

Search for a Github repository and document it. Explain the repository and why to choose it. Describe what is good or bad about it. Add the result to the group research page.

Project Specs Format

We should agree on some format to list the specs. It can be something like that.

Operation
- Type
- Required Fields
- Access

For example;

Register new user
- POST
- [name: str, email: str, password: str]
- Everyone
Create new post
- POST
- [title: str, description: str, tags: Array]
- Users

Please comment on this issue and lets agree upon a format.

After this, we need to specify the database model and schema (User: {id, name, email, passwordEncrypted, interesAreas ...}). It should be a new issue.

Requirements Analysis Revision

Reclassify requirements within the already existing sections.
Enrich the superficial requirements to remove ambiguities.

Please add any requirement topic you want to enrich under this issue.

Creating Research Page

Create a page title 'Research' . Then everyone inspects at least one good GitHub repository or an API. And documents it. The documentation must be in your own words, have a title, and prepared by field.
Provide examples that illustrate your points about what you like dislike, or how it works. For example, provide an API call with your own attributes and describe the return.
Must use Wiki markdown for documentation.

Creating Glossary List

A Glossary documents the terms which are specific to a given domain, project, or endeavor.

Initialize that part on Requirements.
Add existing glossary items.

Notes Of The Fourth Meeting

Tasks:

Taking the notes in the meeting
Arrange the notes in a way that they are compatible with the meeting notes template and upload to drive
Create a new page for the meeting notes in wiki and copy the content there.

who we are wiki

Create a page on Wiki titled 'who we are' and everyone will document who they are on a separate page.

I read this on discord.
Shoould we change that part?

Research and documentation about a repo

Making a research about a GitHub repo and document it according to the research template in the wiki

Creating template for research notes

Template for researched gitHub repositories.

Improve non-functional requirements

Improve non-functional requirements and research to detail more.

Bahadır Gezer About Me Revision

Revise the about me page for Bahadır Gezer. Revise it according to the new avatars and about me page template.

Spring Security Research Revision

Revise spring security repository research section using the new template.

List Team Members with their Avatars in Readme Page

Team members should be listed in Readme Page with their avatars and names.

Create or ask team members to create avatars
List their names and avatars
Embed About Me pages of team members to their names.
Be sure every member has their Github Account in their About Me page.

Revising research page according to template

Add dislikes to research

Add Tags With Descriptions

Add customized GitHub issue tags for the project repository. Give insightful descriptions for each tag.

As I was exploring issues and thinking about how we can make better use of them, I noticed that we cannot assign more than 10 people for an issue. Our team consists of 12 people and we might have some tasks that require everyone's attention. Does anyone know whether we can create some sort of "role" for team members so that we can, for example, assign the members of that particular role for an issue?

Second Meeting Notes

talking repo deficiencies and assigning new tasks, taking notes

Writing fifth meeting notes

Align the first version of Requirements Draft with the answers we received from our customer.

I will add the new items in such a way that we will be able to distinguish them from older items. I may also move items around for correct classification of functional, non-functional, user and system requirements.

The file to be worked on: Requirements Draft

Details Dropdown in Wiki Sidebar

I believe that the dropdown menu in the sidebar should be removed, here is why:

Drop-down menus have been a popular design element for websites for quite some time. However, there are valid reasons to argue that drop-down menus in the sidebar are not required, slow down access times, and can be bad for user experience.

Firstly, drop-down menus in the sidebar are not always necessary. They are often used to organize large amounts of information, but they can easily become overwhelming and difficult to navigate. In fact, studies have shown that users tend to avoid using drop-down menus in favor of more visible navigation options. This means that implementing drop-down menus in the sidebar can be unnecessary and redundant.

Secondly, drop-down menus can slow down access times. Users have to click on the menu to see the options, which adds an extra step to the navigation process. This may not seem like a big deal, but it can add up over time and significantly slow down the user experience. In addition, drop-down menus can also be difficult to use on touch devices, making them inaccessible to a large portion of the user base.

Lastly, drop-down menus can be bad for user experience. They can be confusing and frustrating for users who are not familiar with the website's navigation structure. Users may not be able to find what they are looking for, which can lead to increased bounce rates and decreased user engagement. Additionally, drop-down menus can be difficult to use for users with disabilities, such as those who use screen readers.

In conclusion, drop-down menus in the sidebar are not required and can be detrimental to user experience. While they may seem like a useful design element, they can actually slow down access times and make navigation more confusing for users. By eliminating drop-down menus in favor of more visible navigation options, websites can improve the user experience and make it easier for users to find what they are looking for.

Creating About Me Page

about me and research page

change about me and research page to meet template requirements

Organize the Requirements Elicitation Doc for better structure and navigation.

Organize the Document that was created in the meeting by the team (Egemen Kaplan)
Place it in Wiki in an appropriate way (Bahadır Gezer)

Requirements Elicitation first draft

Research for styled-components.com

I will make a review on styled-components.com

Creating Template for Requirements

A template for requirements should be created. It should contain necessary titles and subtitles of a requirements analysis. It should provide a structured environment to group members for documenting Requirements. It should also ensure a consistent enumeration system for the terms.

Hasan Baki Kucukcakiroglu About Me Revision

About me page of Hasan Baki Kucukcakiroglu needs to be revisioned in a way that it is compatible with About Me template of the team.

Creating a template for the about me page

Template for personal information pages

Bahri Alabey About Me Revision

Bahri Alabey about me page revision according to About Me template .

Meeting 7 Notes

Creating Mockups for Mobile and Web

We need to research about mock ups and create for mobile and web applications separately

Adding A Link To Real Mockups

Current mockups on our wiki page are drafts. We are working on figma file, whose link is on top of the mockup page, to make our real mockups.

Orkun's Research

Problem
I need to find an inspect a repository in terms of its documentation, issues and PRs.

TODO

Select a repo to inspect
Read documentation, issue templates, and PRs (templates, reviews, CI/CD)
Write the research page

          It should be the fourth since the third one is the meeting with Suzan Hoca.

Originally posted by @bakikucukcakiroglu in #30 (comment)

bounswe / bounswe2023group8 Goto Github PK

bounswe2023group8's People

Contributors

Stargazers

Watchers

Forkers

bounswe2023group8's Issues

Recommend Projects

Recommend Topics

Recommend Org