Canek PhillipsPurdue University West Lafayette | Purdue · Purdue University School of Engineering Education
Canek Phillips
Doctor of Engineering Education
About
16
Publications
2,845
Reads
How we measure 'reads'
A 'read' is counted each time someone views a publication summary (such as the title, abstract, and list of authors), clicks on a figure, or views or downloads the full-text. Learn more
154
Citations
Introduction
Skills and Expertise
Additional affiliations
July 2015 - September 2016
Publications
Publications (16)
In this article, we overview the contributions to narrative theory and criticism across four subdisciplines of communication: rhetoric, organizational communication, health communication and cultural studies. We note that much of this work has focused on stories as individual artifacts. We propose that future work on narrative should highlight the...
Severity assessment in concomitant hypertension (HT) and heart valve disease or multiple heart valve disease is vague, and there exists no established severity index. The objective of this study is to propose a theoretical framework to utilize the ventricular power overhead rates of HT, aortic regurgitation (AR), aortic stenosis (AS), and mitral re...
Much research done in engineering education on white women and people of color's underrepresentation relies on methods which necessitate collapsing the experiences of all women together and the experiences of all people of color together in order to gain sufficiently large sample populations for statistical tests. This methodologically necessary ac...
Numerous reports and outreach initiatives stem from a concern over low public understanding of and interest in engineering. Most often, these reports and initiatives express a belief (either implicitly or explicitly) that the public does not understand or appreciate engineering because they are uninformed or misinformed and that, consequently, the...
A developer of user interfaces (UI) should be able to employ a user interface pattern language to design acceptable user interfaces. But, what makes a good pattern language? Three types of validation were identified as requiring consideration: the validity of the individual patterns, the internal validation of the pattern language and the external...
When considering using a UI pattern language three types of validation need to be considered: The validity of the individual patterns, the internal validation of the pattern language and the external validation of the pattern language. A set of six tests that a developer can use to determine the internal validity of a pattern language has been iden...
UML supports the construction of several views of a software
system. The paper reviews use case modelling in UML from the viewpoint
of its suitability as input to the early stages of graphical user
interface design. Three use case representations are compared, and an
extended tabular representation is proposed which assists with the
identification...
Interactive system design requires good descriptive systems, and
the development of tools to support it. In particular, models and
notations are required for describing user tasks, and for describing the
structure of the human-computer dialogue to support these tasks. These
descriptions should ideally be linked. The paper reviews task and
dialogue...
This paper describes the design of the client user interface for
MOOT (Meta Object Oriented Tool). Both functional and non-functional
requirements of the interface are defined and design issues relating to
the look and feel of the interface are discussed. Details of an
instantiation for the Goad and Yourdon OOA/OOD methodology are presented
and dis...
The focus of the paper is on support for the early prototyping of
interactive systems, that is, on support for the initial design phase. A
shortcoming of current early prototyping tools is that although they
permit the designer to construct a mock-up of the look and feel of the
user interface, they provide no model of the interaction. Early
prototy...
The aim of the paper is to derive a framework for the evaluation
of object oriented (OO) computer aided software engineering (CASE)
tools. Some existing evaluation frameworks and methodologies are
discussed. Two orthogonal classification hierarchies are derived: an
inheritance hierarchy of OO CASE tool categories, and a usability
criteria classific...
MOOT (Meta Object Oriented Tool) is an intelligent methodology
independent customisable OO CASE tool. One of the major goals of MOOT is
to provide flexible support for the description of the semantics and
notations of arbitrary methodologies. This is provided through the
employment of two distinct specification languages. The paper describes
the de...
In this paper, the intersection of software engineering (SE) and human-computer interaction (HCI) education is explored through an examination of some current textbooks, papers and curriculum proposals. It is argued that HCI is not well integrated with SE lifecycle models; that interface design is often perceived as a small part of overall system d...
A working group was convened to consider human-computer interaction (HCI) issues in relation to software engineering (SE) courses. Two broad questions were posed to the group: 1. Is this aspect (HCI) of software development adequately covered in SE courses? 2. Do contemporary graphical user interface (GUI) development tools over-emphasise the inter...
Task models are an important abstraction in the design of
graphical user interfaces (GUIs). The role of task modelling in
interface development is briefly reviewed, and an experimental
methodology for high level GUI design is described in which task
modelling forms a continuous thread. The methodology includes a task
decomposition derived from esse...