A. Sutcliffe. Jackson System Development. PrenticeHall,  Home/Search   Document Not in Database   Summary   Related Articles   Check

.... integrate object oriented modelling with Structured Analysis [1, 2, 38, 44, 47] The possibility to combine Jackson System Development (JSD) with an object oriented approach has also roused interest [4] The possibility to combine JSD modelling with ER modelling is briefly discussed by Sutcliffe [42], but is not studied there in detail. These attempts at integration can be taken one step further by showing that there is an underlying idea of these different methods, that can be used as a guideline for combining different methods. It is the aim of this paper to show that there is such an ....

....Throughout the argument, the transaction decomposition table plays a pivotal role. Section 6 discusses how function decomposition and object oriented decomposition can be combined, and section 7 concludes the paper. 2 Jackson System Development (JSD) The major ideas behind JSD are the following [6, 23, 31, 42]: ffl A system model must be partitioned into a model of the universe of discourse (UoD) of the system and a model of the functions of the system. In a database system, the UoD is that part of the world about which the system registers data. In a control system, the UoD is that part of its ....

A. Sutcliffe. Jackson System Development. PrenticeHall,

....are used to design the structure of the information that is manipulated by the system. Recently, several methods for modeling and designing real time systems based on object orientation have been developed, suchasROOM[55] 3.2. Jackson Systems Development (JSD) Jackson Systems Development (JSD)[31, 60] supports seamlessly the processes from requirements analysis to implementation phase. The idea of seamless support of the whole of software development processes is taken to the recent object oriented methods. JSD consists of three phases to construct the systems which are solid to specification ....

A. Sutcliffe. Jackson System Development.Prentice Hall, 1988.

....on the methodology. 2 The Methodology The system design methodology chosen for this example was the Jackson System Development method (JSD) JSD was chosen simply because, of all the system design methodologies that we investigated, JSD had the best introductory material to which we had access [Sut 88] Initially, we envisioned using EVES tools and techniques in all stages of JSD. This would involve specifying and verifying functionalities during the stages of JSD. However, we concluded that this would contravene the spirit of JSD. JSD discourages thinking about functionalities early in the ....

....The method of JSD is organized into three stages, each of which makes extensive use of diagrams: ffl the modelling stage, ffl the network stage, and ffl the implementation stage. The following subsections briefly describe the three stages of JSD. For a more elaborate tutorial on JSD, see [Sut 88] 4.1 The Modelling Stage In the modelling stage, the developer models the system by identifying the system objects (called entities) and the actions on those objects. The intent is to have the model capture all relevant properties of the real world system being modelled. The modelling stage of ....

Sutcliffe, Alistair. Jackson System Development. Prentice Hall, New York, 1988.

.... the attention of a number of researchers [1, 3, 20, 26, 28] The possibility to combine Jackson System Development (JSD) with an object oriented approach has also roused interest [5] The possibility to combine JSD modelling with Entity Relationship (ER) modelling is briefly discussed by Sutcliffe [25], but is not studied there in detail. A comparison of JSD with other methods is useful for at least the following reasons. JSD plays an interesting role in these comparisons, for it This makes comparisons between JSD and other methods relevant in two ways. ffl First, JSD shares with ....

....[11] In addition, as argued in section 5, these reasons for incomatibility carry over to modern object oriented methods and show why using data flow models in combination with object oriented models may cause problems. 2 Jackson System Development Although there are several versions of JSD [7, 15, 17, 25], their differences do not concern us here. In this section, I describe what is common to these different versions. 2.1 UoD models JSD distinguishes models of a database system (DBS) from models of the universe of discourse (UoD) represented by that database system. A UoD model represents the ....

[Article contains additional citation context not shown here]

A. Sutcliffe. Jackson System Development. Prentice-Hall, 1988.

....this. Hierarchical component structures are built using composition, iteration and alternation. We introduce these structures with a graphical notation and show how their performance can be analysed. The graphic notation borrows heavily from that of the Jackson Structured Programming technique [2] [3] 2.1 Composition We use tree like diagrams to show that a component is in fact the composition of a number of components. For example, if a component P, in its execution, calls the components Q and R, we get the diagram shown in Figure 2. 2.1.1 Graphic Notation In Figure 2, P calls component ....

Alistair Sutcliffe, Jackson System Development, Prentice Hall, UK, 1988.

....the transition from SA to OOA. The approach in this paper is to take elements of OOA that can be found in Booch s [7, 8] work on object oriented development and design, and combine this with elements of a traditional information system (IS) development method, Jackson System Development (JSD) [10, 21, 29, 34]. In a companion paper, JSD is analyzed in detail as a method for developing formally specified object oriented models [39] In section 2, we look at an example CM from Gane and Sarson [15] Using this example in section 3, I contrast the task ordering advised by SA and OOA with respect to ....

.... that are common are ffl listing common nouns in descriptions of the UoD [1] ffl looking for real world objects with which the system must interact (these are the external entities in SA) and ffl listing the principal actors that help to solve the problem which the IS is designed to solve [34]. 4.1.2 Objects in SA Although SA is function oriented, it cannot help encountering objects. For example, following Alabiso [2] obvious candidates for objects in a DFD are external entities and data stores in a DFD. However, applying the criteria for objects listed above, we can do better than ....

[Article contains additional citation context not shown here]

A. Sutcliffe. Jackson System Development. Prentice-Hall, 1988.

....the program state machine (PSM) 9] combines the previous two models by permitting each state of a hierarchical concurrent FSM to contain actions described using program instructions. Other models include Petri nets [10] flowcharts [6, 11] entity relationship diagrams [12] Jackson diagrams [13], control dataflow graphs [14] object oriented models [15] and queueing models [16] No one model is ideal for all classes of systems. For example, the dataflow model may be most natural to use for a system that repeats the same data transformations over time on streams of data, such as a ....

A. Sutcliffe, Jackson System Development. New York: Prentice-Hall, 1988.

....in the software engineering literature. Dealing with event permutation requires guarded commands to be designed. The requirements specification can be elaborated with entity life histories which express patterns of correct and incorrect events in a sequential order; see Jackson s method [21] [22]. As Jackson points out, a filter process can be specified to detect abnormal events by test probes in a normal input sequence and then take corrective action if an unexpected event is detected. If the dependencies between the scenario and components in the intended system are predictable then ....

Sutcliffe A.G., Jackson system development. Prentice Hall, 1988.

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