Website Management Solution

1. Features of website project management
A website project is a project with the Web server as the subject and the browser as the client as the basic architecture. Such an architecture project includes three key subjects: Web server, browser, and network. A website project may be a website or a variety of Web applications, such as online stores, virtual post offices, network office management systems, and customer relationship management systems. Website project management refers to the use of knowledge, technology, skills, tools and methods to organize and manage website projects. Its features are shown in the following aspects:

1) There are many fields involved. In a narrow sense, website projects include specialized technologies such as webpage creation, art design, program coding, system and network management, in a broad sense, it also includes the knowledge of enterprise management, marketing, psychology, advertising, and other fields, during the project, project management tools, documents, design and development management specifications, development and test environment deployment, and other special fields are also involved. This puts a high requirement on the personnel involved in project management.

2) There are many roles involved in the project, and the levels may be uneven. For website project management, the most critical roles are project managers, business process analysts, user interface engineers, system analysts, coding personnel (programmers), and quality control engineers. Project managers divide roles based on the project scale and development depth. If strictly subdivided, a large project may have more than 50 roles to ensure that every detail is managed by professional personnel. In the demand analysis process, the main roles include customer representatives, sales personnel, business process analysts, user interface engineers, and project managers, database engineers, and document engineers.

3) The development technology of network applications is improving with each passing day, so that the development model of website application systems has multiple options. To achieve the same goal, there are many different ways to achieve the same purpose, modern application systems are increasingly becoming a huge integration solution. Different operating platforms, different application servers, different databases, different programming languages, and different transmission media must be considered, project management personnel must understand the advantages and disadvantages of various technologies and help users select efficient, inexpensive, and proactive solutions.

2. Role and requirements of Requirement Analysis in website project management

Demand analysis is the beginning of a project and the cornerstone of project construction. Because of the particularity of the above proposed website project, the broad coverage of the industry, and the high risk of demand analysis, the importance of website project demand analysis is self-evident. In the previous construction failure projects, 80% is caused by unclear demand analysis. Therefore, one of the key factors for a project's success is to grasp the degree of requirement analysis.

In the requirement analysis process, customer representatives, sales personnel, business process analysts, user interface engineers, and other roles are required. The sales personnel can obtain the requirements from the customer representatives and form a requirement report; the Business Process Analyst obtains the requirement report from the salesman and analyzes and generates the project model report. After obtaining the project model, the interface engineer designs and creates the corresponding template and user interface prototype, which is finally confirmed by the customer representative. Requirements Analysis documents meet the following requirements.

1) Correctness: each function must clearly describe the delivery function.

2) Feasibility: ensure that each requirement can be met in the current development capability and system environment.

3) necessity: whether the function must be delivered, whether it can be postponed, and whether it can be "cut" when the expenditure reduction happens.

4) Concise: Do not use professional network terms.

5) detection: If the development is complete, the customer can detect the problem as needed.

3. General analysis of website project requirements

Based on past engineering experience, the requirement analysis work method should be positioned in "three stages" (also known as "three-step method ").

Stage 1: "interview style ". This stage is an interview with the leadership and business personnel of a specific user. The main purpose is to grasp the specific demand direction and trend of the user from a macro perspective, understand the current organizational structure, business processes, hardware environment, software environment, existing operating systems, and other details and objective information, and establish good communication channels and methods. It is best to specify the contact person for this project for specific functional departments and committees.

Implementation Means: Interview and survey forms.

Output results: Investigation Report and Business Process report.

Stage 2: "inductive ". This phase is based on the actual and objective information that the publisher has learned about the organizational structure, business processes, hardware environment, software environment, and existing operating systems of specific users, make a simple user process page based on existing hardware and software implementation solutions, and use inductive and heuristic survey methods and methods based on previous project experience, discuss with users the rationality and accuracy of business process design, and the ease and habit of the interface. You can use a simple demo to check the rationality and accuracy of the entire business process, and provide suggestions and methods for improvement in a timely manner.

Implementation Methods: Visiting (induction) and prototype demonstration.

Output results: survey and analysis report, prototype feedback report, and Business Process report.

Stage 3: "validation ". This stage is based on the results of the above two stages, and carries out specific process refinement and data item validation stages. At this stage, the producer must provide the prototype system and clear business process reports and data item tables, it can clearly describe the business flow design objectives of the system to users. Users can provide feedback through review reports and sign and confirm accepted reports and documents.

Implementation Methods: visit (review and confirmation), submit business process reports, data item tables, and prototype demonstration system.

Output results: requirement analysis report, data items, business process report, and prototype system feedback (the latter three can be included in the requirement analysis report and submitted to the user and the supervisor for confirmation and archiving ).

In general, the three stages of demand analysis are an important part of demand research. The implementation and adoption of the three stages or three-step method are as follows, both the user and the publisher are guaranteed to succeed in the project.

