| R. Wieringa and E Dubois. Integrating semi-formal and formal software specification techniques. Information Systems, 23(3-4):159--78, 1998. |
....requirements documents, an approach for generating MSCs from Use Case Maps (UCMs [BuC96] which is introduced in [MAB01] can be applied. The information that is contained in the Use Case Maps diagrams can be considered as being similar to the information stored in the semi1. In accordance to [WiD94], we regard semi formal documents as documents that contain information in a structured form, which allows manipulation of the data conforming to its intended semantics. formal documents of our PROBAnD method (e.g. traceability between requirements is modeled in UCMs through paths that connect ....
R. Wieringa, E. Dubois. "Integrating Semi-formal and Formal Software Specification Techniques" in Information Systems. 19(4). Elsevier Science Ltd. 1994. pp. 35--54
.... Modeling Problem Description Final System Operational Requirements Specification Operational Document Generation Semi Formal Document Parsing Requirements Description Semi formal Requirements Specification Product Model System Prototype Prototype Structure (Domain Specific) Semantics = Wieringa et al.] Classification of Product Model Entities Configuration Document aggregatedArtefact Artefact FeatureView Feature aggregatedArtefact 1. Sub Activity: Document Parsing Artefact aggregatedArtefact Configuration aggregatedArtefact Feature 1. 1. Feature Extraction Document ....
R. Wieringa, E. Dubois. "Integrating Semi-formal and Formal Software Specification Techniques " in Information Systems. 19(4). Elsevier Science Ltd. 1994. pp. 35--54
....The corresponding path through the magic square starts at the upper left corner and moves sufficiently right and down to determine the overall functionality and architecture of the system. It then performs a linear process for each increment of the system. Other strategies are possible too [24, 57, 61]. In each strategy, decisions about interactions and architectures are intertwined in a particular way. In whatever way this is done, the result of these decisions must be justifiable as if they were taken by means of a rational design process [41] This is the design analogy to the way in which ....
R.J. Wieringa and E. Dubois. Integrating semi-formal and formal software specification techniques. Information Systems, 23(3/4), 1998.
.... 2 The TRADE Framework The framework to be presented here is based upon an analysis of frameworks for industrial product engineering [29] and systems engineering [11, 12] It has been applied to requirements engineering methods [34] and to integrated formal semiformal requirements specification [38]. At the top level of the framework, we can identify four dimensions in any system development (software and non software) These dimensions are orthogonal in the sense that the choices of techniques and methods in each of them are largely independent of each other. Time. The temporal ....
....to be combined with any formal specification language that can talk about events and responses (i.e. external system functions) and logical data structures. It has been applied to an industrial case study in combination with the Albert II specification language, which is based upon temporal logic [4, 38]. It has also been applied in combination with dynamic logic to the specification of an industrial production cell [33] I am currently looking at formalizing parts of the UML within the TRADE framework [37] The next section discusses the approach of this formalization. 3 Mapping the UML to ....
R.J. Wieringa and E. Dubois. Integrating semi-formal and formal software specification techniques. Information Systems, 23(3/4), 1998.
No context found.
R. Wieringa and E Dubois. Integrating semi-formal and formal software specification techniques. Information Systems, 23(3-4):159--78, 1998.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC