H. Washizaki, A. Hazeyama, T. Okubo, Hideyuki Kanuka, Shinpei Ogata, Nobukazu Yoshioka
{"title":"物联网模式描述分析","authors":"H. Washizaki, A. Hazeyama, T. Okubo, Hideyuki Kanuka, Shinpei Ogata, Nobukazu Yoshioka","doi":"10.1109/SERP4IoT52556.2021.00010","DOIUrl":null,"url":null,"abstract":"IoT architecture and design patterns document the successes in IoT systems and software design. Although these patterns are often described based on well-accepted common description forms such as the Gang of Four (GoF), Pattern-Oriented Software Architecture (POSA), and Canonical forms, IoT patterns occasionally adopt a unique description form to capture IoT-specific aspects. Such heterogeneity in the description makes it difficult to understand, compare, apply, and verify various IoT patterns in systems and software development processes. To mitigate these issues and provide recommendations on IoT pattern descriptions to the IoT and pattern communities, we conducted an in-depth analysis of the descriptions of the 61 IoT patterns described in 18 papers identified by a systematic literature review. We first analyzed the description forms and sections currently adopted in IoT patterns. We found that about a quarter of IoT patterns are immature and are not well described. Of the well-documented IoT patterns, almost half adopt common pattern forms. “Related Pattern (See also)” is the most used section followed by “Problem” and “Solution.” The high number of adoptions of “Related Pattern” indicates that many IoT patterns can be utilized to constitute large solutions. Then we identified IoT-specific description sections as well as commonalities and differences compared with other types of patterns. “Inspired by” is used to specify general patterns as a basis of the target IoT pattern. A comparison between IoT and security patterns showed that “Problem,” “Solution,” “Related Patterns,” and “Known Uses” are identified as typical sections, whereas “Consequences” is less familiar to IoT pattern descriptions. The IoT and pattern communities should further investigate IoT patterns’ usefulness in IoT systems and software development as well as identify missing IoT-specific aspects to be documented.","PeriodicalId":131447,"journal":{"name":"2021 IEEE/ACM 3rd International Workshop on Software Engineering Research and Practices for the IoT (SERP4IoT)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2021-06-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"3","resultStr":"{\"title\":\"Analysis of IoT Pattern Descriptions\",\"authors\":\"H. Washizaki, A. Hazeyama, T. Okubo, Hideyuki Kanuka, Shinpei Ogata, Nobukazu Yoshioka\",\"doi\":\"10.1109/SERP4IoT52556.2021.00010\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"IoT architecture and design patterns document the successes in IoT systems and software design. Although these patterns are often described based on well-accepted common description forms such as the Gang of Four (GoF), Pattern-Oriented Software Architecture (POSA), and Canonical forms, IoT patterns occasionally adopt a unique description form to capture IoT-specific aspects. Such heterogeneity in the description makes it difficult to understand, compare, apply, and verify various IoT patterns in systems and software development processes. To mitigate these issues and provide recommendations on IoT pattern descriptions to the IoT and pattern communities, we conducted an in-depth analysis of the descriptions of the 61 IoT patterns described in 18 papers identified by a systematic literature review. We first analyzed the description forms and sections currently adopted in IoT patterns. We found that about a quarter of IoT patterns are immature and are not well described. Of the well-documented IoT patterns, almost half adopt common pattern forms. “Related Pattern (See also)” is the most used section followed by “Problem” and “Solution.” The high number of adoptions of “Related Pattern” indicates that many IoT patterns can be utilized to constitute large solutions. Then we identified IoT-specific description sections as well as commonalities and differences compared with other types of patterns. “Inspired by” is used to specify general patterns as a basis of the target IoT pattern. A comparison between IoT and security patterns showed that “Problem,” “Solution,” “Related Patterns,” and “Known Uses” are identified as typical sections, whereas “Consequences” is less familiar to IoT pattern descriptions. The IoT and pattern communities should further investigate IoT patterns’ usefulness in IoT systems and software development as well as identify missing IoT-specific aspects to be documented.\",\"PeriodicalId\":131447,\"journal\":{\"name\":\"2021 IEEE/ACM 3rd International Workshop on Software Engineering Research and Practices for the IoT (SERP4IoT)\",\"volume\":\"1 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2021-06-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"3\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2021 IEEE/ACM 3rd International Workshop on Software Engineering Research and Practices for the IoT (SERP4IoT)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/SERP4IoT52556.2021.00010\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2021 IEEE/ACM 3rd International Workshop on Software Engineering Research and Practices for the IoT (SERP4IoT)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/SERP4IoT52556.2021.00010","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
IoT architecture and design patterns document the successes in IoT systems and software design. Although these patterns are often described based on well-accepted common description forms such as the Gang of Four (GoF), Pattern-Oriented Software Architecture (POSA), and Canonical forms, IoT patterns occasionally adopt a unique description form to capture IoT-specific aspects. Such heterogeneity in the description makes it difficult to understand, compare, apply, and verify various IoT patterns in systems and software development processes. To mitigate these issues and provide recommendations on IoT pattern descriptions to the IoT and pattern communities, we conducted an in-depth analysis of the descriptions of the 61 IoT patterns described in 18 papers identified by a systematic literature review. We first analyzed the description forms and sections currently adopted in IoT patterns. We found that about a quarter of IoT patterns are immature and are not well described. Of the well-documented IoT patterns, almost half adopt common pattern forms. “Related Pattern (See also)” is the most used section followed by “Problem” and “Solution.” The high number of adoptions of “Related Pattern” indicates that many IoT patterns can be utilized to constitute large solutions. Then we identified IoT-specific description sections as well as commonalities and differences compared with other types of patterns. “Inspired by” is used to specify general patterns as a basis of the target IoT pattern. A comparison between IoT and security patterns showed that “Problem,” “Solution,” “Related Patterns,” and “Known Uses” are identified as typical sections, whereas “Consequences” is less familiar to IoT pattern descriptions. The IoT and pattern communities should further investigate IoT patterns’ usefulness in IoT systems and software development as well as identify missing IoT-specific aspects to be documented.