Diseño de interfaces web amigables desde la perspectiva de la semiótica organizacional [Web interfaces design from the perspective of the Organizational Semiotics]

2012 ◽  
Author(s):  
Diego Samir Melo Solarte
Keyword(s):  
Software Engineering ◽  
The Other ◽  
Heuristic Evaluation ◽  
Web Interfaces ◽  
Software Products ◽  
Software Product ◽  
Engineering Models ◽  
Organizational Semiotics

Resumen Este artículo presenta una estrategia para el diseño de productos de software con interfaces web amigables, incorporando modelos de la Ingeniería de Software articulados con la Semiótica Organizacional, lo cual permite abstraer un problema desde diferentes perspectivas y plantear soluciones integrales donde se considere las características del usuario final. La estrategia planteada se basa en el diseño de prototipos no funcionales a nivel de mockups; los cuales permiten tener apreciación inicial del usuario a la vez que permite desenvolver libremente la creatividad del diseñador evitando limitarse por las competencias del personal encargado de la implementación. Por otra parte, en este artículo también se presenta dos modelos basados en inspección para la revisión y evaluación de interfaces, con los cuales se orienta a los encargados de un producto de software sobre los elementos relevantes que constituyen una interfaz usable y accesible. Palabras ClaveSemiótica Organizacional, Interfaces Amigables, Método de Articulación de Problemas, Evaluación Heurística, GOMS, Elaboración de prototipos no funcionales.   Abstract This article presents a strategy for the design of software products with friendly web interfaces including articulated Software engineering models with the Organizational Semiotic. This allows the abstraction of the problem from different perspectives and the planning of comprehensive solutions considering the final user's characteristics. The idea is based on the design of mockups. The mockups help to obtain the user's first appreciation and the designer's creativity fluency at the same time, avoiding the limits created by the competence of those people in charge of the implementation. On the other side, this article intends to show two models based on the inspection for revision and evaluation of interfaces to direct those in charge of the software product to outstanding elements that make a usable and accessible interface.Keywords Organizational Semiotics, friendly interfaces, Problem Articulation Method, heuristic evaluation, GOMS, prototyping nonfunctional. 

Crisis Response and Management

2019 ◽  
pp. 1-12
Author(s):  
Sergey V. Zykov
Keyword(s):  
Information Technology ◽  
Software Engineering ◽  
Human Factors ◽  
Crisis Response ◽  
Software Product ◽  
Product Scope ◽  
Engineering Models ◽  
Product Delivery ◽  
The 1960S ◽  
Software Crisis

Information technology is critically dependent on a number of technological and human factors. Software engineering processes are multi-sided; they include customer and developer parties. Conceptual misunderstanding by either party often results in the products which do not meet customer's expectations. This misconception of the software product scope usually leads to a crisis of software product delivery. To adequately manage and efficiently respond to this crisis, the authors recommend using software engineering models, methods, techniques, practices, and tools. Software engineering is a discipline which started in the 1960s as a response to the so-called “software crisis”; it combines technical and human-related skills. To manage the crisis, the authors suggest architecture patterns and instantiate them by implementation examples.

scholarly journals A Formal Protocol to Conduct Usability Heuristic Evaluations in the Context of the Software Development Process

2018 ◽  
Vol 7 (2.28) ◽  
pp. 10 ◽  
Author(s):  
Freddy Paz ◽  
Freddy A. Paz ◽  
José Antonio Pow-Sang ◽  
César Collazos
Keyword(s):  
Software Development ◽  
Development Process ◽  
Evaluation Method ◽  
Evaluation Process ◽  
Usability Evaluation ◽  
Comprehensive Analysis ◽  
Heuristic Evaluation ◽  
Software Development Process ◽  
Software Products ◽  
Software Product

Heuristic evaluation is one of the most used techniques to evaluate the level of usability of a software product. In this research, we performed a comprehensive analysis of the recent studies which report the use of this method in the context of a software development process. The purpose was to identify the specific way in which each author performs this usability evaluation method, in order to propose a formal protocol. After an indeed examination of these studies, we have determined there are several differences in the way this technique is conducted according to the literature. There is no agreement about the number of inspectors that should participate, the usability principles that should be used, the profile of the specialists who must be part of the assessment team, or the evaluation process that should be followed. This work highlights the available settings and a detailed procedure to perform a heuristic evaluation in the domain of software products.  

