Databases Reference
In-Depth Information
Viewer.getControl()
AppAction.<init>()
AppAction.setText(String)
AppAction.setToolTipText(String)
MenuManager.<init>(String)
MenuManager.setRemoveAllWhenShown(Boolean)
AppMenuListener.<init>()
MenuManager.addMenuListener(AppMenuListener)
MenuManager.createContextMenu(Control)
FIGURE 1.3: Frequent pattern of usage. Context menu using JFace.
must be preceded by an \allocation", etc. Some examples of these rules are
shown in Figure 1.4.
KeAcquireSpinLock -> KeReleaseSpinLock
ExAcquireFastMutex -> ExReleaseFastMutex
ExAllocatePoolWithTag -> ExFreePool
zfcp_reqlist_alloc -> zfcp_reqlist_free
zfcp_fsf_alloc -> zfcp_fsf_req_free
xfrm_policy_alloc -> xfrm_policy_destroy
FIGURE 1.4: Temporal rules: Windows (top) and Linux (bottom).
Another form of specifications is sequence diagram which is composed
of lifelines and messages. They are intuitive to capture the communication
among the various objects through various method calls. There are also some
extensions to standard UML sequence diagrams including Message Sequence
Charts (MSC), which is the standard of International Telecommunication
Union (ITU) [33] and Live Sequence Chart (LSC) [16] that extends MSC with
modalities. LSC is able to express a rule-like property in the form of a modal
sequence diagram. An example of a Live Sequence Chart is shown in Fig-
ure 1.5. It captures the constraint \whenever
PictureChat
calls the
Backend
method
getMyJID()
, and sometime in the future the
PictureHistory
calls
the
Backend
method
send()
, eventually the latter must call the
send()
method of
Connect
and
Connect
must call the
send()
method of
Output
."
From Table 1.1, we notice that there are many studies extracting finite
state machines and rules/patterns. There are also a good number of stud-
ies mining other forms of specifications including value-based invariants and
sequence diagrams.
Search WWH ::
Custom Search