Learning Curve…

MB0047 a). Explain Scott Morton five levels of complexity. b). Explain objects and its behavior with an example.

Posted on: September 29, 2011

MB0047 a. Explain Scott Morton five levels of complexity.

b. Explain objects and its behavior with an example.

Answer: – Scott Morton five levels

 Scott Morton proposes five levels of complexity at which reconfiguration can be applied. The following five levels indicate how it is possible to reconfigure strategic information system based on the influence of IT.

1. Localized exploitation – This is part of the Evolutionary level and exists within individual business functions. It addresses the local efficiency and effectiveness of a information system.

2. Internal integration – this is part of the evolutionary level and exists between different systems and applications. It evolves out of rationalization using a common IT platform. Efficiency and effectiveness are enhanced by coordination and cooperation within the enterprise;

3. Business process redesign – This is part of the revolutionary level. It involves more thorough re-evaluation of the enterprise value-chain and the production process.

4. Business network redesign – This is also part of the revolutionary level. It involves reconfiguration of the scope and tasks of the business network. It also helps in the creation and delivery of products and services. Coordination and cooperation extend, selectively, beyond the enterprise’s boundaries; and

5. Business scope redefinition – It is also part of the revolutionary level. It involves migration of functions across the enterprise’s boundaries. It may change the organization’s conception of the business.


 Objects and its behavior

Objects are key to understanding object-oriented technology. If we look around and we can find many examples of real-world objects: dog, desk, television set, and bicycle.

Real-world objects share two characteristics: They all have state and behavior. Dogs have state (name, color, and breed, hungry) and behavior (barking, fetching, wagging tail). Bicycles also have state (current gear, current pedal cadence, and current speed) and behavior (changing gear, changing pedal cadence, applying brakes). Identifying the state and behavior for real-world objects is a great way to begin thinking in terms of object-oriented programming.

Software objects are conceptually similar to real-world objects: they too consist of state and related behavior. An object stores its state in fields (variables in some programming languages) and exposes its behavior through methods (functions in some programming languages). Methods operate on an object’s internal state and serve as the primary mechanism for object-to-object communication. Hiding internal state and requiring all interaction to be performed through an object’s methods is known as data encapsulation — a fundamental principle of object-oriented programming.

Consider a bicycle, for example:

By attributing state (current speed, current pedal cadence, and current gear) and providing methods for changing that state, the object remains in control of how the outside world is allowed to use it. For example, if the bicycle only has 6 gears, a method to change gears could reject any value that is less than 1 or greater than 6.

Bundling code into objects provides a number of benefits, including:

  1. Modularity: The source code for an object can be written and maintained independently of the source code for other objects. Once created, an object can be easily passed around inside the system.
  2. Information-hiding: By interacting only with an object’s methods, the details of its internal implementation remain hidden from the outside world.
  3. Code re-use: If an object already exists (perhaps written by another software developer), you can use that object in your program. This allows specialists to implement/test/debug complex, task-specific objects, which you can then trust to run in your own code.
  4. Plug ability and debugging ease: If a particular object turns out to be problematic, you can simply remove it from your application and plug in a different object as its replacement. This is analogous to fixing mechanical problems in the real world. If a bolt breaks, you replace it, not the entire machine.

1 Response to "MB0047 a). Explain Scott Morton five levels of complexity. b). Explain objects and its behavior with an example."

Explain object and its behavior with the example of your own

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Learning days (Calendar)

September 2011
« Aug   Oct »

Knowledge Bank (Archives)

I am on Twitter

Blog Stats

  • 532,906 hits

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 43 other followers

%d bloggers like this: