The meaning of website project management (WPM) is the project design and management of web-based project management, namely web applications as the main representation of the architecture, such as browser, network, and web servers and other key main body. It is mainly reflected in the website design to develop project management for web applications for the client (for example, information website, online store, virtual post office, customer relationship management.).
In this article, the author uses the website project management (WPM) and the software engineering, and combines the actual work experience to complete the integration of the role, division of work, division of labor, and processes of website engineering management (WPM). Make the website project management gradually go to normalize.
According to the author's experience, website project management can be divided into the following six phases:
1. Demand Analysis and Change Management 2. Project Model and Business Process Analysis 3. System Analysis and Software Modeling 4. Interface Design, Interaction Design and Program Development 5. System Testing and Document Writing 6. Customer Training, Technical Support and After - sales Service
It should be noted that although these stages have certain continuity, it is not completely partitioned, such as demand change management and testing, and document writing is throughout the project process, while many work is cross-performing. The application of network technology applications cannot completely change the traditional workflow, nor is it simple to replicate traditional workflows, and require reasonable optimization, improvement, and recombination of traditional workflows.
This chapter includes the following:
I. Write a project model document, so that everyone is clear. Business process analysts conduct process design three. Interface engineers design user interface prototype four. Reflections on users - based design.
Summary
I. Write a project model document, so that everyone is clear
Why make project model documents?
Usually the needs of the user is messy, incomplete, or even incorrect, and more detailed demand is often excavated in the development of project development, which is an extremely troublesome problem for developers. Then, after conducting a demand analysis, the project model document can be produced. Before the project enters the development, the two sides have a common understanding of the results of the project to begin, and the need to expose the need to change, then it will greatly improve the development. Efficiency and quality. Project workers who lack experiences often do not wait for systematic analysis and development after accepting the task, and don't want to repeatedly push the project demand and model with customers, and I want to have a lot of falsehoods for customers during the development process. The power of Niu Erhu is not good, and I know, where do you want to go in the marathon game where you don't know where the end is? ! Therefore, after confirming the initial demand for the customer, the business should perform the design description of the project model.
First, we must define the vocabulary, not every customer or project team member can understand the difference between "users", "role", "use case", and it is not necessarily understanding "channel", " Front desk "," Background "does what mean, in order to make the project model document make each viewer correctly understand, define the vocabulary is very desirable, especially for users who have the first time information design for traditional industries.
The model description is described in the most natural language that this document is a further description of the demand analysis report. Make the customer representative, project manager, developer to produce the most intuitive impression of the upcoming project through the project model, and discuss the key issues and reach a unified understanding, such as functional requirements, performance indicators, operating environment, investment scale, etc. Wait.
Second. Business process analysts carry out process design
Business process analysts should be good at simplified work, and must have a professional domain knowledge with Guangbo, and have good communication skills. Business analysts need to assist customers in summarizing the needs, find all the business leads, determine the business leads, and the relevant activities and processes of each protagonist should be clearly developed, and finally designed the logical view, the user interface schematic. For example, an electronic store system, in addition to the role of system administrators, business managers, salespersons, logistics and distributors, customer service personnel, may also have different roles of external collaboration units, such as suppliers, distributors, advertisers, and Buy users, even refine to ordinary consumer users, VIP consumer users, group consumer users, etc., the entrances and processes in each type of role participation in system activities are different, through logic, and schematic, business process analysts will The mechanism of the system is briefly described.
At the business process design, you need to pay attention to the following:
* Investigate user network environment and configuration, enabling architects to develop a reasonable and feasible system architecture;
* Investigate user preferences and skill levels, which will directly affect the depth of project development and user interface design;
"Although developers and managers are easy to think of them understand users, they are often not true. People often pay attention to how users perform tasks, rather than user preferences, and in most cases, preference issues are not just simple It is considered that users need, although it is worth studying itself. Preferences are also determined by experience, capabilities, and use environment. "
* Predict and formulate the performance indicators of the system to provide a basis for the test plan for the test staff.
Many project design pays more attention to the implementation of the function, the test phase seems to meet the needs of customers, but once it is put into use, it will find a bottleneck in performance. Because of the limited level of understanding of expertise, it is often overlooked in this regard, so in order to avoid the dispute in the future, it is very important to predict and formulate performance indicators.
Third. Interface engineers create user interface prototypes
In order to create a user interface model before actual system development, it is very important to develop prototypes than the cost of actual development. In the initial stage of the project, create a complete user interface reveals and test all functions and availability of the system, and It is possible to make the customer representative to participate in discussions and modifications, which can greatly improve the success of the project.
After creating the correct and feasible prototype, system analysis, design and code writing must be carried out in accordance with the prototype, ensuring that the system is correct, the tester and customers can also participate in the inspection in real time during the development process, which can effectively guarantee Quality of the project.
According to the process analysis logic map and schematic provided by the business process analyst, the interface design engineer began designing the original user interface. At present, there is no stage for interface designers who have not entered the fine design, so the most important thing is to business. The process is completely manifested and confirmed and defined by designing style, design specifications.
Interface engineers use reasonable layout design user interfaces after fully understand customer needs and all business processes. For example, the homepage of the website, the homepage needs to be displayed, navigation classification and performance methods, the entrance of various business roles, etc.
It should be noted here that the user interface is not just the interface browsing by the website visitor, but also the different user interfaces such as special users, administrators, business partners, or even prompt interface, warning interface, error interface, etc. Designed a complete user interface prototype not only makes customers and testers more easily and needs, but also acts on the quality of the project.
IV. Reflections on the user-centric design
Regardless of how much the project design developer is, it is not the end user of the system, and the need to meet the needs of customers is the key. The system designer tends to hang the slogan centered on the user, but in actually works. In a large amount of imaginary, or for a lazy or due to conditions, different users who use the system may have unexpected obstacles. Really centered, you must first give up the experience and imagination of the deposition in your mind, go to the customer work, observe how to work, and talk to our customers.
There is a course called "blind square" in the team expansion training. How can people who have seen a group of people do not pull a long rope into a square scene? Will people know how to listen to and obey? We can't assume that the user is a sound person or a blind, and it is impossible to imagine how the user should do it. Only how to observe and communicate can we develop a plan that truly in line with the user needs.
Some experts say that developers should determine the user's composition and let users go as early as possible and make several familiar users, their tasks, and demand:
* Talk to the user * to the office to visit users * Observe users work * Learn about work organization * Self-attempt * Use users want to say while thinking * Let users participate in design * In design groups include expert users in design groups * Perform task analysis * Use survey and questionnaire * to develop tape targets
It is possible to do accurate, objective and meticulous, not only guarantee the quality and maturity of the system, but will also make you a high satisfaction and trust in the future. Cooperate open the door.
V. Production Design Plan
At this stage, you can say that you can master the needs of our customers and have a clear understanding of the system development of the planned implementation. It has reached a consensus with our customers, then the production design plan is very necessary when entering the next stage. .
The design plan is a comprehensive description of the entire system, as the basis for systematic analysis, test staff, and also the standard of customer acceptance, as one of the content of the business contract, so you should carefully write the design plan carefully.
According to the different projects, the content of the design plan may vary, the following author provides a sample for your reference, which basically covers the core elements that need to be confirmed and described in the plan.
Summary
During the working process of this phase, the core task is to analyze the requirements of the previous stage, and the project model design and business process analysis are performed, and the user interface prototype is made to obtain the user's confirmation, and finally complete the "design plan" approved by both parties. As the basis for the next stage of system design and software modeling. How to complete the work of business process analysis at high quality, the experience of the author is as follows:
* True to design and record in the actual working environment of users; * Carefully find various business leads, and express various operational process steps in different protagonists; * Simplify demand, summarize customers' demand, Seize the core questions; * Refine demand, target core issues, simulate user roles, and further confirm process and standards; * Seriously formulate design plan, and lay the foundation for the next stage.
