Differences between "Large Ticketing System" and "physical e-commerce system" in Access Management

Discussion step: http://blog.csdn.net/hu_zhenghui/article/details/27584047

Related Articles:

Have you bought the ticket today? -- Talk about the "massive transaction fast processing" system of e-commerce sites from the 12306.cn website of the Ministry of Railways

We cannot simply use the "physical e-commerce system" to analyze the needs of the "Large Ticketing System ".

There is a huge difference between the "Large Ticketing System" and "physical e-commerce system" in the impact on consumers when goods (services) cannot be provided.

Differences and relationships between system boundaries of "Large Ticketing System" and "physical e-commerce system"

"Large Ticketing System" and "physical e-commerce system" analyze various business forms based on system boundaries

Payment differences and contacts between "Large Ticketing System" and "physical e-commerce system"

Differences and relationships between "Large Ticketing System" and "physical e-commerce system" in malicious orders

Security issues of username and password in large ticket systems
Security issues introduced by features of large ticketing systems

"Large Ticketing System" and "physical e-commerce system" have huge differences in "inventory" Calculation

Connection and misunderstanding between "Large Ticketing System" and "physical e-commerce system" and other enterprise departments

Impact of dependency between "Large Ticketing System" and "physical e-commerce system" and other enterprise departments on Project Management

Database selection for "Large Ticketing System" and "physical e-commerce system"

How to handle malicious hacker requests in the "Large Ticket System"-Verification Code

Handling of malicious access requests in the "Large Ticket System"-"Access Management" section

From the perspective of application characteristics, large ticketing systems and common static content, CMS (content management system, such as news), and Web 1.0 (Content-based interaction, such as forums and blogs) different from Web 2.0 (based on human interaction, such as SNS and Weibo), a user's workflow is a complicated process in the OA system.

The large ticketing system is different from the traditional OA system from the user's perspective. In the traditional sense, the OA system is mainly intended for internal staff of the Organization, such as self-owned ticket forms, or personnel in multiple organizations with cooperation relationships, such as sales representatives, these two types are collectively referred to as "Controlled users ". A large Ticketing System is an OA system that allows ordinary users to renew their tickets, that is, "uncontrolled users ".

For applications such as static content, CMS, Web 1.0, and Web 2.0, users are allowed to submit questions at will. There is no significant difference between "controlled user" and "uncontrolled user. For oa-type applications, the process has a strict sequence of asking questions. For "Controlled users", the system design can be ensured through prior training and post-event supervision. However, "uncontrolled users" cannot be supervised after the event, and it is difficult to ensure the effect even if advance training is performed. Therefore, you cannot rely on the user to ensure that the use meets the system design.

The "physical e-commerce system" also faces this challenge. The "physical e-commerce system" mainly relies on the following measures:

I. Long term credit management. For non-conforming processes, the user's personal credit is counted after the process times out.

2. Short-term credit management. For an incomplete process in progress, restrict user renewals and other processes. For example, in an auction, limit the number of unpaid auctions for users, so as to prevent malicious users from making no payment after taking a large number of goods.

For a "large Ticketing System", because the "inventory" calculation is much more complicated, non-conforming system design processes will put extra and meaningless pressure on the system. Therefore, it is necessary to strictly limit user operations to conform to the system design. In this case, you need to manage user access.

In fact, before a large number of applications are migrated to the browser, almost all network applications manage user access. It contains many client programs and manages user access. When a user logs on at one time, it forces another user to go offline. Even when a user logs on to the browser, the user is forced to go offline (such as a chat tool) on the client ).

Because applications on browsers are mainly static content, CMS, Web 1.0, and Web 2.0. These applications do not have a strong requirement on user access management. Instead, session timeout for simple failover is required. But in fact, from the perspective of users, the lack of access management has always plagued users. For example, if you have been writing a long article for a long time, the content being written may be lost upon submission. However, the infinite extension of the Session Timeout time puts pressure on the system and brings security risks.

To sum up, the "uncontrolled users" such as the "Large Ticketing System" and the OA system should improve the service quality of the system through access management and ensure the quality of service provided to users.

(Note: the concepts of Web 1.0 and Web 2.0 are case-insensitive. This article is only used to illustrate the issues discussed in this article)

Contact QQ 443089607: huzhenghui
Add the product manager to the QQ Group 189763636 group for axure7pm Interaction