1. System Specification

1.1. Business Analyses

When customers have a problem with Vinitor they have to call or send an email to the owners. Owners inform their customers about news by sending out emails.

1.2. Market Research

Vinitor wants to help their customers and show them how to use the software. To support them they want their self programmed website which

  • Helps users by answering user tickets

  • Acts as a social media system

  • Offers the users video material

1.3. CLD 01

Click to see CLD 01
diag 25e7788f98e867cde2051d0fb61a26bf

1.4. CLD 02

diag cdc31a63bef0ad22ee6023579614854a

1.5. Current State Of ERD

cld2

1.6. Problem Definition

The owners can not spread news and information to all their customers in an easy way. Emails can get lost and overseen by customers. Customers can not interact with each other. The owners are overwhelmed with the calls and emails.

1.7. Use-case-diagram

diag 33a009455451ad31e82286902f2c97e3
diag 3963c0237d5de1de157c6672bf1f51ca

1.8. Use-cases (Functional Requirements)

  • Users can log in/log out of the application

  • Users can report bugs

  • Users can upvote reported bugs

  • Owners can comment on the reported bugs

  • Owner has statics over bugs

  • Users can send direct messages to the owners (vise versa)

  • Owners can post announcements (Can be liked, disliked and commented by users)

  • Announcements can have dates → calendar

  • Owners can post learning material like blog posts and video tutorials (Users can watch them)

  • Owners can make a survey/vote (Users can vote)

  • Announcements can be connected with email and social media

1.9. Non Functional Requirements

  • Security

  • Usability

  • Accessibility

  • Stability

  • Coexistence

1.10. Goal

The support platform should help with the cooperation and collaboration of customers and owners by simplifying the communication.

1.11. Framework

IDE: Intellij

Programming Languages: Angular (Front end), Java (Back end)

Database language: MariaDB (open source SQL)

VCS: Git (GitLab)

Organization: Jira

1.12. Acceptance criteria

Every use case needs to be fulfilled. The platform needs to run smoothly for every customer.