scholarly journals A sustainable procedural method of software design process improvements

2021 ◽  
Vol 21 (1) ◽  
pp. 440
Author(s):  
Khalid T. Al-Sarayreh ◽  
Kenza Meridji ◽  
Mamdouh Alenezi ◽  
Mohammed Zarour ◽  
Mohammed D. Al-Majali
Keyword(s):  
Design Process ◽  
Software Design ◽  
Software Process ◽  
Software Systems ◽  
Small Companies ◽  
Design Processes ◽  
Implementation Phase ◽  
Process Improvements ◽  
Different Types ◽  
Procedural Method

In practice, the software process is an intermediate phase for enhancement and improvements the design for different types of software products and help developers to converts the specified requirements into prototypes that implement the design into reality. The objective of this paper is to provide software developers, designers and software engineers who work in small companies with a standards-based process improvement using a procedural method technique including detailed steps for designing the small software systems into their companies. The method used in this paper includes 1) analysis four different types of commonly design processes used by industry such as CMMI, conventional or software process in ISO 19759, generic and engineering design processes. 2)  mapping between those four design processes. 3) collect the dispersed design concepts proposed by those four processes. 4) proposed a sustainable procedural method of software design process improvements 5) Illustration of the applicability of the proposed approach using A template-based implementation. The primary result of this study is<strong> </strong>a guideline procedure with detailed steps for<strong> </strong>software design process improvements to help and guide developers in small companies to analyze and design a small software scales with limited cost and duration. In conclusion<strong>, </strong>this paper proposed a method to improve the design process for different kinds of the software systems<strong> </strong>using<strong> </strong>a template-based implementation to reduce the cost, effort and time needed in the implementation phase<strong> </strong>in small companies. The scientific implication<strong> </strong>behind a template-based implementation helps the system and software engineering to use this template easily in their small companies; because most of the time those engineering developers are responsible for analyzing, designing, implementing and testing their software systems during the whole software life cycle.

SOFTWARE RELIABILITY ESTIMATIONS THROUGH USAGE ANALYSIS OF SPECIFICATIONS AND DESIGNS

1996 ◽  
Vol 03 (02) ◽  
pp. 101-117
Author(s):  
CLAES WOHLIN ◽  
ANDERS WESSLÉN ◽  
PER RUNESON
Keyword(s):  
Software Design ◽  
Software Reliability ◽  
Formal Specification ◽  
Development Process ◽  
Early Stage ◽  
Software Systems ◽  
Implementation Phase ◽  
Failure Data ◽  
Full Analysis ◽  
Usage Analysis

This paper presents a method proposal for estimation of software reliability before the implementation phase. The method is based upon that a formal specification technique is used and that it is possible to develop a tool performing dynamic analysis, i.e., locating semantic faults in the design. The analysis is performed with both applying a usage profile as input as well as doing a full analysis, i.e., locate all faults that the tool can find. The tool must provide failure data in terms of time since the last failure was detected. The mapping of the dynamic failures to the failures encountered during statistical usage testing and operation is discussed. The method can be applied either on the software specification or as a step in the development process by applying it on the software design. The proposed method allows for software reliability estimations that can be used both as a quality indicator, and for planning and controlling resources, development times, etc. at an early stage in the development of software systems.

A Comparative Study on Transformation of UML/OCL to Other Specifications

2020 ◽  
Vol 13 (2) ◽  
pp. 256-264
Author(s):  
Jagadeeswaran Thangaraj ◽  
Senthilkumaran Ulaganathan
Keyword(s):  
Software Design ◽  
Code Generation ◽  
Formal Specification ◽  
Software Systems ◽  
Software System ◽  
Object Constraint Language ◽  
Modelling Language ◽  
Static Verification ◽  
Implementation Phase ◽  
Automatic Code

Background: Static verification is a sound programming methodology that permits automated reasoning about the correctness of an implementation with respect to its formal specification before its execution. Unified Modelling Language is most commonly used modelling language which describes the client’s requirement. Object Constraint Language is a formal language which allows users to express textual constraints regarding the UML model. Therefore, UML/OCL express formal specification and helps the developers to implement the code according to the client’s requirement through software design. Objective: This paper aims to compare the existing approaches generating Java, C++, C# code or JML, Spec# specifications from UML/OCL. Methods: Nowadays, software system is developed via automatic code generation from software design to implementation when using formal specification and static analysis. In this paper, the study considers transformation from design to implementation and vice versa using model transformation, code generation or other techniques. Results: The related tools, which generate codes, do not support verification at the implementation phase. On the other hand, the specification generation tools do not generate all the required properties which are needed for verification at the implementation phase. Conclusion: If the generated system supports the verification with all required properties, code developer needs less efforts to produce correct software system. Therefore, this study recommends introducing a new framework which can act as an interface between design and implementation to generate verified software systems.

