articles+ search results

Iterative and incremental development, Supervisory control, Computer science, business.industry, Event (computing), Usability, User interface, Software engineering, business, Engineering design process, Automation, and Design paradigm

Usability testing is a critical step in the process of agile iterative development. Static and lower-fidelity user-interface mock-ups can suffice during early phases of design or for user-paced environments, but higher-fidelity test beds are required to evaluate event-paced environments especially those exploring the supervisory control of automation. Increased fidelity is desirable as early as possible during the design process to explore the supervisory control design paradigm and generate more numerous and higher-quality user feedback. Complex AI-based systems are more difficult to test during early development phases. Static and low-fidelity prototypes typically cannot adequately represent the complex automation behaviors making usability more difficult to measure. A high fidelity user-interface prototyping approach was employed to simulate the capabilities of pending algorithms that are under development by multiple laboratories for a future intelligent air-defense system. The prototyping tool supported usability data collection by simulating the proposed automation and an initial supervisory control user-interface design within dynamic, group, air defense scenarios. This approach yielded high-quality user feedback early in the system design process even while being subjected to the constraints imposed by remote testing requirements due to COVID-19.

Compatibility testing, Computer science, business.industry, Compatibility (mechanics), Web application, Graphical user interface testing, Web content, business, Web application development, Software engineering, Automation, and Field (computer science)

The main purpose of this paper is to introduce the application area of GUI test automation to researchers in the document analysis and recognition (DAR) field. Continuous integration (CI) represents the main stream in the field of web application development and reducing the burden of testing has become an important issue. In particular, GUI testing relies on human labor in many cases and test automation in this area is the least advanced. Because web content is essentially a type of “document,” DAR technology is useful for promoting automation in this field. However, there have been few presentations on testing technology at conferences in the DAR field. This may be because researchers in the DAR field do not know much about which types of technologies are required in the field of software testing. We developed X-BROT, which is a tool for automatically determining the compatibility of web applications, and attempted to automate GUI testing. X-BROT can detect degradation by comparing the behaviors of web applications between versions under development. Compatibility verification between web documents is realized using DAR technology. X-BROT has shown nearly 100% accuracy for detecting differences between browsers [1] and it seems to be sufficient for automating testing, but many issues have been pointed out in the field of web application development. This paper describes this feedback and discusses new features that have been developed in response, as well as cases where DAR technology is required for GUI test automation.

Computer science, business.industry, Truth table, Adept, computer.software_genre, Automation, Visualization, Subject-matter expert, Computer architecture, Rich client platform, Plug-in, User interface, Software engineering, business, and computer

Automation Design and Evaluation Prototyping Toolset (ADEPT) is a plugin developed on the Eclipse Rich Client Platform(RCP). ADEPT can be used by domain expert designers to create and modify testable prototypes. The aim of the project is to enhance ADEPT by adding dynamic visualizations to the ADEPT user interface. Three types of visualizations are implemented in this project. Table view is helpful to view the hierarchy and nesting of Logic Tables. The State visualization displays all the states in a selected Logic Table. Entropy visualization is a subset of State visualization and displays limited number of states having lowest Entropy value.

History, Teamwork, Computer science, business.industry, Process (engineering), media_common.quotation_subject, Automation, Computer Science Applications, Education, Debugging, Software design, Software engineering, business, and media_common

The evolution of programming began at a time when most programs were developed by a single developer. As the complexity of the programs increased, the complexity of their development, debugging and the number of participants in the process also increased, which led to the development of automation systems for programming and organization of teamwork, and later to the development of tools and methods for software design (CASE-tools).

business.industry, Event (computing), Computer science, Software prototyping, computer.file_format, Automation, Software, Test case, Embedded system, Executable, Software engineering, business, Computer-aided software engineering, Reactive system, and computer

The article of record as published may be found at http://dx.doi.org/10.1109/RSP.2005.49 This paper addresses the need for automatic generation of executable environment models to facilitate the testing of real-time reactive systems under development (SUD) in rapid system prototyping. We present an approach that allows users to model the environment in which the SUD will operate in the terms of attributed event grammar (AEG). The AEG provides a uniform approach for automatically generating, executing, and analyzing tests. The approach is supported by a generator that creates test cases from the AEG models. We demonstrate the effectiveness of the proposed approach with using as a case study a prototype of the safety-critical computer-assisted resuscitation algorithm (CARA) software for a casualty intravenous fluid infusion pump. U.S. Missile Defense Agency.

business.industry, Computer science, Domain model, Integrated circuit, Automation, Domain (software engineering), law.invention, Software, law, Scalability, Systems engineering, Electronic design automation, Physical design, Legacy code, Software engineering, business, Field-programmable gate array, and Software evolution

