Object Oriented Software Engineering Part-A (2MARKS): UNIT I INTRODUCTION 1. What is Software Engineering? Software engineering is a modeling activity. Software engineers deal with complexity through modeling. Software engineering is a problem-solving activity. Models are used to search for an acceptable solution. Software engineering is a knowledge acquisition activity. It is a single piece of additional data can invalidate complete models. Software engineering is a rationale-driven activity. Rationale information represented as a set of issue models enables us to understand the implication of proposed change whwn revisiting a decision. 2. What is modeling? Modeling is a means of dealing with complexity. Modeling means constructing an abstraction of a system that focuses on interesting aspects and ignores irrelevant details. 3. List the steps of problem solving. The five steps are formulating the problem, analyze the problem, search for solutions, decide on the appropriate solution and specify the solution. 4. Why knowledge acquisition is a non linear process? Explain. Knowledge acquisition is a non linear process because of the addition of a new piece of information may invalidate all the knowledge we have acquired for the understanding of a system. Even if we had already documented this understanding in documents and code, we must be mentally prepared to start from scratch. 5. Define Rationale. A design rationale is the explicit listing of decisions made during a design process, and the reasons why those decisions were made when designing a system or artifact . Its primary goal is to support designers by providing a means to record and communicate the argumentation and reasoning behind the design process. 6. Compare participant and role. The client orders and pays for the system. The developers construct the system. The project manager plans & budgets the project & co-ordinates the developers and client. The end users are supported by the system. The persons involved in the project are referred to as participants. The set of responsibilities in the project or a system as a role. 7. What is work product? List it types. A work product is an artifact that is produced during the development, such as a document or a piece of software for other developers or for the client. The types of work product are Deliverable & Internal work product.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Object Oriented Software Engineering
Part-A (2MARKS):
UNIT I INTRODUCTION
1. What is Software Engineering?
Software engineering is a modeling activity. Software engineers deal with complexity
through modeling.
Software engineering is a problem-solving activity. Models are used to search for an
acceptable solution.
Software engineering is a knowledge acquisition activity. It is a single piece of
additional data can invalidate complete models.
Software engineering is a rationale-driven activity. Rationale information represented as
a set of issue models enables us to understand the implication of proposed change whwn
revisiting a decision.
2. What is modeling?
Modeling is a means of dealing with complexity. Modeling means constructing an
abstraction of a system that focuses on interesting aspects and ignores irrelevant details.
3. List the steps of problem solving.
The five steps are formulating the problem, analyze the problem, search for
solutions, decide on the appropriate solution and specify the solution.
4. Why knowledge acquisition is a non linear process? Explain. Knowledge acquisition is a non linear process because of the addition of a new piece of
information may invalidate all the knowledge we have acquired for the understanding of
a system. Even if we had already documented this understanding in documents and code,
we must be mentally prepared to start from scratch.
5. Define Rationale.
A design rationale is the explicit listing of decisions made during a design process, and
the reasons why those decisions were made when designing a system or artifact. Its
primary goal is to support designers by providing a means to record and communicate the
argumentation and reasoning behind the design process.
6. Compare participant and role.
The client orders and pays for the system. The developers construct the system. The
project manager plans & budgets the project & co-ordinates the developers and client.
The end users are supported by the system. The persons involved in the project are
referred to as participants. The set of responsibilities in the project or a system as a role.
7. What is work product? List it types.
A work product is an artifact that is produced during the development, such as a
document or a piece of software for other developers or for the client.
The types of work product are Deliverable & Internal work product.
Each end of an association can be labeled by a set of integers indicating the number of
links that can legitimately originate from an instance of the class connected to the
association end is called as multiplicity. For example the association end author has a
multiplicity of l. This means each EmergencyReport object has exactly one link to an
object of class FieldOfficer.
31. What are the types of associations in multiplicity?
The types of associations in multiplicity are one-to-one association, one-to-many
association, and many-to-many association respectively.
32. Define complex transitions.
Complex transitions are transitions with multiple source states or multiple target states.
Complex transitions denote the synchronization of multiple activities or the splitting of
the flow of control into multiple threads.
33. Difference between work package and work product.
A work package describes the work products to be produced, the resources needed to
perform the work, the expected duration, dependencies on inputs, which are work
products produced by other tasks as well as dependencies on other tasks.
Work products represent the deliverables and intermediate products of the project.
Work products are the visible results of work.
34. What are the events included in planned & unplanned communication events?
The events in planned communication are problem presentation, client reviews, project
reviews, peer reviews, status reviews, brainstorming, releases and postmortem reviews.
The unplanned communication events are requests for clarification, requests for changes
and issue resolution.
35. Enlist the concepts used in project organization.
The concepts used in project organization are project organizations, roles, tasks & work
products and schedule.
36. What are the activities addressed for organizational and communication structure?
The activities addressed for communication structure are joining a team, joining the
communication infrastructure, attending team status meetings and organizing client &
project reviews.
37. Explain the major types of interaction in a project.
The major types of interaction in a project are reporting, decision and communication.
38. Define (I) Management Development (ii) Cross functional rule
Management Development is best described as the process from which managers learn
and improve their skills not only to benefit themselves but also their employing
organizations.
The cross-functional role is also called liaison. The liaison is responsible for
disseminating information along the communication structure from one team to another.
Cross-functional roles are concerned with co-ordination among teams.
39. What types of liaison used by subsystem team?
They are API engineer, document editor, configuration manager and tester.
40. Define tasks and work products.
Work products represent the deliverables and intermediate products of the project.
Work products are the visible results of work.
A task represents an atomic unit of work that can be managed. Tasks consume resources,
result in work products, and depend on work products produced by other tasks.
41. List the planned communication events.
The events in planned communication are problem presentation, client reviews, project
reviews, peer reviews, status reviews, brainstorming, releases and postmortem reviews.
42. What is PERT Chart? Where it is used?
A PERT chart represents a schedule as an acyclic graph of tasks. PERT charts are useful
tools for planning a project and tracking its execution.
Figure 11-10 is a PERT chart for the database subsystem. The planned start and duration
of the tasks are used to compute the critical path, which represents the shortest possible
path through the graph. The length of the critical path corresponds to the shortest possible
schedule, assuming sufficient resources to accomplish in parallel tasks that are
independent.
43. Define briefly the events of unplanned communication.
Requests for clarification: It represents the bulk of the communication among
developers, clients, and users.
Request for change: During a request for change, a participant reports a problem and,
in some cases, proposes solutions.
Issue resolution: A flat organization may select a solution through the brainstorming
process.
44. Explain why multiple choice questionnaires as a primary needs for extracting
information from user are not effective for eliciting requirements.
Multiple choice questionnaires is formalized as a primary needs for extracting
information from user which are not effective for eliciting requirements because of
45. What are the roles assigned for a meeting?
The roles assigned for meeting are group roles, ground roles, and meeting roles.
46. Enlist the organizational activities.
The activities addressed for communication structure are joining a team, joining the
communication infrastructure, attending team status meetings and organizing client &
project reviews.
47. Define Meeting minutes.
Meeting minutes represent a portion of the project history that can be analyzed after the
project is completed. Meeting minutes include a section describing the action items
resulting from the meeting (i.e.) the items describing actions to be taken by the meeting
participants as a consequence of the meeting.
48. What are the terms included in a project forum?
49. What is the difference between client & end user?
Client is a person or a co-operate group for whom product is developed and sold. They
are the ones who pay for that software. It can also mean someone who receives long term
benefits or services from another person whether or not they pay for them.
End user can be any person or a group that uses the software or product once it is sold to
client in their domain. A customer who uses online banking is called as an end user for
that online banking system.
50. What is the difference between cross functional team and subsystem team? A cross-functional team, the architecture team, made of representatives of each team, is
responsible for ensuring the integration of the requirements. Cross-functional team
made up of and selected developers (who will take part in the implementation of the
subsystem). Teams that do not work directly on a subsystem, but rather, accomplish a
project-wide function, are called cross-functional teams.
Each team which negotiates with other teams for the interfaces of the subsystems it needs
is said to be known as subsystem teams. Each subsystem team works with its system
engineering representative to define the metrology requirements for each of the critical
functional responses they have created.
51. Can a role be shared between one or more participants? Why or why not?
Roles can be played by two or more participants in front of the group. This is good for
exploring problem solving and provides a shared experience the entire group can discuss
and perhaps replay. It singles out people which may be inappropriate.
UNIT II ANALYSIS
52. List the activities of Requirement elicitation.
The activities of requirement elicitation are identifying actors, identifying scenarios,
identifying use cases, refining use cases, identifying relationship among actors and use
cases, identifying initial analysis objects, and identifying nonfunctional requirements.
53. Define Joint Application Design.
Joint Application Design (JAD) focuses on building consensus among developers,
users, and clients by jointly developing the system specification. Joint Application
Design (JAD) is a software design methodology developed by IBM to enhance