《中国电子商务》期刊介绍.docx

《《中国电子商务》期刊介绍.docx》由会员分享，可在线阅读，更多相关《《中国电子商务》期刊介绍.docx（18页珍藏版）》请在淘文阁 - 分享文档赚钱的网站上搜索。

1、中国电子商务期刊简介一、期刊名称中国电子商务二、刊号国内标准刊号：CN11-4440/F国际标准连续出版物号：ISSN1009-4067三、主管单位国家工业与信息化部四、主办单位中国电子企业协会五、办刊宗旨中国电子商务以传播信息化理念、报道经济前沿、倡导信息创新、促进经济发展为办刊宗旨，大力普及电子商务知识，弘扬科学精神，传播科学思想，倡导科学方法。六、刊登内容中国电子商务是广大经济和信息化领域的管理人员、科教工作者、高校师生、信息化技术人员发布学术文章的重要理论阵地，是获取精神陶冶、知识滋养和科技经济信息的重要渠道。本刊主要刊登我国当前信息化有关的科技、经济、教育、管理等方面具有一定学术和应

2、用价值的学术文献和反映各学科、各领域的新成果、新技术、新工艺、新产品等方面的论述文章。七、主要栏目1. 经济管理研究：国际经贸、物流论坛、商业研究、物流平台、供应链管理、资本运营、区域经济、投资分析、产业经济、网络营销、企业管理、经营管理、营销策略、品牌战略、市场调研、人力资源、企业文化、财务审计、财经论坛、学术研究、管理科学。2. 信息化研究：信息技术与安全、通讯技术、网络技术、自动识别技术与应用、电子商务、支付与结算、供应链管理、数据库与数据库管理、案例分析。3. 科技研究：科技项目、科技政策 、科技成果、科学普及、技术市场、科技新品、实用科技、科学实践等、机电一体化、电气自动化。4. 教

3、育教学研究：教学研究、教育生活、课程与教学、教育信息化、职教时空、教学园地、信息化教学等。5. 工程技术研究：建筑工程、生物工程、医学工程、环境科学、矿业工程、市政建设、水利工程、交通工程等。八、读者对象经济领域和信息化领域的管理人员、科技企业科研开发人员、高等院校师生、信息化技术科研人员，社会各界关注经济发展和信息化发展的各界人士。联系方式 TEL：010-63309185 Email: zgdzshangwu Some of the material presented in this article was excerpted with permission from The Data

4、Model Resource Book: A Library of Logical Data Models and Data Warehouse Designs published by John Wiley and Sons and authored by Len Silverston, W. H. Inmon and Kent Graziano. The Concept The age of the data modeler as artisan is passing. Organizations can no longer afford the labor or time require

5、d for handcrafting data models from scratch. In response to these constraints, the age of the data modeler as engineer is dawning. Engineers build new products using proven components and materials. In data modeling, the analogue to a component is a universal data model. A universal data model is a

6、generic or template data model that can be used as a building block to jump-start development of the corporate data model, logical data model or data warehouse data model. Resistance to the use of universal data models is usually based on the belief that a particular organization has unique needs or

7、 the dreaded not invented here syndrome. This article describes the application of universal data models to several disparate organizations. It demonstrates that the same basic models, with minor customization, can be successfully applied in each example. One Size Fits All? The belief that a particu

8、lar organization is unique because of its missions, goals, policies, values, functions, processes and rules can be very strong. After all, some businesses sell to people and others sell to other organizations. Some deal with products and others deal with services. Each industry has its own set of bu

9、siness issues, and each organization within an industry varies as much as the differences between the personalities of various individuals. People and Organizations A subject data area that is common to most enterprises involves the people and organizations that are part of conducting business. Ther

10、e is an important need to track the names, addresses, contact numbers and various relationships and interactions between the parties conducting business. Enterprises need to track information about customers, distributors, agents and suppliers as well as the internal organizations and people within

11、the enterprise. This type of information is critical throughout all aspects of business including sales, marketing, customer service, purchasing, shipping, invoicing, budgeting, accounting and human resources. Enterprises spend significant effort and time defining the most effective ways to model th

12、is type of information. The data model may lead to sub-optimal solutions if careful analysis is not conducted. For example, many data models depict separate entities for each type of party that exists in an enterprise. There may be entities for CUSTOMER, SUPPLIER, INTERNAL ORGANIZATION, BROKER, EMPL