4. Precautions and skills for website project Requirement Analysis

The overall risk of a project is often manifested in the unclear demand analysis and unreasonable business processes. As a result, users are unaccustomed to or unwilling to use the software of the publisher. Both the contractor and the customer must pay attention to the importance of demand analysis. In order to better grasp the needs and directions of users, necessary measures and methods should be used for demand research.

4.1 mining user requirements

Users are encouraged to clarify all ideas as much as possible and list all requirements. At this time, you do not have to worry about potential requirements of customers and increase the workload of design and development. You should directly clearly list problems and requirements with customers, put the organization, induction, and analysis aside, and accurately record the most primitive and complete requirements of users.

In many cases, customers are not professionals, and it is difficult to highlight the key points and technical difficulties in their descriptions. This requires us to analyze, summarize, and organize the customers, in particular, there are not many customers talking about, but they are technically difficult to achieve and the intensity is very high. Customers often have vague requirements. Most of the time, the requirements are general and difficult to control the scale. This requires the business staff to listen to the customer's detailed description, help the customer to organize and analyze and predict the potential needs of the customer to make changes during the development process and to make changes and upgrades in future applications.

For example, when designing an Office Automation System for the customer, it is necessary to reserve a channel for the customer to interact with their business units in the future; when designing the email system, you may need to consider the need for advertising management servers; when designing online electronic stores, you need to consider increasing inventory product inventory statistics and analysis in the future; limited by time and financial resources, the customer is generally able to accept the development process implemented in stages. In the demand analysis, the customer is expected to change the requirements in the future in advance, in addition to making the project development more smooth, it also laid a better foundation for further business development in the future.

4.2 Use natural languages and charts to describe the project model

The requirement analysis written when the salesman communicates with the customer and investigates the customer. It can be described in natural or formal languages as much as possible. You can also add graphical expressions and model characterization methods. Although the customer's level and qualifications are different, the most natural description allows all members of the project development to clearly understand the meaning of the requirement, so as not to produce deviations in understanding. For customers, such a model description is the most realistic, easy to participate in the revision, and can be used as a basis for testing and acceptance. There are many production methods. The key is to reflect the customer's needs and the system to be designed. Before System Analysis and program development, both parties can have an intuitive understanding of the products to be completed in the future. In other words, when the product has not actually entered the development stage, both parties reach a unified opinion on the results of the work, which will greatly reduce the troubles caused by demand changes, and the customer is more likely to participate in the project development process.

4.3 demand analysis should participate in each assignment

Project managers, system analysts, development managers, Interaction designers, testers, document personnel, and customer representatives should all view the requirement analysis and discuss with each other to reach an agreement. All personnel involved in project development should have a clear and unified understanding of this requirement, and provide comments on the demand according to their own work, and revise it through communication with the customer, finally, determine the project implementation objectives. This avoids unnecessary disputes between business personnel and developers, contractors, and clients.

For example, a project manager can establish a required team through requirement analysis, including configuring the work environment and developing a development cycle; the development cycle restrictions and functional requirements may affect the programming languages and tools used by programmers. the skill level of operating users will affect the accuracy of Interaction designers in front-end design; the interface designer determines the performance mode based on the nature and positioning of the project. The tester can track and test the project quality only after understanding the test environment and conditions.

4.4 put demand changes under control

Demand changes are almost inevitable. They may be due to customer omissions or are triggered during the development process. It is of great significance to manage changes to website project requirements in a controllable manner. If you perform user research and analysis in a hurry, it usually means unstable requirements. Therefore, demand management should ensure that all requirements analysis activities are fully executed.

In order to timely report changes to all roles of the project, it is very important to make a good requirement change log. The change log is attached to the demand analysis, and the modified demand analysis is made into a new version. The updated version is retained instead of overwritten, in this way, it is easier to track the work adjustments brought about by the demand change process. In the demand analysis of the new version, the change part is represented in a special way, and the change details are recorded in the log.

4.5 review requirement documents

After the requirement documents are completed, they need to be formally reviewed to serve as the basis for the next phase of work. The general review is divided into user review and peer review. The user and the developer's description of the software project is based on the requirement specification. The user acceptance standard is formulated based on the content in the requirement specification, therefore, when reviewing the requirement document, users' opinions are the first. The purpose of peer review is to discover potential defects or errors in the early stage of the software project, so as to avoid these errors and defects missing into the subsequent stage of the project.

5. Summary

With the rapid development of the Internet, the Web technology is increasingly widely used, and the scale and complexity of websites are constantly increasing. The design and development of website projects have entered an era where the process and division of labor need to be emphasized, software engineering methods are increasingly involved in the design and development of website projects. Establish a standardized, effective, and robust development mechanism, especially lay a solid foundation for website project management. Strengthening project demand analysis will help you complete development tasks efficiently, quickly, and with high quality.