[1] State importance of Software Engineering.

software engineering is an engineering approach for software development. W e can alternatively view
it as a systematic collection of past experience. The experience is arranged in the form of methodologies
and guidelines. A small program can be written without using software engineering principles. But if one
wants to develop a large software product , than software engineering principles mare indispensable
to achieve a good quality software effectively. These definitions can elaborated with the help of a
building construction analogy.

[2] Illustrate various application of software engineering.

Software engineering provides methods to handle complexities in a software system and

enables the development of reliable software systems, which maximize productivity. In
addition to the technical aspects of the software development, it also covers
management activities which include guiding the team, budgeting, preparing schedules,
etc. The notion of software engineering was first proposed in 1968. Since then, software
engineering has evolved as a full-fledged engineering discipline, which is accepted as a
field involving in-depth study and research. Software engineering methods and tools
have been successfully implemented in various applications spread across different
walks of life.

[3] What are characteristics of software process ?

A software process can be defined as a set of activities, method, practices, and transformation that
people use to develop and maintain software and the associated product (for example – project plans,
design documents, code, test cases, and user manuals).

 Greater emphasis on systematic development

 Computer Aided for Software Engineering(CASE)
 A concentration on finding out the user’s requirements
 Formal specification of early version of a system (prototyping)
 Greater emphases on trying to ensure error free code

[4] Explain the task regions in spiral model.

The spiral model is a software development process combining elements of both design and
prototyping-in-stages, in an effort to combine advantage of top-down and bottom-up concepts. Also
known as the spiral lifecycle model, it is a system development method (SDM) used in information
technology.
The figure depicts a spiral modal that contains six task regions:

1. Customer communication – tasks required to establish effective communication between

developer and customer.
2. Planning – tasks required to define resources, timelines, and other project related information.
3. Risks analysis – tasks required to assess both technical and management risks.
4. Engineering – tasks required to build one or more representations of the application.
5. Construction & release – tasks required to construct, test, install and provide user support.
6. Customer evaluation – tasks required to obtain customer feedback based on evaluation of the
software representations created during the engineering stage and implemented during the
installation stage.

[5] Describe the importance of requirement validation.

Requirement validation is similar to requirements analysis as both process review the gathered
requirements.
Its importance

 To ensure that the actual requirements of the system are reflected in the srs
 To certify that the SRS contains an acceptable description of the system to be implemented.
 To check the requirement document for completeness, accuracy, consistency, requirement
conflict, conformance to standard and technical errors.

[6] Explain entity types, attributes and primary key.

An entity type is any type of object that we wish to store data about. Which entity types you decide to
include on your diagram depends on your application. An entity type is considered to be a set of objects.
That is simply one member or example or element or instance of the type or set.

Attributes – attributes are data items that describe an entity. An attribute is a single value of an
attributes for an instance of an entity. For example, Name and hire data are attributes of the entity
EMPLOYEE.

Primary key – the primary key is an attribute or a set of attribute that uniquely identify a specific
instance of an entity.

[7] Explain the concept of abstraction in detail.

Abstraction is the process of taking away or removing characteristics from something in order to reduce
it to a set of essential characteristics. In object oriented programming, abstraction is one of three central
principles. Through the process of abstraction a programmer hides all but the relevant data about an
object in order to reduce complexity and increase efficiency.

[8] Explain critical design review in detail.

A review conducted to verify that the detailed design of one or more configuration items satisfy
specified requirements, to establish the compatibility among the configuration items and other items of
equipment, facilities, software , and personnel ,to assess the results of producibility analysis review
preliminary hardware product specification.
[9] Explain the software testing and its need.

Software Testing is evaluation of the software against requirements gathered from users and system
specifications. Testing is conducted at the phase level in software development life cycle or at module
level in program code. Software testing comprises of Validation and Verification.

Its need
 Software testing is really required to point out the defect and errors that were made
during.
 It’s essential since it makes sure of the Customer’s reliability and their satisfaction in the
