A TOOL FOR CONSTRUCTING INTERACTIVE SOFTWARE

Author(s):  
W. DAVID HURLEY

The Tailor is a research tool for refining and evaluating a design representation for software systems that have a high degree of textual and graphical interaction. The design representation incorporates both software engineering and knowledge engineering techniques, providing a set of conventions for describing software design information and software construction knowledge. The Tailor demonstrates that the design representation, when embedded in a productivity tool, overcomes limitations of current generation user interface tools. For example, the Tailor has the capability to foresee construction difficulties arising from earlier design decisions. It uses this capability to provide active guidance in producing a software design that avoids problems otherwise overlooked during software specification and design.

Philosophies ◽  
2021 ◽  
Vol 6 (4) ◽  
pp. 81
Author(s):  
Barry M. O’Reilly

This article will examine the unnamed and potentially devastating constraining effect of software on human autonomy. I call this concept residual causality, where software design decisions made long ago in different circumstances for different reasons constrain human action in an unknown future. The less aware the designers of software systems are of complexity in social systems, the more likely they are to introduce residual causality. The introduction of intricate, ordered machines, to a world largely defined by disorder and heuristics, has caused philosophical perturbations that we have not fully dealt with. The machine in the ghost is the belief that machine thinking can be applied to the environment in which the machine will operate. As hyperconnectivity increases, the ghost becomes more unpredictable, unmanageable, and even less like the machine. If we continue to indulge the machine view of the world, the design of software systems presents real dangers to the autonomy of the individual and the functioning of our societies. The steadfastness of machine ontologies in the philosophies of software architects risks creating increasing residual causality as hyperconnectivity increases. Shifting the philosophical position of software architects opens up the possibility of discovering new methods that make it easier to avoid these dangers.


2012 ◽  
Vol 2 (2) ◽  
pp. 112-116
Author(s):  
Shikha Bhatia ◽  
Mr. Harshpreet Singh

With the mounting demand of web applications, a number of issues allied to its quality have came in existence. In the meadow of web applications, it is very thorny to develop high quality web applications. A design pattern is a general repeatable solution to a generally stirring problem in software design. It should be noted that design pattern is not a finished product that can be directly transformed into source code. Rather design pattern is a depiction or template that describes how to find solution of a problem that can be used in many different situations. Past research has shown that design patterns greatly improved the execution speed of a software application. Design pattern are classified as creational design patterns, structural design pattern, behavioral design pattern, etc. MVC design pattern is very productive for architecting interactive software systems and web applications. This design pattern is partition-independent, because it is expressed in terms of an interactive application running in a single address space. We will design and analyze an algorithm by using MVC approach to improve the performance of web based application. The objective of our study will be to reduce one of the major object oriented features i.e. coupling between model and view segments of web based application. The implementation for the same will be done in by using .NET framework.


2021 ◽  
Vol 2061 (1) ◽  
pp. 012125
Author(s):  
K Goloskokov ◽  
V Korotkov ◽  
V Gaskarov ◽  
T Knysh

Abstract The purpose of the paper is to identify the main problems of creating software systems with a given level of reliability for intelligent transport systems. Considering the importance of this approach and the gained experience, the paper discusses design solutions to ensure software reliability in the development process. The paper is based on domestic and foreign experience of software design for intelligent information systems, which include transport systems. The issues of achieving a given level of software reliability during the control process are considered taking into account the continuation of the development process. It also reflects efforts to model and evaluate the reliability of software systems by considering the most common types of software reliability assessment models during development, as well as to predict the reliability during maintenance. The emphasis is upon detecting and correcting software errors.


2016 ◽  
Vol 2016 ◽  
pp. 1-16 ◽  
Author(s):  
Andrés Solano ◽  
César A. Collazos ◽  
Cristian Rusu ◽  
Habib M. Fardoun

