Milestone Update -- DIAGRAMS 10 APRIL!!!

[kubraaksux]

Discussed in https://github.com/bounswe/bounswe2023group1/discussions/108

^{Originally posted by **kubraaksux** April 3, 2023} Changed to diagrams milestone as 7 April. We have very urgent situation in short notice. We have to focus on this milestone deeply as it is considered checkpoint as instructor. Do your best please! WHAT HAS TO BE DONE UNTIL MILESTONE? - [x] Resolving conflicts - [x] Checking mockups - [x] Use case diagrams - [x] Class diagrams - [x] Sequence diagrams

[kubraaksux]

We need to discuss those in group meeting. And those 5 tasks all has to be done till 7 April.

I recommend making the meeting (04.04.23) extended and doing some tasks at the meeting. We need more meeting as briefings and more work this week.

[kubraaksux]

Those all discussed in group meeting 10.

The tasks

• [x] Resolving conflicts
• [x] Checking mockups are handled in the meeting. Thanks a lot for the efforts to @alperenDagi

And the task

• [x] Use case diagrams pretty much handled and almost done. Thanks to the group for the efforts and mainly to @HarunErgen for extra caring.

Still way to go:

• [x] Class diagrams
• [x] Sequence diagrams

[kubraaksux]

About Milestone Report 1

Deliverables:

Project repository: Up-to-date wiki pages, issue tracking. Requirements: Software Requirement Specification, Scenarios, and Mockups. Software design documents in UML: use case, class, and sequence diagrams. Project plan, RAM (responsibility assignment matrix), and Communication plan. Milestone report.

I made a summarised list. At the briefing 09.04.23 assignees will be decided for overall report and everyone is responsible for individual reports.

Instructions:

Prepare the milestone report as a GitHub Wiki page using wiki Markdown. Name the report "Milestone 1 report" and add it under a section called "Milestone Deliverables" in the GitHub Wiki. Include the following sections in the report: a. Self-introduction with the course name, group number, and contributors. b. Table of Contents. c. Executive Summary: Summary of project status and any changes in plans based on reflections. d. List and status of deliverables. e. Evaluation of the status of deliverables and its impact on your project plan. f. Evaluation of tools and processes used to manage your team project. g. Individual Contribution Reports (in alphabetic order by member SURNAME).

For Individual Contribution Reports, each member will create a separate page using Markdown and add the link to their page under the 'Individual Contribution Reports' section of the milestone report. The individual report should include: a. Member info (name, group). b. Responsibilities: Overall description of assigned responsibilities. c. Main contributions: Overall description of contributions to the project until the milestone, with links to work and related issues in the project repository. d. Management related significant issues: List the most significant issues that contribute to the management of the software project. e. Additional information (optional): Further relevant information related to contributions.

[kubraaksux]

I added a logo to our project to mark the first release milestone of our product. A logo is a crucial element that represents the identity of the product and establishes a visual connection with customers.

[kubraaksux]

logo update @HarunErgen

[kubraaksux]

• [x] Tasks are done before milestone