Table II summarizes the SE activities that our approach addresses and how they relate
to the life-cycle phases described in the Section 3.2.Dataflow specification is a cross-lifecycle
activity related to data semantics and data linking designed to build a dataflow
among components, which runs parallel to all other lifecycle activities.
The following is a description of how to use FAST to develop each activity.
—Requirements. Users have to explicitly state what solution they are looking for in
natural language. The FAST framework parses the statement using NPL techniques
and analyses possible keywords. It uses these keywords to search a set of off-the-shelf
components possibly of interest to users. This is one way of guiding users through
this activity, but any of the other approaches for moving from requirements to design
described in the state of art can be implemented.
Figure 1 shows how FAST recommends components for the problem stated by
users. Users enter the problem description at the bottom of the screen. The framework
then uses context information, information on use by other users and component
catalogue data to provide advice on how to tackle the part of the problem that
returns most results and on which components they should analyse for use to design
their solution.
—Analysis. Users use data supplied by the framework (see right side of Figure 1)
to analyse the components recommended in the requirements activity and rework
ACM Transactions