13、OYEE, INVESTOR and any other role that a person or organization may play in the enterprise. There are problems with modeling the information this way. What if a person or organization plays more than one role in the organization? For instance, what if an organization supplies products and/or service

14、s to our organization and also buys products from us? Does this mean that we maintain their name, addresses, contact numbers and other organizational information in both the CUSTOMER and SUPPLIER entities? Under this scenario, if a name or address changes, the information needs to be changed in two

15、places. Furthermore, does the organization play other roles such as an agent of the company or a distributor of products? Each time an organizations role is modeled as a separate entity, there is a potential for redundant and inconsistent information. The same argument applies to people. Should we h

16、ave a separate EMPLOYEE entity as well as a CONTRACTOR entity? What if a contractor becomes an employee of the enterprise or vice versa? The persons name, demographics and contact information may still be the same. The only thing that has changed is the nature of the relationship between the parties

17、. It only makes sense to refer to pre-defined templates or universal data models when modeling common data structures. Universal data models can point out the most effective means to maintain this information and assure that subtle, yet important, data integrity issues are not overlooked. People and

18、 Organization Information Figures 1, 2, 3 and 4 depict universal data models for the people and organizations involved in conducting business. These data models include information concerning the relationships between each person and organization as well as their associated contact information. Befo

19、re beginning our discussion of these models, lets clarify some data modeling conventions. Entities are represented using rounded-edge rectangular boxes. Sub-types are represented by showing boxes within the larger box. For example, in Figure 1, ORGANIZATION and PERSON are both represented as sub-typ

20、es of PARTY. The lines between entities define relationships. The dashed section of each line represents that a relationship is optional. For example, in Figure 1, a PARTY does not necessarily have an associated PARTY DEFINITION. The part of the line closest to PARTY DEFINITION is solid, and this re

21、presents a mandatory relationship. Therefore, each PARTY DEFINITION must be associated with a related PARTY. The small crossed line across the PARTY DEFINITION to PARTY relationship specifies that the key to PARTY (party_id) is included as part of the key to PARTY DEFINITION. The crows feet (three s

22、mall lines at the end of each relationship line) denote a one-to-many (1:M) relationship. For example, Each PARTY may be defined by one or more PARTY DEFINITIONs. Vice versa, each PARTY DEFINITION must be used to define one and only one PARTY since the line from PARTY DEFINITION to PARTY does not en

23、d with a crows foot. Now lets discuss the data models. Figure 1 identifies a super-type named PARTY, with two sub-types, PERSON and ORGANIZATION. Information about a person or organization is maintained independent of their roles or relationships. This leads to a much more stable and normalized data

24、 structure since information about various people and organizations is only stored once. The same information can then be associated with each of the partys roles. The reason that PERSON and ORGANIZATION are both sub-typed into a PARTY entity is that there is common information related to both peopl

25、e and organizations such as their credit rating, credit limit, address, phone number, fax number or e-mail address. Additionally, organizations and people can serve in similar roles. Both people and organizations may be buyers, sellers, members or parties to a contract. Parties may be classified int

26、o various categories (i.e., industry codes, minority classifications) using the PARTY DEFINITION which stores each category into which parties may belong. Figure 2 depicts that each PARTY may be involved in one or more PARTY RELATIONSHIPs. PARTY RELATIONSHIP is used to define the relationship betwee

27、n two parties. An occurrence of a PARTY RELATIONSHIP may be between two organizations, such as a customer relationship to an internal company. The relationship may be between a person and an organization-for example, an employee of an internal company. Finally, the relationship may be between two pe

28、ople. An example of this is the relationship between a purchasing agent and their preferred supplier representative. The PARTY RELATIONSHIP TYPE defines the possible types of relationships. Possible instances of PARTY RELATIONSHIP TYPE are employer/employee, parent/subsidiary, and customer/customer

29、representative. The PARTY TYPE ROLE defines the two parts of the relationship. For example, one role of the relationship may be employer and the other role for that same relationship may be employee. Finally, the PARTY PRIORITY and PARTY RELATIONSHIP STATUS TYPE entities allow each PARTY RELATIONSHI

30、P to be prioritized (high, medium, low) and defined via a status (active, inactive). By distinguishing whether information should be associated with the PARTY or the PARTY RELATIONSHIP, we can avoid data anomalies. For example, many data models associate a status with a PARTY. This does not account

31、for the fact that three sales representatives may have three distinct relationships with the same party. Each sales representative may want to record a different status for their relationship with the party. If the status were stored with the PARTY, then the sales representatives would have to overr

