基于PHP的网上书店的设计与实现

随着计算机网络技术的飞速发展,电子商务模式越加成熟,以网上书店为代表的网上购物系统极大的方便了人们的购物生活。本文主要介绍了基于PHP和MySQL的网上书店的设计与实现,对系统的研究背景及意义进行分析,按照软件工程的方法,对系统进行需求分析、概要设计、详细设计、编码与测试,提出对系统的观点与前景展望,将PHP和MySQL的有关理论知识应用到系统实现的过程中,完成网上书店平台的构建,对于建立中小型的电子商务网站具有一定程度的借鉴意义。     

一站式网上行政审批系统的设计与实现

文章设计了一个一站式网上行政审批系统。本文首先阐述系统的建设目标,接着对系统的总体结构进行了分析,最后对系统的各个业务功能进行了详细的研究和设计。     

在线书店系统——模块设计

为了跟上国际电子商务的发展潮流,我们应该积极地了解电子商务、参与电子商务,尽快适应飞速发展的信息社会的需要。该文从理论和实践两方面出发,对电子商务进行了全面的探讨。论文研究了电子商务的系统框架结构和它的系统组成。接着就构建一个B-to-C电子商务应用系统——网上书店,按照软件工程的要求,对系统进行需求分析,总体设计,详细设计,编码与测试,在此基础上将理论知识与开发技术运用到系统的实现过程当中,完成了网上书店平台的构建。     

办公自动化中公文流转系统的研究与设计

本文阐述了一个基于B／S模式的公文流转系统的研究与设计,并对系统的框架、设计及安全做了介绍。公文流转系统作为网上办公系统的一个核心模块,关系到整个网络办公的使用与发展。     

基于ASP.NET的网上报名系统的设计与实现

网上报名系统的应用改变了现场集中报名模式,提升了工作效率,为考生报名提供了方便,实现了报名工作的规范化和信息化要求。文章针对考生报名的实际需求,设计并实现了基于ASP.NET的网上报名系统,并对系统的功能模块、数据库设计和关键技术做了分析和介绍。     

基于PDM的网上销售管理通用模型的研究

文章提出了一种用于网上销售管理的通用模型,建立模型的体系结构,描述该模型框架下销售管理的实施流程.该模型与产品数据管理(PDM)系统紧密集成,通过PDM系统与销售管理模型的数据共享和过程集成,实现双向数据交换,有效保证销售数据与设计数据的一致性和数据交换的实时性.以网上销售管理通用模型为基础,构建WIT_SMSW网上销售管理系统,对系统实现、关键技术进行描述,实现客户对企业产品的网上个性化定购.     

基于ASP网上人才管理系统的设计与实现

利用ASP（Active Server Pages）,结合Front Page和SQL Server数据库,开发了一个网上人才管理系统。首先介绍了系统的主要功能及各个模块的相互关系,对系统数据库结构的设计与实现进行了具体描述,最后对系统的开发难点和设计技巧进行了分析．     

基于WEB的网上直报系统的设计与实现

分析了网上信息报送的特点,介绍了基于Web的网上直报系统的设计与实现,同时对系统的开发模式、框架、功能模块和主要的关键技术进行了研究.     

基于Proteus的汽车空调控制系统的设计与仿真

介绍了利用Atmegal6单片机、Proteus仿真软件开发的汽车空调自动控制系统。利用Atmegal6单片机构建了一个智能型汽车空调控制系统,并对系统的液晶模块、热电阻温度采集、液晶模块显示、继电器控制、键盘输入、风向步进电机控制器进行了设计,用Proteus软件对系统进行仿真。结果表明该系统具有电路结构简单、分立元件少、系统界面友好、操作简单等优点,能满足一般要求的汽车空调的自动控制。     

技术市场网络信息平台系统设计

在分析技术市场运行机制厦其相关功能需求的基础上，确定了技术市场网络信息平台的开发目标，对系统进行功能设计、网络结构设计、安全性设计，为网上技术市场的参与者和管理者搭建一个便于沟通、交易、管理。保障信息的安全和系统稳定的平台，使网上技术市场发挥其最大作用。     

种基于监控理论的软件设计方法：状态性质变换方法

基于把离散事件系统监控理论用于软件设计的思想,本文中对软件设计的状态性质变换方法作了详细的讨论. 给定一个系统,其每一个状态的性质都是确定的. 当提出软件需求时,常常是对系统状态的性质提出需求.为设计出满足需求的系统,可以首先按照是否满足该性质对系统状态进行分类,再对不满足该性质的状态控制其可控事件的发生从而改变其性质使之满足要求的性质.本文将这种方法用于软件需求是不变性或可达性时的软件设计问题,通过和已有文献中结论的比较,显示了这种设计思想的广泛适用性和优点,也验证了软件控制论这一思想的可行性.     

Design of a Remote Procedure Call system for object-oriented distributed programming

This paper describes the design of an RPC system for building object-oriented distributed software systems. The general requirements for such a system are to provide mechanisms for supporting inheritance, polymorphism, dynamic binding, and modular development in implementing distributed software systems. This paper presents the functionalities of this RPC system to support these general requirements. It also briefly describes the experiences with two previous versions of this system and how they led to the design of the final system. This system was implemented as a part of the programming environment of the Nexus distributed operating system. © 1998 John Wiley & Sons, Ltd.     

一种基于监控理论的软件设计方法:状态性质变换方法

