Structured analysis—formal design, using stream and object oriented formal specifications

1990 ◽  
Author(s):  
Hans Toetenel ◽  
Jan van Katwijk ◽  
Nico Plat
Keyword(s):  
Object Oriented ◽  
Formal Specifications ◽  
Structured Analysis ◽  
Formal Design

scholarly journals Object Oriented VS Structured Analysis and Design in System Development Courses

2019 ◽  
Vol 8 (6S3) ◽  
pp. 82-88
Keyword(s):  
System Analysis ◽  
Survey Methodology ◽  
System Development ◽  
Object Oriented ◽  
Analysis And Design ◽  
Institutions Of Higher Learning ◽  
Structured Analysis ◽  
The One ◽  
Structured Analysis And Design

Objectives: The main aim of this study was to investigate the factors that influence students’, academicians’, clients’, as well as developer’s preferences in choosing their preferred approach in system development, namely structured analysis design (SAD) or object-oriented analysis and design (OOAD). Methods: The research design was based on a survey methodology and a case study. For the survey, questionnaires were administered to 30 students and 38 academicians, who were randomly selected from several Malaysian universities. For the case study, the requirements of the information system were modeled and presented to several clients to elicit their feedback. The survey data were analyzed using SPSS Findings: The result shows that students preferred the use of OOAD approach, which clearly outnumbered those who preferred the SAD approach, which stood at 33%. Interestingly, the majority (53%) of academicians preferred the use of a mixture of both approaches. Likewise, the clients shared a similar view with the academicians, whereas the developer preferred the OOAD approach. Application/Improvements: Clearly, the findings suggest that both approaches are essential, but the one that is widely used by developers and preferred by students is OOAD, and thus should be given priority when it comes to structured analysis and design. As such, curriculum designers and institutions of higher learning, particularly those offering system analysis and design and related courses, should make the necessary changes to the existing curriculum such that the academic programs offered will be able to produce highly competent and skilled analysts and designers as required by the industry.

TEST SCENARIO GENERATION BASED ON FORMAL SPECIFICATION AND USAGE PROFILE

2000 ◽  
Vol 10 (02) ◽  
pp. 185-201 ◽  
Author(s):  
KAI H. CHANG ◽  
SHIH-SUNG LIAO ◽  
RICHARD CHAPMAN ◽  
CHUN-YU CHEN
Keyword(s):  
Formal Specification ◽  
State Transition ◽  
Object Oriented ◽  
The State ◽  
State Model ◽  
Scenario Generation ◽  
Formal Specifications ◽  
Test Scenario ◽  
Transition Diagram ◽  
State Transition Diagram

This paper presents a method for test scenario generation based on formal specifications and usage profiles. It is a major component of a framework for testing object-oriented programs. In this framework, the requirements of a software system are formally specified. The anticipated application of the system is expressed in a usage profile, which is a state model that indicates the dynamic behavior of the system and execution probabilities for the behaviors. The state model is used as a guide to derive the anticipated operation scenarios. An enhanced state transition diagram is used to represent the state model, which incorporates hierarchy, usage and parameter information. Since the number of feasible scenarios can be extremely large, probability and importance criteria are used to select the most probable and important scenarios.

scholarly journals An Efficient Comparison between Structured Analysis and Object-Oriented Analysis

2021 ◽  
pp. 290-295
Author(s):  
Maulik V. Dhamecha
Keyword(s):  
Object Oriented ◽  
Information Systems Development ◽  
Analysis And Design ◽  
Know How ◽  
Software Analysis ◽  
Develop Software ◽  
Structured Analysis ◽  
Analysis Design ◽  
Object Oriented Approach ◽  
Structured Approach

if you want to find out that which is the best suitable analysis then you have to find outs all the merits and demerits of that both analysis methods. The aspect of this paper is to describe combine both the traditional (structured) and the object-oriented approach, certain methodology for information systems development. Despite the fact that objects-oriented paradigm is actually widely adopted for software analysis, design, and implementation, there are still a large number of companies that continue to utilize the structured approach to develop software analysis and design. The empirical study that we present considers both an Uncontrolled and a controlled experiment with Master students. with the existing structured approach of developing a system there is significant way to know how appropriate the OO topics. So, in recent time, Objects-orientation analysis is largely acceptable subject. This paper discourses some basics about these two design paradigms.

scholarly journals USING UML SCENARIOS IN B2B SYSTEMS

2010 ◽  
Vol 11 (1) ◽  
pp. 1-13 ◽  
Author(s):  
A. Jakimi ◽  
A. Sabraoui ◽  
E. Badidi ◽  
A. Salah ◽  
M. El Koutbi
Keyword(s):  
Unified Modeling Language ◽  
Object Oriented ◽  
Tool Support ◽  
Use Case ◽  
Formal Specifications ◽  
Sequence Diagrams ◽  
Unified Modeling ◽  
Suitable Framework ◽  
Business To Business ◽  
Scenario Approach

Scenarios has become a popular technique for requirements elicitation and specification building. Since scenarios capture only partial descriptions of the system behavior, an approach for scenario composition and/or integration is needed to produce more complete specifications. The Unified Modeling Language (UML), which has become a standard notation for object-oriented modeling, provides a suitable framework for scenario acquisition using Use Case diagrams and Sequence or Collaboration diagrams. In this paper, we suggest an algorithmic and tool support for composing and integrating scenarios that are represented in form of sequence diagrams. We suggest four operators (;: sequential operator, ||: concurrent operator, ?: conditional operator and  * :iteration operator) to compose a set of scenarios that describe a use case of a given system. In this paper, we suggest also to apply the scenario approach to B2B systems (Business to Business). We propose to develop B2B systems as a three activities process deriving formal specifications and code skeletons from UML scenarios. Activities of this proposed process are generally automatic and are supported by a set of developed algorithms and tools.

scholarly journals On Differencing Object-Oriented Formal Specifications.

2010 ◽  
Vol 9 (1) ◽  
pp. 183 ◽  
Author(s):  
Fathi Taibi ◽  
Md. Jahangir Alam ◽  
Junaidi Abdullah
Keyword(s):  
Object Oriented ◽  
Formal Specifications
Sign in / Sign up

Export Citation Format

Share Document