Obstacles for the Integration of HCI Practices into Software Engineering Development Processes

2006 ◽  
pp. 422-428 ◽  
Author(s):  
Xavier Ferre ◽  
Natalia Juristo ◽  
Ana M. Moreno
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Computer Literacy ◽  
Software Process ◽  
Software Systems ◽  
Software Products ◽  
Software Market ◽  
Visible Part ◽  
Software Product ◽  
Development Processes

Usability has become a critical quality factor in software systems, and it has been receiving increasing attention over the last few years in the SE (software engineering) field. HCI techniques aim to increase the usability level of the final software product, but they are applied sparingly in mainstream software development, because there is very little knowledge about their existence and about how they can contribute to the activities already performed in the development process. There is a perception in the software development community that these usability-related techniques are to be applied only for the development of the visible part of the UI (user interface) after the most important part of the software system (the internals) has been designed and implemented. Nevertheless, the different paths taken by HCI and SE regarding software development have recently started to converge. First, we have noted that HCI methods are being described more formally in the direction of SE software process descriptions. Second, usability is becoming an important issue on the SE agenda, since the software products user base is ever increasing and the degree of user computer literacy is decreasing, leading to a greater demand for usability improvements in the software market. However, the convergence of HCI and SE has uncovered the need for an integration of the practices of both disciplines. This integration is a must for the development of highly usable systems. In the next two sections, we will look at how the SE field has viewed usability. Following upon this, we address the existing approaches to integration. We will then detail the pending issues that stand in the way of successful integration efforts, concluding with the presentation of an approach that might be successful in the integration endeavor.

Assessment of Software Quality

2010 ◽  
pp. 200-219 ◽  
Author(s):  
Praveen Ranjan Srivastava ◽  
Ajit Pratap Singh ◽  
Vageesh K. V.
Keyword(s):  
Quality Assurance ◽  
Software Engineering ◽  
Software Quality ◽  
Quality Attributes ◽  
Decision Makers ◽  
Software Quality Assurance ◽  
Quality Attribute ◽  
Software Products ◽  
Multiple Contexts ◽  
Software Product

Software Quality Assurance consists of monitoring the software engineering processes and ensuring the highest quality. But, the software quality attributes that we deal with are not explicit in the outset and cannot be easily measured. The same attribute has multiple significance and importance in multiple contexts. The user, the developer and the manager of a software product may have different stands regarding the significance of a quality attribute. A software quality engineer, while measuring the total software quality should provide appropriate weight to each of the decision makers. This chapter proposes a fuzzy multi-criteria approach to measure the total software quality and to identify the best alternative from a set of software products.

ISSUES AND MODELS IN SOFTWARE PRODUCT LINES

2000 ◽  
Vol 10 (04) ◽  
pp. 527-539 ◽  
Author(s):  
JORGE L. DIAZ-HERRERA ◽  
PETER KNAUBER ◽  
GIANCARLO SUCCI
Keyword(s):  
Software Engineering ◽  
Development Process ◽  
Software Product Lines ◽  
Product Lines ◽  
Standard Format ◽  
Software Products ◽  
Systematic Process ◽  
Software Product ◽  
Business Analysis ◽  
Definition Of

Software product lines are one of the most promising fields in software engineering. They aim at the synergistic construction of software products. A successful introduction of software product lines requires three essential ingredients: a business analysis of the overall advantages that can come from product lines, the definition of a systematic process for product lines development, and the definition of general models, in a standard format, which can guide the development process.

scholarly journals End-User Software Development: Effectiveness of a Software Engineering-Centric Instructional Strategy

10.28945/4580 ◽  
2020 ◽  
Vol 19 ◽  
pp. 367-393 ◽  
Author(s):  
Ilenia Fronza ◽  
Luis Corral ◽  
Claus Pahl
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Instructional Strategies ◽  
Case Studies ◽  
Instructional Strategy ◽  
End Users ◽  
Assessment Framework ◽  
End User ◽  
Software Products ◽  
Software Product