scholarly journals Architecture decisions in different product classes for complex products

2016 ◽  
Vol 30 (3) ◽  
pp. 217-234
Author(s):  
Marija Jankovic ◽  
Claudia Eckert
Keyword(s):  
Empirical Research ◽  
Design Process ◽  
System Architecture ◽  
Architecture Design ◽  
Design Processes ◽  
Complex Products ◽  
Design Methodologies ◽  
Different Types ◽  
System Architecture Design ◽  
Research Studies

AbstractMany of the most fundamental decisions about a product are made during the system architecture design process. However, how system architecture is designed in practice is not well understood. This paper draws on several research studies related to system architecture design to develop a categorization of system architecture design processes to support the adaptation design methodologies and tools to specific situations. The paper reviews different definitions of system architecture and comments on the relevance of the different perspectives taken in the literature on system architecture to different types of system architecture. The research highlights the need for further empirical research on system architecture design processes as well as on tools to support the engineers creating the system architecture.

Assessment of the Relationships Among Design Methods, Design Activities, and Creativity

2012 ◽  
Vol 134 (11) ◽  
Author(s):  
Vicente Chulvi ◽  
Águeda Sonseca ◽  
Elena Mulet ◽  
Amaresh Chakrabarti
Keyword(s):  
Experimental Study ◽  
Functional Analysis ◽  
Design Process ◽  
Design Method ◽  
Design Methods ◽  
Design Phase ◽  
Design Processes ◽  
Different Types ◽  
Design Activities

This paper presents an experimental study that was conducted to compare the results obtained from using different design methods (brainstorming (BR), functional analysis (FA), and SCAMPER) in design processes. The objectives of this work are twofold. The first was to determine whether there are any differences in the length of time devoted to the different types of activities that are carried out in the design process, depending on the method that is employed; in other words, whether the design methods that are used make a difference in the profile of time spent across the design activities. The second objective was to analyze whether there is any kind of relationship between the time spent on design process activities and the degree of creativity in the solutions that are obtained. Creativity evaluation has been done by means of the degree of novelty and the level of resolution of the designed solutions using creative product semantic scale (CPSS) questionnaire. The results show that there are significant differences between the amounts of time devoted to activities related to understanding the problem and the typology of the design method, intuitive or logical, that are used. While the amount of time spent on analyzing the problem is very small in intuitive methods, such as brainstorming and SCAMPER (around 8–9% of the time), with logical methods like functional analysis practically half the time is devoted to analyzing the problem. Also, it has been found that the amount of time spent in each design phase has an influence on the results in terms of creativity, but results are not enough strong to define in which measure are they affected. This paper offers new data and results on the distinct benefits to be obtained from applying design methods.

Causing a Stir

2019 ◽  
Vol 2 (1) ◽  
Author(s):  
Camilo POTOCNJAK-OXMAN
Keyword(s):  
Design Process ◽  
Collaborative Design ◽  
Entrepreneurial Activity ◽  
Design Team ◽  
Design Processes ◽  
Early Stages

Stir was a crowd-voted grants platform aimed at supporting creative youth in the early stages of an entrepreneurial journey. Developed through an in-depth, collaborative design process, between 2015 and 2018 it received close to two hundred projects and distributed over fifty grants to emerging creatives and became one of the most impactful programs aimed at increasing entrepreneurial activity in Canberra, Australia. The following case study will provide an overview of the methodology and process used by the design team in conceiving and developing this platform, highlighting how the community’s interests and competencies were embedded in the project itself. The case provides insights for people leading collaborative design processes, with specific emphasis on some of the characteristics on programs targeting creative youth

Roles of externalisation activities in the design process

2016 ◽  
Vol 11 (1) ◽  
pp. 34
Author(s):  
Maral Babapour Chafi
Keyword(s):  
Design Process ◽  
Design Research ◽  
Research Literature ◽  
Physical Models ◽  
Future Research ◽  
Knowledge Gaps ◽  
Design Processes ◽  
Digital Modelling

Designers engage in various activities, dealing with different materials and media to externalise and represent their form ideas. This paper presents a review of design research literature regarding externalisation activities in design process: sketching, building physical models and digital modelling. The aim has been to review research on the roles of media and representations in design processes, and highlight knowledge gaps and questions for future research.

scholarly journals Explicating concepts in reasoning from function to form by two-step innovative abductions

