scholarly journals Attempt to Determine Non-Fault Case through System Engineer Sensitivity during Each Software Design Process

2021 ◽  
Author(s):  
Kazuo KIHARA ◽  
Hisashi YAMAMOTO
Keyword(s):  
Design Process ◽  
Software Design ◽  
System Engineer

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.

Supporting Quality-Driven Software Design through Intellectual Assistants

2010 ◽  
pp. 181-216 ◽  
Author(s):  
Alvaro Soria ◽  
J. Andres Diaz-Pace ◽  
Len Bass ◽  
Felix Bachmann ◽  
Marcelo Campo
Keyword(s):  
Design Process ◽  
Software Design ◽  
Multiple Solutions ◽  
Object Oriented ◽  
Quality Attributes ◽  
Quality Attribute ◽  
Design Decisions ◽  
Tool Chain ◽  
Architectural Models ◽  
Organization Quality

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.

The Structure of Software Design

1994 ◽  
Author(s):  
Harold Salzman ◽  
Stephen R. Rosenthal
Keyword(s):  
Case Studies ◽  
Design Process ◽  
Software Design ◽  
Software Industry ◽  
Important Change ◽  
Technological Transformation ◽  
Socially Constructed ◽  
Business Applications ◽  
Dual Perspective ◽  
Front Office

The software industry really came of age in the 1970s and 1980s. This was a time of technological transformation in the workplace. The computer expanded from the backroom to the front office and evolved from simple data processing to integrated information systems. The growth of the independent software vendor led to an important change in software design. User firms began to purchase large, standard or semicustom systems from thirdparty vendors rather than purchasing software with hardware and having most applications software custom designed by an in-house programming staff. This added another dimension to the software design process: Software became the product of at least two organizations (the vendor and one or more user firms) and its design and production became mediated by the market. The organizational simplicity of software design occurring within one organization, as difficult a process as that may be, became relatively more complex organizationally. This chapter examines one part of the process of technology design and use: the activities internal to the software design firm. It concentrates on the structure and dynamics of the design process rather than on specific design decisions. The findings presented in this chapter are based on a survey of vendor firms and may represent a different perspective than findings on software developed within a user firm. By focusing on dynamics that transcend choices of particular individuals, we show how decisions are shaped and constrained by the structure of the design process itself. The three chapters following this one present case studies that describe specific choices of software features and functions and analyze the impacts of those choices on software users and customers. Taken together, this chapter and the case studies present the dual perspective necessary to appreciate how software is a socially constructed technology. The business applications software industry for mainframes and minicomputers is composed of hardware manufacturers such as IBM and Digital Equipment Corporation, several large vendors, and numbers of small specialty firms.

Remote Data Acquisition System Based on ARM-Linux

2014 ◽  
Vol 484-485 ◽  
pp. 963-966
Author(s):  
Ming Li Ding
Keyword(s):  
Data Acquisition ◽  
Design Process ◽  
Software Design ◽  
Web Server ◽  
Implementation Process ◽  
Data Acquisition System ◽  
Remote Access ◽  
Acquisition System ◽  
The Web ◽  
Remote Data

The design and implement of remote data acquisition system based on ARM-Linux ARM and embedded Linux was introduced in this paper. Except the introduction of its structure, the implementation process of A/D driver and the web server BOA in the software design process was also emphasized in this paper to achieve remote access A/D data change.

Sign in / Sign up

Export Citation Format

Share Document