Website Project Construction Process overview
I. Concept
Site project management is based on specific specifications, within the budget, on time to complete the site development tasks.
Two. Demand analysis
Project Establishment
We received the customer's business consulting, through the continuous contact and understanding, and through the basic feasibility discussion enough, the preliminary production agreement, then the project needs to be set. A good practice is to set up a dedicated project team that includes: project managers, web design, programmers, testers, editors/documents, etc. Project implementation Project manager system.
Customer's requirement specification
The first step is to require the customer to provide a complete description of the requirements. Many customers are not very clear about their own needs, you need to constantly guide and help analysis. Once, I asked the client, "What is the purpose of your website?" "No purpose, just because everyone else has, I don't!" he replied. "。 Such a customer needs to be patient, analyze carefully, and tap into his potential, real needs. With the customer to write a detailed, complete requirements of the description will take a lot of time, but it is worthwhile, and must be satisfied with the customer, signed and approved. This is a good place to put an end to many mistakes and project failures caused by unclear demand or understanding deviations. Poor demand indicates that there is no way to have high quality websites. So what is the standard of demand specification to achieve? Simply put, it contains the following points:
1. Correctness: Each function must clearly describe the function of delivery;
2. Feasibility: To ensure that each requirement can be achieved in the current development capability and system environment;
3. Necessity: Whether the function must be delivered, whether it can be deferred and whether it can be "chopped off" when the cost of the cuts occurs;
4. Simplicity: Do not use professional network terminology;
5. Detection: If the development is complete, the customer can be tested according to the requirements.
Three. System Analysis
--------------------------------------------------------------------------------
Website overall Design
After getting the customer's demand description, not directly started production, but the project needs to be overall design, detailed design, out of a website construction program to customers. The overall design is a very critical step. It mainly determines:
1. What functions are required for the website;
2. What software is used in website development and what kind of hardware environment;
3. How many people are needed and how much time;
4. What are the rules and standards that need to be followed?
A Master planning manual is also required, including:
1. Sections and sections of the website;
2. The function of the website and the corresponding procedure;
3. Link structure of the website;
4. If there is a database, the conceptual design of the database;
5. Interactive and user-friendly design of the website.
Website Construction Plan
After the overall design, the general need to give customers a website construction program. Many web-making companies are asked to provide solutions when they engage with their business. At that time, the programme was generally general, and the submission of the programme in cases where the client's needs were not very clear, tended to differ greatly from the actual results made. Therefore, we should try to obtain the customer's understanding, in the clear requirements and overall design after the submission of the plan, this will be beneficial to both sides. The site construction program includes the following sections:
1. Customer situation analysis;
2. The objectives and objectives to be achieved by the website;
3. Website image description;
4. Section and structure of the website;
5. The arrangement of the contents of the website, the relationship between links;
6. Use of software, hardware and technical analysis instructions;
7. Development time schedule;
8. Promotion programmes;
9. Maintenance programs;
10. Production costs;
11. The Company profile: Successful works, technology, talent description and so on.
When your proposal through the customer's approval, then congratulations! You can start making a website. But not in the real sense of production, you need to do detailed design:
Detailed website design
The overall design phase presents a solution to the problem in a more abstract and generalized manner. The task of the detailed design phase is to materialize the solution. Detailed design is mainly for the program Development Section. But this stage is not the actual programming, but the design of a detailed specification of the program. The role of this specification is similar to the engineering blueprints often used by engineers in other engineering fields, and they should contain the necessary details such as: Program interface, forms, required data, etc. Programmers can write the actual program code based on them.
Four. Project implementation
--------------------------------------------------------------------------------
Overall image Design
At the same time as the programmer detailed design, the Web designer began to design the overall image of the site and home page.
The overall image design includes standard words, logos, standard colors, advertising language and so on. Homepage design includes layout, color, image, dynamic effect, icon and other style design, also include banner, menu, title, copyright module design. Home General design 1-3 different styles, after completion, for customers to choose.
Remember: After the customer determines the home style, please sign your approval. No further changes in the style of the layout, or as a second design.
Development and production
Here, programmers and web designers at the same time into the full development phase, it should be reminded that testers need to test the Web page and program at any time, found that the bug immediately recorded and feedback changes. Do not wait until the complete production test, this will waste a lot of time and energy. Project managers need to keep abreast of project progress, coordinate and communicate the work of programmers and web designers.
Perfect Commissioning
After the initial completion of the site, upload to the server, the site for a full range of testing. including speed, compatibility, interactivity, link correctness, program robustness, hyper-flow testing, and so on, to find the problem in a timely manner and recorded.
Why do you want to record a document? In fact, the software project itself is a document, is a continuous enrichment and improve the standard. By constantly discovering problems, solving problems, modifying and supplementing documents, this standard becomes more and more standardized and more and more industrialized. Then make the website development trend norm, tend to be reasonable.
Publicity and promotion
The basic methods of publicity and promotion are:
1. Set the appropriate META tag in the Web page;
2. Each search engine login;
3. Prepare the press release on the news bulletin board;
4. Proper use of email mailing lists;
5. Exchange of advertising strips;
6. Paid advertising.
At this point, the site project construction completed, the relevant web site, the use of operating instructions to submit documents such as customer acceptance. If maintenance is required, the maintenance project will be signed separately.
Maintenance
After the successful launch of the site, long-term maintenance work has just begun, we need to do is
1. Timely response to customer feedback, for example, you can take the email auto-reply function, and then solve the problem in 1-3 business days, reply again;
2. Website traffic statistic analysis and corresponding countermeasure;
3. Maximize the promotion and use of your website;
4. Timely updating and maintenance of website content.
Five. Specifications to be followed
1. Website Construction Catalogue Specification
2. website file naming specification
3. Website Construction Size Specification
4. Website Home Head Area code specification
5. Website Connection Structure Specification
With the continuous development of technology and user demand for the functionality of the site continues to improve, now the design of the website project can no longer simply use static HTML files to achieve, and the previous few years web design by one or two web designers free creation compared to the Web site project design and development more and more like a software engineering, is also more and more complex, the design and development of Web site projects into the need to emphasize the process and division of labor in the era, the establishment of a normative, effective and robust development mechanism in order to adapt to the changing needs of users, to achieve the desired planning goals.
The meaning of Web site project Management (WPM) is web-based project Management, which is the design and management of projects based on the architecture of the Web application as the primary manifestation, which includes key subjects such as browsers, networks and Web servers, mainly in web design , Web application development with browser-based clients (such as information-type websites, online stores, virtual post offices, and customer relationship management). ) and other project management.
In this paper, the author of the website Project Management (WPM) and software engineering Unified Process Management (RUP) comparison, and practical work experience, and strive to Web site Engineering Management (WPM) role, Division of labor, the process of a complete exposition, so that the site project management gradually towards the standardization.
According to the author's experience, the website project management can be divided into the following six stages to control:
1. Demand analysis and change management
2. Project model and business process analysis
3. System Analysis and software modeling
4. Interface design, interactive design and program development
5. System testing and document writing
6. Customer training, technical support and after-sales service
It is important to note that although these phases have some continuity, they are not completely cut off, such as requirements change management and testing, documentation is throughout the entire project process, and many of the work is done in a cross-cutting or simultaneous way.
(ii) Project model and business process analysis
The application of network technology can not only change the traditional workflow, but also not the traditional workflow, but the traditional work process should be optimized, improved and reorganized in a reasonable way.
This chapter includes the following content:
I. Writing the project model documentation to make everyone at a glance
Two. Business process analyst for process design
Three. Interface engineer to design user interface prototype
Four. User-centric design considerations
Five. Making design proposal
Six. Summary
I. Writing the project model documentation to make everyone at a glance
Why should I create a project model document?
Often the requirements of users are messy, incomplete, or even incorrect, and more detailed requirements are often found in the development of the project, which is a very disturbing problem for developers. Then, after conducting the requirement analysis, the project model document can be developed, the two sides will have a common understanding of the outcome of the project to be completed, and early exposure to the possible changes in demand, then the efficiency and quality of the development is greatly improved.
Inexperienced project personnel often wait for the task after the system analysis and development, rather than a little more time in and customers repeated deliberation project needs and models, the development process taken for granted to customers a lot of assumptions, fees Dickens but thankless, imagine, Where do you go in a marathon where you don't know where the end is?
Therefore, after confirming the customer's initial requirement, the business person should carry on the design description of the project model.
First of all, we need to define a glossary, not every customer or project team member can understand the "user", "role", "use case" between the difference, not all can well understand the "channel", "foreground", "backstage" exactly what meaning, in order to let the project model document to make each browser correctly understand, Defining a glossary is very much needed, especially in the face of the traditional industry for the first time information design users.
The model description is described in the most natural language, and this document is a further description of the requirements Analysis report. The client representatives, project managers, developers to the upcoming projects through the project model of the description of the most intuitive impression, and the key issues to discuss and achieve a unified understanding, such as functional requirements, performance indicators, operating environment, investment scale and so on.
Two. Business process analyst for process design
The personnel of the business process analyst should be good at simplifying the work, the person who holds this role must have the extensive specialized domain knowledge, and has the good communication skill.
Business analysts focus on the need to assist customers to summarize the needs of the analysis, to find out all the business lead, after the identification of the business lead, the relevant activities and processes of each protagonist should be clearly developed, the final design of a logical view, user interface. For example, an electronic store system, in addition to the system administrator, Business Manager, salesman, logistics distribution, customer service personnel and other roles, there may be external collaboration units of different roles, such as suppliers, distributors, advertisers, as well as the purchase of users, and even subdivided into ordinary consumer users, VIP consumer users, Group consumer users and so on, each type of role participates in the system activities of the entrance and process are different, through the logical diagram and, the business process analyst will briefly describe the system's organization.
In the design of business processes, the following considerations need to be noted:
* Investigate the user network environment and configuration, so that the architect can develop a reasonable and feasible system architecture;
* Survey user preferences and skill levels, which will directly affect the depth of project development and user interface design;
"While it's easy for developers and managers to think they know what users want, it's often not the case. People tend to focus on how users should perform tasks rather than how user preferences are performed. In most cases, preference issues are not simply thought to have mastered the user's needs, although this is worth studying. Preferences are also determined by experience, ability, and use of the environment. "
* Predict and develop system performance indicators to provide a basis for testers to write test plans.
Many project designs pay more attention to the realization of the function, the testing stage seems to meet the needs of customers, but once put into use, you will find that performance is facing a bottleneck. Due to their limited knowledge of the expertise, the customer often ignores this requirement, so it is important to anticipate and develop performance indicators in advance to avoid future disputes.
Three. Interface engineer to create user interface prototype
In order to create the user interface model before the actual system development input, it is very important that the cost of developing the prototype is much lower than the actual development cost, in the early stages of the project, creating a complete user interface to reveal and test all the functions and usability of the system, and enable the customer representatives to participate in discussion and modification, can greatly improve the project's success
After creating the correct and feasible prototype, the system analysis, design and code must be written in accordance with the prototype, to ensure that the system is built correctly, testers and customers can participate in real-time inspection during the development process, effectively guarantee the quality of the project.
Based on the process Analysis logic diagram provided by the business process analyst and the interface design Engineer began to design the user interface prototype, at this stage, for the interface designer has not yet entered the stage of fine design, so the most important thing is to fully express the business process, and customers on the design style, Design specifications are confirmed and defined.
The interface engineer uses a reasonable layout to design the user interface after fully understanding the customer's needs and all the business processes. For example, the homepage of the site style, home page needs to display the various elements, navigation classification and performance methods, various types of business role of the entrance and so on.
It is important to note that the user interface is not only the interface visited by the site visitors, but also the user interface of special users, administrators, business partners, and even the prompt interface, warning interface, error interface, etc., the design of a complete user interface prototype will not only make it easier for customers and testers to clarify the requirements, It also plays an important role in the quality of the project.
Four. User-centric design considerations
No matter how sharp the level of the project design developers, after all, not the end-user of the system, to maximize the needs of customers is the key, system designers are often verbally hung with a user-centric slogan, and actually work in a large number of hypothetical, or out of laziness or conditional restrictions, It can create unexpected hurdles for different users of the system in the future.
To truly be user-centric, we must first give up the experience and imagination that settles in the mind, go to the place where the customer works, observe how the customer works, and then talk to the customer about their work.
There is a course called "the Phalanx of the blind" in the team outreach exercise, and imagine a group of people who can't see how to pull a long rope into a square picture? Can a defiant person listen and obey? We can not assume that the user is a sound person or blind, and can not imagine how the user should do what should not be done, only to carefully observe and communicate, in order to develop a truly meet the needs of the user plan.
Experts suggest that developers should determine the composition of users and allow users to get involved as early as possible, and present several ways to familiarize themselves with users, their tasks, and needs:
* Chat with users
* Visit the user at the office location
* Observe user work
* Record the user's work
* Understanding Work organization
* Self-attempt
* Make the user want to say while working
* Let the user participate in the design
* Include expert users in the design team
* Perform Mission Analysis
* Use surveys and questionnaires
* To develop testable targets
In the possible circumstances, in the requirements and process design efforts to achieve accurate, objective and meticulous, not only to ensure the quality and maturity of the system development, but also will enable you to get high customer satisfaction and trust, for more business cooperation in the future open the door.
Five. Making design proposal
At this stage, it can be said that the needs of the customer and the implementation of the plan to develop a clear understanding of the system and the customer reached a consensus, then in the next stage of work, the production of design proposals is very necessary.
Design proposal is a comprehensive description of the entire system, as a system analysis, the basis for testing personnel work, but also the customer acceptance criteria, as one of the contents of the business contract, therefore, should carefully write the design proposal.
Depending on the project, the content of the design proposal may be different, the following author provides a sample for your reference, the sample basically covers the need to confirm and describe in the proposal of the core elements.
--------------------------------------------- --------------------------
< project name >
Project proposal
Version <x.x>
History revision Record
---------------------------------------------------
Date | Version | Description | Author |
---------------------------------------------------
y/m/d| <x.x> | Revisions | < name > |
---------------------------------------------------
| | | |
---------------------------------------------------
| | | |
---------------------------------------------------
| | | |
---------------------------------------------------
Directory
1. Project Overview
1. 1 Customer Information
1. 2 Project Background
1. 3 Project Prospects
2. Demand analysis
2. 1 User Foot Color
2. 2 Key Technologies
2. 3 site Structure
2. 4 Image positioning
3. Overall scenario
3. 1 System Framework
3. 2 topological structure
3. 3 Deployment Plan
4 Configuration and quotation
4. 1 network environment
4. 2 hardware configuration
4. 3 Software Configuration
4. 4 other configurations
5. Implementation steps and Cycles
6. The system function is described
7. Technical assurance and support
8. Upgrade Training and Services
9. About our
10. Contact Us
11. List of attachments
11. 1 Project Model Documentation
11. 2 Business Process Analysis documentation
11. 3 User Interface design diagram
12. Copyright notice
--------------------------------------------------------------------
Six. Summary
In this stage of the work process, the core task is through the last stage of the requirements analysis, project model design and business process analysis, and the production of user interface prototype to be confirmed by the user, the final completion of the two approved "design plan", as the next stage of system design and software modeling basis.
How to complete the business process analysis phase in high quality, the author summarizes the experience as follows:
* The real user-centric design, to the customer's actual working environment to observe and record;
* Carefully look for various business protagonists, and express the different actors of the various operational process steps;
* Simplify the requirements, the customer needs to summarize and grasp the core issues;
* Refine requirements, target core issues, simulate user roles, and further confirm processes and specifications;
* Carefully formulate design plans for the next stage of work to lay a good foundation. Category: Project management
Website Project Construction Process overview
