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.

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.

Software Development Crisis

2017 ◽  
pp. 126-148 ◽  
Author(s):  
Sergey Zykov
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Nuclear Power ◽  
Oil And Gas ◽  
Software Production ◽  
Number Of Factors ◽  
Software Product ◽  
Software And Hardware ◽  
The 1960S ◽  
General Architecture

Software development is critically dependent on a number of factors. These factors include techno-logical and anthropic-oriented ones. Software production is a multiple party process; it includes customer and developer parties. Due to different expectations and goals of each side, the human factors become mission-critical. Misconceptions in the expectations of each side may lead to misbalanced production; the product that the developers produce may significantly differ from what the customers expect. This misbalanced vision of the software product may result in a software de-livery crisis. To manage this crisis, the authors recommend using software engineering methods. Software engineering is a discipline which emerged from the so-called “software crisis” in the 1960s: it combines technical and anthropic-oriented “soft” skills. To conquer the crisis, this chapter discusses general architecture patterns for software and hardware systems; it provides instances of particular industries, such as oil and gas and nuclear power production.

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. 

Software Development Crisis

2021 ◽  
pp. 1145-1162
Author(s):  
Sergey Zykov
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Nuclear Power ◽  
Oil And Gas ◽  
Software Production ◽  
Number Of Factors ◽  
Software Product ◽  
Software And Hardware ◽  
The 1960S ◽  
General Architecture

Software development is critically dependent on a number of factors. These factors include techno-logical and anthropic-oriented ones. Software production is a multiple party process; it includes customer and developer parties. Due to different expectations and goals of each side, the human factors become mission-critical. Misconceptions in the expectations of each side may lead to misbalanced production; the product that the developers produce may significantly differ from what the customers expect. This misbalanced vision of the software product may result in a software de-livery crisis. To manage this crisis, the authors recommend using software engineering methods. Software engineering is a discipline which emerged from the so-called “software crisis” in the 1960s: it combines technical and anthropic-oriented “soft” skills. To conquer the crisis, this chapter discusses general architecture patterns for software and hardware systems; it provides instances of particular industries, such as oil and gas and nuclear power production.

Implementing Internal Software Process Assessment

2011 ◽  
pp. 78-99
Author(s):  
Shukor Sanim Mohd Fauzi ◽  
Nuraminah Ramli ◽  
Mustafa Kamal Mohd Noor
Keyword(s):  
Information Technology ◽  
Software Engineering ◽  
Process Improvement ◽  
Software Industry ◽  
Software Process ◽  
Process Assessment ◽  
Growing Up ◽  
Size Information ◽  
Software Process Assessment ◽  
Software Crisis

Software process assessments have become commonplace in the software industry because the software industry usually does not recognize the level of their software process. From the time software is developed, a phenomenon called software crisis exists subsuming wrong schedules and cost estimates, low productivity of people, as well as low productivity. A promising approach out of this crisis is now growing up in the software engineering community. One of the approaches is Software Process Assessment. We present our experience in implementing internal software process assessment at one of the mid-size Information Technology (IT) company by using the customized SPA method. The customized model is basically based on Standard CMMI Appraisal Method for Process Improvement (SCAMPI).

Implementing Internal Software Process Assessment

2014 ◽  
pp. 1314-1334
Author(s):  
Shukor Sanim Mohd Fauzi ◽  
Nuraminah Ramli ◽  
Mustafa Kamal Mohd Nor
Keyword(s):  
Information Technology ◽  
Software Engineering ◽  
Process Improvement ◽  
Software Industry ◽  
Software Process ◽  
Process Assessment ◽  
Growing Up ◽  
Size Information ◽  
Software Process Assessment ◽  
Software Crisis

Software process assessments have become commonplace in the software industry because the software industry usually does not recognize the level of their software process. From the time software is developed, a phenomenon called software crisis exists subsuming wrong schedules and cost estimates, low productivity of people, as well as low productivity. A promising approach out of this crisis is now growing up in the software engineering community. One of the approaches is Software Process Assessment. We present our experience in implementing internal software process assessment at one of the mid-size Information Technology (IT) company by using the customized SPA method. The customized model is basically based on Standard CMMI Appraisal Method for Process Improvement (SCAMPI).

Sign in / Sign up

Export Citation Format

Share Document