Foreword
With the continuous development of technology and the demand for the functionality of the website, the design of the website project can no longer use the static HTML file to be implemented, and the previous year's website design is free from one or two web designers. Compared to the design, the design and development of the website project is more and more like a software engineering, and it is increasingly complex, the design and development of the website project enters the era that needs to emphasize the process and division of labor, establish a normative, effective, and robust development. Mechanism can adapt to the needs of the user's changing needs and achieve the expected plan target.
The meaning of website project management (WPM) is a project design and management of web-based project management, which is a web application as a main manifestation architecture. This architecture includes browsers, networks, and web.
The key main body such as the server is mainly reflected in the website design to develop project management for web applications for the client (such as 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, the website project management can be divided into six stages of the following L:
1. Demand analysis and change management
2. Project model and business process analysis
3. Systematic analysis and software modeling
4. Interface design, interaction design and program development
5. System testing and documentation
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.
(1) How to do demand analysis and change management?
The communication of the salesman and the customer, writing a demand analysis report is the foundation of the project. The project is based on customer needs, not for technology.
This chapter includes the following:
1. Let customers speak freely, Ros is all required
2. Analysis of potential demand through phenomenon
Third. Use the natural language description project model
IV. Use the schematic and chart to show the needs of the user.
5. Who wants to see demand analysis report?
6. Establish a demand change log and make a new version of the demand analysis report.
7. Key work roles in this stage
Summary
One: Let customers speak freely, Ros is all of all the needs
Let users explain all the ideas as clear as possible, and list all the requirements, do not miss it. At this time, it should not be afraid to "seduce" the potential demand for customers and increase the workload of design and development, which is dragged into the quagmire by the future customers' endless changes. Incident, the analysis first throws it, and accurately records the most original and most complete requests for users to complete the first step.
Obviously, if the customer's needs are not complete, it may generate changes outside the meaning, and even this change will destroy the model and structure that has been made, then this project is destined to fail from the beginning; such as site all The functions are all achieved, and there is no problem in local testing, but you don't know if the customer's system is to bear access to 1 million independent IP a day, and you think of it is the access traffic of 10,000 independent IP access. A slight experienced developers will understand that such a disaster is a disaster, whether it is the application server, the database is still re-developed!
2: Analyze potential demand through phenomenon
In many cases, customers are not professionals, can't expect them to help us to organize their key and technical difficulties, this requires us to analyze, summarize and organize us, especially those who talk about it, especially customers. It is specially worth noting that there are very difficult to achieve difficulty and high intensity. Customers often have a very blurred concept. It is a generally giving in general, and the scale is difficult to control, which requires business people to listen to the customer's detailed instructions, and predict customers The potential demand for modifying upgrades may be made during the development process and future applications.
For example, when designing an office automation system for the customer, it may be necessary to reserve the access to the customer to interact with their business units; consider the advertising management server when designing the mail system; designing the network electronics store Increase the statistical analysis of inventory products, etc., limited to time financial resources, customers usually can accept the development process of phased implementation, in demand analysis, early development of the future demand changes, in addition to making the project development more smoothly, It is also a better foundation for further deep depth of the future.
The author was responsible for a large news site design. When the customer took nearly 50-page design requirements report, I found that there is a content of the four-page content to be repeated, and one of the pages. The corner painted a button "Search Other Websites Related News", and did not do any description, only the workload of this 10 words completely diverted all other four-page repetitions to the work, the customer is completely I don't know if this requirement is actually the development of search engines. By negotiation, guests agree to modify the engine in the station.
Three: Use the natural language to describe the project model
Demand analysis written while communicating with customers and surveys, as far as possible, use natural language, although customers' level and qualifications are different, the most natural description can clearly clear the members of the project. Understanding the meaning of demand, is not to produce a deviation in understanding. For customers, such model descriptions are closest to real, easy to participate in revisions, and can be based on the basis for testing and acceptance.
Please compare the following two descriptions about demand.
"When the user visits the home page, you can click the 'User Customer Channel' button, pop up the window of the 'User Name and' Password ', and open the first page of the customer channel in the new window, display all the functions of all operable functions on this page. Navigation bar and the latest introduction news link list "
"Site is divided into two states disclosed and encrypted, and the unique users can access the encrypted information through authentication mechanisms and provide different functions than ordinary users."
The previous paragraph describes what we are easily imagined to design the designed website, and the description of the next paragraph may make countless different versions, causing a disagreement on demand.
Four: Use the schematic and chart to show the needs of users.
Demand Analysis No matter how expression is still abstract, it is difficult to understand the customer, and the basicly determined demand production is most intuitive.
Making schematic can have many ways, using the PowerPoint or Visio production process, using the HTML document production interface schematic, the simplest use of the drawing and Word forms can be fully, the key is to use the schematic diagram to put the customer's needs and the future The design system is reflected. Before the system analysis and program development, the two sides will have an intuitive understanding of the products to be completed in the future. In other words, when the product has not really entered the development stage, the two sides reached the results of the work. Unified comments, which will greatly reduce the troubles of demand changes, and customers are more easily involved in the development process of the project, and ensure that the project is carried out in the correct direction.
There is such a description in RUP:
"Use movies, cartoons, pictures, forms and cartoons to start, tell us who users are, what is going to happen, how to happen, help collect and improve user needs in user friendly ways.
Encourage more creative, innovative design solutions.
Encourage team review and avoid all people do not want to appear.
Be sure to implement features in understanding, intuitive manner.
It makes the interview process easily and avoids the occurrence of interviews.
Simply put, the production schematic is how to use the tool to the user (protagonist) system how to adapt to the needs of the organization and indicate how the system will work. The coordinator will show the initial sash to the team, and the team members provide advice. Thereafter, during the seminar, the guide is also evolved in "real-time" evolution. So, you need a drawing tool that can easily change the bidboard. In order to avoid distract attention, it is generally best to use simple tools such as charts, whiteboards or
PowerPoint. "
Five: Who wants to see demand analysis report
Project managers, system analysts, development managers, interactive designers, testers, document staff include customer representatives should look at demand analysis, and conduct common discussions, reach a consistent opinion.
We often encounter the business people's hard work, but it is difficult to implement the developers, and the products designed by technicians often do not understand the customer's recognition, even disputes, so participating in project development. Personnel should have unified and clear understanding of this demand, and make an opinion on the needs according to their own work, and ultimately determine the goal of project implementation by revising the needs of customers.
E.g:
The project manager can form the needs of the team to form the required work environment by providing the needs of the team to form the development cycle.
The restrictions and functional requirements of development cycles may affect what kind of language and tools are prepared by programmers;
The skill level of the user will affect what accuracy does the interactive designer performing the front desk design;
Interface designers determine the performance of the project according to the nature and positioning of the project.
Test persons understand the test environment and conditions to track and detect the quality of the project;
With the table below, we can see the workflow for different roles based on the needs of the needs:
Six: Establishing a change log, making a new version of the demand analysis report
Although we have spent a lot of efforts to make the most possible efforts in demand analysis, it is almost certain that this demand analysis will change in the development process, maybe it is from the omission of customers, or may be during development Inspired, this change is sometimes so frequent and trivial, so that it is often impossible to feed back the changes in time to the various roles of the project, then do a good job of demand change logs is very important.
At the back of the demand analysis, the modified demand analysis is made into a new version, keeping each change version, not override, so it is easier to track the work adjustment of the demand change process. .
In the demand analysis of the new version, the change in multiple parts is indicated in a special way, and the change in the log is recorded.
About demand analysis and change management can refer to the following figure:
7: Key work roles in this stage
During the process of demand analysis and change management, the greatest role is the customer representative, salesman and project manager.
The customer representative proposes the needs, the salesman helps organize and analyzes, and the project manager evaluates the entire project.
In actual work, many project failures are related to demand analysis. Customer representatives and salesmen usually do not engage in technology development, often in order to discuss the technical difficulty, workload, time progress of the project, which requires project manager or technical staff.
In order to reduce the risk of projects, improve work efficiency, there is a need for the need to design specifications to help customer representatives and salesman better completion tasks.
The following is a template for a demand management plan can be used as a reference: 8: Summary
According to the author's experience, we must have a good demand analysis as soon as possible, maybe it may be half-mexion:
Listen carefully, all the requirements of the customers;
Analyze demand to confirm the operational system model;
Use the most natural language to describe the system so that each developer will not disperse;
Quickly determine the user role of the website;
Such as visitors, members, important customers, front desk administrators, website administrators, salespersons, etc .;
Analysis Determines the permissions and operable functions of each role;
For example, members can view special information, modify personal information, exit landing, etc .;
The front desk administrator can log in to the management system to publish editing modifications, and can review membership.
Website administrators can change the column, modify the website interface, etc .;
Production flow charts and schematic will show demand;
Let customers participate in the design of the diagram, and the correct demand changes in time.
Produce the change log, keep the upgrade version, demand management through version control;
Each participant sees a common effort target through a Demand Management Plan.
