StudentHandout.MCA412.oos.150310

8/4/2019 StudentHandout.MCA412.oos.150310

http://slidepdf.com/reader/full/studenthandoutmca412oos150310 1/18

Object Oriented Systems- Preamble (Student Handout)

Version- 1.0

OBJECT ORIENTED SYSTEMS – PREAMBLE

(STUDENT HANDOUT)

VERSION – 1.0

PROJECT NAME- An Approach towards Excellence in

Teaching & Learning Methodology

PROJECT OWNER- XYZ

PROJECT NAME Email- IdCREATED

BY

DATE OF RELEASE-

NEXT PLANNED RELEASE DATE-

SGI PROPERTY – The Handout should be distributed to the students of Master Of Computer

Application Branch studying in 4th semester of their Three Year Post Graduate Degree Course.

TABLE OF CONTENTS

holistiC fix 3

1) Object Modeling (Class & Object) 4

2) Link and Association 4

3) Generalization 5

4) Aggregation & Composition 6

5) Dynamic Modeling 7

6) State 7

7) State Diagram for Phone Line 8

7) Event 8

SGI Property Page 3 of 19




Version- 1.0

9) Event Trace in a Telephone System 8

10) Functional Modeling 9

11) External Entity and Process 10

12) Data Flow and Stores 11

13) Java features 12

RESEARCH RELATED TO DIGITAL COMMUNICATION 13

OTHER AREAS OF RESEARCH WITH THEIR LINKS 14

TOP FIVE COMPANIES OF OBJECT ORIENTED SYSTEMS WITH LINKS 15

PROJECTS THAT CAN BE DONE 15

TRENDS GOING ON FOR DIGITAL COMMUNICATIONS 18

HOLISTIC FIX

● It resembles a comprehensive view of the subject with its pre and postrequirements along with its application in allied fields.

Object Oriented Systems Key Concepts

Basic Knowledge of Computer Fundamentals (Before Graduation)

1. Object Modeling (Object and class)2. Link and Association.

3. Generalization

4. Aggregation

5. Dynamic Modeling

6. State

7. State Diagram

8. Event

9. Event sequence in Telephone System

10. Functional Modeling





Version- 1.0

11. External Entity and Process.

12. Data Flow and Data Stores

13. Java Features

1. Software Engineering

2. Web technology

3. .NET & C#

Pre requisites

Graduation and 1st year P.G.

Related areas of Interest

1. Basics of System development process.2. Algorithms and flowcharting (Logic Building)

3. Programming in Java

1. System Analysis and Design

2. Software Engineering

3. Computer Architecture

4. RDBMS

5. Design patterns and Implementations

Pre requisites

(5th Semester)

Scope in this sector

SGI Property of 19




Version- 1.0

KEY CONCEPTS RELATED TO OBJECT ORIENTED SYSTEMS ALONG WITH

EXAMPLES

Object Modeling- Class & Object

The object model represents the static and most stable phenomenon in the modeled domain.Main concepts are classes and associations, with attributes and operations. Aggregation andgeneralization (with multiple inheritances) are predefined relationships.

Class diagrams are widely used to describe the types of objects in a system and their relationships. Class diagrams model class structure and contents using design elements such as

classes, packages and objects. Class diagrams describe three different perspectives when

designing a system, conceptual, specification, and implementation. These perspectives becomeevident as the diagram is created and help solidify the design.

Classes are composed of three things: a name, attributes, and operations. Below is an exampleof a class and its object.

● Shown above is a class and object diagrams respectively.

Objects of a particular class may have properties called attributes, corresponding to properties of their real-world equivalents. For example, an object representing a

Customer entity may have an attribute name that corresponds to the name property of a

customer class.

At any given time an attribute of an object has a value; that is, specific informationthat the object holds in respect of that attribute. For example, the name attribute of an

object representing a particular customer may have the value “vinod”.

2) Link and Association

Class diagrams also display relationships such as containment, inheritance, associations andothers. Below is an example of an associative relationship:





Version- 1.0

The association relationship is the most common relationship in a class diagram. The associationshows the relationship between instances of classes. For example, the class Order is associatedwith the class Customer. The multiplicity of the association denotes the number of objects thatcan participate in then relationship. For example, an Order object can be associated to only onecustomer, but a customer can be associated to many orders. Associations in class diagrams arecalled as links in object diagrams.

Generalization

Another common relationship in class diagrams is a generalization. A generalization is usedwhen two classes are similar, but have some differences. Look at the generalization below:

