Showing papers on "Rapid application development published in 1996"
12 Sep 1996
TL;DR: The functionality and defects of the first generation of digital set-top-boxes now available are described, and a definition and description of interactive services on a digital integrated receiver decoder is proposed.
Abstract: This paper describes the development process of interactive services for digital TV. As the term `interactive services' is only recently introduced, it proposes a definition and description. This include all interactive applications on a digital integrated receiver decoder: electronic program guide, impulse-pay-per-view, home shopping, home banking, betting, information services etc. It describes the functionality and defects of the first generation of digital set-top-boxes now available, and proposes new standards for next generation set-top boxes. The paper also highlights the problems that the first group of interactive service developers will encounter in the design and development process. As interactive services for digital TV will be a complete new concept into the living room, it is very hard to predict the consumers behaviour to such application. It is therefore unlikely that `crisp and clear' user requirements will be drawn up for the development team. It might therefore be necessary to apply an `unconventional' project methodology, such as rapid application development or fast prototyping. What this means for the parties involved, and how much can be learned from the early developments in the PC-multimedia industry are discussed.
3 citations
01 Jan 1996
TL;DR: The HANSA Framework is evaluated as a guide for rapid application development in the real-world using the MIMENICE Toolkit and a survey of Object-Oriented Integration Methods shows good results in both the short and long-term.
Abstract: 1. Rapid Application Development and the HANSA Project C. Sharpington, S. Khebbal. Part One: Tools for Rapid Application Development. 2. The HANSA Framework S. Khebbal, J. Lapido. 3. The HANSA Toolkit and the MIMENICE Tool E. LeSaint, S. Khebbal. Part Two: Object-Oriented Integration Methods. 4. Survey of Object-Oriented Integration Methods S. Khebbal, J. Lapido. Part Three: Real-World Applications. 5. Direct Marketing Application C. Sharpington. 6. Banking Application T. Look, M. Kuhn. 7. Bankruptcy Prediction Application K. Feldman, et al. 8. Executive Information Systems Application P. Chatelain, L. Moussy. Part Four: Evaluation and Conclusions. 9. Evaluating the HANSA Framework S. Khebbal, J. Lapido. 10. Conclusions and Future Directions C. Sharpington, S. Khebbal. Appendix A: FTP Site for HANSA Framework. Index.
3 citations
01 Sep 1996
TL;DR: Analysis of quality management in a large scale end-user software development involving object based Rapid Application Development (RAD) tools shows limited applicability of existing codebased metrics in such environments.
Abstract: Worldwide, end-user programmers outnumber software engineering professionals by an increasing margin. Despite this, little is known about the quality management of end-user programming even though it is widely deployed in business critical areas. This paper analyses quality management in a large scale end-user software development involving object based Rapid Application Development (RAD) tools. The limited applicability of existing codebased metrics in such environments is demonstrated. Effective methods adopted in this case study are generalised to propose ways of raising quality in end-user programming and RAD.
3 citations
01 Jan 1996
TL;DR: The Systems Development Life Cycle (SDLC) is usually characterized by phases and deliverables as mentioned in this paper, the actual stages, steps and deliverable of systems development will vary depending on the size of the proposed system, the type of work involved, the approved standards and project management.
Abstract: The Systems Development Life Cycle (SDLC) is usually characterized by phases and deliverables. The actual stages, steps and deliverables of systems development will vary depending on the size of the proposed system, the type of work involved, the approved standards and project management.
1 citations
11 Nov 1996
TL;DR: The critical elements in the development and integration of the ASTER PGS system are described, including a remote integration testing approach that was adopted to provide a rapid convergence of the final integrated system.
Abstract: The advanced spaceborne thermal emission and reflection radiometer (ASTER) is designed to provide a high-resolution map of the Earth in both visible, near-infrared, and thermal spectral regions of the electromagnetic spectrum. The ASTER science team has developed standard data product algorithms to permit the estimation of surface radiances and reflectance values, to calculate surface temperatures both over water and land, to provide a color enhanced product with a high degree of surface discriminability, in addition to other functions. The ASTER product generation system (PGS) team is implementing these requirements within the constraints of the EOSDIS system, using a rapid development methodology that emphasizes open lines of communication in a team approach using concurrent engineering techniques. The PGS development environment was structured both to conform to the changing needs of the EOSDIS system and to incorporate experimentation with and modification of the science algorithms as the software was being developed and tested. This challenging environment required a focus on novel methods of requirements tracking, software interface uniformity, toolkit transparency, and platform independence. This approach required a high degree of interoperability of the software development environment, a well as a flexible and highly integrated configuration management and testing approach. In addition in order to validate the PGS software in the operational environment of the EOSDIS, a remote integration testing approach was adopted to provide a rapid convergence of the final integrated system. This paper describes the critical elements in the development and integration of the ASTER PGS system.
1 citations
01 Jan 1996
TL;DR: Looking at the ER model can evaluate whether the relational database design has been completee or not, and through the use of reverse engineering tools, physical database schemas can be converted into their entity-relationship (ER) model.
Abstract: Relational database management systems (RDBMS) share a high percentage of the database market. Coupled with client application development tools like PowerBuilder,* and data modeling and design tools like ERwin/ERX, rapid application development is made possible. However, due to the ease of use of these client-server tools, there is a tendency for application developers to quick start their application development process without going through a formal process of database design. Through the use of reverse engineering tools, physical database schemas can be converted into their entity-relationship (ER) model. By looking at the ER model we can evaluate whether the relational database design has been completee or not.
1 citations