In-Between and Through: Architecture and Complexity

2005 ◽  
Vol 3 (3) ◽  
pp. 335-354 ◽  
Author(s):  
Clarissa Ribeiro Pereira de Almeida ◽  
Anja Pratschke ◽  
Renata La Rocca
Keyword(s):  
Complex System ◽  
Software Engineering ◽  
Complex Systems ◽  
Design Process ◽  
Three Dimensional ◽  
Self Organization ◽  
Three Dimensional Modeling ◽  
Dimensional Modeling ◽  
Complex Thought ◽  
Basic Characteristics

This paper draws on current research on complexity and design process in architecture and offers a proposal for how architects might bring complex thought to bear on the understanding of design process as a complex system, to understand architecture as a way of organizing events, and of organizing interaction. Our intention is to explore the hypothesis that the basic characteristics of complex systems – emergence, nonlinearity, self-organization, hologramaticity, and so forth – can function as effective tools for conceptualization that can usefully extend the understanding of the way architects think and act throughout the design process. To illustrate the discussions, we show how architects might bring complex thought inside a transdisciplinary design process by using models such as software engineering diagrams, and three-dimensional modeling network environments such as media to integrate, connect and ‘trans–act’.

scholarly journals O Processo de Design Digital: endereçando o desafio da multidisciplinaridade

2018 ◽  
Author(s):  
Tânia S. M. Pinheiro ◽  
Ingrid Teixeira Monteiro ◽  
Danilo A. Felipe ◽  
Andréia Libório Sampaio
Keyword(s):  
Software Engineering ◽  
Computer Science ◽  
Design Process ◽  
Lessons Learned ◽  
Digital Design ◽  
Design Communication ◽  
Design Program ◽  
Integrated Project

Integrated Project is a type of course offered in the Digital Design program of the Federal University of Ceará, Quixadá Campus. It has the challenge of integrating into a single project some concepts from the areas of Computer Science, Design, Communication and Arts. For the interdisciplinarity to be productive, it was specified PD3 (Digital Disruptive Design Process), a design process based on HCI, Design, and Software Engineering methodologies. In this paper, we present the PD3 applied to the Integrated Project courses, describing how it has been used and evolved, as well as giving lessons learned.

An Integrated Secure Software Engineering Approach for Functional, Collaborative, and Information Concerns

2017 ◽  
pp. 253-292
Author(s):  
J. A. Pavlich-Mariscal ◽  
S. Berhe ◽  
A. De la Rosa Algarín ◽  
S. Demurjian
Keyword(s):  
Software Engineering ◽  
Access Control ◽  
Design Process ◽  
Security Policies ◽  
Engineering Approach ◽  
Secure Software Engineering ◽  
Secure Software ◽  
Functional Object ◽  
Uml Diagrams ◽  
Role Based

This chapter explores a secure software engineering approach that spans functional (object-oriented), collaborative (sharing), and information (Web modeling and exchange) concerns in support of role-based (RBAC), discretionary (DAC), and mandatory (MAC) access control. By extending UML with security diagrams for RBAC, DAC, and MAC, we are able to design an application with all of its concerns, and not defer security to a later time in the design process that could have significant impact and require potentially wide-ranging changes to a nearly completed design. Through its early inclusion in the software design process, security concerns can be part of the application design process, providing separate abstractions for security via new UML diagrams. From these new UML diagrams, it is then possible to generate security policies and enforcement code for RBAC, DAC, and MAC, which separates security from the application. This modeling and generation allows security changes to have less of an impact on an application. The end result is a secure software engineering approach within a UML context that is capable of modeling an application's functional, collaborative, and information concerns. This is explored in this chapter.

An Integrated Secure Software Engineering Approach for Functional, Collaborative, and Information Concerns

2014 ◽  
pp. 330-368
Author(s):  
J. A. Pavlich-Mariscal ◽  
S. Berhe ◽  
A. De la Rosa Algarín ◽  
S. Demurjian
Keyword(s):  
Software Engineering ◽  
Access Control ◽  
Design Process ◽  
Security Policies ◽  
Engineering Approach ◽  
Secure Software Engineering ◽  
Secure Software ◽  
Functional Object ◽  
Uml Diagrams ◽  
Role Based

This chapter explores a secure software engineering approach that spans functional (object-oriented), collaborative (sharing), and information (Web modeling and exchange) concerns in support of role-based (RBAC), discretionary (DAC), and mandatory (MAC) access control. By extending UML with security diagrams for RBAC, DAC, and MAC, we are able to design an application with all of its concerns, and not defer security to a later time in the design process that could have significant impact and require potentially wide-ranging changes to a nearly completed design. Through its early inclusion in the software design process, security concerns can be part of the application design process, providing separate abstractions for security via new UML diagrams. From these new UML diagrams, it is then possible to generate security policies and enforcement code for RBAC, DAC, and MAC, which separates security from the application. This modeling and generation allows security changes to have less of an impact on an application. The end result is a secure software engineering approach within a UML context that is capable of modeling an application's functional, collaborative, and information concerns. This is explored in this chapter.

Aesthetics in Software Engineering

2011 ◽  
pp. 72-77
Author(s):  
Bruce MacLennan
Keyword(s):  
Software Engineering ◽  
Design Process

It is commonly supposed that software engineering is—and should be—focused on technical and scientific issues, such as correctness, efficiency, reliability, testability, and maintainability. Within this constellation of important technological concerns, it might seem that design aesthetics should hold a secondary, marginal role, and that aesthetic considerations might enter the design process, if at all, only after the bulk of the engineering is done. This article discusses the important role that aesthetics can play in engineering, and in particular in software engineering, and how it can contribute to achieving engineering objectives.

Abstraction: An alternative neurocognitive account of recognition, prediction, and decision making

2020 ◽  
Vol 43 ◽  
Author(s):  
Valerie F. Reyna ◽  
David A. Broniatowski
Keyword(s):  
Decision Making ◽  
Software Engineering ◽  
Systems Engineering ◽  
Evidence Based ◽  
Extensive Literature ◽  
Trace Theory ◽  
Fuzzy Trace Theory ◽  
Abstract Representations ◽  
Technical Systems

Abstract Gilead et al. offer a thoughtful and much-needed treatment of abstraction. However, it fails to build on an extensive literature on abstraction, representational diversity, neurocognition, and psychopathology that provides important constraints and alternative evidence-based conceptions. We draw on conceptions in software engineering, socio-technical systems engineering, and a neurocognitive theory with abstract representations of gist at its core, fuzzy-trace theory.

Investigating the Value of Process Books in the Design Process Using Cognitive Load Theory

2013 ◽  
Author(s):  
Lori B. Stone ◽  
Abigail Lundquist ◽  
Stefan Ganchev ◽  
Nora Ladjahasan
Keyword(s):  
Cognitive Load ◽  
Design Process ◽  
Cognitive Load Theory ◽  
Load Theory
Sign in / Sign up

Export Citation Format

Share Document