Overview

A proof of concept "API" to define and send custom forms like Google Forms.

Business and Semantics

Class model

The primary goal of this class model is to define the major elements of the product and identifies the important relationships between them. It specifies the policies and rules to be enforced. It shows classes, attributes, associations, and generalizations in the Form Application domain for both Owner and End Users.

High‐Level Design

This section illustrates a high‐level design for Form Application domain, it shows classes, operations, and dependencies derived from the previous class model.

High‐Level Design Class Diagram for View-controller region(Owner and End User UI)

The UI is a single page application for both Owner and End User and has use cases/sections such as:

Create Form
Edit Form
Form Details?
Add question
Drop question
Edit Question
Confirm send form
Add answers
Confirm submit form
...etc

High‐Level Design Class Diagram for Model region(Owner and End User business logic/functionality)

Persistence

If the end goal of this project is to have a persistence layer, e.g., a relational database, each class becomes a database table in design. Each attribute becomes a column in the corresponding table. Arbitrary keys can be used for each table in the database as primary keys and foreign keys can be used to represent the relationships between the classes.