Task 1
The use case options that have been used for description of the activity diagram are:
Payment and Running a match
Payment
Running a Match
HOME
MATCHES
USER
MESSAGES
Sequence Diagram 1
Sequence Diagram 2
Sequence Diagram 3
Sequence Diagram 4
State Chart Diagram
The state chart diagram for the class match is provided here
Entity Relationship Diagram
Basic Java Class
The basic java class Members have been described below. The user object is considered in the member class in this description:
public class member {
private int memberID;
public String memberName;
public int Height;
public int Age;
public void getDetails(){
}
}
Zachman Framework
|
Data (What) |
Function (How) |
Network (Where) |
People (Who) |
Time (When) |
Motivation (Why) |
|
|
Objectives / Scope |
Subscription types Member Types Transcripts |
Register User Messages |
Valentino Agency |
Agent Employees |
Long term Short term |
Find Friends Find Partners Store conversations |
|
Business Model |
High-level Class model |
Business Model Use Case Diagram |
Links |
Organization Chart |
Subscribe Unsubscribe |
Strategic Plan |
|
Model of the Information System |
Data Models |
Object oriented class implementation |
Systems Architectures |
Job Description |
||
|
Technology Model |
SQL DB Design |
Technical Architecture |
Database Administrator |
Finding potential matches |
||
|
Detailed Representations |
User ID data Definition |
Program to register user |
Network Architecture |
|||
|
(Working systems) |
||||||
|
Functioning Enterprise |
Member data Selection criteria |
Set up selection criteria |
Interface architecture |
User |
Long Term Short Term |
Finding potential matches |
Dick, J., Hull, E. and Jackson, K., 2017. Requirements engineering. Springer.
Richards, L.L., 2016. Teaching Data Creators How to Develop an OAIS-Compliant Digital Curation System: Colearning and Breakdowns in Support of Requirements Analysis. The American Archivist, 79(2), pp.371-391.