In this example the classes Corporate Customer and Personal Customer have some similaritiessuch as name and address, but each class has some of its own attributes and operations. Theclass Customer is a general form of both the Corporate Customer and Personal Customer





Version- 1.0

classes. This allows the designers to just use the Customer class for modules and do not requirein-depth representation of each type of customer.

Aggregation & composition

Class diagram showing Aggregation between two classes

Aggregation is a “kind of” or “part-whole” relationship. It is a variant of the "has a"

or association relationship; aggregation is more specific than association. It is an

association that represents a part-whole or part-of relationship. As a type of association,an aggregation can be named and have the same decoration that an association can.

However, an aggregation may not involve more than two classes.

Aggregation can occur when a class is a collection or container of other classes, butwhere the contained classes do not have a strong life cycle dependency on the container—

essentially, if the container is destroyed, its contents are not.

It is graphically represented as a hollow diamond shape on the containing class end of thetree of lines that connect contained class(es) to the containing class.

Class diagram showing Composition between two classes at top and Aggregation

between two classes at bottom

Composition is a stronger variant of the "owns a" or association relationship; composition

is more specific than aggregation. It is represented with a solid diamond shape.

Composition usually has a strong life cycle dependency between instances of thecontainer class and instances of the contained class(es): If the container is destroyed,

normally every instance that it contains is destroyed as well. Note that a part can (where

allowed) be removed from a composite before the composite is deleted, and thus not bedeleted as part of the composite.

Graphical representation of a composition relationship is a filled diamond shape on the

containing class end of the tree of lines that connect contained class(es) to the containingclass.

Differences between Composition and AggregationThe whole of a composition must have a multiplicity of 0..1 or 1, indicating that a part

must be for only one whole. The whole of an aggregation may have any multiplicity.

When attempting to represent real-world whole-part relationships, e.g., an engine is part

of a car, the composition relationship is most appropriate. However, when representing a

software or database relationship, e.g., car model engine ENG01 is part of a car modelCM01, an aggregation relationship is best, as the engine, ENG01 may be also part of a





Version- 1.0

different car model. Thus the aggregation relationship is often called "catalog"

containment to distinguish it from composition's "physical" containment.

Dynamic modeling

The dynamic model represents a state/transition view on the model. Main concepts are

states, transitions between states, and events to trigger transitions. Actions can bemodeled as occurring within states. Generalization and aggregation (concurrency) are

predefined relationships.

State● State is a status of object at a certain time

● Represented by attribute values and links

Example 1: A State Diagram for a door that can only be opened and closed

State diagrams are used to give an abstract description of the behavior of a system. This

behavior is analyzed and represented in series of events, that could occur in one or more

possible states. Hereby "each diagram usually represents objects of a single class andtrack the different states of its objects through the system".

Example 2: A State Diagram for “Phone Line”


http://www.google.com/url?q=http%3A%2F%2Fbehavior&sa=D&sntz=1&usg=AFQjCNFJtSL9v1jBayt0FDEx2xw1m7uwcA


http://www.google.com/url?q=http%3A%2F%2Fsystem&sa=D&sntz=1&usg=AFQjCNGBTF36FnSga5zavkT0n4m6ffo46Q







Version- 1.0

Event

● Stimulus which an object transmit to other objects●

Object reacts to events and perform associated tasks● Event has no duration time.

● Event may have attributes, which represents its contents

In the most general terms, an event is an occurrence in time and space that has

significance to the system.

For example, Keystroke is an event for the keyboard, but each press of a key is not an

event but a concrete instance of the Keystroke event. Another event of interest for the

keyboard might be Power-on, but turning the power on tomorrow at 10:05:36 will be just

an instance of the Power-on event.

An event can have associated parameters, allowing the event instance to conveynot only the occurrence of some interesting incident but also quantitative information

regarding that occurrence. For example, the Keystroke event generated by pressing a keyon a computer keyboard has associated parameters that convey the character scan code as

well as the status of the Shift, Ctrl, and Alt keys.

Example 1:

Event Trace

diagram for

telephone call





Version- 1.0

Functional Modeling

Functional model

The functional model handles the process perspective of the model, corresponding

roughly to data flow diagrams. Main concepts are process, data store, data flow, andactors.

A data-flow diagram (DFD) is a graphical representation of the "flow" of data through an

information system. DFDs can also be used for the visualization of data processing

(structured design).On a DFD, data items flow from an external data source or an internal data store to an

internal data store or an external data sink, via an internal process.