基于把离散事件系统监控理论用于软件设计的思想,本文中对软件设计的状态性质变换方法作了详细的讨论,给定一个系统,其每一个状态的性质都是确定的,当提出软件需求时,常常是对系统状态的性质提出需求,为设计出满足需求的系统,可以首先按照是否满足该性质对系统状态进行分类,再对不满足该性质的状态控制其可控事件的发生从而改变其性质使之满足要求的性质。本文将这种方法用于软件需求是不变性或可达性时的软件设计问题,通过和已有文献中结论的比较,显示了这种设计思想的广泛适用性和优点,也验证了软件控制论这一思想的可行性。     

Relating evolving business rules to software design

In order to remain useful, it is important for software to evolve according to the changes in its business environment. Business rules, which can be used to represent both user requirements and conditions to which the system should conform, are considered as the most volatile part in today's software applications. Their changes bring high impact on both the business processes and the software itself. In this paper, we present an approach that considers business rules as an integral part of a software system and its evolution. The approach transcends the areas of requirements specification and software design. We develop the Business Rule Model to capture and specify business rules, and the Link Model to relate business rules to the metamodel level of software design elements. The aim is to improve requirements traceability in software design, as well as minimizing the efforts of software changes due to the changes of business rules. The approach is demonstrated using examples from an industrial application.     

Design traceability

Traceability is about documenting the relationships between layers of information, for instance, between system requirements and software design. Many software development tools manage design relationships, for instance, between modeling elements (such as classes) and source code, or between tasks and source code files. Whatever development scale we engage in, we systematically apply information traceability. It's a vehicle for thinking about the way the software meets its requirements; it captures design rationale to help others understand and review; and it gives us far greater confidence in managing future changes.     

Design of a component-based integrated environmental modeling framework

Integrated environmental modeling (IEM) includes interdependent science-based components that comprise an appropriate software modeling system and are responsible for consuming and producing information as part of the system, but moving information from one component to another (i.e., interoperability) is the responsibility of the IEM software system. We describe and discuss the Framework for Risk Analysis in Multimedia Environmental Systems (FRAMES), a component-based IEM system, from the standpoint of software design requirements which define system functionalities. Design requirements were identified in a series of workshops, attended by IEM practitioners, and reported in the development of a number of IEM software systems. The requirements cover issues associated with standards, component connectivity, linkage protocols, system architecture and functionality, and web-based access, all of which facilitate the creation of plug & play components from stand-alone models through a series of software support tools and standards.     

An intelligent assistant for requirements validation

The process of determining user requirements for software systems is often plagued with uncertainty, ambiguity, and inconsistency. Rapid prototyping offers an iterative approach to requirements engineering that can be used to alleviate some of the problems with communication and understanding. Since the systems development process is characterized by changing requirements and assumptions, involving multiple stakeholders with often differing viewpoints, it is beneficial to capture the justifications for the decisions in the development process in a structured manner. Thisdesign rationale captured during requirements engineering can be used in conjunction with the rapid prototyping process to support various stakeholders involved in systems development. CAPS (the Computer Aided Prototyping System) has been built to help software engineers rapidly construct prototypes of proposed software systems. REMAP (Representation and MAintenance of Process knowledge) provides a conceptual model and mechanisms to represent and reason with (design) rationale knowledge. In this paper, we describe how in the context of evolving requirements, the CAPS system augmented with REMAP helps firm up software requirements through iterative negotiations via examination of executable prototypes and reasoning with design rationale knowledge.     

An Application of Structural Modeling to Software Requirements Analysis and Design

In software development, it has been pointed out that software engineers must pay attention to software requirements definition. One of the important problems in software engineering is to rationalize the processes from requirements definition to design. Computer tools are most useful and efficient for this purpose. This paper proposes a computer-aided software design system (CASDS), which supports software engineers with a series of structural modeling. As is well-known in systems planning, structural modeling helps to extract concepts from many fuzzy requirements. This system contains three structural modeling methods. They are used 1) to determine functional terms from fuzzy software requirements, 2) to obtain modules by structuring the functions with respect to the data flows, and 3) to make a program skeleton by imposing control flows on the functional elements obtained by breaking down the modules.     

Developing a quantitative intelligent system for implementing concurrent engineering design

This research focuses on the development of a quantitative intelligent system for implementing concurrent engineering design. The paper first discusses the task of concurrent engineering design and the basic requirements for conducting integrated concurrent engineering design. The proposed quantitative intelligent system approach combines qualitative reasoning, based upon design and manufacturing knowledge, and quantitative evaluation and optimization, conducted using design information and manufacturing data generated in the knowledge-based reasoning. The method allows considerations on non-operating principle aspects of a product to be incorporated into the design phase, such as manufacturing, maintenance, service, recycle, etc., with an emphasis on production costs. The proposed method serves as a convenient software tool for gathering information required in the concurrent engineering design process and integrates tasks from different parts of the product development life cycle, particularly function design, manufacturability analysis and production cost estimation. A prototype software system is developed based upon this method using Smalltalk-80. In the prototype system, concurrent engineering design is carried out by: (1) describing and representing design requirements; (2) generating feasible design candidates and evaluating their design functions; (3) representing design geometry; (4) finding the associated production processes and predicting the production costs of each feasible design; and (5) identifying the costeffective design that satisfies given design requirements and requires minimum production costs.