Loading...
|
Please use this identifier to cite or link to this item:
http://140.128.103.80:8080/handle/310901/22215
|
| Title: | Providing a behavioral and static formal model to elicit the functional software requirement |
| Authors: | Wang, C.-H., Chu, W.C., Wang, F.-J. |
| Contributors: | Dept. of Computer Science, Tunghai University, |
| Keywords: | Goal-Oriented definition language;Requirement specification;Software requirement |
| Date: | 2005-08-15 |
| Issue Date: | 2013-05-15T09:13:10Z (UTC)
|
| Publisher: | Las Vegas, NV; United States |
| Abstract: | Information techniques have been changing in the past few years. Facing the highly changeable environment, software development encounters more and more difficulties and challenges because extracting the requirements of products is getting more difficult than before. Since the correctness of product requirements is the key point determining the success or failure of project developments. However, there is no perfect solution currently. Additionally, requirements are often written in a natural language that is inherently ambiguous. One way to avoid the ambiguity is to write the requirement specifically within a particular required specification language [5]. Consequently, requirement specification should use a special descriptive language to comprise several essential parts, namely, the purposes of specification, terms definition, specific constrains, audiences, and communication interfaces, which dominate the development effort. However, these parts have always been ignored in previous studies. In this article, we propose a requirement specification formal model which synthesizes a behavior model from the scenario [1] and operational software model [2] from goal-oriented requirement elaboration [2][3][4] to refer to the IEEE recommended practice for software requirements specifications [5]. The proposed formal model may help developers produce data in proper sequence, establish the basis functional requirement according to the top level goal under inviolate limitation, specify components interaction time slide consider system essential components, and organize the outside communication interfaces of the system referring components interaction scenario. ? 2005 IEEE. |
| Relation: | Proceedings of the 2005 IEEE International Conference on Information Reuse and Integration, IRI - 2005 2005 , art. no. 1506447 , pp. 44-49 |
| Appears in Collections: | [資訊工程學系所] 會議論文
|
Files in This Item:
| File |
Size | Format | |
|---|
| index.html | 0Kb | HTML | 212 | View/Open |
|
All items in THUIR are protected by copyright, with all rights reserved.
|
