NDLI: Structured analysis and object oriented analysis

Please wait, while we are loading the content...

The design of the C++ Booch Components

An iterative-design model for reusable object-oriented software

Graphical specification of object oriented systems

Viewing object as patterns of communicating agents

LO and behold! Concurrent structured processes

Actors as a special case of concurrent constraint (logic) programming

Beyond schema evolution to database reorganization

Kaleidoscope: mixing objects, constraints, and imperative programming

What tracers are made of

A logical theory of concurrent objects

Message pattern specifications: a new technique for handling errors in parallel object oriented systems

Garbage collection of actors

Structured analysis and object oriented analysis

Strong typing of object-oriented languages revisited

Type substitution for object-oriented programming

A parallel object-oriented language with inheritance and subtyping

Contracts: specifying behavioral compositions in object-oriented systems

When objects collide experiences with reusing multiple class hierarchies

PCLOS: stress testing CLOS experiencing the metaobject protocol

Reasoning about object-oriented programs that use subtypes

Type consistency of queries in an object-oriented database system

Issues in object database management

A framework for visualizing object-oriented systems

Painting multiple views of complex objects

MoDE: a UIMS for Smalltalk

COOL: kernel support for object-oriented environments

The performance of an object-oriented threads package

Object-oriented real-time language design: constructs for timing constraints

OOP in the real world

Mixin-based inheritance

The point of view notion for multiple inheritance

Exception handling and object-oriented programming: towards a synthesis

OOPSLA distributed object management

Structured analysis and object oriented analysis

Content Provider	ACM Digital Library
Author	Jacobson, Ivar Constantine, Larry Ward, Paul Mellor, Stephen de Champeaux, Dennis Yourdon, Edward
Abstract	The object-oriented paradigm still faces an open challenge: Delivering huge software systems routinely and cost effectively. To quote Ed Yourdon: “A system composed of 100,000 lines of C++ is not be sneezed at, but we don't have that much trouble developing 100,000 lines of COBOL today. The real test of OOP will come when systems of 1 to 10 million lines of code are developed.”Although the object-oriented community has an opening flirtation with exploratory programming and rapid prototyping by exploiting reuse via inheritance, there is for now, in my opinion, no hope that huge systems can be developed without giving due attention to what a target system is supposed to do. Which should produce an (electronic) (graphical) (Pseudo-formal) document, the requirements, that a customer can initially sign off. We believe as well that for huge systems a programming language independent design activity, that bridges the requirements and the actual programming effort, is mandatory. It goes without saying that we do not suggest that these activities constitute a waterfall sequence.Consequently, the object-oriented community needs to address the question whether well established analysis techniques, like Structured Analysis, Jackson's JSD, etc. can be reused for object-oriented system development or whether a dedicated object-oriented analysis (and design) method is called for.The panel members have been asked to consider the following of question: What is the relationship between Structured Analysis (SA) and Object Oriented Analysis (OOA)?More specifically:Can SA be used effectively to produce the requirements for a system that will be designed and implemented in an OO fashion?If not, is it possible to adjust SA, what needs to be added? If SA cannot be used at all, what is the key obstacle?In case SA and OOA have different applicability ranges, how do we circumscribe — positively and negatively - these ranges? Any overlap?We appreciate that the organizing committee of this conference has selected this crucial topic.
Starting Page	135
Ending Page	139
Page Count	5
File Format	PDF
ISBN	0897914112
DOI	10.1145/97945.97962
Language	English
Publisher	Association for Computing Machinery (ACM)
Publisher Date	1990-09-01
Publisher Place	New York
Access Restriction	Subscribed
Content Type	Text
Resource Type	Article

Sl.	Authority	Responsibilities	Communication Details
1	Ministry of Education (GoI), Department of Higher Education	Sanctioning Authority	https://www.education.gov.in/ict-initiatives
2	Indian Institute of Technology Kharagpur	Host Institute of the Project: The host institute of the project is responsible for providing infrastructure support and hosting the project	https://www.iitkgp.ac.in
3	National Digital Library of India Office, Indian Institute of Technology Kharagpur	The administrative and infrastructural headquarters of the project	Dr. B. Sutradhar bsutra@ndl.gov.in
4	Project PI / Joint PI	Principal Investigator and Joint Principal Investigators of the project	Dr. B. Sutradhar bsutra@ndl.gov.in Prof. Saswat Chakrabarti will be added soon
5	Website/Portal (Helpdesk)	Queries regarding NDLI and its services	support@ndl.gov.in
6	Contents and Copyright Issues	Queries related to content curation and copyright issues	content@ndl.gov.in
7	National Digital Library of India Club (NDLI Club)	Queries related to NDLI Club formation, support, user awareness program, seminar/symposium, collaboration, social media, promotion, and outreach	clubsupport@ndl.gov.in
8	Digital Preservation Centre (DPC)	Assistance with digitizing and archiving copyright-free printed books	dpc@ndl.gov.in
9	IDR Setup or Support	Queries related to establishment and support of Institutional Digital Repository (IDR) and IDR workshops	idr@ndl.gov.in

Using object oriented structured development to implement a hybrid system

Panel: object oriented requirements analysis vs. structured analysis as a front end for object oriented design

Bridging the gap between structured requirements and object-oriented analysis and design.

A Software Requirements Engineering Methodology Comparative Analysis: Structured Analysis, Object-Oriented Analysis, and Problem Frames (2002)

Using object modeling to transform structured analysis into object oriented design

Transitioning from structured analysis to object-oriented design

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

A process for combining object oriented and structured analysis and design

CASAT-HOOMT: Computer Aided Software Analysis Tool Based on High Order Object-Oriented Modeling Technique

Structured analysis and object oriented analysis

Similar Documents

Using object oriented structured development to implement a hybrid system

Panel: object oriented requirements analysis vs. structured analysis as a front end for object oriented design

Bridging the gap between structured requirements and object-oriented analysis and design.

A Software Requirements Engineering Methodology Comparative Analysis: Structured Analysis, Object-Oriented Analysis, and Problem Frames (2002)

Using object modeling to transform structured analysis into object oriented design

Transitioning from structured analysis to object-oriented design

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

A process for combining object oriented and structured analysis and design

CASAT-HOOMT: Computer Aided Software Analysis Tool Based on High Order Object-Oriented Modeling Technique

Structured analysis and object oriented analysis