Paul S Grisham's research while affiliated with University of Texas at Austin and other places
What is this page?
This page lists the scientific contributions of an author, who either does not have a ResearchGate profile, or has not yet added these contributions to their profile.
It was automatically created by ResearchGate to create a record of this author's body of work. We create such pages to advance our goal of creating and maintaining the most comprehensive scientific repository possible. In doing so, we process publicly available (personal) data relating to the author as a member of the scientific community.
If you're a ResearchGate member, you can follow this page to keep up with this author's work.
If you are this author, and you don't want us to display this page anymore, please let us know.
It was automatically created by ResearchGate to create a record of this author's body of work. We create such pages to advance our goal of creating and maintaining the most comprehensive scientific repository possible. In doing so, we process publicly available (personal) data relating to the author as a member of the scientific community.
If you're a ResearchGate member, you can follow this page to keep up with this author's work.
If you are this author, and you don't want us to display this page anymore, please let us know.
Publications (11)
In many software projects, mistakes are often repeated due to knowledge that has been forgotten from past practice. In order to capture such knowledge, recording, visualizing and identifying underlying contexts and process phenomena in project data is very important. However, directly inferring such contexts from software documents or formal report...
The second workshop on Sharing and Reusing Architectural Knowledge (SHARK) and Architecture rationale and Design intent (ADI) was held jointly with ICSE 2007 in Minneapolis. This report presents the themes of the workshop, summarizes the results of the discussions held, and suggests some topics for future research.
As part of a graduate course on software architecture and design intent, we designed a class project in which teams of students performed software engineering tasks that required them to understand the design of an open source project and evolve the architectural design in response to a set of additional functional requirements. The students used i...
The shift of the software architecture community towards architectural knowledge has brought along some promising research directions. In this workshop we discuss the issues that lead to the application of architectural knowledge in research and industrial practice as well as presenting ongoing research and new ideas to advance the field. We expect...
Design intent is a collection of decision-making factors that explain a design. Annotating software architecture models with design knowledge such as design intent may benefit maintenance activities. Unfortunately, researchers do not understand how software maintainers conduct design activities and use design documentation. This position paper pres...
This paper presents an experience report on teaching Data Engineering as a graduate-level class using a real-world project domain. Traditional computer science database courses focus on relational database theory and typically offer a background in SQL and database implementation. Our course presented databases within the context of Systems and Inf...
Architecture and design intent are critical elements in the development and evolution of software systems. They are critical in two ways. First, there must be a shared understanding of them to adequately and effectively build and evolve our systems. Second, this shared understanding is needed to coordinate the various developers and teams of develo...
We define secure communication to require message integrity, confidentiality, authentication and non-repudiation. This high-level definition forms the basis for many widely ac-cepted definitions of secure communication. In order to understand how security constrains the design of our se-cure connectors, we have created new logical formulas that def...
Extreme Programming (XP) brings the customer and development team together into a tight functional unit, while eliminating many of the process activities of more structured software development processes. While agile methods may yield benefits in terms of product cost and quality, there is also a risk that the very practices that make agile methods...
This paper describes Sage, a software environment supporting software development, synthesis, and testing for distributed computing applications. While the principal domain of interest is applications that must be fault-tolerant ( i.e. , be able to withstand the failure of some of the participants) Sage is not limited to this; it can be extended to...
We define secure communication to require message integrity, confidentiality, authentication and non-repudiation. This high-level definition forms the basis for many widely ac-cepted definitions of secure communication. In order to understand how security constrains the design of our se-cure connectors, we have created new logical formulas that def...
Citations
... (assert (not (or (= (select coi-response 0) coi-r)))) (check-sat) c) The Confidentiality: For a system to be secure, it is important to consider the confidentiality constraints. The confidentiality is defined as a liaison between two or more persons in which the communicated information is not disclosed deliberately to another person [54]. By following the definition of the confidentiality, we have made an assertion for testing the xDAuth protocol. ...
Reference: Formal Verification of the xDAuth Protocol
![[object Object]](https://i1.rgstatic.net/ii/profile.image/280295912820738-1443839161566_Q64/Dewayne-Perry.jpg)
... : In Study 1, the participants explored ADs in Microsoft Word or printed format. In Study 2, the participants explored ADs in the form of wiki pages in an Atlassian Confluence Enterprise Wiki(Atlassian, 2013) environment, where, KaitoroCap was installed as a plug-in. ...
![[object Object]](https://i1.rgstatic.net/ii/profile.image/277611763781635-1443199210256_Q64/Paris-Avgeriou.jpg)
![[object Object]](https://i1.rgstatic.net/ii/profile.image/272395474829322-1441955550926_Q64/Philippe-Kruchten.jpg)
![[object Object]](https://i1.rgstatic.net/ii/profile.image/272394111680523-1441955225942_Q64/Patricia-Lago.jpg)
... These kinds of whiteboard sketches, and the design processes that they support, have seen an increase in interest from the software engineering research community in the past several years. Building upon work that looks at software designers 'in action' more generally (e.g., [13,19,21,41,60]), the design work of software designers at the whiteboard has been examined from a range of per-spectives, including idea generation [2], design notations [6,33,42,56], decision making [59][60], epistemic uncertainty [4], and collaboration [32]. ...
![[object Object]](https://i1.rgstatic.net/ii/profile.image/272405545353236-1441957951451_Q64/Hajimu-Iida.jpg)
... In [23] and [20], the authors study with an Alloy model Chord [12], a wellknown peer-to-peer distributed hash table protocol. As in our work, Alloy has been applied to study the convergence of other protocols as well [3], [7]. In [3] for example, Alloy is used to analyze the properties of the Stable Path Problem (SPP), and to verify sufficient conditions on SPP instances. ...
... Specifically, we opted to use S5 [7] , which is a sound and complete logic for describing knowledge. S5 has been previously used to describe other distributed system problems [16, 9] , and is easily extendible with temporal operators and suitable for use with automated reasoning systems [17]. The basic operator in S5 is K, which is used in the predicate KP (φ) (P knows some fact φ). ...
... Real customer involvement means "the direct involvement of end-users and other business stakeholders on the project" (Martin et al., 2009). In traditional approaches, the interaction between customer and supplier or team is limited to the planning phase and providing feedback about the end product (Grisham and Perry, 2005;Judy and Involving the customer means working in close collaboration with them. Since the customer is the main focus in agile projects agile methodologies, therefore, stand on the principles of "improved customer satisfaction, adapting to changing requirements, frequently delivering working software, and close collaboration of business people and developers" (Paetsch et al., 2003). ...
... Additionally, we believe that classroom instruction will be most effective if it is tightly coupled with problems students are currently facing in their projects, providing context, frameworks, and tools to help them approach issues that are already at the top of their mind. A number of programs in computer science [15,33] and introductory courses in data science [34] have found advantageous effects to pairing instruction with real-world context through projects and we have likewise seen this sort of "priming" effect at play several times in working with students in the Data Science for Social Good summer program [9] , informing our perspective on how learning and practice interact. Our proposed approach to instructional hours for Residency Master's therefore breaks from the typical concept of quarter-or semester-long topic-centric courses in favor of a concept of instruction that better reflects the skills students will put to use through the lifecycle of a data science project. ...
![[object Object]](https://i1.rgstatic.net/ii/profile.image/280157018443783-1443806046557_Q64/Herb-Krasner.jpg)
... Much of this time is spent trying to determine the original intent of a legacy design [2]. The Perry/Wolf model of software architecture explicitly includes rationale [3], although we now prefer to use the term design intent to describe a collection of decision-making factors that explain the design—including, but not limited to, rationale [2] [4]. ...
... Design decisions are concerned with the system's application domain, architectural patterns employed in the system, Commercial off-the-shelf components, other infrastructure selections, and other aspects needed to satisfy all requirements [26]. According to Avgeriou et al. [27], failing to make architectural design decisions during software development has well-known implications, such as costly system evolution, weak stakeholder communication, limited reusability of architectural assets, and poor traceability between specifications and implementation. ...
... The combination of agile methods and the new architectural practice led in the case study to "increased progress visibility, early identification and solving of technical problems, shared responsibility, efficient information sharing, high process practice coherence, low defect density in released products, and constant development rhythm". Several other studies suggest that existing agile methodologies can be integrated in other software engineering paradigms, e.g., model-driven development [16,17], product line engineering [18,19], and service-oriented technologies [20]. ...
