A method to Formalise the Rapid Prototyping Process

Facing the increasing complexity of the product design area, (reduction of cycle times, introduction of simultaneous engineering, introduction of digital mock-up, ... ) a research department which wants to define a rapid prototyping process is confronted to the problem of the tools’ choice. Therefore, we will propose in this article, a method allowing to conceive such a process. In a first chapter, we present the rapid prototyping area in the product design environment, in a second chapter we will propose our method illustrated by an industrial case

Validation of the Parlay API through prototyping

The desire within the telecommunications world for new and faster business growth has been a major drive towards the development of open network API. Over the past 7 years several (semi) standardization groups have announced work on network API, including TINA-C, JAIN, IEEE P1520, INforum, 3GPP, JAIN, Parlay. The Parlay group seems most successful in attracting industry awareness with their API, called the Parlay API. The rational behind the Parlay API is that it attracts innovation from third parties that are outside the network operator's domain to build and deploy new network-hosted applications. This also means that the public telecommunication network is opened for niche and short-lived applications as well as for applications that possibly integrate telephones with other terminals such as PC. The Parlay group has successfully passed the first two phases of success, namely publishing their API on the right moment in time and attracting a critical mass within the telecommunication industry with their results. Prototyping the API on a real network execution platform is the only way to show its technical feasibility. Such an exercise was executed internally within Lucent Technologies and raised a number of questions as well as recommendations on both the technical and the semantical behavior for systems that will be interconnected via the Parlay API. We share these results, showing the drawbacks and advantages as well as challenges for this AP

Tools and technologies for expert systems: A human factors perspective

It is widely recognized that technologies based on artificial intelligence (AI), especially expert systems, can make significant contributions to the productivity and effectiveness of operations of information and knowledge intensive organizations such as NASA. At the same time, these being relatively new technologies, there is the problem of transfering technology to key personnel of such organizations. The problems of examining the potential of expert systems and of technology transfer is addressed in the context of human factors applications. One of the topics of interest was the investigation of the potential use of expert system building tools, particularly NEXPERT as a technology transfer medium. Two basic conclusions were reached in this regard. First, NEXPERT is an excellent tool for rapid prototyping of experimental expert systems, but not ideal as a delivery vehicle. Therefore, it is not a substitute for general purpose system implementation languages such a LISP or C. This assertion probably holds for nearly all such tools on the market today. Second, an effective technology transfer mechanism is to formulate and implement expert systems for problems which members of the organization in question can relate to. For this purpose, the LIghting EnGineering Expert (LIEGE) was implemented using NEXPERT as the tool for technology transfer and to illustrate the value of expert systems to the activities of the Man-System Division

Internet Predictions

More than a dozen leading experts give their opinions on where the Internet is headed and where it will be in the next decade in terms of technology, policy, and applications. They cover topics ranging from the Internet of Things to climate change to the digital storage of the future. A summary of the articles is available in the Web extras section

A method to Formalise the Rapid Prototyping Process

Facing the increasing complexity of the product design area, (reduction of cycle times, introduction of simultaneous engineering, introduction of digital mock-up, ... ) a research department which wants to define a rapid prototyping process is confronted to the problem of the tools’ choice. Therefore, we will propose in this article, a method allowing to conceive such a process. In a first chapter, we present the rapid prototyping area in the product design environment, in a second chapter we will propose our method illustrated by an industrial case

An overview of very high level software design methods

Very High Level design methods emphasize automatic transfer of requirements to formal design specifications, and/or may concentrate on automatic transformation of formal design specifications that include some semantic information of the system into machine executable form. Very high level design methods range from general domain independent methods to approaches implementable for specific applications or domains. Applying AI techniques, abstract programming methods, domain heuristics, software engineering tools, library-based programming and other methods different approaches for higher level software design are being developed. Though one finds that a given approach does not always fall exactly in any specific class, this paper provides a classification for very high level design methods including examples for each class. These methods are analyzed and compared based on their basic approaches, strengths and feasibility for future expansion toward automatic development of software systems