application
 Testing is required for an effective performance of software application or product.
 It’s important to ensure that the application should not result in to any failures because
it can be very expensive in the future or in the later stages of the development.
 It’s required to stay in the business.

[10] Explain how to decide a white box or black box testing.

White box testing is concerned only with testing the software product . Black box testing is concerned
only with testing the specification. White box testing cannot guarantee that the complete specification
has been implemented. Black box testing cannot guarantee that all parts of the implementation have
been tested. In order to completely test a software product both black or white box testing are required.
White box testing is much more expensive (in terms of resources and time ) than black box testing.

[11] What are objectives of walkthrough?

A walkthrough is normally organized and directed by the author of the technical document Any
combination of interested or technically qualified personnel (from within or out side the project)may be
included as seems appropriate.

The objective walkthrough

 Detect errors early.

 Ensure established standard are followed.
 Train and exchange technical information among project teams which participate in the
walkthrough.
 Increase the quality of the project, thereby improving moral of the following roles.

[12] What is software configuration control and its benefits?

Software configuration control is the systematic way of controlling the changes to the software item.
The process is the primary responsibility of the software development staff. Many software
development project teams groups changes to be implemented into a new version of the system.

Its benefits

 Help to store and retrieve the configurable items

 Allows to maintain customization to the product in effective way
 Manages the versions along with change descriptions to help differentiate between the versions

[13] What are primary goals in design of UML?

The primary goals in the design of the UML.

1. Provide users with a ready-to-use, expressive visual modeling language so they can develop and
exchange meaningful models.
2. Provide extensibility and specialization mechanisms to extend the core concepts.
3. Be independent of particular programming language and development process.
4. Provide a formal basis for understanding the modeling language.
5. Encourage the growth of the OO tools market.
6. Integrate best practices.

[14] What is object oriented analysis and design approach?

Object oriented analysis and design 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 characterized by its class its state, and its behavior. Various models can be created to show the static
structure, dynamic behavior, and run time deployment of these collaborating object. There are number
of different notations for representing these models, such as the Unified Modeling Language.

[15] Explain the extreme programming.

Extreme programming is a software development methodology which is intended to improve software

quality and responsiveness to changing customer requirements. It advocates frequent “releases” in
short development cycles, which is intended to improve productivity and introduce checkpoints at
which new customer requirement can be adopted.

[16] What are code of ethics in software engineering ?

There are code of ethics

1. PUBLIC – software engineering shall act consistently with the public interest.
2. CLIENT AND EMPLOYER - software engineering shall act a manner that is in the best interests
of their client and employer consistent with the public.
 3. PRODUCT – Software engineering shall ensure that their product and related modification meet
the highest professional standards possible.
4. JUDGEMENT – Software engineering shall maintain integrity and independence in their
professional judgment.
5. MANAGEMENT – Software engineering managers and leaders shall subscribe to and promote
an ethical approach to the management of software development and maintenance.
6. PROFESSION – Software engineering shall advance the integrity and reputation of the
profession consistent with the public interest.
7. COLLEAGUES – Software engineering shall be fair to and supportive of their colleagues.
8. SELF - Software engineering shall participate in lifelong learning regarding the practice of their
profession and shall promote an ethical approach to the practice of the profession.

[17] Explain cohesive and coupling criterion of functional independence.

Cohesion is an indication of relative function strength of a module. A cohesive module perform a single
task , requiring little interaction with other component in other parts of program.

Coupling is an indication of the relative interdependence among modules, the point at which entry or
reference is made to module and what data passes across the interface.

Functional independence the concept of functional independence is a direct outgrowth of modularity

and the concepts of abstraction and information hiding. Functional independence is achieved by
developing modules with “single-minded” function and an “aversion” to excessive interaction with other
modules.

[18] Illustrate the data entity in data flow diagram.

[19] Explain different notation used for programming language.

[20] Explain generic class of prototyping method.