Object-oriented methodologies are adopted by industry rather than traditional methods for system development. popular among them are Rumbaugh et al.’s object modeling technique, Booch methodology, Jacobson Et Al. methodology. Each method has its own strong and weak points.
Rumbaugh et al.have a strong method for producing domain object models. Jacobson et al. have a strong method for producing object oriented analysis.Booch methodology concentrates on providing a detailed object-oriented design models.
a brief look at Booch methodology. It is useful in analysis and design.it consists of the following diagrams-Class diagrams,Object diagrams,State transition diagrams,Module diagrams,Process diagrams,Interaction diagrams.it includes macro development process and micro development process.
Macro development process
It is a combination of many micro development process.it takes int account technical details about a project.it may take weeks or months to complete. it involves the following phases:
· Conceptualization-the entire concepts of project is taken into consideration rather than dividing it into modules.the concept can be clarified by developing a prototype of the concept.
· Analysis and developmebt of the model- initially class diagrams are used to identify the roles of objects. Later Object diagrams are used which defines a ‘is a’, ‘has a’ relationship.
· Design or creation-class diagrams are initially used to define the existence of classes and the relationships between various classes.collaboration among the object is then regulated using object diagram. Module diagrams are then used for mapping of classes and objects and where they should be declared. Finally process diagrams are used for processor allocation.
· Evolution-it is a step-by-step correction or rectification process.the rectification has to be done before the product is delivered and not after the delivery. Addition of modules can also be carried out here.
· Maintenance-success of a project depends on the maintenance. It rectifies the localized errors and bugs are fixed.
Micro development process Represents the day- to-day activities of an organization.all the steps in micro development makes the macro development.it involves the following steps:
· Identify classes and objects
· Identify class and object relationship
· Identify class and object semantics
· Identify class and object interfaces and implementation
In an automobile company the micro development occurs as follows. Various objects(parts) of vehicles are identified and their place of manufacture are decided. The specification of the parts like specialized engine are decided. Each and every part and their assembling features and relations are decided. Interface for user and their access is given special care.various additional features like extra milage,power-stearing,engine capacity etc are mentioned. All this represents the micro development process in an automobile company.
Reusability
code and object reusability is one of the important feature of program design.its major advantages are listed below:
· Reduction in time if the same problem arises again.
· Helps in preventing errors that occurred earlier.
· The error in a project with integerted reusable codes can be rectified easily as the error lies only in the added module.
· It helps in preventing the wastage of resourses.
· Expertise over a new area can be achived easily by including reuseable codes.
Consider the example of an automobile company where the engine has to be given extra features. Instead of trying it from the scratch by the concept of reusability the additional features can be added which in turn reduces the cost and time thus making it highly efficient.
Object Persistence
Usually the life time of an object is within a program. when a program and its modules terminate the objects associated with it that have lost their references are lost or are sometimes subjected to garbage collection. This is done to prevent the wastage of memory and space. If an object needs to be used even after the program termination it needs to be stored in files or database.this concept is referred to as object persistence. Object persistence promotes the concept of reusability.if later in development of some projects the same object with the specified attributes are required then it be used as the object persists even after the program termination. thus it helps in saving time,cost and is efficient.
Component based development
It is a policy that is widely adopted in the industry for object oriented systems development. building
a user specific device is expensive and impractical. So the modern industry has adopted the policy of taking well-developed,tested components and adds its own features.this is the idea behind component based development. Rather than developing the whole component the required additional components are added to currently existiong satisfactory components according to the needs of the customer.
Its advantages are as follows-large amount of expertise is obtained as specilisation of components are done developing it from scratch.much time and money is saved here. Variety of products can be manufactured by this method.
One of its major feature is the wrapping technology.it means a combination of data and logic that reprents some real world entity.it can interact with new components thus giving the user required components.
| |
|
Welcome to KnowledgeSutra - Dear Guest | |
Object-oriented Methodologies
Started by nirmaldaniel, Feb 15 2010 07:22 PM
1 reply to this topic
#2
Posted 07 May 2010 - 10:03 AM
Hi!
Since you've mentioned about system maintenance, I was hoping you'd have the answer to a common question that organizations have - how can effort for a maintenance project be estimated? If we do use function points or a different metric, such as the classes within the system, they only provide an indication of how much effort it takes to build the system and it isn't a measure of the effort required for maintenance.
Since you've mentioned about system maintenance, I was hoping you'd have the answer to a common question that organizations have - how can effort for a maintenance project be estimated? If we do use function points or a different metric, such as the classes within the system, they only provide an indication of how much effort it takes to build the system and it isn't a measure of the effort required for maintenance.
Reply to this topic

1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users