The current integrated circuit technologies are approaching their physical limits in terms of scaling and power consumption, in this context, the electronic design automation EDA industry is pushed towards solving ever more challenging problems in terms of performance, scalability and adaptability. Meeting these constraints needs innovation at both the algorithmic and the methodological level. Amongst academic EDA tools, Madeo toolkit has been targeting field-programmable gate array FPGA design-automation at the logic and the physical level since the late 1990s. As many other long-living software, despite embedding valuable legacy, Madeo exhibits unwanted characteristics that penalize evolution and render the automation problems even more difficult. This study presents a methodological approach to physical-design automation relying on model-driven engineering, which is illustrated through the incremental redesign of the Madeo framework. A benefit of this approach is the emergence of a common vocabulary to describe the EDA domain in an FPGA scope. A second advantage is the isolation of the optimization algorithms from the structural domain models. However, the main asset is the possibility to re-inject into the newly designed toolkit most of the legacy code. The redesigned framework is compared with and scored against initial code-base, and demonstrates a regression-free remodeling of the environment with net improvements in terms of size and complexity metrics. As a consequence, the evolution capability is back on stage, and the domain-space exploration widens to the algorithmic axis. Copyright © 2013 John Wiley & Sons, Ltd.

Rapid prototyping, business.industry, Computer science, Software development, Automation, Software development process, Formal specification, Software construction, Software requirements, business, Software engineering, Requirements analysis, Simulation, and Software evolution

Rapid prototyping is a promising approach for formulating accurate software requirements, particularly for complex systems with hard real-time constraints. Computer aid is needed for realizing the potential benefits of this approach in practice, because the problems associated with software evolution arce greatly amplified in the context of iterative prototyping and exploratory design. Our computer-aided prototyping system CAPS provides automated support for many aspects of requirements analysis and software prototyping, including: (I) maintaining logical dependencies between assmnptions about needs of different groups, software requirements, and design decisions, (2) managing designn history, alternatives and dependencies, (3) planning, assigning and scheduling job assigments for teams of designers in the presence of uncertainty, (4) checking and propagating design constraints, (5) maintaining consistency between graphical and text views of a design, (G) constructing real-time schedules, (7) generating control code, and (8) retrieving and instantiating reusable software components. The principles and methods that make this possible and the practical application of the system are explained via examples.

Workflow, Traceability, Pluralistic walkthrough, Computer science, business.industry, Visibility (geometry), Tracking (particle physics), Software engineering, business, and Automation

As you saw in Chapter 2 there is more to ALM than the three pillars (Traceability, Visibility, and Automation) of high-level processes. You also saw that the following four topics are important: Collaboration Workflow Security Reporting and analysis

Iterative and incremental development, Iterative design, Computer Networks and Communications, business.industry, Programming language, Computer science, Process (engineering), Software development, computer.file_format, computer.software_genre, Computer Graphics and Computer-Aided Design, Automation, Artificial Intelligence, Software system, Executable, business, Software engineering, Requirements analysis, computer, and Software

Prototyping languages form a new category in the computer language family. They are different from the commonly familiar computer languages because they are used to support a higher level of automation at early phases of software development as well as throughout the entire process. They are used to create mechanically processable and executable descriptions or models of proposed software systems. Prototyping languages are also used to firm up requirements via frequent modifications and demonstrations of the models in an iterative process of prototype evolution. The benefits of a prototyping language are fully realized when it is used with its computer-aided prototyping system (CAPS). In this paper, we describe the background, requirements, characteristics, computational features, and general principles for the design of prototyping languages. An example of a prototyping language design is used to illustrate these concepts.

Engineering, Object-oriented programming, Engineering drawing, business.industry, General Engineering, Feature recognition, Automation, Feature model, Prolog, Feature (computer vision), Islands of automation, Software engineering, business, computer, Logic programming, and computer.programming_language

In recent years, there have been tremendous amount of interest in manufacturing automation and Computer-integrated Manufacturing (CIM). To attain a high level of automation in CIM, there has been relentless effort in trying to integrate the islands of automation in manufacturing. These are often fraught with much frustrations and difficulties. The main clamity in integration is due to the mismatch of information available from the CAD system and that required by CAPP system. The geometric information generated by the solid modellers in most CAD systems are low level whilst the CAPPs will operate efficiently only at a higher level of abstraction. CAPP systems thrives on feature information but such information in CAD databases are rather implicit and at times not even available. Although there has been much research and development work in making these feature information in CAD databases more explicit through feature recognition and extraction, this is really a regressive step. A much better approach is to define features as they exist right at the start at the modelling stage and store these feature definitions in a feature database which can be assessed directly by CAPP. In this way the likelihood of making errors in interpretation is minimized as the feature information are derived at source. This paper describes the prototyping of a feature-based modelling system in an AI logic language, Prolog. Feature hierarchy depicting the part-feature relationships can be defined by the designer when he is making the design of the part. By defining features as objects and through object oriented programming, generic and specialized feature properties can be defined or inherited through a child/parent relationship. These constituent features are composed semantically and meaningfully through a bottom-up strategy based on feature composition rules and feature primitives. The result of the parsing exercise is a solid representation of the global model depicted as a CSG tree of features. This solid model will ultimately be translated into solid modeller specific commands and further evaluated to give active boundaries representing geometric and topological information for rendering.

Modeling and simulation, General Computer Science, business.industry, Robustness (computer science), Computer science, Robotics, Artificial intelligence, Software engineering, business, and Automation

Electronic prototyping, i.e. building a computer model of an object to verify its design, faces a number of obstacles. The Cornell modeling and simulation project, which was created to develop the necessary science base to overcome these barriers, is discussed. In particular, the project's progress in improving robustness of solid modelers and its ongoing research in electronic prototyping are examined. A key component of the project, a model-driven simulator capable of supporting a wide range of multidisciplinary research, is described. >