A DFD provides no information about the timing or ordering of processes, or aboutwhether processes will operate in sequence or in parallel. It is therefore quite different

from a flowchart, which shows the flow of control through an algorithm, allowing a

reader to determine what operations will be performed, in what order, and under whatcircumstances, but not what kinds of data will be input to and output from the system, nor

where the data will come from and go to, nor where the data will be stored.

Example: data-flow diagram

External Entity and Process



http://www.google.com/url?q=http%3A%2F%2Fvisualization&sa=D&sntz=1&usg=AFQjCNFNdqaUYQF1R0vewOXGd2ZbzeHmNg


http://www.google.com/url?q=http%3A%2F%2Fprocessing&sa=D&sntz=1&usg=AFQjCNERl9JS1LNtHtKGCdGqxKweVw33BQ

http://www.google.com/url?q=http%3A%2F%2Fflowchart&sa=D&sntz=1&usg=AFQjCNFVsibgcvXIW7o7q6kbzu5dGGnqzw











Version- 1.0

Data process

A data process transforms data values.

You can make a distinction between the following types of processes:Process Type Indicates

High-levelProcess containing nonfunctional components such as data stores or

external objects that cause side effects

Low-level Pure function without side effects, such as the sum of two numbers

Leaf or atomic

processesProcess that is not further decomposed

The name of a process is usually a description of the transformation it performs.

There are three sorts of transformation:

● Transformation of the structure, for example, reformatting● Transformation of information contained in data

● Generation of new information

If you open a process, you can either create a new DFD or open an existing DFD inwhich the process is specified.

The data flows of the opened process are connected in the new diagram to the process

with the name of the opened process. Vertices, and the flows and objects connected tothem, are transferred with the flows that are connected to the decomposed process.

If a data process has a decomposition at a lower level, an asterisk is placed inside theellipse. The data process can be opened only if it has a name.

Data store

A data store stores data passively for later access. A data store responds to requests tostore and access data. It does not generate any operations. A data store allows values to

be accessed in an order different from the order in which they were generated.

Input flows indicate information or operations that modify the stored data such as addingor deleting elements or changing values. Output flows indicate information retrieved

from the store; this information can be an entire value or a component of a value.

Actor

An actor produces and consumes data, driving the DFD. Actors lie on the boundary of the

diagram; they terminate the flow of data as sources and sinks of data. They are also

known as terminators. Data flows between an actor and a diagram are inputs to andoutputs of the diagram. The system interacts with people through the actor.





Version- 1.0

Anchor

A DFD anchor provides a start or end point. In decomposition diagrams, anchorsrepresent the nodes connected to the decomposed process in the higher level diagram.

Data flowA data flow moves data between processes or between processes and data stores. Assuch, it represents a data value at some point within a computation and an intermediate

value within a computation if the flow is internal to the diagram. This value is not

changed.

The names of input and output flows can indicate their roles in the computation or the

type of the value they move. Data names are preferably nouns. The name of a typical

piece of data, the data aspect, is written alongside the arrow.

Result flow

A result flow is a data flow that generates an object used as the target of another operation. The value of the flow is subsequently treated as an object, usually a data store.

Control flow

A control flow is a signal that carries out a command or indicates that something hasoccurred. A control flow occurs at a discrete point in time. The arrow indicates the

direction of the control flow. The name of the event is written beside the arrow.

Control flows can correspond to messages in CCDs or events in STDs; however, becausethey duplicate information in the DFD, use them sparingly.

Update flow

Update (or bidirectional) flows are used to indicate an update of a data store, that is, aread, change, and store operation on a data flow.

Example: DFD to compute triangle area.

Inputs Output

Java Features

● Simple





Version- 1.0

● fixes some clumsy features of C++

● no pointers

● automatic garbage collection

● rich pre-defined class library http :// java .sun .com / j 2 se /1.4.2/ docs /api /

● Object oriented

●

focus on the data (objects) and methods manipulating the data● all functions are associated with objects

● almost all data types are objects (files, strings, etc.)

● potentially better code organization and reuse

● Interpreted

● java compiler generate byte-codes, not native machine code

● the compiled byte-codes are platform-independent

● java byte codes are translated on the fly to machine readable instructions in

runtime (Java Virtual Machine)

● Portable

● same application runs on all platforms

●

the sizes of the primitive data types are always the same● the libraries define portable interfaces

● Reliable

● extensive compile-time and runtime error checking

● no pointers but real arrays. Memory corruptions or unauthorized memory

