# Design Document

**Author**: \<Team 099\>

## 1 Design Considerations

### 1.1 Assumptions
- This project will be focusing on creating a simple android app for a single user to compare job offers on cellphone.
- It will be a Java-coded program operating on Android mobile platform. All the design should fit for the features of Android.
- There will only be a single system for the app to run (no need to communicate/login between devices). Hence the design should be focusing on functionality of manipulating/comparing offers.
- The app will be designed for users specifically looking for jobs in United States. Hence the app units (US Dollar), location schema (City + States) will only support US situation.
- The app will be used as a personal tool. Thus there will be no requirement for running with big scale database. The app only needs to deal with at most dozens of offers.
- Default dependencies: Junit, Espresso, Mockito, Android SDK, etc.

### 1.2 Constraints
- The app will only be operated on mobile Android devices so is subjected to all constraints of this type of devices.
- The app is designed for single device to use without cloud support or inter-device interaction. Hence the whole system should be able to run independently.
- The resource and time is limited for the team to develop this app from scratch to delivery. Thus the key required features should be prioritized while other additional features will only be considered when core functions are full filled perfectly.

### 1.3 System Environment
Hardware: Google Pixel 4XL
System version: Android API level 30

## 2 Architectural Design （注意这是大标题，下面2.1，2.2是小标题）
*The architecture provides the high-level design view of a system and provides a basis for more detailed design work. These subsections describe the top-level components of the system you are building and their relationships.*
UI, BACKEND HANDLING, 文件系统/androidsqlite

### 2.1 Component Diagram
*This section should provide and describe a diagram that shows the various components and how they are connected. This diagram shows the logical/functional components of the system, where each component represents a cluster of related functionality. In the case of simple systems, where there is a single component, this diagram may be unnecessary; in these cases, simply state so and concisely state why.*

### 2.2 Deployment Diagram
*This section should describe how the different components will be deployed on actual hardware devices. Similar to the previous subsection, this diagram may be unnecessary for simple systems; in these cases, simply state so and concisely state why.*

## 3 Low-Level Design （同理LLD是大标题，内容是3.1,3.2等diagram）
*Describe the low-level design for each of the system components identified in the previous section. For each component, you should provide details in the following UML diagrams to show its internal structure.*

### 3.1 Class Diagram
*In the case of an OO design, the internal structure of a software component would typically be expressed as a UML class diagram that represents the static class structure for the component and their relationships.*

### 3.2 Other Diagrams
*<u>Optionally</u>, you can decide to describe some dynamic aspects of your system using one or more behavioral diagrams, such as sequence and state diagrams.*

## 4 User Interface Design
*For GUI-based systems, this section should provide the specific format/layout of the user interface of the system (e.g., in the form of graphical mockups).*
andorid studio