Aim/Purpose: This work aims to introduce and evaluate an instructional strategy that aids end-users with developing their software products during intensive project-based events. Background: End-users produce software in the labor market, and one of the challenges for End-User Software Engineering (EUSE) is the need to create functional software products without a formal education in software development. Methodology: In this work, we present an instructional strategy to expose end-users to Agile-based Software Engineering (SE) practices and enhance their ability to developing high-quality software. Moreover, we introduce a SE approach for the collection of metrics to assess the effectiveness of the instructional strategy. We conducted two case studies to validate the effectiveness of our strategy; the comprehensive analysis of the outcome products evaluates the strategy and demonstrates how to interpret the collected metrics. Contribution: This work contributes to the research and practitioner body of knowledge by leveraging SE centric concepts to design an instructional strategy to lay the foundations of SE competencies in inexperienced developers. This work presents an instructional strategy to develop SE competencies through an intensive and time-bound structure that may be replicated. Moreover, the present work introduces a framework to evaluate these competencies from a product-centric approach, specialized for non-professional individuals. Finally, the framework contributes to understanding how to assess software quality when the software product is written in non-conventional, introductory programming languages. Findings: The results show the effectiveness of our instructional strategy: teams were successful in constructing a working software product. However, participants did not display a good command of source code order and structure. Recommendations for Practitioners: Our instructional strategy provides practitioners with a framework to lay foundations in SE competencies during intensive project-based events. Based on the results of our case studies, we provide a set of recommendations for educational practice. Recommendation for Researchers: We propose an assessment framework to analyze the effectiveness of the instructional strategy from a SE perspective. This analysis provides an overall picture of the participants’ performance; other researchers could use our framework to evaluate the effectiveness of their activities, which would contribute to increasing the possibility of comparing the effectiveness of different instructional strategies. Impact on Society: Given the number of end-user developers who create software products without a formal SE training, several professional and educational contexts can benefit from our proposed instructional strategy and assessment framework. Future Research: Further research can focus on improving the assessment framework by including both process and product metrics to shed light on the effectiveness of the instructional strategies.

Crisis Response and Management

2018 ◽  
pp. 1396-1406
Author(s):  
Sergey V. Zykov
Keyword(s):  
Information Technology ◽  
Software Engineering ◽  
Human Factors ◽  
Crisis Response ◽  
Software Product ◽  
Product Scope ◽  
Engineering Models ◽  
Product Delivery ◽  
The 1960S

Information technology is critically dependent on a number of technological and human factors. Software engineering processes are multi-sided; they include customer and developer parties. Conceptual misunderstanding by either party often results in the products which do not meet customer's expectations. This misconception of the software product scope usually leads to a crisis of software product delivery. To adequately manage and efficiently respond to this crisis, the authors recommend using software engineering models, methods, techniques, practices and tools. Software engineering is a discipline which started in the 1960s as a response to the so-called “software cri-sis”; it combines technical and human-related skills. To manage the crisis, the authors suggest architecture patterns and instantiate them by implementation examples.

Digital education: Using electronic resources in psychological support of the educational process

2020 ◽  
pp. 55-61
Author(s):  
Ju. A. Tikhonova
Keyword(s):  
Preschool Education ◽  
Educational Process ◽  
Psychological Support ◽  
Diagnostic Methods ◽  
Practical Application ◽  
Software Products ◽  
School Year ◽  
Psychological Service ◽  
Software Product ◽  
The City

The article discusses the development trends of the modern preschool education system in the aspect of the activity of the teacherpsychologist of the preschool educational organization. The experience of using 1C software products in the practical work of the psychological service of kindergarten 318 of the city of Perm in the aspects of psychological monitoring of children’s readiness to study at school and correctional and developmental work with preschool children is presented. The components of the child’s psychological readiness for school are described. On practical examples, diagnostic methods for determining the level of readiness of children for schooling are analyzed. The data of testing kindergarten pupils at the beginning of the 2019/2020 school year on the parameters allowing to identify urgent problems and determine the direction of the necessary correctional development work are presented. Features of the practical application of the software product 1C:Preschool Psychodiagnostics in the process of psychological support of preparing children for school are considered. Methods are described, the scope of which is aimed not only at the study of personality traits, but also at its development. The possibilities of using games of the 1C:Educational Collection in the correctional and developmental work are disclosed. The description of game collections is given, options for their use are presented.

Analysing Mechanical Systems in Domestic and Foreign CAD Systems

