From UML Activity Diagrams to Specification Requirements
| dc.contributor.author | Drusinsky, Doron | |
| dc.contributor.department | Computer Science (CS) | |
| dc.date.accessioned | 2014-03-25T16:47:06Z | |
| dc.date.available | 2014-03-25T16:47:06Z | |
| dc.date.issued | 2008 | |
| dc.description | The research reported in this article was funded in part by a grant from NASA. The views and conclusions contained herein are those of the authors and should not be interpreted as necessarily representing the official policies or endorsements, either expressed or implied, of the U.S. Government. The U.S. Government is authorized to reproduce and distribute reprints for Government purposes notwithstanding any copyright annotations thereon. | en_US |
| dc.description.abstract | Formal verification of system-of-systems uses computer-based techniques to assure that the behavior of a subject system of systems complies with its formal correctness specifications. Such formal specifications are often created on the basis of natural-language (NL) requirement specifications. While NL documents such as marketing requirement documents and concept-ofoperation (CONOPS) documents contain NL requirements, they are almost never complete, i.e., they omit necessary NL requirements. To that end, UML analysis is an increasingly popular technique for requirement elicitation. This paper describes the process of identifying NL requirements of interest from UML analysis diagrams such as activity diagrams) and Message Sequence Diagrams. | en_US |
| dc.identifier.uri | https://hdl.handle.net/10945/39586 | |
| dc.rights | This publication is a work of the U.S. Government as defined in Title 17, United States Code, Section 101. Copyright protection is not available for this work in the United States. | en_US |
| dc.title | From UML Activity Diagrams to Specification Requirements | en_US |
| dc.type | Article | en_US |
| dspace.entity.type | Publication |
Files
Original bundle
1 - 1 of 1