The demand analysis of mobile application development in "Lower kitchen"

I. Overview

1.1. Development background

1.2. Development Goals

1.3. References

1.4. Design principles

Second, demand analysis

2.1. Project Definition

2.2. Demand statement

2.3. Operation Use Cases

2.4. Functional Analysis Division

2.4.1, Login Registration

2.4.2, user Management

2.4.3, Community module

2.4.4, meal plan

Third, the overall design and implementation

3.1. System modeling

3.2. Database

3.3. Code implementation

3.3.1, Login interface design

3.3.2, user management interface design

Iv. Testing

Slightly

V: Maintenance

First, Overview

1.1. Development background

The bottom kitchen is a mobile app with a core element of reasonable diet and social networking.

In the rational diet, the "kitchen" is expected through the user input of the recent body parameters, the system according to the parameters of the database for the user to match a reasonable meal plan. As a result, users can arrange food according to the scientific diet plan provided by the system, and can play the function of keeping healthy.

Second, in the present society, the network has become the necessities of life for people. People use the Internet to socialize, work, play, and shop. Social functions are becoming more and more important, so the bottom kitchen is looking to use the social features of the web to make cooking and food a point of entry, and to build an exchange community that shares both culinary and culinary interests. Through the platform provided by the community, users can publish a variety of content, including but not limited to their own understanding of food and cooking, as well as the record of their own cooking process, or a variety of cooking tutorials and so on. Through the aggregation of the community, people can find like-minded friends, improve the communication between people, so as to obtain psychological satisfaction and existence.

1.2. Development Goals

1. Objective statement

For users, "under the kitchen" is an Internet-based mobile application, the system provides users with meal planning and release and management of dynamic features, through the community to provide these features, users can reasonably arrange food and share happiness.

2. Key Features

1: Registration/Login in multiple ways, including: mobile number, email, third-party account

2: Enter your own recent body indicators, the system retrieves the database to match the meal plan

3: Publish, delete, manage dynamic

4: View, bookmark, block, delete other people's News

1.3. References

The core function of the system is the community, the basic model can refer to the knowledge, watercress. Specific templates can be consulted on the online forum to provide open source projects.

1.4. Design principles

Operating Environment: Android system

Platform development: Android Studio

Database: MySQL

Second, Demand Analysis

2.1. Project Definition

Serial number	Terminology or abbreviations	Defined
1	Tourists	The non-logged-on person enters the system's default identity and can view the basic functionality of the software.
2	User	Registered users, can be published dynamic and other actions
3	As	Android Studio,app Development environment
4	Mysql	Database storage System
5	Leangoo	Submission Phase Results

2.2. Demand statement

The application mainly consists of two main function modules:

1. Meal Plan

The meal plan function is pre-deposited with the relevant data by the database, and when the user types the relevant body indicator parameters, match and output the scientific meal plan to the user according to the corresponding algorithm.

2. Dynamic release

The user enters the "community" interface, optionally publishing the dynamic, and can dynamically do the appropriate permissions to set the action. At the same time, the user can browse, collect, block, report and so on the dynamic of others (in the case of others opening the appropriate permission).

2.3. Operation use case:

Main players	Case
Tourists	1: Browse User Dynamics 2: View basic health knowledge
User	1: Registered Account 2: Login Account 3: Modify My Information 4: Publish, delete dynamic 5: Modify a published dynamic 6: Browse, comment (like), collect, block other people's News 7: report violation News 8: View basic health knowledge 9: Enter recent health indicators to match meal plans
System administrator	1: User Management 2: Data backup 3: Dynamic Audit Management

Operation Case diagram:

2.3.1: Visitors and users

2.3.2: System administrator

2.4. Functional Analysis Division

2.4.1: Register Login

When a user is a non-registered user, that is, as a visitor, the system is entered by default, and the system only provides permission to browse the dynamic and basic health knowledge provided by other registered users. Visitors can register the system in a variety of ways, including mobile phone number registration, email registration, third-party account registration. Users who sign up for login have the privileges provided by the system for all ordinary users.

2.4.2: User Management

User management refers to the system provides users with their own account information management rights, including modifying the user name, modify the binding mobile phone number, modify the mailbox, cancel the account and other operations.

2.4.3: Community Module

Community module is one of the core applications, registered users can use the Community platform for the dynamic of all operations, including the release of dynamic, delete the dynamic and the published dynamic changes and other operations, but also can comment, collect, block other people's dynamic, but also for others dynamic. The system provides a reporting function, and the user has the right and obligation to report the release of a dynamic user that does not conform to international laws and regulations and platform specifications.

2.4.4: Meal Plan

Meal plan refers to the system based on the algorithm for users to retrieve matching and output the appropriate user's scientific diet plan after the user entered their own body indicators. This is the core of the "under the Kitchen" application and its characteristics.

The demand analysis of mobile application development in "Lower kitchen"