Usability is a fundamental quality characteristic for the success of an interactive system. It is a concept that includes a set of metrics and methods in order to obtain easy-to-learn and easy-to-use systems. Usability Evaluation Methods, UEM, are quite diverse; their application depends on variables such as costs, time availability, and human resources. A large number of UEM can be employed to assess interactive software systems, but questions arise when deciding which method and/or combination of methods gives more (relevant) information. We proposeCollaborative Usability Evaluation Methods, CUEM, following the principles defined by the Collaboration Engineering. This paper analyzes a set of CUEM conducted on different interactive software systems. It proposes combinations of CUEM that provide more complete and comprehensive information about the usability of interactive software systems than those evaluation methods conducted independently.


2014 ◽  
pp. 1415-1439
Author(s):  
Marta (Plaska) Olszewska ◽  
Marina Waldén

For most of the developers and managers, the structure and the behaviour of software systems represented in a graphical manner is more understandable than a formal specification of a system or than plain code. Our previous work combined the intuitiveness of UML with the development rigour brought by formal methods and created progress diagrams. In progress diagrams, the design decisions within a system refinement chain are assisted by the application of patterns and illustrated in a comprehensible and compact manner. In order to rigorously assess and control the design process, we need to thoroughly monitor it. In this chapter we show how the application of generic refinement patterns is reflected in measurements. We establish measures for the evaluation of the design progress of the system, where the progress diagrams are assessed from the size and structural complexity perspective. Our motivation is to support the system developers and managers in making the design decisions that regard the system construction.


Author(s):  
Bogdan D. Czejdo ◽  
Maciej Zakrzewicz ◽  
Govindarao Sathyamoorthi

The Chapter discusses the need and the problems associated with WEB based cooperative activities in which several team members work in parallel on a common task. Models for software systems supporting such cooperative activities are discussed. Our models describe structure of the cooperation object, cooperation modes and the network message synchronization, that are of prime importance when the system members work at different places and communicate over the Internet. We introduce and describe a component requirements graph and show how to translate it into an interaction graph. The state diagrams and the design graphs are the basis for the WEB software design. The discussion of software architecture for implementing cooperative activities over the Web is also provided.


Author(s):  
Alvaro Soria ◽  
J. Andres Diaz-Pace ◽  
Len Bass ◽  
Felix Bachmann ◽  
Marcelo Campo

Software design decisions are usually made at early stages but have far-reaching effects regarding system organization, quality, and cost. When doing design, developers apply their technical knowledge to decide among multiple solutions, seeking a reasonable balance between functional and quality-attribute requirements. Due to the complexity of this exploration, the resulting solutions are often more a matter of developer’s experience than of systematic reasoning. It is argued that AI-based tools can assist developers to search the design space more effectively. In this chapter, the authors take a software design approach driven by quality attributes, and then present two tools that have been specifically developed to support that approach. The first tool is an assistant for exploring architectural models, while the second tool is an assistant for the refinement of architectural models into object-oriented models. Furthermore, the authors show an example of how these design assistants are combined in a tool chain, in order to ensure that the main quality attributes are preserved across the design process.


Author(s):  
Javier Àlvez ◽  
Paqui Lucio ◽  
German Rigau

In this paper, the authors present Adimen-SUMO, an operational ontology to be used by first-order theorem provers in intelligent systems that require sophisticated reasoning capabilities (e.g. Natural Language Processing, Knowledge Engineering, Semantic Web infrastructure, etc.). Adimen-SUMO has been obtained by automatically translating around 88% of the original axioms of SUMO (Suggested Upper Merged Ontology). Their main interest is to present in a practical way the advantages of using first-order theorem provers during the design and development of first-order ontologies. First-order theorem provers are applied as inference engines for reengineering a large and complex ontology in order to allow for formal reasoning. In particular, the authors’ study focuses on providing first-order reasoning support to SUMO. During the process, they detect, explain and repair several important design flaws and problems of the SUMO axiomatization. As a by-product, they also provide general design decisions and good practices for creating operational first-order ontologies of any kind.


Sign in / Sign up

Export Citation Format

Share Document