arXivDaily arXiv每日学术速递 周一至周五更新
arXiv周末暂无论文更新,休息一下吧,周末愉快~~
arXiv 1706.09172cs.SE
收藏

草图和图表在实践中

Sketches and Diagrams in Practice

Sebastian Baltes, Stephan Diehl

摘要:

草图和图表在软件开发人员的日常工作中起着重要的作用。在本文中,我们探讨了草图和图表在软件工程实践中的使用。为此,我们使用了定量和定性方法。我们提出了一个探索性研究的结果,在三家公司和一个在线调查,394名参与者。我们的参与者包括软件开发人员、软件架构师、项目经理、顾问以及研究人员。他们在不同的国家工作,从事广泛应用领域的项目。调查中的大多数问题都与参与者创建的最后一个草图或图表有关。与我们的期望和以前的工作相反,大多数草图和图表至少包含一些UML元素。然而,其中大多数是非正式的。创建草图和图表最常见的目的是设计,解释和理解,但分析需求也经常被提及。超过一半的草图和图表是在纸或白板等模拟媒体上创建的,并且在创建后进行了修改。其中大多数使用了一个多星期,并被存档。我们发现,大多数参与者将他们的草图与方法、类或包相关联,而不是与抽象级别较低的源代码工件相关联。

英文摘要:

Sketches and diagrams play an important role in the daily work of software developers. In this paper, we investigate the use of sketches and diagrams in software engineering practice. To this end, we used both quantitative and qualitative methods. We present the results of an exploratory study in three companies and an online survey with 394 participants. Our participants included software developers, software architects, project managers, consultants, as well as researchers. They worked in different countries and on projects from a wide range of application areas. Most questions in the survey were related to the last sketch or diagram that the participants had created. Contrary to our expectations and previous work, the majority of sketches and diagrams contained at least some UML elements. However, most of them were informal. The most common purposes for creating sketches and diagrams were designing, explaining, and understanding, but analyzing requirements was also named often. More than half of the sketches and diagrams were created on analog media like paper or whiteboards and have been revised after creation. Most of them were used for more than a week and were archived. We found that the majority of participants related their sketches to methods, classes, or packages, but not to source code artifacts with a lower level of abstraction.

机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。

↑