Goal-Oriented Software Design Reviews
Some software requirements are omitted or ambiguous depending on the design context, although these requirements would not necessarily be omitted or ambiguous when viewed as requirements alone. The design context sometimes causes inconsistencies among implementations that realize the same requiremen...
| Main Authors: | , |
|---|---|
| Format: | Article |
| Language: | English |
| Published: |
IEEE
2022-01-01
|
| Series: | IEEE Access |
| Subjects: | |
| Online Access: | https://ieeexplore.ieee.org/document/9739666/ |
| _version_ | 1818744976670982144 |
|---|---|
| author | Michiyo Wakimoto Shuji Morisaki |
| author_facet | Michiyo Wakimoto Shuji Morisaki |
| author_sort | Michiyo Wakimoto |
| collection | DOAJ |
| description | Some software requirements are omitted or ambiguous depending on the design context, although these requirements would not necessarily be omitted or ambiguous when viewed as requirements alone. The design context sometimes causes inconsistencies among implementations that realize the same requirement. Existing detection and analysis methods do not limit evaluation of review materials to implementations of context-dependent design. An evaluation technique that limits the evaluated parts to the parts describing context-dependent design implementations is expected to be efficient. This paper proposes a method for detecting inconsistent implementations (context-dependent requirement defects) caused by context-dependent requirement omissions and ambiguities in design reviews. The proposed method defines goal-oriented check items for design review using a goal tree obtained by goal-oriented requirements analysis. Reviewers use the goal-oriented check items to detect inconsistent implementations that realize the same requirement. This paper also evaluates the proposed method through a case study. The results of the case study showed that the proposed method defined five goal-oriented check items and that reviewers detected 24 context-dependent requirement defects with goal-oriented check items. The results also showed that the sum of the estimated additional effort to define goal-oriented check items and perform design reviews with goal-oriented check items was 19.6 person-hours. Furthermore, the results showed that an engineer with general skills and knowledge of software development but without system-specific skills and knowledge could define a goal tree and the corresponding goal-oriented check items. |
| first_indexed | 2024-12-18T02:52:52Z |
| format | Article |
| id | doaj.art-edf329ebf73d46d1a24e28bad13663f9 |
| institution | Directory Open Access Journal |
| issn | 2169-3536 |
| language | English |
| last_indexed | 2024-12-18T02:52:52Z |
| publishDate | 2022-01-01 |
| publisher | IEEE |
| record_format | Article |
| series | IEEE Access |
| spelling | doaj.art-edf329ebf73d46d1a24e28bad13663f92022-12-21T21:23:26ZengIEEEIEEE Access2169-35362022-01-0110325843259410.1109/ACCESS.2022.31615459739666Goal-Oriented Software Design ReviewsMichiyo Wakimoto0https://orcid.org/0000-0003-4873-9616Shuji Morisaki1https://orcid.org/0000-0002-8290-0584Graduate School of Informatics, Nagoya University, Nagoya, Aichi, JapanGraduate School of Informatics, Nagoya University, Nagoya, Aichi, JapanSome software requirements are omitted or ambiguous depending on the design context, although these requirements would not necessarily be omitted or ambiguous when viewed as requirements alone. The design context sometimes causes inconsistencies among implementations that realize the same requirement. Existing detection and analysis methods do not limit evaluation of review materials to implementations of context-dependent design. An evaluation technique that limits the evaluated parts to the parts describing context-dependent design implementations is expected to be efficient. This paper proposes a method for detecting inconsistent implementations (context-dependent requirement defects) caused by context-dependent requirement omissions and ambiguities in design reviews. The proposed method defines goal-oriented check items for design review using a goal tree obtained by goal-oriented requirements analysis. Reviewers use the goal-oriented check items to detect inconsistent implementations that realize the same requirement. This paper also evaluates the proposed method through a case study. The results of the case study showed that the proposed method defined five goal-oriented check items and that reviewers detected 24 context-dependent requirement defects with goal-oriented check items. The results also showed that the sum of the estimated additional effort to define goal-oriented check items and perform design reviews with goal-oriented check items was 19.6 person-hours. Furthermore, the results showed that an engineer with general skills and knowledge of software development but without system-specific skills and knowledge could define a goal tree and the corresponding goal-oriented check items.https://ieeexplore.ieee.org/document/9739666/Context-dependent requirement (CDR)goal-oriented reviewssoftware reviewssoftware quality |
| spellingShingle | Michiyo Wakimoto Shuji Morisaki Goal-Oriented Software Design Reviews IEEE Access Context-dependent requirement (CDR) goal-oriented reviews software reviews software quality |
| title | Goal-Oriented Software Design Reviews |
| title_full | Goal-Oriented Software Design Reviews |
| title_fullStr | Goal-Oriented Software Design Reviews |
| title_full_unstemmed | Goal-Oriented Software Design Reviews |
| title_short | Goal-Oriented Software Design Reviews |
| title_sort | goal oriented software design reviews |
| topic | Context-dependent requirement (CDR) goal-oriented reviews software reviews software quality |
| url | https://ieeexplore.ieee.org/document/9739666/ |
| work_keys_str_mv | AT michiyowakimoto goalorientedsoftwaredesignreviews AT shujimorisaki goalorientedsoftwaredesignreviews |