We then write the function of the "Complaint handling" module.
To start with the needs analysis, let's look at our needs:
Interface Description:
2.7.2 Function Description
(1) Complaints handling management: Query the user submitted complaints information, can be based on the complaints Department (department A/b), the time period of complaints, the status of inquiries. In the list information to show the complaint title, the department of complaint, the complainant, the time of complaint, status (pending, accepted, expired), operation; The contents of the Action Bar is "processing", click "Processing" in the Open query page to view the specific complaint information and can reply to the complaint information multiple times , once the reply indicates that the complaint has been accepted.
(2) I would like to complain: Click on the "I want to complain" entry page in the "Work homepage" to add the following: The complaint title, the Department of the complaint (department A/b), the complainant, the details of the complaint, whether the complaint is anonymous.
(3) Complaint details: In this page first of all to clearly show whether the current complaint has been accepted, and then display the complainant's information, the complaint information, processing information (historical reception information) three parts, and in the page can be unlimited to the acceptance of the reply. The complainant's information includes: whether anonymous complaint, the complainant's unit, the complainant's name, the complainant's mobile phone, if it is an anonymous complaint, it does not show the complainant unit, name and the number of the middle 4 digits of the mobile phone numbers using the * number instead. The complaint information includes: The time of complaint, the Department of complaint, the complainant, the title of the complaint and the content of the complaint. Reception information: If there are multiple responses will be multiple reply message display, display content including reply time, reply to Department, reply person, accept reply content, can reply again.
(4) Automatic complaint processing: The last day of the month before the end of this month, the complaint is automatically processed, the status of the complaint information is changed to invalid. You cannot reply to this type of complaint in background management.
Statistics: The number of complaints per month in the corresponding year is counted according to the year and displayed on the page in the form of a chart, with the option to view the current year and the number of complaints in the previous 4 years. You can select a different year in the page, and then the page shows the curve chart for that year.
Attention:
demand must read and then go to do, or understand wrong to do is just not work hard, so in demand up and down the kungfu is not a waste of time.
We first construct our conceptual model (using PowerDesigner):
The first is the concept map of the complaint information sheet:
Then a conceptual model of complaint response information
Finally, make a relationship between them:
Then use the "Generate physical Data Model ..." feature under tools in PowerDesigner to turn the conceptual model into a physical model:
Then double-click each entity and click on "Preview" to generate the build statement:
The two built-in statements were:
CREATE table complain ( comp_id varchar (+) NOT NULL, comp_company varchar, comp_name varchar, comp_mobile varchar, is_nm bool, comp_time datetime, comp_ Title varchar (+) NOT NULL, to_comp_name varchar (+), to_comp_dept varchar (+), Comp_content text, state varchar (1), primary key (comp_id)); Create Table complain_reply ( reply_id varchar (+) not null, comp_id varchar (+) NOT NULL, replyer varchar (a), reply_dept varchar (+), reply_time datetime, reply_content varchar, Primary KEY (REPLY_ID)); ALTER TABLE complain_reply add constraint fk_comp_reply foreign key (comp_id) references com Plain (comp_id) on the delete restrict on update restrict;
Copy the Build table statement to the database to create the related table (here we use the SQLyog GUI management tool):
Here we build the database tables successfully, and next time we use reverse engineering to create entity classes and mapping files in the project.
Reprint Please specify source: http://blog.csdn.net/acmman/article/details/50016001
"SSH Project Combat" national tax cooperation platform-28. Complaint Request Analysis &CDM&PDM