2018 ◽  
pp. 10-17
Author(s):  
V. A. Martynyuk ◽  
V. A. Trudonoshin ◽  
V. G. Fedoruk
Keyword(s):  
Sheet Material ◽  
The Finite Element Method ◽  
Cad Systems ◽  
Cad System ◽  
Software Products ◽  
Foreign Products ◽  
Nonlinear Algebraic Systems ◽  
Software Product ◽  
Pipeline Design ◽  
The Mathematical Model

The article considers applications of foreign CAD-systems in creating the challenging projects at domestic enterprises and design bureaus. As stated in the article "... presently, there is no domestic CAD-system that could completely replace such foreign products as NX, CATIA, Credo". Besides, due to international cooperation in creating the challenging projects (for example, the project to create a modern wide-body aircraft, proposed jointly with China), it makes sense to use the worldwide known and popular CAD systems (the aforementioned NX, CATIA, Credo). Therefore, in the foreseeable future, we will still have to use foreign software products. Of course, there always remains a question of the reliability of the results obtained. Actually, this question is always open regardless of what software product is used - domestic or foreign. This question has been haunting both developers and users of CAD systems for the last 30 to 40 years. But with using domestic systems, it is much easier to identify the cause of inaccurate results and correct the mathematical models used, the methods of numerical integration applied, and the solution of systems of nonlinear algebraic systems. Everything is much more complicated if we use a foreign software product. All advertising conversations that there is a tool to make the detected errors available to the developers, remain only conversations in the real world. It is easily understandable to domestic users, and, especially, to domestic developers of similar software products. The existing development rates and competition for potential buyers dictate a rigid framework of deadlines for releasing all new versions of the product and introducing the latest developments into commercial product, etc. As a result, the known errors migrate from version to version, and many users have accepted it long ago. Especially, this concerns the less popular tools rather than the most popular applications (modules) of a CAD system. For example, in CAD systems, the "Modeling" module where geometric models of designed parts and assembly units are created has been repeatedly crosschecked. But most of the errors are hidden in applications related to the design of parts from sheet material and to the pipeline design, as well as in applications related to the analysis of moving mechanisms and to the strength or gas dynamic analysis by the finite element method.The article gives a concrete example of a moving mechanism in the analysis of which an error was detected using the mathematical model of external influence (a source of speed) in the NX 10.0 system of Siemens.

THEORETICAL PRINCIPLES OF FORECASTING THE COST OF A SOFTWARE PRODUCT

2017 ◽  
Author(s):  
Pavlo Rodionov ◽  
◽  
Anna Ploskonos ◽  
Lesya Gavrutenko ◽  
◽  
...  
Keyword(s):  
Selection Process ◽  
Individual Characteristics ◽  
Successful Implementation ◽  
Software Products ◽  
Software Product ◽  
Continue Research ◽  
Cocomo Model ◽  
Factors Of Influence ◽  
The Individual ◽  
The Cost

The paper analyzes the factors that affect the amount of effort required to create a mobile application and its cost. It is established that the main factors of influence are the design of the application, its functionality, the type of mobile platform, the availability and level of testing and support, as well as the individual characteristics of the developer. Based on the analysis of information sources, the main methods and approaches to forecasting the cost of software products are identified, which include the COCOMO model, Price-to-win method, expert evaluation, algorithmic methods and the method of analogies. It is proposed to consider the method of analogies as a tool that allows you to make predictions about the cost of resources required for the successful implementation of IT projects based on the experience of similar projects. It is proved that the advantages of this method are the simplicity of its implementation and the clarity of the results obtained, which follows from the practical orientation of this tool. Among the limitations of the method of analogy is the mandatory need for reliable data relating to similar projects, as well as the difficulty of taking into account unspecified indicators. Taking into account the mentioned limitations of the method of analogies and on the basis of the analysis of scientific sources the possible directions of its optimization are determined. Thus, among the ways to improve the effectiveness of this method are those aimed at optimizing the project selection process, the data for which are used as a basis for forecasting. Attempts to improve the method of analogies by including parameters that were previously ignored by this technique seem promising. This in turn can lead to an expansion of the scope of the method of analogies and increase the accuracy of forecasts. As prospects for further research, the need to continue research in the field of optimization of the method of analogies with the subsequent practical verification of theoretical positions on the data of real projects.

Sign in / Sign up

Export Citation Format

Share Document