accesses are impossible

● automatic garbage collection tracks objects usage over time

● Secure

● usage in networked environments requires more security

● memory allocation model is a major defense

● access restrictions are forced (private, public)

● Multithreaded

● multiple concurrent threads of executions can run simultaneously

● utilizes a sophisticated set of synchronization primitives (based on monitors

and condition variables paradigm) to achieve this

● Dynamic

● java is designed to adapt to evolving environment

● libraries can freely add new methods and instance variables without any

effect on their clients

● interfaces promote flexibility and reusability in code by specifying a set of

methods an object can perform, but leaves open how these methods should

be implemented

● can check the class type in runtime

RESEARCH RELATED TO OBJECT ORIENTED SYSTEMS

1. Active Object-Oriented Database Systems





Version- 1.0

An active object-oriented data model, named TriGS (Triggersystem for GemS tone), has

been developed on top of the commercial object-oriented database management system

GemStone. TriGS supports the definition of both, local and global rules on class level byusing inheritance and overriding techniques. Due to the possibility of defining rules

dynamically, TriGS is especially suited for evolving applications with changing

requirements such as production planning and control systems. A workflow prototype based on TriGS called TriGSflow is operational.

Ongoing research focuses on the design of active object-oriented database applications

based on pattern technology, on extended transaction management for active databasesystems, and on integrating active object-oriented database technology with the WWW.

2. Object-Oriented Development of Information Systems

Designing object-oriented models of information systems is one of today's key problems

in object-oriented software engineering. Based on the BIER-Model ( Behavior I ntegrated E ntity Relationship Model) the design method OBD (O bject Behavior Diagrams) has been developed for the design of object-oriented databases and for information systems in

general.Questions like cooperative behavior specification and object-oriented design quality based on coupling and cohesion are among the main research interests. Moreover, an

object-oriented software life cycle model answering questions of reuse and reuseability

has been developed.

3. Distributed Information Systems

Not least since the emergence of the Internet, design guidelines for distributed

information systems are badly needed. Currently, we are concentrating our research onextending object-oriented models (OBD, UML) with interfaces and components, on

distributed persistence for Java applications, and on WWW database connectivity.

4. Hypermedia Document Management

Open hypermedia systems in general and cooperative electronic publishing environments

in particular are becoming more and more important. We have investigated the process of electronic publishing and the requirements for supporting this process by distributed

multimedia information technology like the World Wide Web (WWW) and Java. The

key research interests are platform independent representations of time dependent,structured hypermedia documents, the use of workflow management systems with regard

to cooperative electronic publishing applications, and the use of agent technology for

user-centric hypermedia information systems.

List of publications are available at the link given below:

http://www.ifs.uni-linz.ac.at/ifs/research/publications/papers98.html .

OTHER AREAS OF RESEARCH WITH THEIR LINKS





Version- 1.0

1. Conceptual Design of Secure Workflow Systems: An Object-Oriented Approach

to the Uniform Modeling of Workflows, Organizations, and Security http :// www .dke .uni - linz .ac .at /research / publications /abstracts /PT 9803 e .html

2. Metadata-Based Middleware for Integrating Information Systems

http :// www .ifs .uni - linz .ac .at /ifs /research /publications /kapsammerdiss .html

Conceptual Design of Active Object-Oriented Databases

http :// www .dke .uni - linz .ac .at /research / publications /abstracts /PT 9701 e .html

Active Object-Oriented Databases: From Conceptual Design to Logical Design

http :// www .dke .uni - linz .ac .at /research / publications /abstracts /PT 9801 e .html

GAMMA - A platform independent framework for reusable authentication, authorization,and auditing components

http :// www .ifs .uni - linz .ac .at /ifs /research /publications /probstdiss .html

TOP FIVE COMPANIES OF OBJECT ORIENTED SYSTEMS WITH LINKS

PUBLIC SECTOR PRIVATE SECTOR

1. Electronics Corporation of India

Limited.

www.ecil.co.in

2. Bharat Electronics Limited.www.bel-india.com

3. Hindustan Aeronautics Limited.

www.hal-india.com

4. Defense Research & Development

Organization.

www.drdo.org

5. Bharat Sanchar Nigam Limited.

www.bsnl.co.in

1. Sun Microsystems

http :// in .sun .com /

2. Tata Consultancy Services

http :// www .tcs .com

3. Oracle Corp.

http :// www .bixee .com /oracle / jobs -

in /india /

4. IBM

http :// www -07.ibm .com /in /careers /

