采用简化原型法进行需求分析

本文提出一种新的管理信息系统需求分析方法一简化原型法。这种方法采用文档原型和系统简化原型，促进分析人员与用户的交流，利于发现和解决问题。实践证明简化原型法提高了MIS工程的需求分析和设计开发效率，简化了用户培训过程。     

用原型法实现小型网站的需求分析

需求分析是软件项目开发中必需经历的一个阶段,小型网站在开发中因其需求简单,在开发中为了降低成本等原因,需求分析往往得不到重视。使用原型法实现小型网站的需求分析,强化了用户参与系统开发的过程,避免了开发人员和用户之间因沟通的问题而导致的需求误解,提高了软件需求实现的质量。     

应用第四代语言MAPPER开发管理信息系统—快速原型法开发MIS的方…

本文介绍采用第四代语言工具的快速原型法，开发ＭＩＳ的方法。应用第四代语言和快速原型法开发ＭＩＳ的过程分为三个阶段：了解业务流程和收集原始资料、建立原型、生成实用系统。文章以第四代语言ＡＰＰＥＲ背景，讨论了在各个阶段，开发人员和业务人中和工作方法和注意事项。     

原型法在MIS开发中的应用

原型法是开发MIS的一个方法,越来越受到人们重视。本文简略地讨论了原型法的概念、实质及用原型开发MIS的具体步骤。结合开发《粮食调运微机处理系统》,说明原型法的具体应用。     

面向信息服务的界面原型驱动开发模型

面向服务架构(SOA)的开发和管理使信息管理系统可以实现灵活的业务流程,根据SOA的优点提出一种面向信息服务的界面原型驱动开发模型,给出相应的形式化描述。基于该模型,结合信息管理项目实例,分析如何应用该模型指导项目开发过程,较好地实现从需求分析到有效设计的快速切换。     

快速原型法在GIS中的应用

由于传统方法在开发GIS（Geographical Information System）系统中有一定的局限性，为了寻找一种合适的开发方法，文中从分析GIS的特点和要求人手，阐明了传统开发方法在GIS中的不足，论述了快速原型法在GIS系统开发中的地位与作用，简述了原型法开发模型的思路，结合基于GIS的森林防火系统实例对快速原型法在GIS中的应用进行了分析，提出了一种适合于GIS系统的开发模式。     

基于MATLAB的车用快速控制原型软件平台的研究与实现

通过对现代控制系统设计开发方法中的快速原型技术的分析,研究实现了基于MATLAB的快速控制原型开发软件平台。系统提供了用户透明和面向THECU-2003控制原型硬件平台的快速原型开发、自动代码生成、目标代码下载、在线调试支持和代码管理的快速开发辅助工具。     

在快速原型法中嵌入SSM思想

文中以一个成功地开发了的ＭＩＳ为实例，阐明了在用快速原型法开发ＭＩＳ的过程中嵌入软系统方法论的思想使原型法进一步完善的过程。     

面向对象法、原型法及CASE方法的有机复合在大型MIS开发中的应用研究

通过对以往软件开发方法的研究,结合具体的MIS开发实践,文章给出了一种开发大型MIS的复合方法。即将原型法、面向对象法和CASE方法在MIS开发各阶段有机结合,相互补充,从而达到快速有效地开发MIS系统的目的。     

SCADA系统设计与实现的原型法

文中力求从广义的角度看待原型化方法，论述了ＳＣＡＤＡ系统开发策略及采用增量式原型法开发ＳＣＡＤＡ系统的全过程，阐明了系统快速生成依赖于辅助原型开发工具，并为之设计，创建了一系列用于界面开发的工具集。     

A model-based computer-aided prototyping system

Computer aided prototyping systems which allow application domain experts to compose prototypes using domain specific components, semantics, and primitives can reduce the time and effort needed for prototyping considerably.The notion of domain model is introduced as a vehicle for defining, generating, and categorizing domain specific components. Facilities to compose the components generated from the domain model to implement complex functionality are presented.A rapid prototyping system which provides a domain modeling tool and a visual direct manipulation composition tool is described. The main element of the domain modeling tool is a domain modeling language which provides: (i) a class construct to define object, (ii) rule, trigger, event, and relationship constructs to define interactions among objects, and (iii) process, task, and signal constructs to define the activities in the domain.The composition tool is the extension of a visual tool called IntelligentPad (IP) which supports unified data and control flows through a simple paste and connect metaphor. Domain models are translated to generate components, which are then composed using the extended IP.     

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.     

ProNoC: A low latency network-on-chip based many-core system-on-chip prototyping platform