2016 ◽  
Vol 30 (2) ◽  
pp. 125-137 ◽  
Author(s):  
Ehud Kroll ◽  
Lauri Koskela
Keyword(s):  
Conceptual Design ◽  
Design Process ◽  
Abductive Reasoning ◽  
Parameter Analysis ◽  
Critical Examination ◽  
Functional Aspect ◽  
Specific Design ◽  
Design Processes ◽  
Step Process ◽  
Design Reasoning

AbstractThe mechanism of design reasoning from function to form is suggested to consist of a two-step inference of the innovative abduction type. First is an inference from a desired functional aspect to an idea, concept, or solution principle to satisfy the function. This is followed by a second innovative abduction, from the latest concept to form, structure, or mechanism. The intermediate entity in the logical reasoning, the concept, is thus made explicit, which is significant in following and understanding a specific design process, for educating designers, and to build a logic-based computational model of design. The idea of a two-step abductive reasoning process is developed from the critical examination of several propositions made by others. We use the notion of innovative abduction in design, as opposed to such abduction where the question is about selecting among known alternatives, and we adopt a previously proposed two-step process of abductive reasoning. However, our model is different in that the two abductions used follow the syllogistic pattern of innovative abduction. In addition to using a schematic example from the literature to demonstrate our derivation, we apply the model to an existing, empirically derived method of conceptual design called “parameter analysis” and use two examples of real design processes. The two synthetic steps of the method are shown to follow the proposed double innovative abduction scheme, and the design processes are presented as sequences of double abductions from function to concept and from concept to form, with a subsequent deductive evaluation step.

Classification of Iteration in Engineering Design Processes

1998 ◽  
Author(s):  
Michael J. Safoutin ◽  
Robert P. Smith
Keyword(s):  
Engineering Design ◽  
Design Process ◽  
Design Automation ◽  
Automated Design ◽  
Design Processes ◽  
Standard Definition ◽  
Design Iteration ◽  
Formal Study ◽  
Poor Understanding

Abstract As engineering design is subjected to increasingly formal study, an informal attitude continues to surround the topic of iteration. Today there is no standard definition or typology of iteration, no grounding theory, few metrics, and a poor understanding of its role in the design process. Existing literature provides little guidance in investigating issues of design that might be best approached in terms of iteration. We review contributions of existing literature toward the understanding of iteration in design, develop a classification of design iteration, compare iterative aspects of human and automated design, and draw some conclusions concerning management of iteration and approaches to design automation.

Collaboration in research: weaving Kaupapa Māori and computer science

2021 ◽  
pp. 117718012110431
Author(s):  
Anna K Rolleston ◽  
Judy Bowen ◽  
Annika Hinze ◽  
Erina Korohina ◽  
Rangi Matamua
Keyword(s):  
New Zealand ◽  
Computer Science ◽  
Indigenous People ◽  
Design Process ◽  
Software Design ◽  
Integrated Process ◽  
Engineering Project ◽  
Aotearoa New Zealand ◽  
Treaty Of Waitangi ◽  
Kaupapa Māori

We describe a collaboration between Māori (Indigenous people of Aotearoa/New Zealand) and Tauiwi (non-Māori) researchers on a software engineering project. Te Tiriti o Waitangi (The Treaty of Waitangi) provides the basis for Māori to lead research that involves Māori as participants or intends to impact Māori outcomes. Through collaboration, an extension of the traditional four-step software design process was created, culminating in a nine-step integrated process that included Kaupapa Māori (Māori ideology) principles. The collaboration experience for both Māori and Tauiwi highlighted areas of misunderstanding within the research context based on differing worldviews and our ability to navigate and work through this. This article provides context, guiding principles, and recommended research processes where Māori and Tauiwi aim to collaborate.

Toward a Reasoning Framework of Design As Synthesis

1999 ◽  
Author(s):  
Masaharu Yoshioka ◽  
Tetsuo Tomiyama
Keyword(s):  
Decision Making ◽  
Problem Solving ◽  
Design Process ◽  
Process Modeling ◽  
Implementation Strategy ◽  
Multiple Model ◽  
Hypothetical Reasoning ◽  
Design Processes ◽  
Design Process Modeling ◽  
Do So

Abstract Most of the previous research efforts for design process modeling had such assumptions as “design as problem solving,” “design as decision making,” and “design by analysis,” and did not explicitly address “design as synthesis.” These views lack notion and understanding about synthesis. Compared with analysis, synthesis is less understood and clarified. This paper discusses our fundamental view on synthesis and approach toward a reasoning framework of design as synthesis. To do so, we observe the designer’s activity and formalize knowledge operations in design processes. From the observation, we propose a hypothetical reasoning framework of design based on multiple model-based reasoning. We discuss the implementation strategy for the framework.

Sign in / Sign up

Export Citation Format

Share Document