5. HCL Infosystems

http :// www .hclinfosystems .in

PROJECTS THAT CAN BE DONE

1. ModelCVS: A Semantic Infrastructure for Model-based Tool Integration


http://www.google.com/url?q=http%3A%2F%2Fwww.dke.uni-linz.ac.at%2Fresearch%2Fpublications%2Fabstracts%2FPT9803e.html&sa=D&sntz=1&usg=AFQjCNHBxZ4eICO-cweqOSY8jKUbQ0Ll0A


http://www.google.com/url?q=http%3A%2F%2Fwww.ifs.uni-linz.ac.at%2Fifs%2Fresearch%2Fpublications%2Fkapsammerdiss.html%2520&sa=D&sntz=1&usg=AFQjCNG8qn5GfQmDm9sZtHFtKCd7UodsXw

http://www.google.com/url?q=http%3A%2F%2Fwww.dke.uni-linz.ac.at%2Fresearch%2Fpublications%2Fabstracts%2FPT9701e.html%2520&sa=D&sntz=1&usg=AFQjCNGCLoJYiqnDItqd41FlIUdtCk1FMQ


http://www.google.com/url?q=http%3A%2F%2Fwww.dke.uni-linz.ac.at%2Fresearch%2Fpublications%2Fabstracts%2FPT9801e.html&sa=D&sntz=1&usg=AFQjCNGv9KzvidgdJxmlVpMKz5MQt0PjGA


http://www.google.com/url?q=http%3A%2F%2Fwww.ifs.uni-linz.ac.at%2Fifs%2Fresearch%2Fpublications%2Fprobstdiss.html&sa=D&sntz=1&usg=AFQjCNFHi9zDWMLNfDPW6VR29gykTjs-TQ





























































































































Version- 1.0

With the rise of model-driven software development, more and more development tasks

are being performed on models. A rich variety of modeling tools is available supporting

different tasks, such as model creation, model simulation, model checking, and codegeneration. Seamless exchange of models among different modeling tools increasingly

becomes a crucial prerequisite for effective software development processes. Due to lack

of interoperability, however, it is often difficult to use tools in combination, thus the potential of model-driven software development cannot be fully utilized - unless we find

some scalable way of integration. We are aiming at providing a semantic infrastructure

for model-based tool integration, enabling to facilitate any tool appropriate for themodeling task at hand. The key innovations provided are a set of scalable architectural

model integration patterns supported by a high-level metamodel integration language,

thus going beyond existing low-level model transformation approaches. Ontology-based

metamodel integration considerably lowers the manual effort required for toolintegration, enabling a novel synergic use of technologies from the model engineering

and ontology engineering domains. An open knowledge base for tool integration captures

essential knowledge about modeling languages and tools in terms of ontologies, fostering

reuse within and beyond the scope of this project. These innovations will be realizedwithin the ModelCVS prototype and case study. The core of the system will be based on

a versioning system such as CVS, thus providing a loosely-coupled and well-proofedintegration architecture. Transparent transformation of models between different tools'

languages and exchange formats, as well as versioning capabilities exploiting the rich

syntax and semantics of models represent the key functionalities of ModelCVS. In this

way, ModelCVS will serve as both, a research vehicle and testbed for exploringapplications of semantic technologies in model-based tool integration and a prototype for

a succeeding industrial product.

Web-link of the project: ftp :// ftp .ifs .uni - linz .ac .at /pub /publications /2005/0805.pdf

2. WEE-NET - Web Engineering Network of Excellence

The Web has become more than a distribution medium for resources: it is now a full

development and run-time environment for large-scale and complex systems. However,

application development in Web environments is mostly anarchic and ad hoc; methodsand techniques for ensuring the interoperability, integrity, quality assurance and

maintainability of web applications are still lacking. WEE-NET will address the

increasing demand for qualified Web Engineers by organizing advanced training events, by enhancing learners mobility, and by bringing together leading R&D groups so that,

through the exchange of know-how and experiences, they can help raise the current state

of awareness and practice in Web Engineering.

This project has been carried out with the support of the European Community - ALFA(América Latina - Formación Académica) Programme. ALFA is a programme of co-

operation between higher education institutions of European Union and Latin America.

The content of this project does not necessarily reflect the position of the EuropeanCommunity, nor does it involve any responsibility on the part of the European

Community.

Web-link of the Project: http :// cosy .ted .unipi .gr /weenet /


ftp://ftp.ifs.uni-linz.ac.at/pub/publications/2005/0805.pdf


