Professional Documents
Culture Documents
Ec Two Marks Unit-I
Ec Two Marks Unit-I
(i)A class is a discrete module of code that has a set of variables (aka fields)
associated with it, as well as a set of function calls (aka methods).Methods define those
interfaces to the class that take a set of zero or more input parameters and return a set of
zero or more output parameters.
(ii)An object represents an instance of a class in memory. The state of the object is
defined by the values assumed by the class fields. The behavior of the object is a function
of the method implementations, the return values from method calls, and the state change
of the object.
(iii)Visibility levels associated with class fields and methods can define what level of
access other classes have to those fields and methods.
(iv) A package refers to a collection of one or more classes. Classes in a package have
some cohesive logical relation and tend to offer a very specific service. Whenever classes
are tightly coupled in some logical sense, they tend to be collected into a package.
6. State the importance of OOSD
OO practices foster the development of modular programs with encapsulated state and
implementation behavior, as well as facilitate the abstraction of problems. Modularity of
classes enables one to discretely represent concepts that are used in defining a problem
Solving a problem is usually most efficiently performed by first partitioning a problem
and then addressing smaller pieces of the original problem. Modularity and abstraction in
OO allow for the encapsulation of a problem domain into discrete classes and therefore
facilitate more efficient problem solving.
Dependencies between modules are reduced by forcing dependencies to be created
through interfaces as opposed to allowing dependencies to be created on state and
functions that are to be encapsulated
7.Represent the basic flow of OO software development
1. Project Charter: Establish a charter detailing goals and objectives for the effort to
be undertaken.
2. Requirements Analysis: Perform analysis of expected system behavior and system
interfaces.
3. Preliminary System Design:
Perform a preliminary design of a system with consideration for Commercial Off
The Shelf (COTS) software, custom software, and reuse. Partition design into
smaller problems to solve.
4. Detailed Design:
Perform detailed design of core classes and interfaces.
5. Implementation:
Implement the software. May involve custom code writing, as well as integrating
with COTS.
6. Unit Test:Unit test the implementation.
7. Assembly:Assemble individual elements into discrete elements of behavior.
8. Thread Test:Test threads of behavior on assembled elements.
9. Configuration Specification:Define the assumed COTS and custom software
configura tion and versions.
10. System Test:Test a fully assembled and configured system.
11. Deployment:Deploy the system per the configuration specification.
12. Maintenance:Maintain operational software for bug fixes and upgrades.
8. State the purpose of preliminary system design
2
Component APIs:
A component Application Programming Interface (API) defines a set of standard
interfaces that applications can use to tap the services of a component.
Design Patterns:
Component SPIs:
A component Service Provider Interface (SPI) defines a set of standard interfaces
that the provider of some service adheres to and implements
Component-to-Container Interfaces:
A component-to-container interface defines the interface to a container environment
assumed by a component.
Container-to-Component Interfaces:
A container-to-component interface defines the interface to a component as assumed
by a container.
16. Define Component-Based Development (CBD) process
CBD is the process by which organizations develop software using components.
Components may be premade and purchased as commercial off the shelf (COTS) entities,
they may be modified versions of COTS components
17.Write notes on Javabeans
The JavaBeans component model defines a standard model for writing Java code
that can be customized at design-time, and exposes its attributes, events, and
interfaces to JavaBean containers. Containers are typically embedded into an
integrated development environment such that JavaBean components can be
customized during design-time using GUI-based tools. A standard JavaBeans
container context interface and standard component-to-component interface model
known as the InfoBus have also been defined for the JavaBeans component model.
18.Specify the method which enables the access to components
The Common Object Request Broker Architecture (CORBA) defines a standard
model for enabling distributed access to components implemented in any language. A
standard communications container environment, known as the ORB, handles
transforming calls from distributed clients into data sent via a standard communications
protocol to server-side container code that invokes the distributed object method.
In addition to a standard component communications and invocation
infrastructure, a standard set of higher-level distributed component services and facilities
is also defined within the CORBA model.
19. What does RMI and COM represented in an environment
RMI:
The Remote Method Invocation (RMI) framework defines a Java-specific interface
model for enabling distributed access to components. The RMI container environment
is equipped with the Java platform and has been extended to support communication
using the same underlying communications protocol as CORBA's standard protocol.
COM:
Microsoft's Component Object Model (COM) defines a standard model for interfacing
with components implemented on Microsoft platforms.
Type 2 Driver
Type 3 Driver
Can be downloaded and configured "on-the-fly" just like any Java class file.
. Type 4 Driver
Can be downloaded and configured "on-the-fly" just like any Java class file.
Unlike Type III driver, talks DIRECTLY with the DBMS server.
Resources / Asserts
People / User
Enterprise Information
Enterprise Knowledge
32.
BIG QUESTIONS:1. Explain the need for OOSD and its process
2. Describe the primary objectives of an enterprise
3. Explain the various types of JDBC drivers with neat diagram
4. Explain RMI Architecture with neat diagram.
5. Describe the architecture of RBMS with neat diagram.
6. Explain the architecture of Network Client and Network Server with neat
diagram
7. Define OOSD and the various elements present in the OOSD
8. What are the problems solved with components in CBSD?
9. Explain in detail about the various types of JDBC drivers with neat
diagrams.
10. Describe the architecture of DBMS with neat diagram.
11. Explain the RMI development process with example
10