The following is completed from three aspects: 1. Understand the customer's demand, the customer needs, the customer needs do not refer to the customer's business, and for the programmer's concern, the customer business can only make the idea, here I will proceed The staff and system analysts are disassembled, how the customer business is complete, it should be an additional job, not the program design, so the work to be done should be based on the custom needs to complete the program. The demand that I will talk about here refers to the customer's data needs, that is, collect information on all work sections, such as what kind of data in the first link needs to enter, how many fields can make him entry, what is the future? Reports, the issues contained in the report are clear, but also clearly ask if each entry section contains data provided by the system, such as the water number, time. The next step is to make all the data provided by the customer (unless the customer provides no relationship), then further analyzes the data structure, the data structure is set, and the design of the relational database is completed. Second, the interface design interface design has two premise: 1. It has existed design ideas and corresponding methods that make the interface and background data. 2. There is a report design that can be customized by the user to define the interface element into the database, and the different template is called according to different forms. The interface is generated after the record fill the interface element in accordance with the record obtained by the current interface. Follow the function call to update the data to the memory table or actual database. The data printed by the report is automatically displayed by the record conditions corresponding to the current interface and the record set required for printing. Third, the authority setting permission part is the most core problem of the entire MIS, I divide it into two parts, horizontal privileges and longitudinal permissions lateral privileges: user permissions corresponding to user interfaces each user's corresponding to each interface Elements correspond to visual, available permissions to achieve control data updates, default values, and changing status by changing the corresponding permissions. Longitudinal Permissions: Permissions to the user interface Permissions to each user compare the data and permissions corresponding to the data items when browsing the data, to achieve the purpose of the completed service control user privilege. For the above design, the customer service can be completely thrown, let the programmer only care about the data, by the system analyst, according to the data available to the user and the auxiliary data, and provide the corresponding report, and the programmer pays attention to the relationship between the data and the data. The structure is designed to achieve the purpose of dynamically controlling user needs.
All of the above are personal opinions, I hope the seniors and experienced friends will refer to the problem.
