19-11-2012, 04:19 PM
Object Oriented Analysis and Design Solved Assignments Ignou 2011
MCS-032 Solved Assignment Ignou 2011.pdf (Size: 73.77 KB / Downloads: 30)
Object-orientation is a software engineering approach that models a system as a group of
interacting objects. Each object represents some entity of interest in the system being modeled, and is
characterised by its class, its state (data elements), and its behavior. Various models can be created to
show the static structure, dynamic behavior, and run-time deployment of these collaborating objects.
There are a number of different notations for representing these models, such as the Unified Modeling
Language (UML).
Object-oriented analysis (OOA) applies object-modelling techniques to analyze the functional
requirements for a system. Object-oriented design (OOD) elaborates the analysis models to produce
implementation specifications. OOA focuses on what the system does, OOD on how the system does it.
The object-oriented approach has the following advantages: when the expert system is large,
complexity is reduced through modularization, that is, by subdividing the system into manageable size
components, such as objects, and establishing well-defined relationships between them. The internal
design of each object is localised so that it does not depend on the internal design of another
component. The design concepts are separated from the implementation details.
That means that rules are developed separately from the objects that they manipulate. Objects can be
reused. They are written and debugged once, and then matched to form new applications.
Briefly explain , need of different UML Diagrams.
Ans : Modeling is an activity that has been carried out over the years in software development. When
writing applications by using the simplest languages to the most powerful and complex languages, you
still need to model. Modeling can be as straightforward as drawing a flowchart listing the steps carried
out by an application. Why do we use modeling? Defining a model makes it easier to break up a
complex application or a huge system into simple, discrete pieces that can be individually studied. We
can focus more easily on the smaller parts of a system and then understand the "big picture." Hence, the
reasons behind modeling can be summed up in two words:
* Readability
* Reusability
Readability brings clarity—ease of understanding. Understanding a system is the first step in either
building or enhancing a system. This involves knowing what a system is made up of, how it behaves,
and so forth. Modeling a system ensures that it becomes readable and, most importantly, easy to
document. Depicting a system to make it readable involves capturing the structure of a system and the
behavior of the system.
Reusability is the byproduct of making a system readable. After a system has been modeled to make it
easy to understand, we tend to identify similarities or redundancy, be they in terms of functionality,
features, or structure.
UML does not have any dependencies with respect to any technologies or languages. This implies that
you can use UML to model applications and systems based on either of the current hot technologies;
for example, J2EE and .NET. Every effort has been made to keep UML as a clear and concise modeling
language without being tied down to any technologies.