1. Use-Case Diagram:

Architecture Decision Record

Status:

Proposed.

Context:

It is an effective technique to build a Use-case diagram for representing system requirements in terms of users by specifying the system behaviours.

Decision:

Use-Case will help us in visualising the different actors in the system, like admin, end-user and use cases.

Consequences:

It summarizes the relationship between use cases and systems.

2. Activity Diagram:

Architecture Decision Record

Status:

Proposed

Context:

It tells the basic flow of the process and how an input changes the system according to the user’s behaviour.

Decision:

Activity diagrams will help us to identify the particular steps needed to take to conclude.

Consequences:

Activity diagrams help us know the pre - postconditions for use cases and the workflow between use cases.

3. Class Diagram:

Architecture Decision Record

Status:

Proposed

Context:

A class defines the method and the variables in the object, which is a specific entity in a program or the unit of code representing that entity.

Decision:

The class diagram gives a sense of orientation and provides detailed insight into the structure of the system.

Consequences:

In some cases, a class diagram is possible to have a big picture of the application without seeing one line of code.

4. Entity-Relationship (E-R) Diagram:

Architecture Decision Record

Status:

Proposed

Context:

An Entity-relationship diagram shown above is representing the flow of data and information between the administrator as well as the client-side server within the application system.

Decision:

Each state of flowing and exchanging data is represented in the diagram and making the application according to the requirements will be carried out easily and efficiently.

Consequences:

By following the particular approach shown in the diagram will lead to the easy maintenance of this system due to the easily intelligible methods used to make the system and it is also designed using specified methods so that we can add some more features according to the need of users.

5. Data Flow Diagram (DFD):

Status:

Proposed

Context:

Data flow diagrams represent the flow of information within the system. How data is utilised and processed to reach the result from the database’s to perform certain operations.

Decision:

We are using a data flow diagram to check the logical flow of information in the system, which in turn will help us in determining the system requirements.

Consequences:

By maintaining mutually exclusive databases for admin and end-users it will be easy to maintain and there will be fewer chances of any mishap due to changes in any one of them.