Network-on-chip (NoC) is an emerging interconnect infrastructure to address the scalability limitation of conventional shared bus architecture for many-core system-on-chip (MCSoC). Current field-programmable gate arrays (FPGAs) have over million lookup tables, making it possible to prototype a complete NoC-based MCSoC on a single FPGA device. FPGA prototyping allows rapid system verification and optimum design parameters estimation. However, existing NoC-based MCSoC prototypes are usually adopting simple NoC architectural functionality. These NoC prototypes cannot represent a realistic projection of the state-of-the-art application-specific integrated circuit (ASIC) NoCs as these prototypes have limited overall system performance. This paper presents ProNoC, an integrated tool for rapid prototyping and validation of NoC-based MCSoC projects targeting FPGA devices. ProNoC adopts most advanced NoC features such as the support of virtual channel (VC), virtual network, low latency routing and different routing algorithms. Results show that NoC interconnect in ProNoC outperforms CONNECT, the most recent VC based prototype NoC with lower logic cell utilization, higher maximum operating frequency, higher average saturation throughput, and lower average communication latency. Moreover, ProNoC is equipped with graphical user interface to facilitate the development of MCSoC prototypes on FPGA platforms.     

SCRAM–CK: applying a collaborative requirements engineering process for designing a web based e-science toolkit

This paper presents SCRAM–CK, a method to elicit requirements by means of strong user involvement supported by prototyping activities. The method integrates two existing approaches, SCRAM and CK theory. SCRAM provides the framework for requirements management, while CK theory provides a framework for reasoning about design and its evolution. The method is demonstrated with the definition and refining of requirements for the BioVeL web toolkit. The objective of BioVeL is to allow scientists to understand, run, modify and construct workflows for data analysis with minimal training using a web-based interface. The proposed method is supported by prototyping activities for gathering user feedback, and refining requirements and design proposals. Using this method, the prototypes evolved from simple workflow execution enablers to include more complex functionalities for reviewing, modifying and building workflows in later versions. This paper presents a contribution to the application of techniques for requirements engineering. SCRAM–CK is an amalgamated method that combines a user-centred continuous refinement approach with support for design evolution through prototyping. The paper also shows the influence of the requirements engineering process in the evolution of design proposals.     

Multipurpose prototypes for assessing user interfaces in pervasive computing systems

In pervasive computing systems, prototypes serve several uses and have different requirements related to those uses. We've developed CogTool to enable low-cost, rapid construction of interactive prototypes that serve all three UI purposes. CogTools core prototyping technique is storyboarding -specifically, interactive storyboarding using HTML. Rather than covering all possible pervasive systems, CogTool focuses on systems involving deliberate commands that the user invokes by some motor action. Such systems include PDAs, cell phones, handheld terminals (such as those used by rental car return personnel), in-vehicle driver information systems, and certain wearable computers that run desktop- or PDA-like applications.     

基于多维数据建模的一体化平台

基于快速原型开发思想,设计并实现了一个一体化的多维数据建模平台,该平台为OLAP应用系统设计人员提供了一个快速构建原型系统的支撑环境,采用图示化的方法描述了用户需求,经过简单的操作,可以演示对应的分析结果,便于用户修正与确认,并为系统设计人员提供了一个导向,加快了系统的开发速度。     

Requirements engineering in health care: the example of chemotherapy planning in paediatric oncology

Health care is characterized by highly complex processes of patient care that require unusual amount of communication between different health care professionals of different institutions. Sub-optimal processes can significantly impact on the patient’s health, increase the consumption of services and resources and in severe cases can lead to the patient death. For these reasons, requirements engineering for the development of information technology in health care is a complex process as well: without constant and rigorous evaluation, the impact of new systems on the quality of care is unknown and it is possible that badly designed systems significantly harm patients. To overcome these limitations, we present and discuss an approach to requirements engineering that we applied for the development of applications for chemotherapy planning in paediatric oncology. Chemotherapy planning in paediatric oncology is complex and time-consuming and errors must be avoided by all means. In the multi-hospital/multi-trial-centre environment of paediatric oncology, it is especially difficult and time-consuming to analyse requirements. Our approach combines a grounded theory approach with evolutionary prototyping based on the constant development and refinement of a generic domain model, in this case a domain model for chemotherapy planning in paediatric oncology. The prototypes were introduced in medical centres and final results show that the developed generic domain model is adequate.     

快速原型虚拟逼真设计原理及体系结构

在分析设计的特点和发展趋势的基础上,提出快速原型虚拟逼真设计,并对其特点和原理进行了讨论,快速原型虚拟逼真设计是面向并行工具,基于虚拟原型和虚拟环境仿真的设计,强调虚拟原型的快速生成和演化,在关键技术,原型系统以及开发环境三个层次上论述了快速原型虚拟逼真设计的研究,提出快速原型虚拟逼真设计模型以及基于该模型的体系结构。     

A Method for Extracting and Stating Software Requirements that a User Interface Prototype Contains

User interface and requirements prototyping is a requirements elicitation technique. A user interface and requirements prototype is built during the requirements engineering phase of a software system development. Along with the user interface prototype are produced various documents such as the system requirement specification. When a prototype and other documents exist, they may not describe the same functionality, particularly because there may be behaviour of the prototype, artefacts of prototyping, that may not be intended. The problem is that in later development stages, when there is a prototype and other documents, it is often difficult to reconcile the difference between the prototype and the other documents. This paper presents an approach for avoiding this difficulty. It demonstrates the approach by showing its application to parts of a real software development.