Analysis of "Student part time system"
Introduction
Get the title of the system, first of all, analyze it. How many users will there be? How
many tables should a database design have? How many functional modules should
there be? What is a flowchart? How many pages are reasonable?
Remember, we only have four weeks, so don't be greedy, just do the basic core
functions.
It is suggested that there are 2-3 users and 3-5 tables in the database.
Take the "Student part-time system" as an example to illustrate
Suppose that students can see what part-time content they have on the website.
Click the part-time job you are interested in to view in detail, and select the
part-time job you want to do to submit an order. The administrator is responsible
for publishing part-time job content, reviewing orders submitted by students and
arranging interview time.
In order to make the system simple, it is no longer considered to log in by the
part-time provider, and the administrator should complete the input, release and
audit work. Students can only submit one order at a time.

 

2. Data flow chart analysis (1) Student user data flow chart: Change password Has an account pumber or not? Exit the Student -Yes Login system Enter the part- time module. No Register No Anterested n View part- Approved or not? Submit -Yes part-time jobs or not? time content. the order -No- Yes Check the interview time (2) Administrator user data flow chart: Edit category Edit part-time information Administrator Login Edit student Review order Change password