Demonstrate the skills required to:

Develop UML use case diagrams, class diagrams, and sequence diagrams depicting the design of the case study domain layer.

Design your domain layer such that it includes a minimum of four established design patterns in addition to the Builder design pattern.

Provide in the design the necessary links$/$connections to both the presentation layer and data management layers.

Develop a UML class diagram and deployment diagram depicting the design of the multi$-$tiered Java application.

Instructions

The first stage is composed of three main tasks, which will lead to three deliverables.

Task $1$: Establish a realistic situation

The first step is to establish the context for the project that your team would be asked to work on$.$ The context should be as realistic as possible so that as you go through the course material, you can imagine how you might apply all of you learning. If you are currently working on a web development project or have worked on one in the past, you can use that for establishing the context, or as an inspiration of your own version.

Do not worry if you do not have such personal experience. Your project can also be based on theoretical need, on a web application you use or on any old or new idea you may have in terms of solving a problem you may have seen or thought should be solved through a web application. This means that you can also liberate all your potential as entrepreneurs and do not limit yourselves. After all, lots of good products have resulted from school projects themselves.

Your realistic situation idea should be expressed in no more than one page and clearly state the problem you are trying to solve and your proposed solution to it$.$ Do not worry about the how, focus only on the what.

Task $2$: Product Requirements Document

A product requirements document $($PRD$)$ is an artefact used in the product development process to communicate what capabilities must be included in a product release to the development and testing teams. This document is typically used more in waterfall environments where product definition, design, and delivery happen sequentially, but may be used in an agile setting as well.

There are several different ways to present this document. For the purposes of this project, you can use any format you want, so long as it helps you define the:

Objective

Release

Features

User flow and design

Analytics

Future work

See the article: What is a good product requirements document template? $[6]$

As a recommendation, use the "Product Hunt" template which is widely used by startups and freelancing consultants $[2].$

In terms of features, there is one that you must have in your project, regardless of the nature of it$.$ That is $-$ User Authentication. Keep that in mind.

Task $3$: Initial design

A minimum viable product $($MVP$)$ is a concept from Lean Startup that stresses the impact of learning in new product development. Eric Ries defined an MVP as that version of a new product, which allows a team to collect the maximum amount of validated learning about customers with the least effort. This validated learning comes in the form of whether your customers will purchase your product. $[1]$

Although it is expected that you come up with a full concept of the product you are intending to build, it is always important to keep in mind that you should not try to do everything at once. Choose a subset of features that would make your MVP$.$

Here is where we get a little more technical. Although this is an early stage in development and we are not intending to define everything now, it is always good to know where we are heading. So$,$ an initial modelling for the solution you are going to be working on will be a good start.

For those features you have decided that will be part of your MVP$,$ you should write UML use case diagrams, class diagrams, and sequence diagrams.

Although you may be already familiar with them, you can find a quick and yet complete reference in the web publications: UML Use Case Diagrams $[3],$ UML Class and Object Diagrams Overview $[4]$ and UML Sequence Diagrams $[5].$

Submission:

Your submission should include:

Context overview document. A realistic situation idea expressed in no more than one page that clearly states the problem to solve and the proposed solution to it$.$

Product requirements document. A description of the entire product that can be expressed in terms of the "Product Hunt" template.

MVP initial design document. A set of UML diagrams that includes: use case diagrams, class diagrams, and sequence diagrams.