Structured programming and structured design as art forms

A use case model describes the functional requirements of a software system and is used as input to several activities in a software development project. The quality of the use case model therefore has an important impact on the quality of the resulting software product. Software inspection is regarded as one of the most efficient methods for verifying software documents. There are inspection techniques for most documents produced in a software development project, but no comprehensive inspection technique exists for use case models. This paper presents a taxonomy of typical defects in use case models and proposes a checklist-based inspection technique for detecting such defects. This inspection technique was evaluated in two studies with undergraduate students as subjects. The results from the evaluations indicate that inspections are useful for detecting defects in use case models and motivate further studies to improve the proposed inspection technique.

show abstract

“…A walkthrough is a peer group review of a software document [21]. It involves several people, each of whom plays a well defined role.…”

Section: Inspections Reviews and Walkthroughsmentioning

confidence: 99%

Towards an inspection technique for use case models

Anda

Sjøberg

2002

Proceedings of the 14th International Conference on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

show abstract

“…The "low coupling, high cohesion" (LCHC) principle helps decide how many. This principle states that components in a component-based system should have few couplings between different components and high cohesion within a component (Yourdon and Constantine, 1979) as a tight coupling of components would cause invasive changes on them when modifications are needed (Heim et al, 2015).…”

Section: Principle: Low Coupling High Cohesionmentioning

confidence: 99%

Robotic world models—conceptualization, review, and engineering best practices

Sakagami,

Lay,

Dömel

et al. 2023

Front. Robot. AI

View full text Add to dashboard Cite

The term “world model” (WM) has surfaced several times in robotics, for instance, in the context of mobile manipulation, navigation and mapping, and deep reinforcement learning. Despite its frequent use, the term does not appear to have a concise definition that is consistently used across domains and research fields. In this review article, we bootstrap a terminology for WMs, describe important design dimensions found in robotic WMs, and use them to analyze the literature on WMs in robotics, which spans four decades. Throughout, we motivate the need for WMs by using principles from software engineering, including “Design for use,” “Do not repeat yourself,” and “Low coupling, high cohesion.” Concrete design guidelines are proposed for the future development and implementation of WMs. Finally, we highlight similarities and differences between the use of the term “world model” in robotic mobile manipulation and deep reinforcement learning.

show abstract

“…Lastly, we would like to have the tactic implemented in a way that the final code has a high quality. There are a variety of techniques that quantify the quality of the code from different perspectives, e.g., high-cohesion and loosecoupling as two fundamental quality metrics for code [25]. In this paper, we focus on high-cohesion, but we will discuss how loose-coupling could also be incorporated as future work.…”

Section: Criteria 4: Synthesized Code Qualitymentioning

confidence: 99%

ArCode: A Tool for Supporting Comprehension and Implementation of Architectural Concerns

Shokri

Mirakhorli

2021

2021 IEEE/ACM 29th International Conference on Program Comprehension (ICPC)

View full text Add to dashboard Cite

Integrated development environments (IDE) play an important role in supporting developers during program comprehension and completion. Many of these supportive features focus on low-level programming and debugging activities. Unfortunately, there is less support in understanding and implementing architectural concerns in the form of patterns, tactics and/or other concerns. In this paper we present ArCode, a tool designed as a plugin for a popular IDE, IntelliJ IDEA. ArCode is able to learn correct ways of using frameworks' API to implement architectural concerns such as Authentication and Authorization. Analyzing the programmer's code, this tool is able to find deviations from correct implementation and provide fix recommendations alongside with graphical demonstrations to better communicate the recommendations with the developers. We showcase how programmers can benefit from ArCode by providing an API misuse detection and API recommendation scenario for a famous Java framework, Java Authentication and Authorization (JAAS) security framework.

show abstract

Structured programming and structured design as art forms

Cited by 14 publications

References 0 publications

Towards an inspection technique for use case models

Towards an inspection technique for use case models

Robotic world models—conceptualization, review, and engineering best practices

ArCode: A Tool for Supporting Comprehension and Implementation of Architectural Concerns

Contact Info

Product

Resources

About