Business Analyst

Large scale changes in requirements may require a separate
engineering study to understand the costs and benefits of
the proposed change.  But by the wording of the question, a
decision has already been made to change the requirements.

As a requirements analyst, the first thing that I would do
is to call together the immediately impacted stakeholders in
development and test to discuss the change.  I would present
the proposed change and allow for negotiation of wording. 
Then I would enter a change request (CR) to document the
change and to gain approval.  Once approved, I would change
the requirements document and check the changes into a
source control tool like DOORS, VSS, or ClearCase.  I would
then change the status of the CR to resolved or closed.

hi guys i dont know the exact answer of this
question.According to me this ans will be given in a bit
different way.Basically I am an all rounder cricket player.i
can bat ,bowl and field at all situations.So if i can show
my talent in this respect so being an electrical engineer i
am confi that i can base my plans,work items and products on
the reqrment...........

Requirement Specification Document

Requirements are documented in SRS document. The 
arrangement of requirement depends upon the way you are
documenting it, like using SSAD or OOAD aproach.

Persistent objects are on this heap, while transient 
objects are in the transient memory. Transient and 
persistent objects can access each other mutually. 
Accessing a persistent object leads to loading the object 
into the transient heap. It it is not accessed from 
transient objects any more, it will be written back to the 
persistent heap. A transient object becomes persistent as 
soon as it can be reached from a persistent root

Persistent is permanent storage and transient is for memory.
Persistemt objects when call transient objets ,first it is 
loaded into memory.After process a transient objects can be 
stored as persitent objects in hard disk.

it means leaving the implementation to the implementer, 
i.e. interface. you leave the implementation of 
functionality to the class who is implementing this 
interface

In a realization relationship, one entity (normally an 
interface) defines a set of functionalities as a contract 
and the other entity (normally a class) "realizes" the 
contract by implementing the functionality defined in the 
contract.

It is similar to generalization.It indicates that one class 
implements behavior specified by another.

Realization denotes implementing an interface.Arrow with 
dotted line 
Generalization denotes extending a class.Arrow with solid 
line.

I just want to add that realization is not only for 
interfaces or class it is also for use cases and use case 
realizations is to design its inner diagrams like sequence 
diagram …etc.

Facade Pattern 
Strategy Pattern
Bridge Pattern
Abstract Factory Pattern
Adapter Pattern

Producer Consumer Pattern
Singleton Pattern

Flyweight Pattern
Command Pattern
Mediator Pattern
Iterator Pattern
Proxy Pattern

Basic(
   interface,
   Abstract parent class,
   Private methods,
   accessor methods,
   constant data manager,
   immutable object,
   monitor
)
Creation(
   Factory method,
   Singleton,
   Abstract Factory,
   Prototype,
   Builder
)
Collectional(
   Composite,
   Iterator,
   Flyweight,
   Visitor
)
Structural(
   decorator,
   adapter,
   chain of responsibility,
   facade,
   proxy,
   bridge,
   virtual proxy,
   counting proxy,
   aggregate Enforcer,
   Explicit Object release
   Object cache
)
behavioral(
   Command,
   Mediator,
   Memento, 
   Observer,
   Interpreter,
   State,
   strategy,
   Null Object,
   Template Method,
   Object Authenticator,
   Common attribute registry    
)
concurrency(
   critical section,
   consistent lock order,
   guarded suspension,
   read-write lock
)

Object-Oriented Analysis (OOA) aims to model the problem 
domain, the problem to be solved, by developing an OO 
system. The source of the analysis is generally a written 
requirements statement. Object-Oriented Design (OOD) is an 
activity of looking for logical solutions to solve a 
problem by using encapsulated entities called objects.

#include in C/C++: #include makes a compiler to copy header 
file code into a C/C++ program.
 Dis Adv:It increase the program size unnecessarly.wastage 
of memory and process time.

import in java : import statement makes JVM to go to the 
java library execute the code there at finally substitute 
the result into java program.JVM physically will not copy 
any code.

 import is efficient than #include....

Class is an object.
But an object is not a class.

object is an instance of a class or in other words object 
is a snapshot(blueprint)of a perticuler class.
class is real world object.

Class is a user defined data type whereas Object can be 
veiwed as a variable of class type
For example fruit is a class & mango,apple are different 
objects of class fruit.
Class can be a person whereas objects can be any existing 
person like Ram ,Shayam,Rahul etc

a class is a class which is an object but class is not an 
object

Yes, class is an object but an object is not a class.
We can compare class with a factory and object with product.
A factory can be a product of another factory; but a 
product can not be a factory.

A class is a generalized template from which object
is created based on its various instances,therefore
we can consider a class as an object while vice-versa 
is not possible.

Constraint rule:
     Much of what you are doing in drawing a class diagram 
is indicating constraint.

     EX:Corporate customers have credit limits but Personal 
customer do not.

Design by contract:
     It provides rigorous defn. of operation's purpose and 
class's legal state. This is to enhance the debugging.

Dynamic classification allows objects to change type within 
the subtyping structure whereas static classification does 
not Ex:for dynamic classification is person's job(It can 
change).EX:for static classification sex.(male & female).

static means constant. Dynamic means randomly we can change 
in genral sences. So, static diagram we can not change it 
si fixed attributes but dynamic diagram we can change. As 
given example:- person job is attribut we can change the 
job . so, it is dynamic but sex of person male / female we 
canot change it is static