Behavioral views for software requirements engineering

Isazadeh, Ayaz; Lamb, David; MacEwen, Glenn H.

doi:10.1109/ecbs.1996.494542

Cited by 6 publications

(15 citation statements)

References 54 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…A client's view of a server, for example, is the behavior that the client expects from the server. Isazadeh argues that a fully-developed methodology based on views would significantly reduce the complexity of creating and understanding software requirements [11]. He takes some efficient steps towards such a methodology.…”

Section: Viewchartsmentioning

confidence: 99%

“…The SEPARATE composition has been explained by renaming the events as in [8]. Here we also rename the events and then replace SEPARATEed views by ANDed views and continue the process upwards in the hierarchy of views.…”

Section: Formal Descriptionmentioning

confidence: 99%

“…In his Ph.D. thesis [8], Isazadeh introduces the notion of software behavioral views. Intuitively, this is a complete description of the behavior of a system observable from a specific point of view.…”

Section: Viewchartsmentioning

confidence: 99%

“…The next logical work was to extend FSM in hopes of overcoming this complexity. This work include Jahanian and Mok's Modechart [12] [2,3,4,5], and Isazadeh's Viewcharts [10,8]. We believe that the Viewcharts formalism for its ability in combining the notion of view with an extended FSM provides a good method for large-scale systems requirements specification.…”

Section: Introductionmentioning

confidence: 99%

“…We believe that the Viewcharts formalism for its ability in combining the notion of view with an extended FSM provides a good method for large-scale systems requirements specification. There has been two semantics provided for Viewcharts: An algorithmic semantics [9] and a set theory based semantics [8], both of which, establish the semantics of Viewcharts via translation to Statecharts. Still, due to the visual nature of Viewcharts, it can be viewed as a graph.…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

A graph theoretic semantics for viewcharts

Mehri

Isazadeh²

2006

imf

Self Cite

View full text Add to dashboard Cite

Most of current methods for systems behavioral specifications are suitable only for small systems. Behavioral requirements engineering of large-scale software systems using current Formal Description Techniques (FDT), is complex and difficult. In general, when the scale of the system grows linearly, the number of states (in FSM-based methods) grow exponentially. Therefore, much research continues on introducing new techniques for eliminating (or at least reducing) this problem.The introduction of Viewcharts is a considerable step in this direction. Work on the semantics of Viewcharts, however, is limited to its semantics via translations to Statecharts. We believe that due to the visual nature of the Viewcharts formalism, a graph theory based semantics is more suitable to establish a sound foundation for the formalism. Furthermore, since FSMs are more established and have stronger foundation than Statecharts, we prefer an FSM-based semantics. In this paper we provide a semantics for Viewcharts based on solely FSMs and graph theory.

show abstract

Section: Viewchartsmentioning

confidence: 99%

Section: Formal Descriptionmentioning

confidence: 99%

Section: Viewchartsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

A graph theoretic semantics for viewcharts

Mehri

Isazadeh²

2006

imf

Self Cite

View full text Add to dashboard Cite

show abstract

Behavioural Views for Software Requirements Engineering

1999

Self Cite

View full text Add to dashboard Cite

This paper introduces the idea of a software behavioural view: intuitively, this is a complete description of the behaviour of the system observable from a specific point of view. We believe that a fully developed methodology based on views would significantly reduce the complexity of creating and understanding software requirements. In this paper we take the first steps towards such a methodology. We define a formal notation, Viewcharts, with a well-defined semantics based on Statecharts. Viewcharts gives a means for precisely describing views and their compositions. We show that Viewcharts reasonably capture the informal idea of a view by giving an example: a manufacturing control system. We show that Viewcharts have some advantages over Statecharts; in particular, Viewcharts add name space control to limit the scope of broadcast communication, solving a problem with Statecharts presented by Harel.

show abstract

Software reliability assessment based on a formal requirements specification

Alipour

Isazadeh

2008

2008 Conference on Human System Interactions

View full text Add to dashboard Cite

Assessment of reliability using characteristics of software development process phases is one of the discussions which has been attracting more and more attentions during the recent three decades. Most of the techniques and models use the result of design, implementation and test phases; there are only a few models that are employed at the early phase of software development. Assessment of software reliability in the early phases of software development process, however, is very important for better prognosis and management of risks. In this paper we propose an approach for early software reliability assessment, based on software behavioral requirements. The major difference between our approach and those of others is the fact that we use a formal method, called Viewcharts, to specify the behavior of software systems.

show abstract

Behavioral views for software requirements engineering

Cited by 6 publications

References 54 publications

A graph theoretic semantics for viewcharts

A graph theoretic semantics for viewcharts

Behavioural Views for Software Requirements Engineering

Software reliability assessment based on a formal requirements specification

Contact Info

Product

Resources

About