Scribd
Upload
18 views4 pages

2 M Bit

Uploaded by

Jasvan Sundar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
18 views4 pages

2 M Bit

Uploaded by

Jasvan Sundar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

1

1. Define Object.
An object is a real-world element in an object–oriented environment
that may have a physical or a conceptual existence. Each object has −
• Identity that distinguishes it from other objects in the system.
• State that determines the characteristic properties of an object
as well as the values of the properties that the object holds.
• Behavior that represents externally visible activities performed
by an object in terms of changes in its state.
2. Discuss Information Hiding.
In object-oriented programming, information hiding (by way of
nesting of types) reduces software development risk by
shifting the code's dependency on an uncertain
implementation (design decision) onto a well-defined
interface.
3. Define CRC.
Class-responsibility-collaboration (CRC) cards are a
brainstorming tool used in the design of object-oriented
software. They were originally proposed by Ward
Cunningham and Kent Beck as a teaching tool,[1] but are also
popular among expert designers[2] and recommended by
extreme programming supporters.[3] Martin Fowler has
described in his book about UML that if you want to explore
multiple alternative interactions quickly, you may be better off
with CRC cards, as that avoids a lot of drawing and erasing.
4. List the approaches for
identifying classes.
Approaches for identifying classes & their behaviours in problem
domain • Noun phrase approach • Common class patterns •
Use—case driven approach • Classes, Responsibilities and
Collaboration (CRC) approach
5. Discuss the need for axiomatic
approach.
Axiomatic design is a systems design methodology using matrix
methods to systematically analyze the transformation of
customer needs into functional requirements, design
parameters, and process variables.
2

6. Define the followings:


An Axiom
An axiom is a fundamental truth that always is observed to be
valid and for which there. is no counterexample or exception. •
The axioms cannot be proven or derived.
• A theorem is a proposition that may not be self-evident but can
be proven from accepted.
Theorem.
A theorem is a proposition that may not be self evident but can
be proven from accepted axioms. • A corollary is a proposition
that follows from an axiom or another proposition that has been
proven.
7. Discuss Error-based Testing.
Testing where information about programming style, error-prone
language constructs, and other programming knowledge is
applied to select test data capable of detecting faults, either a
specified class of faults or all possible faults.
8. Define Debugging.
Debugging is the process of detecting and removing of existing
and potential errors (also called as 'bugs') in a software code
that can cause it to behave unexpectedly or crash. To prevent
incorrect operation of a software or system, debugging is used
to find and resolve bugs or defects.
9. Differentiate Alpha and Beta
Testing.
Alpha testing is performed by testers who are usually internal
employees of the organization. Beta testing is performed by
clients who are not part of the organization. Alpha testing is
performed at developer's site. Beta testing is performed at end-
user of the product.
10. List the issues in software
quality. Auditing
Development of standards and guidelines
Production of reports
Review of quality system
3

11. List out the three steps in CRC


process.
Find classes.
Find responsibilities.
Define collaborators.
Move the cards around.
12. Define Association.
Association is a group of links having common structure and
common behavior. Association depicts the relationship between
objects of one or more classes. A link can be defined as an
instance of an association.
13. Define package.
A package in the Unified Modeling Language is used "to group
elements, and to provide a namespace for the grouped
elements". A package may contain other packages, thus
providing for a hierarchical organization of packages.
14. List some testing strategies. Unit
Testing. ...
Subsystem Testing. ...
System Testing. ...
Grey Box Testing. ...
Techniques for Subsystem Testing. ...
Categories of System Testing. ...
Software Quality. ...
Quality Assurance.
15. Define Usability testing.
Usability testing is a method of testing the functionality of a
website, app, or other digital product by observing real users as
they attempt to complete tasks on it. The users are usually
observed by researchers working for a business.
16. List the types of Errors in a
program.
Syntax Errors.
Logic Errors. ...
Compilation Errors. ...
Runtime Errors. ...
Arithmetic Errors. ...
4

Resource Errors. ...


Interface Errors.
17. Define patterns.
In object-oriented programming, a pattern can contain the
description of certain objects and object classes to be used,
along with their attributes and dependencies, and the general
approach to how to solve the problem. Often, programmers can
use more than one pattern to address a specific problem.
18. Define Framework.
The generalized UML pattern framework is an object-oriented
framework that provides support for the base classes that the
standard pattern implementation model extends.
19. Encapsulation
Encapsulation is the process of binding both attributes and
methods together within a class. Through encapsulation, the
internal details of a class can be hidden from outside. It permits
the elements of the class to be accessed from outside only
through the interface provided by the class.
20. Define coupling and its types.
Coupling: Coupling is the measure of the degree of
interdependence between the modules. A good software will
have low coupling. Types of Coupling:
• Data Coupling
• Stamp Coupling
• Control Coupling
• External Coupling
• Common Coupling
• Content Coupling
21. Define primary key&foreignkey.
A primary key is used to ensure data in the specific column is
unique. A foreign key is a column or group of columns in a
relational database table that provides a link between data in
two tables. 2. It uniquely identifies a record in the relational
database table.

You might also like