Data storage and data communication technology are the core technologies to realize this function. This system helps users to obtain information efficiently through e-mail, search engine and data publishing technology, which improves the speed of data exchange and the efficiency of information sharing. Information sharing e-commerce system can reduce the loss caused by poor information communication, reduce daily paperwork, improve work efficiency and manage the information use of enterprises more effectively. 2 e-commerce transactions
The key to realize this system is to realize every step in the process of business transaction electronically to adapt to the rapid development of business. E-commerce transaction system is the most challenging field at present, and its technical core is application system development ability and transaction processing technology, including SET and related technologies that support online interface of financial system. At present, both B2C and B2B belong to this kind of system. E-commerce trading system is an important means for modern enterprises to expand new markets in the Internet era. A well-designed trading system can enable enterprises to operate 24 hours a day and provide quality services to customers. If the core business system of an enterprise can be organically integrated with the Internet system, it can greatly expand the business scope of the enterprise and reduce the operating cost and sales cost. 3 Application services on the Internet server
Expanding the service capacity of Internet servers and customizing application services to meet customers' needs may include all the functions of e-commerce systems, and JAVA technology and transaction processing technology are the technical cores of such systems. This kind of system usually refers to enterprise portal or ASP. Because of its extremely high processing load, it also needs to provide additional complex technical support, such as cluster technology and performance management. This kind of system either integrates the original enterprise core business system with the Internet server, or develops a fully functional application service system on the Internet server. Customers accessing such Internet servers can get the latest data automatically updated and get customized self-service. This kind of system has a large number of customer visits, which requires good scalability, and its performance will not be affected by the change of the number of customer connections. It needs to adopt complex technologies such as connection management technology, transaction management and resource coordination. This paper is divided into three parts, which respectively introduce the organization method of system requirements analysis and system design, as well as the process of function check and performance test, focusing on the basic principles and not involving the details of specific related technologies. As for the technologies and methods adopted in the system implementation stage, due to the complexity of e-commerce system and the constant emergence of new technologies, it is really beyond the coverage of an article or even a book or two. System requirements analysis System requirements analysis is for system developers to accurately understand the objectives of business departments and make appropriate implementation plans. We should not only emphasize the importance of system requirements to system implementation, but also avoid several common misunderstandings in the process of system requirements collection: 1 System requirements analysis is not an overnight work, but a process of repeated progress. With the popularization of e-commerce application system, business departments will put forward new requirements or change the original business requirements. This is allowed and normal. The technical department can't refuse the new requirements put forward by the business department, but should actively cooperate and modify the original implementation plan accordingly.
The root of system demand is the demand of business department operation, not the demand put forward by technical department to realize some advanced technology. The system scheme cannot be changed because of the emergence of new technologies. After all, using new technology is only a means, and supporting the business operation of enterprises is the ultimate goal.
System requirements are not limited to business requirements, but also include various restrictions of objective conditions, such as the requirements of project progress, compatibility with existing systems (for example, all core data of the enterprise have been stored in Sybase database, or thousands of terminals left over from the old system of the enterprise must be used) or other policies and regulations (for example, the cryptographic system used by commercial systems must be certified by relevant government departments). These factors should be considered when making the implementation plan of the application system.
The main way to collect system requirements is for system analysts to explore "real" system requirements through talking with end users, gain users' approval, accurately understand the business environment with the help of business departments (which is what most technicians lack most), collect enough complete information, and complete a series of documents as inspection marks to confirm the work at this stage, which will be the basis for the next work.
What are "real" and "accurate system requirements"? When a customer asks a system analyst, "We want to build an online shopping mall so that customers of our company can place orders directly online", this is an absolutely real demand, but it is not necessarily an accurate system demand, or it is not necessarily the most suitable target for the actual needs of enterprises. Because customers generally have some preconceived ideas about e-commerce when making requests, they think that e-commerce is like this, or it can only be like this, or peers and competitors have already done so, so we should do the same. In fact, what they really need may be more than this requirement, less than this requirement, or even another system completely. At this time, the system analyst should patiently explore the actual needs of customers, usually by asking such questions:
Which of the following goals do you hope this e-commerce application can achieve for your enterprise after it is established? What do you want to achieve most? What do you think are the main problems of your enterprise in these aspects at present? To what extent do you want the e-commerce system to solve these problems?
Increase the number of customers, reduce the operating costs of enterprises or increase turnover.
Enhance the overall image of the company
Accelerate the speed of product listing.
Make enterprises more competitive than their peers.
Shorten the development cycle of new products
Improve the efficiency of inventory management and procurement process management.
Improve the cooperative relationship between enterprises and agents
Improve customer satisfaction and customer service quality
Improve the cooperation and communication efficiency of employees in this enterprise.
It's best to talk to system analysts and business leaders of enterprises to help enterprises develop new markets, not to talk to technical leaders of computer departments of enterprises. Only in this way can we find out the real needs of the system. System analysts usually get some information completely unrelated to e-commerce technology from the person in charge of the enterprise, such as "customers complain that our delivery time is not on time" and "our enterprise is too big, and the cooperation and communication between departments are very problematic, and the left hand always doesn't know what the right hand is doing". This kind of dialogue can help system analysts accurately locate e-commerce systems and define their functional boundaries.
The person in charge of an enterprise usually pays more attention to the overall business planning. System analysts and project managers in charge of demand analysis should take this opportunity to explain in detail the functions and applications of several types of e-commerce systems to enterprise managers, inspire them to explore the needs of enterprises more deeply, explain the expected goals of enterprise e-commerce systems to them with practical experience and successful cases, and help them establish correct expectations. Most enterprises are implementing e-commerce system for the first time. Due to the influence of external factors such as media hype, they may have unrealistic expectations for the expected effect of the system. System analysts should accurately grasp and adjust customers' psychological expectations in the demand analysis stage. Customer's expectation is also an important factor of system requirements, which directly affects the implementation effect after the system is completed.
Customer's attitude and technical level are important factors affecting the system designer's scheme, and they are also part of the system requirements. In the stage of system requirements analysis, we should fully communicate and evaluate with customers. Customer attitude refers to the degree to which enterprise decision makers accept new technologies and are willing to take risks. New technologies emerge one after another in the field of e-commerce. The functions of mature technologies are not as good as those of new technologies, but the risks are low. The attitude of enterprise decision makers in this respect affects the technical choice of system designers when designing schemes. If enterprise decision makers choose more advanced new technologies, system analysts have the responsibility to remind them of the risks they may face when adopting new technologies: the possibility of failure is high, and the project schedule and development cost may exceed expectations. Don't vote for the favor of customers, and hide the disadvantages behind new technologies. Enterprise decision makers should also be cautious when choosing system integrators. The technical level of integrators is not determined by the degree of mastering new technology, but by their level of using technology to solve practical problems.
Most large enterprises in China have special computer departments, which will be responsible for the maintenance and management and even the secondary development of e-commerce systems after their completion. When designing the scheme, we should also consider the knowledge base and professional training level of the customer's technical personnel. In the stage of system requirements analysis, it is best to conduct a comprehensive evaluation of the technical personnel of the client to examine their mastery of the relevant technical fields of e-commerce systems. The contents of the evaluation include: Internet server, object technology, JAVA, application development tools, database technology, transaction processing technology, security technology and understanding of industrial standards.
System analysts should summarize these scattered requirements into system objectives, make a preliminary system summary requirement book, accurately and completely describe the overall requirements of the enterprise, re-emphasize the expected objectives of the system, and get the approval of the person in charge of the enterprise, and then carry out the preliminary design of the system on this basis.
The work of system requirements analysis did not end there, but just started. The project manager should make some preparations and hold the first project meeting. Participants in the meeting include the business and technical leaders of customers and the project manager of the project owner. The main purpose of the meeting is to further confirm and refine the requirements listed in the system summary requirements and determine the direction of system construction. In principle, these meetings should achieve the following objectives: 1. Discuss the current environment and system requirements in detail. 2. Review the current application system and clearly list the problems that need to be solved. 3. Exchange their ideas and views on the e-commerce system at an appropriate time, and create a cognitive foundation that is easier to reach * * * *. 4. Determine the main objectives of the system. When the scope of system requirements is wide, system goals can also be divided into short-term goals and long-term goals. 5. List the main problems that need to be solved in order to ensure the smooth operation of the system, extract the most prominent and urgent problems, strive for the cooperation of customers, and solve them before the system starts to be implemented. 6. Explain to customers the core technologies used in the process of system implementation and the general idea of the scheme. 7. Make an action plan for everyone according to the knowledge gained at the meeting. This kind of meeting can not be completed in an hour or two, but may take several days, or even be organized in different forms on different occasions, such as scheme display, seminars, on-site visits, etc. If conditions permit, organizing project meeting members to visit some similar e-commerce systems as background reference materials to guide project meeting members to refer to the implementation experience of successful e-commerce systems is of great help to the success of the meeting. IBM's experience in helping to implement e-commerce system on a global scale shows that this kind of project meeting is of great significance to the success of the project. In the project meeting, technicians and business people communicate face to face, saving a lot of time. Technicians can better understand the needs of business personnel, make feasible scheme design, and business personnel can better understand the limitations of technical means. The communication between the two parties can also promote the improvement of the business process of the enterprise in a more reasonable and suitable direction for computer management.
In practice, the time for managers to attend project meetings is very precious, and there are not many opportunities to gather everyone. The convener of the project meeting can't simply agree to hold the meeting at one time, but should make serious preparations before holding the meeting. The preparatory work mainly includes the following contents: 1. Determine the customer's attendee list, talk to each attendee individually, explain the purpose of the meeting, listen to their opinions and collect more detailed requirements. The number of participants in the client should be four to six. If there are too many, the communication efficiency will be reduced. 2. Determine the list of participants of the developer. The number of developers should be about four, mainly project leaders, system designers, development managers and technical leaders. Determine the topics to be discussed at the meeting, and designate the person in charge of each topic to explain to the customer. The total number of participants of both parties shall not exceed 12. 3. Prepare the requirement analysis document as the basis of discussion. The main contents of these documents are:
Overview of the target system: main function description and operation mode of the target system.
* System structure: the logical and physical structure of the current system, the running software and its configuration diagram.
* Database structure: describe the structure of enterprise core data, determine which data will be open to Internet servers, and the way and scope for Internet users to access data.
* Network environment: the network topology diagram of the current system, the network structure diagram of the target system, and the industrial standards adopted on the network, such as communication protocols and naming rules.
* Security requirements: the security management methods currently used by enterprise systems and what security management improvements should be made to adapt to the operation of e-commerce systems.
* Performance requirements: System performance is affected by many factors. Performance requirement analysis decomposes the transaction process, discusses the performance requirements of each link, fully discusses the unfavorable factors restricting performance and the technical means to ensure performance requirements.
System organization chart: the personnel organization structure and business flow chart of the enterprise, which lists the organizational structure configured to ensure the smooth operation of the e-commerce system and the technical quality requirements of each post. 4. Announce the theme of the meeting and the list of participants before the meeting, and attach background materials such as each person's position and role in the project. In short, a clear theme and adequate pre-meeting preparation (including pre-meeting document preparation and individual communication) are the basis for the success of the meeting. As the convener of the meeting, we should make directional guidance at the meeting according to our own technical foundation and industry knowledge, control the time well, and stop some discussions that cannot reach a conclusion in a short time in time. The focus of the meeting should be on the analysis of the current situation and requirements of the system, so as to avoid introducing specific technical means too early and setting restrictions on the design of the scheme in advance. System status analysis can not only summarize and review the achievements of system requirements made in the first stage, but also make technical analysis of the existing environment.
The technical analysis of the system environment mainly includes the following contents:
* Network environment analysis: analyze the network topology, the network structure of the current system, the server configuration on the network, etc. Network traffic demand analysis, analyze whether the current network bandwidth can meet the requirements of the new system. The security system and security management strategy of the network system, e-commerce system is more open than the traditional enterprise network, and the security requirements are more stringent.
* Analysis of application environment: the software configuration and version of the current system, the running mode of application programs (running platform, whether real-time access and online transaction processing are needed, etc. ). Database structure, the core data mode of the application system. Users' familiar application development methods and skilled development tools may be valuable resources, which can speed up the progress of system development and ensure the effect of system use, because it saves costs and reduces risks, and there is no need for further training; This may also be the main obstacle to the adoption of new technologies. Because of habitual psychology, people resist new development tools and application operation modes. Even if they invest a lot of resources in retraining, they still have to take great risks. System maintenance personnel may make human errors due to inexperience, resulting in operation failure. This situation is particularly common in domestic enterprises, and system designers should be very cautious.
* Analysis of customer operating environment: The customers of e-commerce system are those who use browsers or other devices on the Internet, which is different from the traditional intranet. In the intranet, the operating environment of all customers is predetermined and customized. System requirements list customers' environmental requirements for e-commerce system support, such as browser type, whether JAVA is supported, whether Internet mobile phones are supported, etc.
* Other special requirements, such as the customer's system must adopt Linux platform, or have special multilingual character support problems.
After detailed analysis, the most likely result of the project meeting is to hear a lot of opinions and demands. It is impossible for a project with controllable schedule and budget to meet uncontrollable requirements. Only by prioritizing can we solve the problem simply and directly. The project leader should be recognized by the participants first. There are too many goals to be accomplished in a project. Please first select the goals to be achieved in the current project, and then evaluate the importance of these goals. If opinions cannot be unified, there are still many goals that are listed as very important, and these goals should be re-screened. For the final listed goals, please ask for your opinions again and confirm that these goals have included the basic functions of the target system, and there are no major mistakes or omissions. System designers should pay special attention to the objectives and requirements listed as very important, which are the main factors affecting the system scheme. The result of the first project meeting is a detailed and clear system requirement, and the system designer carries out detailed scheme design according to the system requirement and goal.