32、ide each others information. In actuality, there are really three separate relationships, and the status should be associated with the PARTY RELATIONSHIP. Figures 3 represents address or location information about parties. It shows that ADDRESS is its own entity and can be applied to many parties. T

33、he PARTY ADDRESS is a cross-reference or associative entity that allows each party to have many addresses (home address, work address) and each address to have many parties (an office location of many employees). Each PARTY ADDRESS may have many PARTY ADDRESS ROLES and vice versa. These relationship

34、s determine the purpose of the address. Examples of PARTY ADDRESS ROLE include corporate headquarters, sales office and warehouse. Figure 4 is a model to maintain phone numbers, fax numbers, cell numbers, e-mail addresses and all other CONTACT MECHANISMs. Instead of defining these contact mechanisms

35、 as attributes, this model provides flexibility in allowing as many contact mechanisms to be stored for a PARTY or PARTY LOCATION as needed. The CONTACT MECHANISM TYPE entity identifies the type of mechanism such as phone, fax, cellular or pager. The PARTY CONTACT MECHANISM is an associative entity

36、that allows each CONTACT MECHANISM to be related to many PARTY ADDRESSes or PARTYs (a shared telephone number for several consultants). Conversely, each PARTY or PARTY ADDRESS may be contacted via many PARTY CONTACT MECHANISMs (a person or location with numerous contact mechanisms of different types

37、). The line connecting the two relationships under PARTY CONTACT MECHANISM represents an exclusive arc and states that either one of these relationships exists, but not both. A PARTY CONTACT MECHANISM may be either the mechanism to contact a PARTY or a PARTY ADDRESS. Similar to addresses, contact me

38、chanisms may have roles. Examples of PARTY CONTACT MECHANISM ROLE TYPEs include general information number, sales information and customer service number. After extensive analysis and consideration of many alternate data models, I believe that these four universal data models represent a very effect

39、ive way to model people and organizations for most enterprises. Now lets take a look at how these universal data models can be applied to specific enterprises. A Manufacturing Enterprise Lets consider the needs of a particular type of enterprise, specifically a manufacturing firm. Suppose this firm

40、manufactures personal computers. They sell their products to retail chains, distributors and directly to individuals and organizations. It is important to record contact information on each distributor and the people within those organizations. They need to track supplier information to indicate who

41、 provides PC components for their machines. Information on their end-user customers who have bought their equipment is critical. They also maintain employee information as well as information about the many subsidiaries, divisions and departments and their associated locations. The first comments an

42、 enterprise may make about using the previously presented universal data models are Where is the customer entity? Our most important information needs are about our customers. We need to record their credit limit, billing options and their customer status. Similarly, where are the entities for suppl

43、ier, employee, distributor or internal organization? Each of these business entities is characterized by very common information. They all have names, addresses, phone numbers, statuses and other contact information. This leads us to the conclusion that they could be sub-typed together. Should we th

44、en modify the model to add the sub-types CUSTOMER, SUPPLIER, DISTRIBUTOR, INTERNAL ORGANIZATION and EMPLOYEE all within the PARTY entity? An issue is that a single person or organization may be involved in more than one of these relationships. For example, a distributor of the manufacturer may also

45、be a supplier of some of their PC components. Again, we do not want to maintain more than one occurrence of the same person or organization as this can lead to data inconsistencies. Figure 5 illustrates how the previously described universal data models can be modified to meet the information needs

46、of our manufacturing example. For simplicity reasons, only a few important entities are shown in Figure 5, but all previously described entities also apply to our manufacturing firm. The PARTY RELATIONSHIP is sub-typed into the applicable business relationships, CUSTOMER, SUPPLIER, DISTRIBUTOR, EMPL

47、OYEE and INTERNAL ORGANIZATION. This allows each person or organization to be involved in one or more of those relationships. If there are other types of relationships such as sales agents, government agencies who regulate manufacturing or stockholders, they can also be defined as additional PARTY R

48、ELATIONSHIP sub-types. The basic information about each person or organization such as their names, credit rating, addresses, phone numbers and other contact information is associated with the PARTY. The information about each relationship is stored in the PARTY RELATIONSHIP entity. All sub-types of

49、 PARTY RELATIONSHIP have a from_date, through_date and comments. Each PARTY RELATIONSHIP sub-type may have different attributes to define that specific relationship type. For example, the CUSTOMER sub-type has a credit limit, statement_day (defined as the closing day for statements), and statement_frq (defining the frequency of statements such as weekly,