More and more fancy personal websites are easy to make a website that is easier to do. After reading this article, you will know the hardships of building a business website. Personal sites like children's drawing boards, business sites are a software. Personal websites are easily colorful, because it doesn't have to consider purposes, integrity, scalability, and load, it is more just a time; business website is platform, it is related to future work, continuity, safety, It is not to fail. If you are a SME, you just have to build a job-based website. If you really want to put the workshelf on the Internet, not a new odd, then you read this article, you can eliminate a lot of mistakes. After reading this article, if you feel that it is too much a business website, you don't do it, it is also a harvest. Now, many "commercial" website shapes are also done, the most important reason, the establishment of the builders, did not work as a commercial website at all.
In 1998, the Internet fired, the freshly released nematon sent an email online, on the BBS, immediately became a new wave; in 1999, the personal homepage fire, a few lines of HTML, gather, and take the personal site " Prawn ", 2000, Dotcom fire, portal, chat, game, community flower pattern, mixed bamboo network management Dangdang, sudden scenery; 2001, network application fire, buy and sell things, pull customers, management management , A little technology guy starts the bull; in 2002, the company applied solutions, .NET platform looks also ... now what to do? ? ?
A lens: You are arranged by the boss to be responsible for information construction, is it like a tiger to bite the hedgehog? B lens: You want others to design a website, are they perfunctory, Mon you? C lens: There is a tempting item to put in front of it, until the end is not a mess, but inverted the old? How can I do? ? ? From now on, let's find our new cheese. The name of this cheese is "Website Project Management".
Website Project: That is, the web server is the main body, the browser is a project for the client as a basic architecture. Such a web server, browser, and network in this architecture project include three key main bodies. Website projects may be a website or may be a variety of web applications, such as online stores, virtual postclaies, network office management systems, customer relationship management systems, and more. Website Project Management: It is organized around the website project to use knowledge, technology, skills, tools and methods. Its common feature is: ● Managers implement, not machines; ● Project has time period, including startup time and end time; ● Project is restricted by resource restrictions, including staff, funds, venues, equipment, etc .; control;
The A lens, B lens and C lens started with the article, can be included in the category of website project management. The following is a few important concepts of website project management: (1) Role: means that the project staff participates in the design of the design in a particular environment during the management process. For example, project managers, database engineers, interface designers, document engineers, etc. For website project management, the most critical role is: project manager, business process analyst, user interface engineer, system analyst, coding personnel (programmer), quality control engineer. According to the scale and development of the project, the project manager is divided by the project manager. If strict segmentation, a large project can reach more than 50 to ensure that each detail has a professional person responsibility and management. It should be noted that the role is not equal. A person may act as a plurality of characters, one role may also be composed of many people. For example, if it is a system analyst, it is also a test engineer, or is both user interface engineers, and a documentation and management. A project management team may only have three or five people, or may be 35 hundred people, the project group can be large, but project groups The management process requires a detailed role division. (2) Process: Work sequences performed during the project. Each role obtains and outputs the corresponding results in the process. For example, in a demand analysis process, there is a need for customer representatives, salesmen, business process analysts, user interface engineers, etc., the salesman gets demand from the customer, and forms a demand report; business process analysts have obtained from salesperson Demand report, analysis generation project model report; interface engineers are designing the corresponding template and user interface prototype after the project model, eventually confirmed by the customer representative. (3) Business lead: refers to a variety of different roles that interact with the system. For example, a online store system, the business leads have ordinary visits, order members, manage members, and orders, the website's product information publishers, business management personnel, logistics distribution administrators, etc.
Regardless of how complex website projects, when we start picking up, you can expand in accordance with certain specifications and processes. There are many fields involved in the website project, including web-production, artistic design, program code, system and network management, and network management, including more fields such as enterprise management, marketing, psychology, and advertising. Knowledge, in the process of project development involving project management tools, documentation and design development management specifications, development and testing environment deployment, etc., which is a serious test for a project manager and group. Website design has experienced static websites, interactive websites, commercial applications, special applications. With companies' understanding and understanding of network applications, the functional requirements for websites are more complicated, and now the design of the website project is no longer only again. Simply use the static HTML file to achieve, compared to the website design of the previous year, the design and development of the website project is more and more complicated, more and more complex, website items Designing and development 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 users, "Website software!", Learn from software engineering, and can find out The law and method of website project management. Website project management is divided into the following six stages: 1) Demand Analysis and Change Management; II) Project Model and Business Process Analysis; III) System Analysis and Software Modeling; Trim Edge Design, Interaction Design and Program Development; V. Test, deployment, and documentation; 6) Customer training, technical support and after-sales service. At each stage, "milestones" must be established, representing the phased outcome of the current work, and with this as the standard to enter the next stage, the control and management of the project quality is implemented.
The first stage: demand analysis and change management, if the patient is going to the hospital, the doctor needs "hope, smell, ask, cut". After the patient is carefully understood, they will dare to kill the prescription after the cause. And when we take over a website project, do you really figure out the "cause" of the customer? How many times, when I wait until half of the project, I found that the customer's demand is not like this. ! The project was originally conducted to meet the customer's demand goal, but the result is often not the case, because: "Customers don't know what their needs!" In all unsuccessful cases, this sentence may be our most. . This is true, this is very frustrating. Fortunately, the biggest difference between website projects and construction projects is that when the building is built, it is impossible to re-cast the foundation, but the website project is often produced, and the core design has been completed. Core can also change the core. Even restructuring. Do a good job in demand analysis and establish a change management mechanism is the original foundation that guarantees the successful completion of the project. ● Important role: project manager, salesman, customer representative. ● Get document: obtain demand by various channels such as the customer's discussion. ● Milestone: "Demand Analysis Report" ● Note: ☆ Technology is to serve customers, using the most effective and economical design methods for users, rather than adopting the best technology and configuration The best solution. The so-called subsimette of the best technology is often a high cost, long development cycle and potential instability, can't treat customers as a technical test field. ☆ Remember "The demand will change", do not fear customers in demand. If you only touch the legs of the elephant because you are afraid to see the elephants, it is impossible to design the system you need. ☆ Lock demand, learn to give up. The demand for exceeding the plan and goals can be transferred from the current project by developing an upgrade plan or secondary project, otherwise the system may always be modified and increased in design and development, but no version can be released. ☆ "Demand Analysis Report" should be jointly recognized by customers and all project teams, do not know the public's reason, and the mother said that only all members have clear and consistent cognitions for their goals, they can maximize work efficiency. . ● Skills and methods: ☆ Listen carefully, all the requirements of the Russen customers; ☆ Analyze the needs to analyze the needs, confirm the operational system model; ☆ Describe the system with the most natural language, so that each developer does not generate ambiguity; ☆ Quickly determine the business leadship of the system; ☆ Analyze the permissions of each role and operable function; ☆ Production flowchart and schematic will show demand; ☆ Let customers participate in the design of the diagram, and correct demand changes in time; ☆ Produce the demand change log, retain the upgrade version, to perform demand management through version control; ☆ Through the "Demand Analysis Report", each participant will see a common effort. At this stage, we have a preliminary understanding of the project through demand analysis, and by writing a "Demand Analysis Report" to get an objective reference important document, this is a good starting point. Customers' needs are basically clear, but customers don't teach us what to do. When the customer throws the ball to the project team, see how you pick the ball. Ok, let us continue ...
The second stage: Project model and business process analysis We need business process analysts to decompose customer demand and optimization. The electronic process works generated by the application of network technology can neither change the traditional workflow, nor for the traditional workflow. Simple replication, but requires reasonable optimization, improvement, and recombination of traditional workflows. The demand proposed by the user is usually messy, incomplete, or even incorrect, and more accurate and finer demand often has been excavated in project development. 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 needs and models with customers. During the development process, they want to do a lot of false ideas for customers. It can only be fees. After the hard work of Nine Bull, I don't want to eat. Business process analysts need to assist customers in summarizing the needs, find all the business leads, determine the business leads, clearly formulate the relevant activities and processes of each protagonist, and finally designed business logic. In order to make the user better understand the system design, it is a very effective way to make user interface prototypes for the system in the case of time conditions permit. Before the development has not been developed, the customer can visually see the effect on the system to be completed, and can be adjusted as needed, which will greatly improve the probability of success, while minus workload in the design process. ● Important role: Business process analyst, user interface engineer, system analyst. ● Get a document: "Demand Analysis Report". ● Route monument: "Project Model Report", "User Interface Original", Design Development Plan. ● Precautions: ☆ Business process should comply with customer preferences and habits, with customer environment and skill level design system, avoid free design of the project team; ☆ Please contact customer and user simulation, find blind spots and divergence points, the problem It has already found that the easier it is, the smaller the loss; ☆ Develop performance and functional indicators, as the work basis for the next stage of test engineers. Customers are relatively sensitive to functional demand, but it is difficult to make specific requirements for performance requirements, which requires system analysts to clearly make one of the basis for system design. ● Tips: ☆ Really use the user-centered design to observe and record in the actual working environment of the customer; ☆ Carefully find various business leads, and describe the various operational processes and steps of different protagonists; ☆ Simplify demand Demand summarizes the core problem; ☆ Refine demand, focus on core issues, simulate user roles, further confirm process and standardization; ☆ Seriously formulate design plan, lay the foundation for the next stage; at this stage, we Conversion of customer needs into a practical design and re-operate business optimization and combination, and set project objectives. Now we finally found the direction, and the rest is to start attacking. Down to the next stage ...
The third phase: system analysis and software modeling If the two stages of the front is the design building blueprint, then we have to start playing the foundation. Systematic analysis and modeling is the core work of project development. For an experienced developer, customers have many ways to achieve, but different architectures have the future maintenance, upgrade and expansion of the system. Impact, a unreasonable structure has been used for a long time to completely abandon, revisit. If the vision is only placed in the needs of customers, when the problem occurs, it is constantly repairing, headache medicine, foot pain, or even system architecture needs to constantly adjust or redesign, then, will soon fall into code quagmire or fall into The spare abyss developed by the system, the sense of accomplishment when the project is completed will be replaced by endless depression. Systematic analysis determines the success or failure of system development, software modeling makes system development to mature. The customer's demand will change, the server and client environment are constantly changing, considering different operating platforms, different application servers, different databases, different programming languages, different transmission media, etc., System analysts face difficult choices, anyone is impossible to master and even say that all technologies are proficient, and what is good? We seem to have walked to the center of the maze, all are the channel, but not know where is the fastest export. "Adopt object-oriented development mode and use UML (unified modeling language) to system modeling!", Website, software, software development method also applies to website project development, which points to system analysts. Modeling is not equivalent to program coding, using the same UML model to generate different language frame code, and can be generated in reverse generation, updating the UML model in time during the writing code, which is for system analysts and project management people. It's dreaming. As long as you can carefully grasp the customer's needs, constantly improve the software model, then what kind of language development has become secondary, a large number of demand accumulation and analysis work can be highly reused when customer demand changes, even if the system adopts new The language is re-developed, and it is only the work of the encoding part. ● Important role: System analyst, architect designer, database engineer, business process analyst. ● Acquire document: "Demand Analysis Report", "Project Model Report", "User Interface Original", Design Development Plan. ● 里 程: "System Analysis Report", "Design and Code Specification", "System Model Workpiece". ● Note: ☆ Customer is more concerned about functional implementation, but does not mean that customers don't care about the performance of the system, the successful project development will not only neglect the defects and flaws of the system on the surface, and the website project also needs. "Boutique" consciousness, establish a brand that will win more opportunities and more rumors for themselves. ☆ The initial demand of customers is very simple, but developers cannot make a solid foundation for the potential huge demand for customers. ☆ Maybe because the project cycle is too short, the developer's skill is not reached, and it is difficult to adopt system analysis design and modeling in small project development. At this time, modular design should be used as much as possible to maximize code. Reuse. ● Skills: ☆ Supplement to improve the system performance requirements that may be lacking in the previous stage; ☆ System analyst needs to stand in the overall start, design reasonably and feasible system solutions; ☆ Design a variety of solutions in the case of unknown demand for customers to choose ☆ Use the UML modeling mode to map the needs of customers to the model, greatly improve the system's scalability and development efficiency. Going to this step, the hardest bones were smashed. When a reasonable and reliable system core was designed, the customer would ask him why he couldn't see a line of code, but the mature system analyst has become a bamboo.
Let us take a look at how the entire system is built ... Fourth stage: interface design, interaction design and program development during website project development process, this stage is also called building stage, the biggest workload, the most hard, most It is difficult to control the stage. Regardless of a building blueprint design, if there is no pipeard, mud horses, water and electric artifroes, all kinds of craftsmen, one tile, and close collaboration, this building is always the air building, the sea.
If the customer visits the project team at this time, he can see: ● Artist designer is designed according to the user interface prototype, accurately position the image image; ● Interactive designer puts the artist's work on the business process Edit, designed an interactive program for the user; ● According to the module allocated by the system analyst, the line code puts the system, and one module begins to live; ● The test engineer continues to test everyone. Work, unit test, integrated test, load testing; ● Document engineers began collecting, managing various development documents, checking update records every day, keeping important documents in the latest version; ● System administrators deploy development environment for each developer, and Guaranteed the best working status; the project team is in order to start under the leadership of the project manager. The system construction phase, control development quality, guarantee progress is the focus of the project manager, and the effective communication between group members can effectively improve the development quality and progress by reasonably allocate resources and tasks. ● Important role: American analyst, interactive designer, programmer, test engineer, document engineer. ● Get document: "Demand Analysis Report", "Project Model Report", "User Interface Original", "Design Development Plan", "System Analysis Report", "Design and Code Specification", "System Model Workpiece". ● 里 程: "Program Module", "Development Document", "Systems Developed by Customer Demand". ● Note: ☆ People are not machines. When people become a chain in the project development process, no one must work as accurately and not tired as the machine, so project management personnel must ensure effective communication and collaboration between group members. In the rowboat competition, the more people will play, the faster, when someone shouts the number, everyone will work together to coordinate action, this kayak can quickly retrop the target. ☆ Test is to ensure the most direct and effective way of quality, only constantly testing, testing, and then tested, in order to achieve satisfactory quality. Putting bugs in a germination state is ideal, unfortunately, the tiger also has a snoring, let alone people still lazy? When the system builds the fastest progress is usually the most bug generated, only the testing of repeated cross-crossed can ensure quality. ☆ Interaction designers are bridges between systems and users, truly from the user's convenience and habit, whether it is a pop-up window or the navigation design of the site, even unexpectedly missed tips, etc., you need to carefully design, repeat. Interaction Design If the new user can have the fear of the system, it will win unexpected effect. ☆ Programmer needs to maintain close collaboration and communication during the encoding process, and in the standard system development process, casual personalization is extremely harmful, and any custom functions or fields may cause the system to crash. Build a system better than the 1000 pieces of bricks into a stack. When the programmer adds a module to the module, we have to think about it. Otherwise, when the base is less than dozens of pieces, the system collapsed. The system is such a thing, not laugh at all. ● Tips: ☆ Using the project management tool to manage the project, whether it is Project or StarTeam, or other tools; ☆ Establish a document management specification, use the corresponding document management tool to control the version, PVCS or VSS is Choose tools; ☆ Create a team's communication environment and channels, use email or forums, meet or hand in note, everything is conducive to communication, to ensure that the collaborative members will bypass obstacles, go to the target, human resources Manager's advice is that communication is the most effective way to improve team cohesiveness; ☆ Establish a BUG report and processing system.
As long as it is software, there must be bug, although this is a gray joke, but capturing and eliminating bug is a developer's natural obligation, establishing a BUG management system can make the same mistake no longer commit a second time, when the system is getting more and more The long bug destroyed list is like the tired results of engineers. The system of the system is finally revealed, and the customer's heart is finally practical. However, at this time, it is not an end, during the software development process, the remaining 10% workload may delay 90% of the project.
The fifth stage: system testing, deployment, and document preparation accidents are not a new word in website project management, the biggest accident is not unexpected. After the system development is completed, although it has been tested again, there is still an accident at any time during the deployment process. At this time, I often hear a sentence that the developer said is: "Strange?! How to be good here, can't you put it in someone else?" Simulation test environment, fully testing the functionality and performance of the system according to the test indicators, and notify the project member for amendment. ● Deploying engineers will arrange configuration and debugging with the customer representative until it is officially released. ● Document engineers write a variety of documents, including system white paper, user manual, administrator manual, customer training document, user assistance, etc., and summarize design and development documents, and summarize the project. China has an old saying: "Good start." The project team assisted customers to quickly deploy and provide corresponding documentation, not only saving a lot of energy and cost for after-sales service, but also significantly increase customer satisfaction. ● Important role: test engineers, document engineers, deploy engineers, and customer representatives. ● Get document: "Demand Analysis Report", "Project Model Report", "User Interface Original", Design Development Program, "System Analysis Report". ● Route Shendon: "Test Report", "Technical White Paper", "User Handbook", "Customer Training Document", "User Help". ● Note: ☆ Test not only functional tests, especially need to note performance testing and compatibility testing, you should create different simulation environments, achieve intact test data, and improve the system for test results. ☆ The development of the environment and deploying the environment has caused "unexpected" in the implementation process. It is not surprising that only the customer can control the system well. ☆ "Demand Analysis Report" and "Project Model Report" made before the first two phases have been implemented? The horse tiger project team may have been developing for a long time, and the earliest project goal has been forgotten, and the demand plan may have changed a lot of changes in the development process. The truth may be the case, wait until finished, the customer and you have found the truly needed. thing. ● Skill method: ☆ According to the system's characteristics, special test software or writing test tools can help improve the efficiency, accuracy and integrity of the test. ☆ Select typical user simulation operations that are completely unfamiliar with the system, and you can find a large number of system defects. ☆ Whether it is a web template or a program module, develop a good habit of writing a comment in the source code, which is very important to handover, error correction or secondary development in the development process. ☆ The more standardized for the customer, the more standardized, and the later cost is saved. When the system is finally running as scheduled, it will congratulate you, the system has been developed, and the project team is close to the end, but for the customer is a starting point, the project enters the final stage is starting from customer training. Finally let us turn on the key ...
The sixth stage: customer training, technical support and after-sales service development an old customer cost is far below expands a new customer, the website project is especially important for customers' training and technical support, and for customers, Once the technical guarantee is lost, what kind of dilemma will be faced when there is a problem or need to expand and upgrade? ! Therefore, for the establishment of after-sales support, the rapid response system, which may not only win more business, but also eliminate the worries of customers. As for the cost of customer service support, you can always find the conditions for both parties. ● Important role: Training engineer, customer support engineer, salesman. ● Get document: "Demand Analysis Report", "Test Report", "Technology White Paper", "User Manual", "Customer Training Document", "User Help". ● Libeor Monument: Training Manual, "Customer Service Record". ● Note: ☆ Customer training is not only a final point of the current project, but also the best opportunity to open a new project, and do a good job in training documentation, and transfer the relay stick to the past, and will benefit endless. ☆ Technical support and service is a very important part of the website project. It maintains the contacts and business deals between the two parties, and reasonably controls service costs, which can increase customer loyalty. ● Skills: ☆ Phone, email, website is a good means of establishing customer support, which will be more convenient to publish the corresponding document on the website. ☆ The reaction time and method of customer support can be determined according to the urgency of the customer, so that customers support more efficient. ☆ Establish customer service records, track customer health and change records, and establish close contacts for the next cooperation. When I have a hard time to get here, I will celebrate it, and the joy and experience of success are carefully afraid ...
Ideal and reality always have a distance. When we really start implementing website projects, we find: ☆ The cycle of the project is too short, write code is still too late, which has so much time to write a document! ☆ The person is limited, one project is only two or three people, experience is not enough! ☆ Mastering the cost of project management software and corresponding tools is too high, a temporary team has no training time! ☆ The project team is scattered around the ground, cannot be concentrated, and the progress quality can't be controlled! ☆ No one will test the method, no one will model, no one will ... what should I do? ☆ ......
For website projects, there is a variety of problems. This paper discusses the general method, not form, the goal is to organize and manage the website project in phases, score roles, thereby completing the requirements of website projects. . Although there is no matter whether the black cat white cat can catch the mouse's cat is a good cat, but the cat that will be placed in the mouse is more likely to be a most excellent cat.
Finally, let's take a look at the typical characteristics of the website management success and failure: failure website project has the same reason: ● Always unclear the needs of customers, lose three-scale four, especially for changes; ● Total expectations In the event of a hero to complete the impossible task; ● No one can do it clearly, which day can do the project; ● There is no test report and performance analysis; ● Programmer has become the project dominated, in case the programmer The project is unable to go; ● The customer is the result, the development document is written; ● The same mistake is made, and each battle; ● ......
Successful website project management has a common feature: ● Clear division of labor and phase control, every stage is seriously completed "milestones"; ● True design by users, careful and meticulous demand analysis and business process analysis; ● Complete The standard document management, the document has become an important part of the development of system development; ● Valid team communication and collaboration, not seriously affecting system quality and progress due to personal factors; ● Establish quality control security system, standard rigorous test methods and report ; ● There is a fast response capability and solution for unexpected conditions; ● ... The network is like a huge maze, some people look at the trap, some people can find fresh cheeses, today, someone lost their own cheese. The new cheese was found in other places tomorrow. Cut your own arms and complete our website project!
Appendix: Related Management Software Description:
1.Microsoft Project 2000 Microsoft Project 2000 is an internationally renowned general project management tool software that is suitable for project management in various industries. The software agglutes many mature project management modern theories and methods, so it is possible to manage various types of large and medium-sized projects in high quality. Microsoft Project 2000 provides a number of important features, such as the development of the Gantt chart (activity schedule), planning and actual results, the development of the PERT chart (network chart), the definition of tasks, the definition of the relevant task, the task Resource allocation and resource balance. Comparative highlighted management techniques such as: ● Time management: cross track, milestones, critical path law (CPM), plan review technology (PERT). ● Cost management: Self-point estimation technology, cost accumulated curve (S curve), net value evaluation technology. ● Human resource management: target management, responsibility matrix, resource demand histogram. ● Risk management: Monto Carlo simulation method, basic statistical technology. ● Communication management: Based on the project coordination technique of email and web.
2. Primavera Project Planner 3.0 Primavera Project Planner (P3) provides a modern project manager with the most valuable thing: progress plan control method. Mainly used for project schedules, dynamic control, resource management, and cost control. It has the following features: ● Simultaneous plan, manage and coordinate multiple projects. ● Multi-program analysis comparisons, follow the target plan tracking management. ● Can share engineering data safely in multi-user environments. ● Optimize resources using advanced resource balance technology. ● Reflect the engineering data over a variety of ways such as network diagrams, cross track, time standard network diagrams, and resource intensity maps. ● Packet, sort, screening, and summarizing data according to Work Decomposition Structure (WBS), Organizational Decomposition Structure (OBS), Classification Code and Fees. ● Data exchange in a variety of ways and other software. ● Remote data transfer via Internet / Intranet.
3. The main functionality of the StarTeam Standard Edition StarTeam is to improve the work efficiency of today's distribution mixed software engineering development team. ● Easy: STARTEAM's operation is the same as Microsoft's Windows Explorer, and its simpleness has awarded many times. ● Visual project structure management: StarTeam uses each part of the project with folder, multi-layer perspective management. The project can be observed from different angles. ● Upgrade development model: By using Views and Views Labels, StarTeam allows users to define upgrades and transplant the entire application structure from a certain phase of the development cycle to another. ● Active change requires management: StarTeam uses a unified architecture for software components and its changes, and changes can be used in multiple ways. ● Collaborative communication: STARTEAM provides communication with a single interface to make all players can participate in the decision-making process. ● Compatible with Microsoft Network Conference System: All players can participate in online discussion, display function, share information through the StarTeam unified interface. The virtual conference feature can be used through the desktop menu. ● Anyone participates in any location: StarTeam real client / server structure and support for TCP / IP protocols make each team member enjoy the same function on the network anywhere. ● Compatible with PVCS, Microsoft Visual SourceSafe: Therefore, users do not have to give up the original standards to use StARTEAM's enhancement. 4. PVCS PVCS can improve multiple versions in the software system during software development; automatically create a complete document, safeguard software maintenance; comprehensive record of system development history, including any changes, what, why Modify; managing and tracking the quality of the software and the defects and changes affecting the development cycle; management requirements analysis. PVCs contain a variety of tools. ● PVCSVersionManager will complete the changes and modifications arising from the development process in detail, and automatically upgrade the revision. ● PVCSTRACKER, PVCS Notify automatically tracks the above changes and modifications. ● PVCSRequisitePro provides a unique MicrosoftWord interface and demand database, which can make the development mechanism real-time, intuitively track and manage project requirements and demand changes from end users, and effectively avoid duplication development, guarantee development projects on time. Deliver users according to the original fund budget.
5. Virsual Source Safe Microsoft Visual Studio Enterprise Edition contains version management tools. This tool includes a server and a client that can connect to a server through a network. VSS provides basic authentication security and version control mechanisms, including Checkin, Checkout, Branch (branch), Label (calibration) and other functions; almost any type of text, binary, graphic image The file is controlled; providing historical version contrast; can be integrated in Visual Studio. The VSS client can be connected to the server, or it is very suitable for version management of personal program development in this unit.
