数字化环卫系统解决方案
收藏资源简介：
一、设计方针 本项目采用MVC模式进行开发和设计，我们采用各层分离的方式使层次之间达到低耦合，从而增加程序的灵活性，并降低了维护的成本。数据结构和服务采用模型驱动的方式进行开发。二、系统设计说明2.1 总体功能结构设计 2.2功能模块划分原则系统功能模块的划分，遵循着松耦合易扩展的原则，将每一个功能模块高度封装，模块与模块间完全通过接口实现信息传递。模块通过接口构建起紧凑牢固的系统结构，而某一个功能模块影响不到整个系统的正常运转，达到松耦合的目的。通过现有模块接口可以轻松挂接新的功能模块，且可以达到“即插即用”的效果，即实现了系统的易扩展性。2.3 系统物理结构设计逻辑业务通过调用基础数据来管理监控考核作业任务的执行情况，外部系统通过系统服务接口来访问数据。系统功能严格按照用户的权限来实现功能。2.4 网络拓扑网络拓扑结构及硬件规划：系统主要通过考核人员对作业现场的实际考评，通过对讲设备将在指定时间内向平台报告考核区域/点的考核情况。为保证数据的安全性，系统部署在环卫局的计算机中心机房，服务器与互联网分离，采用防火墙进行安全隔离,系统的访问采用严格的权限体系以保网络数据的安全。2.5 软件层次结构三、软件功能设计3.1 系统管理（1）用户管理针对使用该系统的管理人员进行帐号基本信息的增加、修改、删除和查询统计，明确用户使用范围。（2）角色管理 角色是系统使用的权限集合，针对系统用户的特点，可分别赋予不同的角色，从而使得用户方便继承角色的所有权限。（3）权限管理 管理系统所涉及的所有业务模块的权限信息，包括权限编码、相关URL、权限层次、权限类型等。（4）数据字典管理对系统常用的数据进行定义，定义其含义，标准值，标准范围以及数据变量等基础信息。（5）数据库管理查看数据库的实时状态，包括数据库容量和数据数量，并可进行数据库的备份、还原等操作。（6）作业区域管理 根据职责的划分，将作业任务计划纳入系统的管理，方便查询浏览。3.2 作业对象管理(1) 监测人员维护监测人员的基本信息，包括增加/删除监测人员和监测人员的基本信息维护，如姓名、性别、座机、手机号码等。监测人员可通过系统对保洁公司的责任区进行及时的考核评分，考核评分细则及分值视具体规则而定。同时，系统将对监测人员划分责任监测区域，系统会采用实时GPS定位和对讲机通讯的方式对监测人员进行定时考勤监督。（2）保洁公司 维护保洁公司的基本信息，包括增加/删除保洁公司和保洁公司的基本信息维护，如公司名称、简称、地址、联系电话、负责人等。 可实时查看各保洁公司的考核得分，并分等级予以不同的提示（如颜色红黄绿），可对保洁公司的历史得分情况进行查询和统计。 保洁公司可随时查询统计自己的区域考核得分。（3）环卫车辆 维护环卫车辆的基本信息，包括增加/删除环卫车辆和环卫车辆的基本信息维护，如车辆类型、车型、车牌号、驾驶员、租用公司等。（4）果皮箱 维护果皮箱的基本信息，包括增加/删除果皮箱和果皮箱的基本信息维护，如果皮箱编号、道路名称、管理单位（各环卫分公司及各办事处）、管理人姓名、安装时间、种类（不锈钢式，环保式等）、安装状态（预安装，已安装），可提供模糊查询。可在地图上定位果皮箱的位置，并提供果皮箱编号、种类、管理单位以及状态等基本信息展示。可查询统计果皮箱的使用情况，并导出报表。（5）垃圾桶 实现垃圾桶搜索功能：用户可以根据垃圾桶编号、道路名称、管理单位（各环卫分公司及各办事处）、管理人姓名、安装时间、种类（地埋式垃圾桶，立式垃圾桶等）、安装状态（预安装，已安装）进行搜索，可提供模糊查询。搜索结果除能在地图上显示以外，还能以表格的形式显示垃圾桶的详细信息和统计数量。实现垃圾桶地图定位功能：地图可根据用户的搜索结果显示单个或多个垃圾桶的图标及编号，当用户点击地图上垃圾桶图标时，应显示这个垃圾桶的编号、图片、种类、所在位置、管理单位、管理人员姓名、管理人员联系方式、安装时间。实现垃圾桶信息增加、删除、修改的功能：用户可以批量增加、删除、修改垃圾桶信息，并在提交到数据库之前显示增加、删除、修改垃圾桶信息后的结果，提醒用户检查是否有错，并提示用户是否发消息通知其他用户，最后经用户确认后提交。实现预安装垃圾桶功能：在地图上显示两种不同状态（预安装，已安装）的垃圾桶的时候，可以用不同的颜色或图标进行区分。当预安装垃圾桶安装完成后，用户可修改垃圾桶状态为已安装。实现垃圾桶撤除功能：考虑到今后垃圾桶有可能因损坏而撤除或更换新型垃圾桶的可能性，用户可将垃圾桶状态改为撤除或退路。（6）公厕实现公厕搜索功能：用户可以根据公厕名称、道路名称、管理单位（公司）、管理人姓名、管理人员联系方式、投入使用时间、建设状态（已建成、预建设、建设中）、种类（一类公厕、三类公厕）进行搜索，可提供模糊查询。搜索结果除能在地图上显示以外，还能以表格的形式显示公厕的详细信息和统计数量。实现公厕地图定位功能：地图可根据用户的搜索结果显示单个或多个公厕的图标及名称，当用户点击地图上公厕图标时，应显示这个公厕的名称、图片、种类、所在位置、管理人姓名、管理人员联系方式、投入使用时间（预建设公厕和建设中公厕显示预建设时间）、备注。实现公厕信息增加、删除、修改的功能：用户可以批量增加、删除、修改公厕信息，并在提交到数据库之前显示增加、删除、修改公厕信息后的结果，提醒用户检查是否有错，并提示用户是否发消息通知其他用户，最后经用户确认后提交。实现预建设公厕管理功能：在地图上显示三种不同状态（预建设，建设中、已建成）的公厕的时候，可以用不同的颜色或图标进行区分。当预建设公厕投入建设后，用户可将预建设公厕状态修改为建设中，当建设中公厕投入使用后，用户可将建设中公厕状态修改为已建成。（7）转运站实现转运站搜索功能：用户可以根据转运站名称、道路名称、管理单位（人环卫公司）、管理人姓名、管理人员联系方式、投入使用时间、建设状态（已建成、预建设、建设中）、种类（原建、翻建）进行搜索，可提供模糊查询。搜索结果除能在地图上显示以外，还能以表格的形式显示转运站的详细信息和统计数量。实现转运站地图定位功能：地图可根据用户的搜索结果显示单个或多个转运站的图标及名称，当用户点击地图上转运站图标时，应显示这个转运站的名称、图片、种类、所在位置、管理人姓名、管理人员联系方式、投入使用时间（预建设转运站和建设中转运站显示预建设时间）、备注。实现转运站信息增加、删除、修改的功能：用户可以批量增加、删除、修改转运站信息，并在提交到数据库之前显示增加、删除、修改转运站信息后的结果，提醒用户检查是否有错，并提示用户是否发消息通知其他用户，最后经用户确认后提交。实现预建设转运站管理功能：在地图上显示三种不同状态（预建设，建设中、已建成）的转运站的时候，可以用不同的颜色或图标进行区分。当预建设转运站投入建设后，用户可将预建设转运站状态修改为建设中，当建设中转运站投入使用后，用户可将建设中转运站状态修改为已建成。3.3 地图管理（1）区域管理 对辖区的区域进行维护，可在地图上直接标注地图区域，并进行责任对象的绑定。（2）作业点管理对辖区的作业点进行管理维护，可在地图上直接标注作业点，并进行责任对象的绑定。3.4、 系统选型3.1 选型原则根据系统构架设计，结合招标技术规格要求，确定如下选型原则：（1）软件开发环境选型原则：符合用户提出的技术参数和产品要求采用成熟的、稳定的技术和标准支撑环境/产品的售后服务和后续升级质量高采用接口标准、扩展性好的结构设计满足具体产品的性能、技术要求软件开发平台要提供对比选优具有开发和应用这些软件的经验（2）数据库选择原则：结合系统的规模、部署等实际情况，以及应用开发的需要，在进行数据库选型时主要考虑以下因素：对平台的支持、管理海量数据、并发处理、并行处理、支持分区表和分区索引等等。（3）操作系统选择原则：操作系统选择重点从系统安全性好，系统运行稳定，系统运行效率高，系统支持及维护成本低廉几方面考虑。（4）应用服务器选择：平台支持：应用服务器支持的操作系统和机型的种类和数量直接影响其应用范围。WebService支持：应用服务器应支持与各种Web服务器无逢的集成，稳定的协作，扩展其支持web应用的能力。安全代理支持：应用服务器应用能够支持第三方的安全代理产品。配置信息数据库的支持：如果支持当前主流的关系数据库，则可充分利用数据库的优化能力来安全有效的利用用户的配置信息。集成开发工具： 应提供全面的智能化配套开发工具和各类组件。管理工具：优秀的应用服务器应提供多种管理方式及友好的图形界面管理工具，并提供API编程接口供用户可以编写自己控制程序，方便的操作配置文件。应用服务器专有特性：应用服务器产品有其自己产品独特的优化设计，在具体的应用环境中可保证应用的高效性，安全性等。最后再综合考虑用户的使用习惯、普遍计算机操作能力，及因此影响的系统长期TCO成本，最后确定选型结论。（5）操作系统选择系统的业务服务器操作系统推荐使用Microsoft Windows Server 2003 Enterprise x32 Edition中文版。Windows 2003 Server执行效率高、安全性高、系统稳定，和数据库结合紧密，为多用户环境和Web系统提供了强大的优化支持。而且Windows系统的用户接受程度较好，操作简易，可以大大降低服务器维护的费用。数据库服务器操作系统推荐使用Microsoft Windows Server 2003 Enterprise x64 Edition中文版。能够保证发挥硬件作用，执行效率高、安全性高、系统稳定，和数据库结合紧密，为多用客户环境和Web系统提供了强大的优化支持。并且Windows系统的用户接受程度较好，操作简易，TCO成本较低。（6）数据库选择根据选型原则，数据库需要考虑以下方面：平台支持：对多种平台的支持能大大扩展数据库的应用范围。管理海量数据：管理海量数据需要大量的工作，也是对数据库性能的挑战。并发处理：OLTP系统的大量并发用户会加重任何计算机系统的负荷，甚至使系统瘫痪。因此DBMS应安全管理大量并发用户对同一资源的操作，有效均衡计算机资源，使大量并发用户可以快速的进行工作。并行处理：支持各种不同的多处理器计算机体系结构，如共享内存、共享磁盘以及不共享的多处理器配置。对并行处理的支持能充分利用多处理器计算机系统的并行处理和高可用性能力。安全性：保证合法用户合法的使用分配其资源；提供各种保护数据库信息措施，可恢复从简单的电源故障到灾难性的场地损毁引起的信息丢失。开放性：在异构的数据库环境中,支持标准化查询多种数据源,甚至可统一访问调用各数据库存储过程和外部过程。对多种操作系统、机型的支持决定了数据库的应用范围。能满足不同企业环境的需要。对XML支持：我们网络技术基于Web Service，要求数据库对XML标准有很好的支持。丰富好用的工具：提供性能调试工具，网络管理工具，开发工具，备份与恢复工具，发布工具，名字服务工具，DBMS管理工具等可高效方便运用数据库。依据以上考虑，我们决定系统选择Microsoft公司的SQL SERVER数据库系统。SQL SERVER数据库系统是Microsoft公司的拳头数据库产品，是世界上知名的大型数据库之一，也是一种最主流的关系型数据库。SQL Server 数据平台是一个全面的、集成的、端到端的数据解决方案，它为组织中的用户提供了一个更安全可靠和更高效的平台用于企业数据和 BI 应用。SQL Server数据库引擎为关系型数据和结构化数据提供了更安全可靠的存储功能，使得可以构建和管理用于业务的高可用和高性能的数据应用程序。SQL SERVER获得Microsoft公司的全面技术支持，足以解决目前绝大多数的大型企业应用。同时由于 SQL Server 是 Windows Server System 的一部分，通过 Windows Server System 产品中实现的通用工程策略可增强管理性和集成性，从而降低总拥有成本，加快开发速度，为客户提供更多额外收益，能够有效降低TCO（总体拥有成本）。数据库选择Microsoft SQL Server 2005 x64（SP2）中文标准版。SQL Server DBMS技术成熟，性能稳定，和Windows系统结构紧密，能够有效降低TCO。其应用程度和数据承载量足以满足资金系统目前和将来的应用。（7）开发平台选择基于操作系统选择Microsoft Windows，数据库系统选择Microsoft SQL Server，在此平台上最适合的企业级开发平台是Microsoft .Net Framework。.NET开发平台是Microsoft公司首推的开发平台，技术先进稳定，与Windows平台、SQL Server数据库结合紧密，效率高。在企业级应用（性能、安全、多层）方面具有完整成熟的解决方案，非常适合开发网络应用。采用Microsoft Visual Studio 2008 IDE 进行基于.NET3.5的开发，符合本系统开发技术规格要求。系统接口设计系统通过接口与多个子系统相互通讯。接口是基于通用的WebService方式来设计的，并使用通用的XML作为与系统之间交换数据的标准。允许异构系统通过WebService访问共享信息。
1. Design Guidelines This project adopts the Model-View-Controller (MVC) pattern for development and design. We separate each layer to achieve low coupling between layers, thereby improving program flexibility and reducing maintenance costs. Data structures and services are developed using a model-driven approach. 2. System Design Specifications 2.1 Overall Functional Structure Design 2.2 Principles of Functional Module Division The division of system functional modules follows the principles of loose coupling and easy extensibility. Each functional module is highly encapsulated, and information transmission between modules is completely achieved through interfaces. Modules build a compact and solid system structure via interfaces, so that a single functional module will not affect the normal operation of the entire system, achieving the goal of loose coupling. New functional modules can be easily hooked up through existing module interfaces, achieving the "plug-and-play" effect, which realizes the system's easy extensibility. 2.3 System Physical Structure Design Logical business manages and monitors the execution of assessment tasks by calling basic data, while external systems access data through system service interfaces. System functions are strictly implemented in accordance with user permissions. 2.4 Network Topology Network Topology and Hardware Planning: The system mainly relies on assessors to conduct on-site actual assessments, and reports the assessment status of the assessment area/point to the platform at specified times via walkie-talkie devices. To ensure data security, the system is deployed in the computer center machine room of the Sanitation Bureau. The server is isolated from the Internet, and a firewall is used for security isolation. The system access adopts a strict permission system to safeguard network data security. 2.5 Software Hierarchical Structure 3. Software Function Design 3.1 System Management (1) User Management Manage the basic account information of system administrators, including adding, modifying, deleting, querying and statistics, and clarify the user's usage scope. (2) Role Management A role is a collection of permissions for system use. According to the characteristics of system users, different roles can be assigned respectively, so that users can conveniently inherit all permissions of the role. (3) Permission Management Manage permission information of all business modules involved in the system, including permission codes, related URLs, permission levels, permission types, etc. (4) Data Dictionary Management Define commonly used system data, including basic information such as their meanings, standard values, standard ranges and data variables. (5) Database Management View the real-time status of the database, including database capacity and data volume, and perform operations such as database backup and restoration. (6) Work Area Management According to the division of responsibilities, include work task plans into the system management for convenient query and browsing. 3.2 Work Object Management (1) Monitor Maintenance Maintain the basic information of monitors, including adding/deleting monitors and maintaining their basic information such as name, gender, landline phone number, mobile phone number, etc. Monitors can timely assess and score the responsibility areas of sanitation companies through the system, and the assessment rules and scores are determined according to specific regulations. At the same time, the system will divide the responsibility monitoring areas for monitors, and adopt real-time GPS positioning and walkie-talkie communication to conduct regular attendance supervision on monitors. (2) Sanitation Companies Maintain the basic information of sanitation companies, including adding/deleting sanitation companies and maintaining their basic information such as company name, abbreviation, address, contact number, person in charge, etc. Users can view the assessment scores of each sanitation company in real time, provide different prompts according to levels (such as red, yellow, green colors), and query and statistics the historical scores of sanitation companies. Sanitation companies can query and statistics their own regional assessment scores at any time. (3) Sanitation Vehicles Maintain the basic information of sanitation vehicles, including adding/deleting sanitation vehicles and maintaining their basic information such as vehicle type, model, license plate number, driver, leasing company, etc. (4) Trash Receptacles Maintain the basic information of trash receptacles, including adding/deleting trash receptacles and maintaining their basic information such as receptacle ID, road name, management unit (each sanitation branch and office), manager name, installation time, type (stainless steel, environmental protection, etc.), installation status (pre-installed, installed). Fuzzy query is supported. The position of trash receptacles can be located on the map, and basic information such as receptacle ID, type, management unit and status can be displayed. The usage status of trash receptacles can be queried and statistics, and reports can be exported. (5) Garbage Bins Implement garbage bin search function: Users can search for garbage bins based on bin ID, road name, management unit (each sanitation branch and office), manager name, installation time, type (buried garbage bin, vertical garbage bin, etc.), installation status (pre-installed, installed). Fuzzy query is supported. The search results can be displayed on the map, and can also display the detailed information and statistical quantity of garbage bins in tabular form. Implement garbage bin map positioning function: The map can display icons and IDs of single or multiple garbage bins based on user's search results. When the user clicks the garbage bin icon on the map, the bin ID, picture, type, location, management unit, manager name, manager contact information and installation time should be displayed. Implement garbage bin information add, delete, modify functions: Users can batch add, delete, modify garbage bin information, and display the results after adding, deleting, modifying garbage bin information before submitting to the database, remind users to check for errors, prompt whether to send messages to notify other users, and finally submit after user confirmation. Implement pre-installed garbage bin function: When displaying garbage bins in two different statuses (pre-installed, installed) on the map, different colors or icons can be used to distinguish them. After the pre-installed garbage bin is installed, users can modify the bin status to installed. Implement garbage bin removal function: Considering that garbage bins may be removed due to damage or replaced with new ones in the future, users can change the garbage bin status to removed or decommissioned. (6) Public Toilets Implement public toilet search function: Users can search for public toilets based on toilet name, road name, management unit (company), manager name, manager contact information, put into use time, construction status (completed, pre-construction, under construction), type (first-class public toilet, third-class public toilet). Fuzzy query is supported. The search results can be displayed on the map, and can also display the detailed information and statistical quantity of public toilets in tabular form. Implement public toilet map positioning function: The map can display icons and names of single or multiple public toilets based on user's search results. When the user clicks the public toilet icon on the map, the toilet name, picture, type, location, manager name, manager contact information, put into use time (pre-construction and under construction toilets show pre-construction time), remarks should be displayed. Implement public toilet information add, delete, modify functions: Users can batch add, delete, modify public toilet information, and display the results after adding, deleting, modifying public toilet information before submitting to the database, remind users to check for errors, prompt whether to send messages to notify other users, and finally submit after user confirmation. Implement pre-construction public toilet management function: When displaying public toilets in three different statuses (pre-construction, under construction, completed) on the map, different colors or icons can be used to distinguish them. After the pre-construction public toilet starts construction, users can modify the status to under construction. After the under construction public toilet is put into use, users can modify the status to completed. (7) Transfer Stations Implement transfer station search function: Users can search for transfer stations based on station name, road name, management unit (sanitation company), manager name, manager contact information, put into use time, construction status (completed, pre-construction, under construction), type (original construction, reconstruction). Fuzzy query is supported. The search results can be displayed on the map, and can also display the detailed information and statistical quantity of transfer stations in tabular form. Implement transfer station map positioning function: The map can display icons and names of single or multiple transfer stations based on user's search results. When the user clicks the transfer station icon on the map, the station name, picture, type, location, manager name, manager contact information, put into use time (pre-construction and under construction transfer stations show pre-construction time), remarks should be displayed. Implement transfer station information add, delete, modify functions: Users can batch add, delete, modify transfer station information, and display the results after adding, deleting, modifying transfer station information before submitting to the database, remind users to check for errors, prompt whether to send messages to notify other users, and finally submit after user confirmation. Implement pre-construction transfer station management function: When displaying transfer stations in three different statuses (pre-construction, under construction, completed) on the map, different colors or icons can be used to distinguish them. After the pre-construction transfer station starts construction, users can modify the status to under construction. After the under construction transfer station is put into use, users can modify the status to completed. 3.3 Map Management (1) Area Management Maintain the jurisdiction areas, and directly mark map areas on the map and bind responsible objects. (2) Work Point Management Manage and maintain the work points in the jurisdiction, and directly mark work points on the map and bind responsible objects. 3.4 System Selection 3.4.1 Selection Principles (1) Software Development Environment Selection Principles Meet the technical parameters and product requirements proposed by users; adopt mature and stable technologies and standard support environments/products with high-quality after-sales service and subsequent upgrade quality; adopt interface-standardized and highly extensible structural designs to meet the performance and technical requirements of specific products; the software development platform should provide comparative optimization options and have experience in developing and applying such software. (2) Database Selection Principles Combined with the actual situation of system scale, deployment, etc., and the needs of application development, the following factors are mainly considered when selecting a database: platform support, management of massive data, concurrent processing, parallel processing, support for partitioned tables and partitioned indexes, etc. (3) Operating System Selection Principles The selection of operating system mainly focuses on the following aspects: good system security, stable system operation, high system operating efficiency, and low system support and maintenance costs. (4) Application Server Selection Platform Support: The types and quantities of operating systems and models supported by the application server directly affect its application scope. Web Service Support: The application server should support seamless integration with various Web servers, achieve stable collaboration, and expand its ability to support Web applications. Security Proxy Support: The application server should support third-party security proxy products. Configuration Information Database Support: If it supports current mainstream relational databases, it can make full use of the optimization capabilities of the database to safely and effectively utilize user configuration information. Integrated Development Tools: It should provide comprehensive intelligent supporting development tools and various components. Management Tools: An excellent application server should provide multiple management methods and friendly graphical interface management tools, and provide API programming interfaces for users to write their own control procedures and conveniently operate configuration files. Exclusive Features of Application Server: The application server product has its own unique optimized design, which can ensure the efficiency and security of applications in specific application environments. Finally, comprehensively consider users' usage habits, general computer operation capabilities, and the long-term TCO (Total Cost of Ownership) of the system affected by these factors, and then determine the selection conclusion. (5) Operating System Selection The operating system for the system's business server is recommended to use the Chinese version of Microsoft Windows Server 2003 Enterprise x32 Edition. Windows 2003 Server has high execution efficiency, high security, stable system, and is closely integrated with the database, providing powerful optimization support for multi-user environments and Web systems. Moreover, Windows system has good user acceptance and is easy to operate, which can greatly reduce server maintenance costs. The operating system for the database server is recommended to use the Chinese version of Microsoft Windows Server 2003 Enterprise x64 Edition. It can ensure the full play of hardware functions, has high execution efficiency, high security, stable system, and is closely integrated with the database, providing powerful optimization support for multi-user environments and Web systems. In addition, Windows system has good user acceptance, is easy to operate, and has low TCO. (6) Database Selection According to the selection principles, the database needs to consider the following aspects: Platform Support: Support for multiple platforms can greatly expand the application scope of the database. Management of Massive Data: Managing massive data requires a lot of work and is also a challenge to database performance. Concurrent Processing: A large number of concurrent users in OLTP (Online Transaction Processing) systems will increase the load on any computer system, even causing the system to crash. Therefore, the DBMS should safely manage the operations of a large number of concurrent users on the same resource, effectively balance computer resources, and allow a large number of concurrent users to work quickly. Parallel Processing: Support various different multi-processor computer architectures, such as shared memory, shared disk and non-shared multi-processor configurations. Support for parallel processing can make full use of the parallel processing and high availability capabilities of multi-processor computer systems. Security: Ensure that legitimate users legally use their allocated resources; provide various measures to protect database information, and can recover information lost from simple power failures to catastrophic site damage. Openness: In heterogeneous database environments, support standardized queries of multiple data sources, and even uniformly access and call database stored procedures and external procedures. Support for multiple operating systems and models determines the application scope of the database, which can meet the needs of different enterprise environments. XML Support: Our network technology is based on Web Service, which requires the database to have good support for XML standards. Rich and Useful Tools: Provide performance debugging tools, network management tools, development tools, backup and recovery tools, release tools, name service tools, DBMS management tools, etc., to efficiently and conveniently use the database. Based on the above considerations, we decide to select the SQL Server database system from Microsoft Corporation. SQL Server database system is Microsoft's flagship database product, one of the world's well-known large-scale databases, and also one of the most mainstream relational databases. The SQL Server data platform is a comprehensive, integrated, end-to-end data solution, which provides users in organizations with a more secure, reliable and efficient platform for enterprise data and BI (Business Intelligence) applications. The SQL Server database engine provides more secure and reliable storage functions for relational data and structured data, enabling the construction and management of high-availability and high-performance data application programs for business. SQL Server obtains comprehensive technical support from Microsoft, which is sufficient to solve most current large-scale enterprise applications. At the same time, since SQL Server is part of the Windows Server System, the general engineering strategies implemented in the Windows Server System products can enhance manageability and integration, thereby reducing total cost of ownership, speeding up development, providing more additional benefits for customers, and effectively reducing TCO (Total Cost of Ownership). The database selected is Microsoft SQL Server 2005 x64 (SP2) Chinese Standard Edition. SQL Server DBMS has mature technology, stable performance, and is closely integrated with the Windows system structure, which can effectively reduce TCO. Its application scope and data carrying capacity are sufficient to meet the current and future applications of the capital system. (7) Development Platform Selection Based on the selection of Microsoft Windows as the operating system and Microsoft SQL Server as the database system, the most suitable enterprise-level development platform on this platform is Microsoft .NET Framework. The .NET development platform is the first-launched development platform of Microsoft, with advanced and stable technology, closely integrated with the Windows platform and SQL Server database, and has high efficiency. It has complete and mature solutions for enterprise-level applications (performance, security, multi-tier), and is very suitable for developing Web applications. Microsoft Visual Studio 2008 IDE is used for development based on .NET 3.5, which meets the technical specifications of this system development. System Interface Design The system communicates with multiple subsystems through interfaces. The interfaces are designed based on general Web Service, and uses universal XML as the standard for data exchange between systems. Heterogeneous systems are allowed to access shared information through Web Service.