http://www.google.com/url?q=http%3A%2F%2Fcosy.ted.unipi.gr%2Fweenet%2F&sa=D&sntz=1&usg=AFQjCNEB2BwUVyftqEkb_lFhTyhAe2I-nw




































Version- 1.0

3. MEDINA - MEDiterranean by INternet Access

1. The creation of the 'MEDINA PORTAL', in order to promote cultural

tourism in different Mediterranean countries2. The development of National Web Sites, to provide further information

and a better understanding of local cultural and tourism resources, through

the use of avant-gard information technology and communication3. The promotion of 'Thematic Pathways for Cultural Tourism', that will

guide the user in a 'virtual tour' across different countries, linking cultural

heritage in a intelligent and structured way, and that provides relatedcultural and tourist information

4. The grouping together of cultural and tourist resources, both thematically

and geographicallyThese are just some of the objectives of the MEDINA - MEDiterranean by INternet

Access - Project, co-ordinated by IMED, The Mediterranean Institute, and co-financed

by the European Commission within the Eumedis Initiative - Information Society

(MEDA funds). The total cost of the MEDINA Project is 2.898.862 Euros, with thecontribution of 2.231.544 Euros from the EC.

MEDINA is a Euro-Mediterranean Project that involves a vast and well organised

partnership, composed of 14 countries: 5 Member States (Italy, France, Greece, Austriaand Belgium) and 9 Mediterranean Partner Countries (Algeria, Tunisia, Morocco,

Lebanon, Jordan, the Palestinian Authority, Syria, Malta and Cyprus). MEDINA will

look at all aspects of the cultural heritage of the Mediterranean: material heritage, performing arts, popular traditions, food and gastronomic culture, crafts.

Web-link of the Project: http :// www .istituti .usilu .net /speronim /web /medina /

4. Ubiquitous Web Applications

In the near future there will be an explosion of multi-device ubiquitous web applications.

These applications are targeted to inexpert users, who need friendly high qualityapplications, delivered at right time and at low costs. Quality and effectiveness of thisclass of applications is strongly related to the quality of its design. Thus, the main

objective of the UWA project is to define a set of methodologies, notations, and tools to

support the design and fast prototyping of complex, multi-device, ubiquitous webapplications.

More specifically, the project will produce an innovative, integrated design environment

covering the whole spectrum of design activities, from requirements to detailed design.The tight coupling of hypermedia design and operation (transaction) design, flexible and

powerful customization of design (taking into account the specific user profile, multi-

device and ubiquitous delivery, situation of use, location and time, etc.), design based

upon families of applications with strong “reuse” of design features (based upon design patterns), are some of the key innovative aspects.

A set of notations based on "extended" and customized UML will be developed, as long

as a set of heuristics and guidelines to help the developers. A number of design tools willmake more efficient the design activity, by producing flexible and exportable design

documentation (with internal representation based upon XML).

Web-link of the Project: http :// www .uwaproject .org /


http://www.google.com/url?q=http%3A%2F%2Fwww.istituti.usilu.net%2Fsperonim%2Fweb%2Fmedina%2F&sa=D&sntz=1&usg=AFQjCNE9xAobpKGrlaFfOJ3uThXQeJTLKw

http://www.google.com/url?q=http%3A%2F%2Fwww.uwaproject.org%2F&sa=D&sntz=1&usg=AFQjCNG__t3jr9J7kLIKkyZ9EelZkObT9Q




























Version- 1.0

TRENDS GOING ON FOR OBJECT ORIENTED SYSTEMS:

● 1986: Booch came up with the object-oriented design concept, the Booch method.

● 1987: Sally Shlaer and Steve Mellor came up with the concept of the recursive design

approach.

● 1989: Beck and Cunningham came up with class-responsibility-collaboration (CRC)cards.

● 1990: Wirfs-Brock, Wilkerson, and Wiener came up with responsibility-driven design.● 1991: Peter Coad and Ed Yourdon developed the Coad lightweight and prototype-

oriented approach.

● 1991: Jim Rumbaugh led a team at the research labs of General Electric to develop the

object modeling technique (OMT).

● 1994: Ivar Jacobson introduced the concept of the use case.





Version- 1.0

Latest technologies are as:Real-time Systems

Event-driven simulations of the business

Transaction-processing

Record-keeping reporting systemsDistributed Computing Machines


StudentHandout.MCA412.oos.150310

Documents

Transcript of StudentHandout.MCA412.oos.150310