Program flow chart
- A graphical representation of a specific step in the execution of a program using a universally specified standard symbol
- The design of program block diagram is on the basis of processing flow chart, through the detailed analysis of input and output data and processing process, the main operation steps and content of the computer identified
- Program block diagram is the most basic basis of program design, so its quality is directly related to the quality of program design
The above is baidu Baike's explanation of the flow chart
- As long as there are tasks, things, there will be a process to complete the task, so there is a flow chart
I understand it
The role of flowchart drawing
- For communication with non-development departments
What kind of work should people do? Describe the main tasks
Example: The business process of thousands of recruitment interviews:
HR invitation – sign in – fill out the resume – attend the lecture – interview – the interviewer input the interview results
- For communication with developers: for developers, more attention is paid to the whole check-in process, the flow of data. What if I failed to fill in the small program? What if I can’t check in? How to deal with it?
First of all, after we get the requirements, we often start to draw the interactive prototype as soon as we get started. In this way, our process may be unclear and the prototype needs to be redrawn. So we’d better draw a flow chart first, then a prototype
Second, developers often say that design has no logic, and flowcharting is one way to establish your logic, which is ultimately used in design review presentations.
Classification of flow charts
Common Flow diagrams include Transaction Flow and Page Flow.
At work, as a UED, you might find that PD talks a lot about business processes, while we, as interaction designers, produce more page flowcharts. What is the relationship between a page flowchart and a business flowchart? Who came first and who came next?
Similarly, take the hr interview system as an example: From collecting information to the end of the interview, what methods should I use to complete the whole process, which departments should cooperate with me, and how should I cooperate? How can existing operations be optimized?
Through the above story, is it better to understand the relationship from strategy, tactics, business flow chart to page flow chart?
To summarize: first, there is a business need and a business goal. What is our vision? (strategic)
Then what tasks do we need to break down and how do we execute tactics? (tactics)
What departments and posts should be organized and coordinated? (Organizational Structure)
And then the business process when different departments collaborate to accomplish something? (Business process)
After the business process is basically stable, it is often considered to optimize efficiency, so a system is born to support the process, reduce human links, and promote data collection (System vision)
In order to design this system, PD needs to think about what functions can replace the human work of a certain link (functional requirements, system processes).
No matter what kind of function will eventually be presented in the form of interface, designers will pay attention to the user’s task flow and behavior path in the system, so that users can complete tasks more efficiently and happily. (Page flow)
Of course, in addition to business processes, system processes, page processes, and data processes are concerned.
Drawing flow chart
Tool processon
Next, start your act