2016
DOI: 10.1007/978-3-319-48992-6_2
|View full text |Cite
|
Sign up to set email alerts
|

Software Architecture Design Reasoning: A Card Game to Help Novice Designers

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

1
5
0

Year Published

2018
2018
2024
2024

Publication Types

Select...
3
2
1

Relationship

1
5

Authors

Journals

citations
Cited by 14 publications
(9 citation statements)
references
References 21 publications
1
5
0
Order By: Relevance
“…The research results presented in this paper extend our previous research paper (Schriek et al, 2016). In our previous work, we found that students who used the reminder cards used more reasoning techniques and found more design rationale.…”
Section: Introductionsupporting
confidence: 87%
See 1 more Smart Citation
“…The research results presented in this paper extend our previous research paper (Schriek et al, 2016). In our previous work, we found that students who used the reminder cards used more reasoning techniques and found more design rationale.…”
Section: Introductionsupporting
confidence: 87%
“…We test if such an approach would improve reflective thinking during the design discourse without putting an extra cognitive burden on the designers. Consistent with our previous research works (Tang and Lau, 2014;Schriek et al, 2016), the goal is to enable the creation of design methods to facilitate design reasoning and the generation of design rationale during design discourse. We differentiate our approach with the traditional software architecture inspection and evaluation approaches in that our approach focuses on reasoning during design discourse, whereas the traditional architecture evaluation approach evaluates the completed design, typically after most of the design discourse has completed and design ideas may have been well anchored.…”
Section: Introductionmentioning
confidence: 88%
“…The author also made participants fill a survey and concluded that this activity has shown positive results [23, 29]. Category‐based approach (reminder card‐based approach) [ 1, 2 ]: Software Engineers (while designing software) think naturalistically and not logically/rationally. There is a need to devise a process which helps software engineers to elicit rationally.…”
Section: Related Workmentioning
confidence: 99%
“…The team members may consist of software engineers or art designers or members from the client team (which may have no prior experience). By involving logical reasoning, the requirements engineers and the other team members can contribute more to the design process [1, 2]. Most of the studies performed in the past focused on making the process of gathering and eliciting requirements easier for business analysts and requirement engineers.…”
Section: Introductionmentioning
confidence: 99%
“…As an example, instructors may examine Moodle as an example of an organizational software that is domain focused on education. Readings: [6,8,18,21,53,55,56,58,62]. Due: Quiz 1 (20%) during first half of class for topics from W01 to W05.…”
Section: Topic Description and Assessmentmentioning
confidence: 99%