Petelai project experience collection (5) ___ system process design, petela __

Petelai project experience collection (5) ___ system process design, petela __

There is a process design problem in the design of petelai project, though. NET and Java have workflows, but considering the small size of this project, I simply borrowed some workflow ideas, designed several tables, and then controlled the process through code. The following describes the specific process design by taking the physical process in the "service identification Ticket Business Process" as an example. The business process of physical service identification includes the following steps: fill in the form of the agent, print the QR code, unpack the package, communicate with the Agency, split, analyze the fault, each role approves the fee, and submit the fee to the expense pool (where the money of each agent is counted ). For the process of the repair ticket, see:

Because there is more than one business flow in the system, the system process design table has a task table (such as the service identification service and Order Management Service), the process step table corresponding to each task (such as the steps to be completed in the repair base process), the Maintenance appraisal process table (equivalent to the third table, contains the repair ticket ID, process step ID, and completion status. For details, see:

The task table mainly records the tasks with procedures in the system. The process step table records the process steps corresponding to each task. One field has a priority, which indicates that each step is the first step; the Business Process Table mainly records the process of a task to the first step, and uses the State field for statistics at the first step. This table also records the operations, content, and time of each step.

The chart shows that the process design is relatively simple. The implementation process is as follows: after the ticket is filled out, the agent manually clicks the button to bind the repair ticket to the process steps, the status of the first process is yes, and that of other processes is no. After the first process is completed, 2nd processes are performed, the third process is performed, and the subsequent processes are performed in sequence. This design only modifies the state of the node each time a knot is completed.

 

How can I query the list information (list) of a node? You can do this by using a line of code:

SELECT * FROM View_DLS_WXJDLC where id in (select id from View_DLS_WXJDLC where yxj = @ YXJ-1 AND State = 'Yes ') and yxj = @ yxj and State = 'no' AND IsFYC = 'no'

 

The view used in the Code is the view created in the two tables of the maintenance authentication process and process step. This line of code queries the list of repair tickets that have been completed in the previous step and have not been completed in this step.

At this point, the system process design is simply described. Another design is to create two tables in addition to the task table and task step table. One is to maintain the current process steps, record the steps completed by each task. After thinking about the two methods, we can achieve our business. We use the first method. You are welcome to give suggestions on this design !!! (Too many rows )~

 

The software change process to correct errors or meet new needs is A test B Software Design C code implementation D software maintenance

Software Engineering
1. Definition of Software Crisis: software crisis refers to a series of serious problems encountered during computer software development and maintenance.
2. Two major problems in the Software Crisis: how to develop software to meet the increasing demand for software;
How to keep the number of existing software expanding.
3. Typical Performance of Software Crisis: (1) Estimation of software development costs and progress is often inaccurate.
(2) Users' dissatisfaction with "complete" software systems often occur.
(3) the quality of software products is often unreliable.
(4) software often cannot be maintained.
(5) The software usually does not have proper documents.
(6) The proportion of software costs in the total cost of computer systems is increasing year by year.
(7) The productivity improvement speed of software development lags far behind the rapid popularization of in-depth computer applications.
4. Analyze the software crisis based on the typical performance of the software crisis:
Known production models can be seen as "hands-on workshops" in traditional industrial production methods ". In the past, even now, some companies in China's software industry have developed in a similar way. To be fair, many successful application development projects have been achieved in one way or another. It can be said that this method supports the reasons for early stages of software development. However, in our factory, "there are too many projects that fail, for example, development cycles that cannot be controlled, this project shows the results to users and does not realize that the final project with severe losses exceeds our expectation. the pain of this failure is our loss. It is difficult to manage software development if the technical staff are seriously insufficient.

Do you think the software is "a correct view? If not, refute it.
1. Solve the problem in the following situations based on your own experience.
The view of the software program is incorrect because the software is equal to the program plus document plus data.
(1) file software is a very important component and plays a very important role in the software development process.
(2) Documents should be prepared at each stage of software development. This is a medium communication between developers and users as well as developers and project managers.
(3) The performance of the file software in different stages.
(4) Documents of programs and documents must be valuable.
(5) Documents directly determine the quality level of software quality.
(6) basis for software testing and maintenance of documents. In the absence of files or incomplete files, testing and maintenance of large software is unimaginable.
(7) The file is based on reusable software.

5. Software Engineering definition: software engineering is an engineering discipline that guides computer software development and maintenance. The concept, principles, technologies, and methods of engineering are used to develop and maintain software. After time tests, it has been proved that the correct management technology is combined with the best possible technical methods, cost-effectively develop high-quality software and maintenance, which is software engineering.
6. The basic principles of software engineering, case studies (strict management, evaluation phase, review of the Brooks' Principles) of enterprise information system projects developed by the company. As the project progresses, the Project Manager detects the progress of the project according to the plan and starts to recruit personnel. However, for special reasons, the project manager fails to recruit the ideal person. Only in this way can the requirement for new employees be lowered after they arrive, the project manager finds that the progress of the project is slow, and the best manager is not its solution. Analysis of the Basic Principles of software engineering.
? Software development is different from traditional mechanical manufacturing, and many people do not have the same power. For outdated projects and new plans, you may have more project delays. Because there will be a lot of new errors and confusions for new visitors, developers should spend time communicating with their original work and ideas. Therefore, the actual development time is shorter, so it is very important, formulate corresponding project plans to explain new projects.
7. Software Engineering Methods: methods, tools, and processes

The software life cycle defined by the software (from the three time periods of the concept, 8), software development, operation and maintenance (also known as software maintenance) 3.
The software-defined cycle is generally divided into three phases: problem definition, feasibility study and requirement analysis.
1 problem definition 2 feasibility study, requirement analysis overall design, detailed design, coding and unit testing 7 testing 8 software maintenance
Software development found an error. Later, some people said that the higher the price was paid to correct it. Isn't it? Please explain your answer.
Pair
10. Software Process... the remaining full text>

A system has five concurrent processes and shares N tape drives. Each process requires a maximum of three. Ask the minimum number of N instances in which the system will not experience deadlocks.

3 3 3 3 3 => 2 2 2 2 2 + 1 = 11
(A deadlock occurs in the case of five or two processes. If another process is added to any process, the process can be fully satisfied. After the process is executed, three other processes can be released for use by the remaining processes)