Web-Based Tourism Information Management System, Assignments of Design

Download Web-Based Tourism Information Management System and more Assignments Design in PDF only on Docsity! IT 12 004 Examensarbete 30 hp Februari 2012 Design and Implementation of a Web-Based Tourism Information Management System: Travel-SYS Zhang Shuo Institutionen för informationsteknologi Department of Information Technology Table of Contents 1 Introduction ....................................................................................................... 5 1.1 Background ....................................................................................................... 5 1.2 Related work .................................................................................................... 6 1.3 Thesis Purpose ................................................................................................ 7 1.4 Thesis Outline .................................................................................................. 5 2 Requirements Analysis ..................................................................................... 9 2.1 The overall system requirements ............................................................. 9 2.2 Feasibility Analysis...................................................................................... 10 2.3 Functional Requirements ......................................................................... 11 2.3.1 User Requirements ....................................................................... 11 2.3.2 Administrator Requirements ................................................. 14 2.3.3 Requirements of Vendors .......................................................... 15 2.4 Non-functional requirements ................................................................. 16 2.4.1 Performance Requirements ...................................................... 16 2.4.2 Usability Requirements .............................................................. 17 2.4.3 Security Requirement ................................................................. 18 2.5 System Data Analysis .................................................................................. 19 2.5.1 Data Requirements ....................................................................... 19 2.5.2 E-R Diagram .................................................................................... 20 3 The design of Travel-SYS System .................................................................. 23 3.1 Overall Design ............................................................................................... 23 3.1.1 Design Principles .......................................................................... 23 3.1.2 Overall System Structure ........................................................... 24 3.2 Design of Two-dimensional User Management Model .................. 25 3.3 Detailed Design of the System ................................................................ 26 3.3.1 Hierarchical Management Module of Attractions ............. 26 3.3.2 Basic Information Management Module of Attractions .. 27 3.3.3 Image Management Module of Attractions .......................... 29 3.3.4 Travels Management Module of Attractions ....................... 30 3.3.5 Vendors Information Management Module ........................ 31 3.3.6 User Management Module ......................................................... 32 4 The implementation of Travel-SYS System .................................................. 35 4.1 Realization of attraction hierarchical management module ....... 35 4.2 Realization of attraction basic information management module ……39 4.3 Realization of attraction picture management module ................. 41 5 Summary & Outlook ...................................................................................... 54 5.1 Summary ......................................................................................................... 54 5.2 Outlook ............................................................................................................ 55 References ........................................................................................................... 56 5 Chapter 1 Introduction 1.1 Background During recent years tourism has become one of the world's largest and most powerful industries. With the expansion in tourism, the application of information technology in that area has also developed rapidly. Traditional management tools usually artificially manage text, icons and pictures, and make decision through these. But, in today's fast-developing environment, traditional management cannot meet the demand of updating speed, and it has significant limitations in saving and data modification, and also data would easily be missing. All the shortcomings can lead to inaccurate information, as a basis for managers and decision makers. Tourism information management systems can be developed to meet these growing needs. A tourist information management system is a product which is required when tourism develops to a certain stage [9]. It allows tourism resources to be effectively managed, offers timely and accurate travel information to travelers, and provides tourism management departments the basis for tourism planning and decision-making in order to improve their efficiency. As China's economy rapidly develops and the people‟s income increases, more and more people choose tourism as a way of spending their leisure time, with self-tourism becoming the major trend. [10]In this case, many travelers highly depend on tourist information services. They need to search for as much information as possible to help making their decisions, including itinerary, transportation, hotel and so on. Experts point out that a travel decision-making of tourist, in fact, is a process including tourist information input, processing, output, and feedback. [11] Therefore, this put forward a great demand on large amount of high-quality easy-to-get tourism information. Web-based tourism information management system can well meet the demand, in which database is used to store large amount of tourism information, and web pages are used to present the information. Besides, search engine is incorporated to provide powerful search capability. Different from traditional information management 8 2. The overall design of the Travel-SYS The B/S structure with three-tier architecture is adopted, which has the advantages of easy to use and easy to maintain. The clear separation of presentation, business logic and data has made it much easier to extend and modify. The system is divided into six modules: attractions level management, attractions information management, image management, travel management, business information management and user management. A two-dimensional role-based user access control model is adopted, which allows for an implementation of very flexible user management. 3. Detailed design of the Travel-SYS Based on the overall design, we designed the logic of each module and a collection of specific functions for each module. We also designed database structure and database tables of the system. 4. Implementation of the Travel-SYS The Travel-SYS system is implemented using C# in the framework of .NET. The database used is SQL Server. We have finished all the programming and debugging. [7] 1.4 Thesis Outline The report is organized as follows. Chapter 2 presents the requirement analysis. Chapters 3 and 4 describe the design and the implementation of the system, respectively. Finally, some concluding remarks about the results from the project are given in Chapter 5. 9 Chapter 2 Requirements Analysis Requirement is what a particular product must meet, which is an indispensable feature of the product. Two being reasons for this: one is that products must obtain some function and quality; the other is customers expect such requirement to be a part of the products delivered. Requirements analysis includes a series of processes and its ultimate goal is to locate a customer or user‟s needs. [1] After collecting, extracting and summarizing the needs, the requirement will be patterned to form a requirement specification, which serves as the foundation for following software development sections. Requirements analysis is receiving increasing attention and becomes a very long, complicated section in project cycle, during which experts talk with their customers, write down the conversation results, analyze the collected information, extract key points, sum up a general concept, and then discuss the identified problems with the customers. This process can be repeated and across the entire life cycle of some projects. Requirements specifications, i.e., documentation generated during the requirements analysis section generally includes functional requirements, non-functional requirements and design constraints, etc. 2.1 The overall system requirements The Web-based tourism information management system (“the System”) is an open platform which integrates tourists, vendors and tourism-related information resources. The System is designed to provide an information management system which is tourism-relevant, well-structured and with high satisfaction in user experience. The System can meet visitors‟ needs of pre-travel planning and post-travel experience sharing. It also provides basic travel information, pictures, and travel notes sharing functions, etc. With the System, vendors can expand their business scope and provide 10 better service with reference to visitors‟ feedback. Vendors' information becomes a seamlessly integral part of travel information. The web-based tourism information management system should have the following basic features: 1. High Integration Weak points like imperfect connection of vendors‟ information with attraction information and limited operation of post-travel experience sharing generally exist in previous systems. The System is committed to narrowing the gap between tourists‟ and businesses‟ perspectives and integrating needs of pre and post-travel, thus providing more efficient and reasonable access to travel information. 2. High Usability The System must have high usability because they are for the general public and travel enthusiasts. The interface should be simple to avoid ambiguity. Page-level distribution should be clear and common functions should not be buried in the bottom layer structure. The accurate and real-time information also affects the System's usability. 3. Complete Functions The System shall meet general needs of ordinary users. It provides the information collections from food, housing, transportation to the attraction itself, which are necessary for tourism activities. After traveling, the System provides tourists a platform to share experiences including photos, travel notes and reviews. Loss of users due to functional defection should be avoided in the early days when the System is on line. 4. Security Security is a generally considered factor for all systems, including confidentiality of users‟ and businesses‟ information, database backup, network security and other safety factors. Detailed description is presented in the section of non-functional requirements. 2.2 Feasibility Analysis 1. Technical feasibility 13 Users can choose to upload travel notes in their own interfaces after login and share their travel experience. Visitors can share their latest and most reliable travel resources with others by writing travel notes after traveling. 6. Delete Pictures, Travel notes or Comments After login, users can see their previously uploaded travel notes, pictures or comments in their own interfaces. If they want to delete them for some reason, they can choose the delete link. 7. Modify Pictures or Travel notes After login, users can see their previously uploaded travel notes, pictures or comments in their own interfaces. They can choose the modify link if they want to modify pictures or travels for some reason. 8. Comment on Others’ Photos or Travel notes After login, users can comment pictures or travel notes and communicate with other users through commenting their pictures or travel notes. 14 9. Rating Pictures, Travel notes, or Attractions After login, users can rate pictures, travel notes and attractions which they have browsed. Rating reflects how much the public like the picture, travel note or attraction. Users can express their own views to provide reference to others. This is a very important feature of the web 2.0, which users can participate in, rather than just passively receiving information of. Thus, users have become the information provider as well. 2.3.2 Administrator Requirements The administrator is responsible for controlling the system‟s proper operation. Figure 2-3 is a use case diagram [4] for administrators. 1. Add / modify Province - City - Attractions Information Tourist attractions are logically organized in Province - City - Attractions hierarchy according to geographic location. The administrator is responsible for maintaining such hierarchy. When new attraction needs to be added, the administrator should add introduction, traffic information, and weather conditions for the new attraction on the new attraction‟s page. When attraction information is updated, the administrator can modify the tourist attraction information page. Figure 2-2 Sequential Diagram Figure 2-3 Administrator Use Case Diagram 15 2. Management of User Authority Two-dimensional user management model is adopted here. High-level administrators can authorize low-level administrators. The administrator can allocate his/her jurisdiction and authority. In the user management interface, administrators can choose the authority-adding link to authorize operations. Administrators can forbid ordinary users‟ operations for some reason as well. 3. Management of vendors’ Information Administrators need to review and approve the application submitted by vendors so as to ensure the correctness and relevance, and also guarantee user's interests. The approved information should be added to the related web page and open to users. Administrators are to monitor the information which includes its validity and user feedback on the vendors. 4. Review Network platform system has a large degree of freedom. In order to ensure the legality of the content submitted by users, the administrator has to review the whole system. This review includes each administrator‟s review within their responsible scope. 2.3.3 Requirements of Vendors Quality of food, accommodation, and transportation directly relates to the quality of the whole trip. Figure 3-4 is a vendor use case diagram. Vendors provide visitors with service information of the surroundings, which includes catering, accommodation, local travel agency services. In this way, vendors‟ information is promoted and brings convenience to users as well. 1. Submit Application Vendors need to fill out an application if they want to move from general user into a Figure 2-4 Vendor Use Case Diagram 18 habits and clear navigation, etc. Help information is also very critical and should be provided in appropriate place. When error occurs, the system can correct the error or return to the previous step, which also means good performance of the system robustness. 4. Efficiency Efficiency requirement of the system can be measured by the time taken to complete a task or the average number of tasks completed in unit time by users. Efficient user experience will directly increase customer satisfaction. Efficiency of the system can be divided into two parts: efficiency of the user-controllable and the efficiency of the system itself. Reasonable interface layout, buttons, and logical hierarchy enable high operating efficiency for users; background processing and connectivity speed of database will affect the efficiency of the system itself. 5. High User Satisfaction User satisfaction, a more or less abstract measure, means that users enjoy using the system and fell satisfied with the whole process. As for Travel-SYS system, the number of registered users can be regarded as a measure of satisfaction. If users are willing to use the system as a travel information search platform and share their experiences with others on this platform, user satisfaction will prove to be high. In addition, user's feelings can be obtained through customer satisfaction investigation. 2.4.3 Security Requirement Security requirement is a critical requirement, for big risks may be brought by products that fail to meet security requirement. Security of system information tends to be even more important nowadays when the Internet wins wide popularity. Security involves confidentiality, availability and auditing. 1. Confidentiality Confidentiality means that only authorized users have access to data. Who is the authorized user and under what circumstances the authorization is valid must be specified. After given a role by the administrator, a user turns into an authorized user within his/her competence. The high-level administrator can authorize the low-level user roles and specify available time of the roles. Higher administrators can only manage their subordinate administrators. 2. Availability Availability refers to that the authorized user can have access to data without 19 limitation, which means data will be still available even they are archived to somewhere else or wrong operation occurs. In practice, backing up data can prevent data loss. Measures to recover the lost data are also available. In the Travel-SYS, user‟s data transferred to the custody of the system, including uploaded pictures and travel notes, are extraordinarily valuable and should not be lost. Availability of data must be ensured through database management and design. 3. Auditing Auditing requires the system to maintain an audit trail record which includes data about who has access to what kind of information as well as all transaction logs within a certain period of time so as to avoid casual mistakes. Auditing can also provide proof for future objections or disputes. It is particularly important in terms of business-related information. 2.5 System Data Analysis 2.5.1 Data Requirements One of the most important functions of the web-based tourism information management system is to manage a large number of tourist information data. Data should be ensured as accurate, consistent and real time. Both internal structure and external form of the data will directly affect the quality and performance of the system. Accuracy of the data is always the most basic requirement. A complete data collection specification is required before the data collection to ensure the integrity of the data collected, for there is a wide range of tourist information and data. After collection, input of the data is a key part that can affect the accuracy. Therefore, operators should be proficient and responsible; the system can also reduce the probability of error through correction mechanism. Travel information and data are very open and users can participate in activities to ensure the accuracy of the data through the appropriate link in the page and provide error mechanism. Consistency here means that information consistency should be maintained when the same content appears in different places. So the data need to be constrained. Relevance of the data is required when designing the database so as to provide consistency for the future maintenance of data protection. For the possible distributed data, data redundancy should be noted. [2] 20 Tourist information demands high requirement on instantaneity. In order to meet the real-time features, information collection sensitivity and efficiency should be high, but technical requirements can be relatively low. For this tourism information management system, specialized staffs are responsible for updating the information on tourism. 2.5.2 E-R Diagram Database structure design focuses on information structure design, which is the key point of the entire database system. An independent conceptual model is generated through integration, induction and abstraction of users‟ requirements. Conceptual model usually have the following four characteristics: [6] 1. Rich semantic skills can express various needs of users, including descriptions of objects in the real world and connections between the objects. These skills can meet the needs of users for data processing. 2. Easy to communicate and understand. Database developers and users can communicate through the conceptual model. 3. Easy to modify. When requirements and conditions change, the conceptual model can be modified. 4. Easy to transfer to other data model transformation and derive DBMS-related logical model. In development process, this system also adopts the most commonly used method of concept model design: ER model, also called the Entity - Relationship Model. ER diagram is composed of entity set, attributes and connections. The member of the entity sets is an entity and can be understood as the real world objects. Attribute means the properties of entities. Connection refers to relationship between the entity sets. Figure 2-5, 2-6 and 2-7 lists the attraction E-R diagram, picture ER diagram and the user ER diagram respectively. 23 Chapter 3 The design of Travel-SYS System 3.1 Overall Design 3.1.1 Design Principles 1. System Reliability Reliability of computer systems usually refers to the probability of correct computer system operation under specified conditions and within a given period of time. In specific applications, failure probability of the system is commonly used to measure the reliability. This tourism information management system has strict requirement for reliability, but no so stringent as that of 24 * 7 systems. To meet the system reliability, unreliable factors should be avoided in the design phase. Risk analysis can help, to some extent, to meet this requirement. Risk analysis begins with risk identification and then goes to intensive study of risk to determine the specific content and scope of risk as well as its possible probability. Further analysis intents to determine the extent of the impact of risk. Risk aversion measures will be worked out based on the selected risks, though which system reliability can be effectively protected. 2. System Scalability System scalability is particularly important when technology is rapidly developing nowadays. People are ready to accept new concepts with the rapid development of software and hardware technology as well as flourishing innovative ideas. Meanwhile, only one-time development tends to more and more impossible to meet the growing needs of application. Scalability has become a vital quality indicator of systems, which determines whether the system can be upgraded in the future. System should have the characteristics of backward compatibility. This tourism information management system should also follow the principle of scalability of the system. As a platform for all travel enthusiasts, Travel-SYS will inevitably undertake the second development with the growing number of users, expansion of user demand and development of tourism industry. During the design process, there should be independent module function, complete module interfaces and clear structure of associated data in database to ensure system scalability. Demand for capacity expansion can‟t be ignored, either. 24 3. Functional Integrity of the System Definition of functional integrity varies from system to system. Generally speaking, functional integrity means there is the smallest full-featured set and combined functions can be fulfilled. For the Travel-SYS, a complete system not only means to meet the basic needs of different users, i.e., users before and after travel as well as vendors, but also to maintain complete structure of each functional unit. Integrity of function should be considered in both requirement and design phases. In the design phase, design should be strictly in accordance with the requirements defined in the specification. 3.1.2 Overall System Structure Travel-SYS，a web-based tourism information management system, is engaged to provide tourist information, information inquiry and sharing platform to the public. The system integrates the common needs of tourists and businessmen and provides information sharing platform to tourists and businesses. To meet the various needs of different users, the system provides comprehensive functions, including information search of attractions and business information search before travelling; requirement of individual sharing after traveling is also taken into account. The overall system is divided into six modules: attractions hierarchical management module, attractions basic information management module, picture management module, travel notes management module, vendors information management module, and user management module. Relationship between the modules is peering, as shown in Figure 3-1. Details of each module will be discussed in the following chapters. 25 3.2 Design of Two-dimensional User Management Model With the popularity of information management systems, more and more companies choose to use a dedicated unit of information management system for business management. Considering huge user community, complex hierarchy and distinction of multi-user identity and responsibility, two-dimensional management model of users can better satisfy the corresponding functional requirements. Two-dimensional user management module is a role-based authority management model which adopts design methods based on role and hierarchical structure to achieve management of user accounts / information and authority management. There exist four basic objects in the two-dimensional user management module: basic rights, authority, roles and users. The hierarchical relationship is shown in Figure 3-2. Relationships between various concepts can be seen from the figure. Basic right is the smallest unit that can be a simple operation or a combination of several operations. A single task can be completed through basic right, like adding, deleting and so on. Authority is a combination of basic rights. For example, review authority in the Travel-SYS can involve basic rights as viewing content, deleting contents that violate relevant regulations and alerting users. Scope means effective area of authority. For example, a user has review authority and the range covers the East China provinces; another user also has the review authority, but its scope is provinces in the Southern China. Thus, different roles are distinguished. Either same authority within different ranges or different authorities within same scope is regarded as different roles. Figure 3-1 Travel-SYS system T rav el-S Y S M an ag em en t S y stem Attraction Hierarchical Management Attraction information Management Picture Management Travel Notes Management Vendor Management User Management 28 1. Introduction to Attractions Added by the related administrator, description of the attraction is available on the attraction home page, including distinguishing features, history and folk culture of the attraction. Any visitor can browse. 2. Traffic Information Traffic information is available on the attraction home page, including transport frequency, routes, and fares of flights, trains, buses and other vehicles. It provides visitors with accurate and useful transportation information and brings convenience to their trip planning. 3. Weather Weather condition of the next three days is provided on the attraction home page. Weather is one of the key factors that affect traveling and is substantially concerned by visitors. Weather conditions will be automatically updated with plug-ins provided by third party. 4. Attraction commenting Attraction evaluation can be submitted on the attraction home page by visitors who log in as users. The evaluation includes attraction rating and comments. Rating counts from one star to five stars and the five stars represent the best. Comments of the attraction are no more than 300 words. The same user can only rate the attraction once within half a year, but comments are not restricted. 5. Information of surrounding commercial facilities Information of surrounding commercial facilities is available on the attraction home page, including catering, accommodation and travel agency services. When making preparation for travelling, visitors can grasp more detailed information of local service Basic Info. Of Attraction Descri ption Comm ents Traffic Info. Weath er info. Vendor s Info. Figure 3-4 Basic information Management Module of Attraction 29 and have a more comprehensive knowledge of the local food as well as handicrafts, etc. 3.3.3 Image Management Module of Attractions Image management module of attractions includes five sub-modules which refer to image upload, image deletion, image information modification, image comment and image review, as shown in Figure 4-5. 1. Upload Image After login, users can choose to upload pictures on their own interfaces and share photographs taken in an attraction. Users select the local picture and then location information of the picture within which select province, city and attraction successively. Filling of image name and image description are optional. After that, upload the picture through clicking the image uploading link. Pictures will appear on website after verification. 2. Delete Image Both users and administrators can delete images. After login, users can see uploaded images on their own interfaces. Select deleting link and the system will pop up a dialog box to confirm the deletion. Users can not delete other people‟s images. Administrators can delete all images within their authority range. If catching sight of an illegal image, administrators can click the deletion link after logging in. Images will be deleted after administer enters his/her password and confirms it. 3. Modify Picture Information Users can modify information of their uploaded images, including image name and description. After login, users select the modification link under the image, make modification in image editing interface and then submit. 4. Comment Images After login, users can comment images available, which involve rating and Image Management Upload Image Image comm ent Delete Image Edit Image info. Image Review Figure 3-5 Image Management Module of Attraction 30 commenting just like commenting attraction. Rating counts from one star to five stars, one for the worst and five for the best. A user can only make comments on the same image for once. Images arranged according to star level are located in image area on the home page. Comment refers to visitors‟ feelings of the image and their suggestions. Users can comment images after login through editing comments and then submitting them. Comments should be no more than 300 words and ordered down by time increments. 5. Review Images Photo Review is complied after uploading of images and before releasing them on the website. Related administrators should review images uploaded by users and delete those violating relevant regulations. 3.3.4 Travels Management Module of Attractions Travels management module includes four sub-modules as travel note uploading, deletion, modification and rating, as shown in Figure 3-6. 1. Upload Travel notes Users can share their travel knowledge and experience and keep notes of what is heard and seen. After login, users can choose to upload travel notes, edit the text part and insert images which can be selected from image gallery. Like uploading images, related geographic location information should be selected. Finally, click travels uploading link. 2. Delete Travel notes Users can choose to remove their uploaded travel notes. After login, users can see their travel notes uploaded previously. If the deletion link is clicked, a dialog box will pop out. Deletion will take effect after confirm the dialog box. Users can not delete other travels. 3. Modify Travel notes Travel Management Upload Travel Notes Rate Travel Notes Delete Travel Notes Delete Travel Notes Figure 3-6 Travel Management Module of Attraction 33 approval. Vendors can see their own business information page among the public business information.  Review travel notes / photos / comments. The administrator can review travel notes, pictures or comments within his/her authority range. As for any contents against relevant regulations, the administrator has right to delete or shield them.  Publish vendors. After completing application of becoming vendors, the user‟s business information will be published by the administrator. With open status, such business information can be browsed on the vendor‟s attraction home page.  Remove travel notes / images / comments. When necessary, the authorized administrator can remove a travel notes, pictures or comments.  Add or delete attractions. With the growth of requirements, the administrator can add new attractions, put them into the hierarchical structure, add basic information of the attractions and set up new attraction home pages. If necessary, the authorized administrator can choose the deletion link and delete the attraction information after confirm the dialog box. All images, travel notes and business information subordinate to this attraction will be deleted all together.  Add or delete roles. Only administrators of highest level can add or remove roles. Adding a role begins with naming the role and then chooses its authorities through check boxes. Authority can be more than one and its range should be defined. Choose a certain range within the province-city-attraction tree structure, click the adding button and then a scope set will be generated. Repeated adding is available. When deleting a role, the operating user should be granted with authority. The user with such role will automatically become common user when the role is deleted.  Add or delete authority scope. The administrator needs to add authority range before setting effective range of a certain role. The authority range appears as content tree structure; provincial or municipal node can be regarded as a range. New range will be generated simply after filling the range‟s name and choose its related province and city in the drop-down box. Attraction is the smallest unit of authority scope. 2.2 Apply and authorize authority Users can apply for different roles. After the user submits an application of role, the administrator can endow him/her the role, which includes authority and its effective range. 34 As for Travel-SYS system, visitor need undergo several procedures to obtain authority. Visitors become common users after register and can ask the administrator for relevant authority. The administrator can allocate authorities directly and give the authority to users. Thus, users have access to module of their role ranges and carry out relevant operations. Before each operation comes into force, the system will apply the authority check module to ensure the validity of the operation, as shown in Figure 4-9. 3. Register When visitors require more services provided by this system than browsing, they have to register to become users. Register process is very simple. Offer e-mail as the unique identifier, enter a password and re-enter it. After acceptance of the Terms of Service, the visitor will become a common user. 4. User Login Enter e-mail address and password when login. If forgetting the password, users can regain it through e-mail and enter their main interfaces. Register User Enter Module Execute Function Call Authority Verification Config Authority Config Range Config Role User Management Check Authorization Assign Role User Management Wait for authorization After Authorization Figure 3-9 Processes of User Management 35 Chapter 4 The implementation of Travel-SYS System On the basis of the above requirement analysis and system design, realization of this traveling information management system is displayed in the following paragraphs. The realization is typically includes realization of attraction hierarchical management module, attraction basic information management module, attraction picture management module and attraction travel note management. 4.1 Realization of attraction hierarchical management module As explained before, attractions are organized according to hierarchical relationship of geographic locations. Province node includes city node and the city node includes county node under which titles of attractions are arranged. Visitors can locate at their preferential attractions through directory-tree-type hierarchical structure. The administrator can operate the directory tree and set its hierarchical structure, including adding, editing and deleting nodes. 1. Add nodes Right click on the mouse where the sub-node needs to be added and then choose “add sub-node” option, as shown in diagram 4-1. Diagram 4-1 Add Sub-node 38 } break; The above codes use GetNodeByID function of TreeViewWS which belongs to WebService. This function takes the return value of the onGetComplete function as the key function parameter and the onGetComplete function will take the value obtained from the WebService as the node title in the directory tree and transfer it to node textbook. 3. Delete nodes When deleting nodes, right click on the mouse where the node needs to be deleted and choose the “delete node” option. After confirm the dialog box, this node together with its sub-nodes will be taken away in the directory tree. Javascript code is applied to realize node deleting operation of the attraction hierarchical structure, i.e. directory tree, and the main code realization is as follows: case "Delete": PresentNodeID = SelectedParentNodeID ; SelectedParentNodeID=0; if ( PresentNodeID !=0){ if (confirm("谨慎！！您确定要删除节点 '" + SelectedParentNodeDesc + "'?")){ TreeViewWS.DeleteNodeByID(PresentNodeID, onDeleteComplete, onWebMethodTimeout, onWebMethodError); function onDeleteComplete(result, response, context){ alert("节点 '" + SelectedParentNodeDesc + "'. 删除成功...."); RefreshParentNode(whichDiv); document.getElementById(HdnCurrentFileID).value = (new Date()).getDate(); doPostBack(HdnCurrentFileID, ''); } } } else{ alert("不能删除此节点！"); } break; The above codes use DeleteNodeByID function of TreeViewWS within 39 WebService. The function takes the return value of the onDeleteComplete function as the key function parameter and the onDeleteComplete resets the value obtained from the WebService. 4.2 Realization of attraction basic information management module Each attraction has a homepage of attraction basic information of which the left shows the directory tree. The administrator can set catalogues of the directory tree through adding, editing and deleting nodes in the directory tree. Click any node in the directory tree and information of this node will appear in the right part of the page. If the clicked node has no sub-node, it means that this node is a leaf node. Then the right page will display the related attraction homepage, including attraction description, transportation information, weather information, attraction evaluation and the information of surrounding commercial facilities. What is shown in the homepage is summarized information of each part. If you want the detailed information, click the “more” link after every header. If you want to check the pictures and travel note of the attraction, click “enter attraction information resource base” button, as shown in diagram 4-4. The attraction homepage‟s directory tree is achieved with TreeView control which makes the directory tree show in the homepage in two steps. First do initial set of the TreeView control tree form catalogues and then obtain the title of each node of the directory tree in the database. Fill the title into the TreeView control tree form Diagram 4-4 Homepage of Attraction 40 catalogues through taking DataTable-type data structure as the connector. Main code realization of the two steps is as follows: 1. Tree form catalogue of the initialized TreeView control public void InitNodeTreeView(TreeView tv) { DataTable dt = NodeBLL.GetNodeList(); if (dt == null) return; dt.Columns.Add(new DataColumn("url", typeof(string))); Cache.Insert("NodeList", dt); //缓存数据，以便后面直接从缓存中获取数据节省存取时间 tv.Nodes.Clear(); //清空树的所有节点 DataRow[] rowList = dt.Select("Node_ParentID=0 and Node_DeleteFlag='V'"); if (rowList.Length < 1) return; TreeNode root = new TreeNode();//创建根节点 root.Text = rowList[0]["Node_Name"].ToString();//设置根节点属性 root.Value = rowList[0]["NodeID"].ToString();//设置根节点的value值 root.Target = "rightFrame";//rightFrame表示<iframe>的ID root.ImageUrl = "~/Images/computer.gif"; root.NavigateUrl = "~/Nodes/NodesList.aspx?nodeid=" + root.Value; root.Expanded = true; root.SelectAction = TreeNodeSelectAction.SelectExpand; tv.Nodes.Add(root);//添加根节点 CreateChildNode(root, dt, "rightFrame");//创建其他节点 } 2. Save the database content in DataTable form and then fill the tree node through reading the database content. private void CreateChildNode(TreeNode parentNode, DataTable dt, string target) { string url = string.Empty; DataRow[] rowList = dt.Select("Node_DeleteFlag='V' and Node_ParentID=" + parentNode.Value); 43 string tempFilePath = "..\\UploadFiles\\private\\" + ViewState["username"] + "\\"; bool haveFile = File.Exists(saveFilePath + "\\" + fullFileName); filePath = tempFilePath + fullFileName;// 数据库中保存文件的路径 previewPath = tempFilePath + "PreviewImage\\" + fileName; // 数据库中保存预览图的路径 // 文件大小转换 if (tempFileSize > 1024 * 1024 * 1024) fileSize = Convert.ToString(Math.Round( (tempFileSize + 0.00) / (1024 * 1024 * 1024), 2)) + " GB"; else if (tempFileSize > 1024 * 1024) fileSize = Convert.ToString(Math.Round( (tempFileSize + 0.00) / (1024 * 1024), 2)) + " MB"; else if (tempFileSize > 1024) fileSize = Convert.ToString(Math.Round( (tempFileSize + 0.00) / (1024), 2)) + " KB"; else fileSize = Convert.ToString(Math.Round( (tempFileSize + 0.00), 2)) + " B"; if (txt_fileName.Text.Trim() != "") { fileName = txt_fileName.Text.Trim();// 重命名 fullFileName = fileName + "." + fileExtentName; filePath = tempFilePath + fullFileName; } if (haveFile) { int counter = 1; while (haveFile) { fileName = "(" + counter.ToString() + ")" + fileName; fullFileName = "(" + counter.ToString() + ")" + fullFileName; filePath = tempFilePath + fullFileName; counter++; } 44 } file.SaveAs(saveFilePath + "\\" + fullFileName + ".重命名 "); // 防止文件上传攻击，在文件全名后加„.重命名‟ } else { if (tempFileSize == 0) Page.ClientScript .RegisterStartupScript(GetType(), "upnull1", "<script>alert('请不要上传空文件！');return false;</script>"); if (tempFileSize >= 1073741824) Page.ClientScript .RegisterStartupScript(GetType(), "upnull2", "<script>alert('最大上传1G的资源！');return false;</script>"); } } } 2. Picture review Uploaded pictures of the users need to be revived by the administrator who can examine all pictures and their specific information in administrator page. The administrator can review pictures in batches through checking the box before each picture and has right to delete pictures that violate related regulations, as shown in diagram 4-6. 45 Code for reviewing pictures is as follows: protected void btn_execute_Click(object sender, EventArgs e) { bool flag = false; string select = Request.Form["select_action"].ToString(); string[] ckbNum = Request.Form.GetValues("CheckSingle"); for (int i = 0; i < ckbNum.Length; i++) { switch (select) { case "check": if (ResourceBLL.Update(Convert.ToInt32(ckbNum[i]), 'Y') > 0) flag = true; else flag = false; break; case "uncheck": if (ResourceBLL.Update(Convert.ToInt32(ckbNum[i]), 'N') > 0) flag = true; else flag = false; break; case "del": if (ResourceBLL.Delete(Convert.ToInt32(ckbNum[i]))) flag = true; else Diagram 4-6 Picture Review 48 set { _resourcereviewid = value; } get { return _resourcereviewid; } } public int ResourceID { set { _resourceid = value; } get { return _resourceid; } } public int UserID { set { _userid = value; } get { return _userid; } } public string ResourceReview_Content { set { _resourcereview_content = value; } get { return _resourcereview_content; } } public DateTime ResourceReview_Date { set { _resourcereview_date = value; } get { return _resourcereview_date; } } public float ResourceReview_Grade { set { _resourcereview_grade = value; } get { return _resourcereview_grade; } } } The evaluation class is instantiated; evaluation adding operation of pictures is completed through obtaining and setting property values of the evaluation class through get and set functions. Code for adding comments is as follows: protected void btn_review_Click(object sender, EventArgs e) { 49 if (txt_reviewContent.Text != "") { Travel.Model.ResourceReview Model = new Travel.Model.ResourceReview(); Model.ResourceID = Convert.ToInt32(ViewState["ResourceID"]); Model.UserID = SessionBox.GetUserSession().LoginId; Model.ResourceReview_Content = txt_reviewContent.Text; //.Replace("\\r", "<br>") Model.ResourceReview_Date = DateTime.Now; Model.ResourceReview_Grade = float.Parse(this.Rating1.CurrentRating.ToString()); Add(Model); UpdateReviewsCount(Convert.ToInt32(ViewState["ResourceID"])); //更新评 论数 BindReviewList(Convert.ToInt32(ViewState["ResourceID"])); BuildPagers(); this.txt_reviewContent.Text = ""; } else ScriptManager.RegisterStartupScript(this, this.GetType(), "click", "alert('评论 内容不能为空！'); ", true); } 5.4 Realization of user management module User management module is divided into three parts: users‟ register, login, and users‟ authority and role management. Common users can register and login; the administrator manages users‟ authority. 1. Register When register, users need to enter E-MAIL, username, password and identifying code and then click the submit button, as shown in diagram 4-8. 50 2. Login After register, the visitor can login as a user. Users‟ login interface is shown in diagram 4-9. 3. Users‟ authority and role management Users‟ authority and role management mainly includes two parts: users‟ authority management and role management. Authority management includes Diagram 4-8 User Register Diagram 4-9 User Logon 53 ScriptManager.RegisterStartupScript(this, this.GetType(), "muti_del", "alert(' 您没有选择任何项！');", true); return; } if (flag) { ScriptManager.RegisterStartupScript(this, this.GetType(), "muti_del", "alert(' 所选角色删除成功！');", true); BindRoleList(); upList.Update(); } else { ScriptManager.RegisterStartupScript(this, this.GetType(), "muti_deln", "alert(' 所选角色删除失败 ！');", true); } } 54 Chapter 5 Summary & Outlook 5.1 Summary Along with people‟s growing needs for traveling activities, traveling information management system will inevitably develop rapidly. Self-help traveling, with an increasing popularity, takes up the major tourism market. Self-help travelers need substantial and high-quality information before traveling. Thus, how to provide travelers with convenient and fast service in a circumstance of high information density becomes the subject of this research paper. This research paper project begins with analysis on nowadays main traveling information management systems and then through requirement analysis determines the overall structure and main functions of the system. System study and development is carried out according to general software development procedure. Two dimension user management model is adopted here, whose practical application is displayed through study on its integration with specific application systems. Finally, a web-based traveling information management system within the Microsoft NET frame is realized. This paper mainly involves the following work: (1) Do market survey and analysis of the traveling information management system, summarize its current situation and study its domestic as well as overseas development situation, thus bringing out the key research objective of this paper; (2) Study and analyze related technologies adopted in this system development, including ASP.NET、ADO. NET under NET development platform, database and UML modeling technologies. (3) Based on theoretical and practical experience, do a detailed requirement analysis on the traveling information management system; start from functional as well as non-functional requirements with UML modeling method and succeed a complete set of system requirements which includes security requirement and data requirement. (4) Do a top-down system design of the traveling information management system through a comprehensive understanding of the requirement analysis conclusions. Adopt WBS method to divide the system into six sub models and design these sub models in proper sequence. Introduce conception of two dimension users‟ 55 management model and analyze its feasibility and practical value through integrating it with specific application system. Design the database with E-R diagram. (5) Use Microsoft Visual Studio 2008 development software, SQL Server database software to develop the system and design its interface, achieving an open information platform which satisfies both travelers and business‟ needs. 5.2 Outlook The writer of this paper gains a relatively deep understanding of the traveling information management system‟s current situation through its study and development process. Due to the writer‟s limitation of time and capability, this system still has some imperfections which need to be improved, as summarized below: (1) Improvement of interface design and users‟ experience which is easy to be ignored. With extensive use of the information system, people tend to have higher and higher requirement of users‟ experience. This improvement has to undertake a process, during which users‟ feedback can be referred to. Excellent interface design can increase the efficiency of system usage, bring people convenience and at the same time attract more users. (2) Improvement of exception handling. Current exception handling version is still elementary and needs to be improved. Excellent exception handling can strengthen the system‟s availability, increase system efficiency and reduce error rate. (3) Improvement of system function. This system has some functions which can meet the basic requirements of travelers and businessmen. However, many other functions need to be added, such as search function, follow attraction and user‟s function, which can be realized in 2.0 version of the system. (4) Improvement of system security. System security, the key part of any system, should be attached substantial attention. This system only provides the essential security mechanism, that is, password and users‟ right management. Advanced security mechanism should be adopted in the future.