Part- A

Q1: Is it important to check the feasibility of a project. Comment. When our project
is called feasible? Is there any drawback if we don’t check the behavior feasibility in
system development? Justify.
Ans: Yes, It is important to check the feasibility of the system.
It is the measure of how beneficial or practical the development of an information
system. Therefore, we conduct feasibility analysis.
Analysis and evaluation of a proposed project to determine if it
 is technically feasible,

 is feasible within the estimated cost, and

 will be profitable.

BEHAVIOURAL FEASIBILITY
People are inherently resistant to change, and computers have been known to facilitate
change. An estimate should be made of how strong a reaction the user staff is likely to
have toward the development of a computerized system.
Introduction of a candidate system requires special effort to educate, sell, and train the
staff on new ways of conducting business.
Drawbacks of not checking behavioral feasibility
If we don’t check the behavioral feasibility the staff remains unaware of new ways and
techniques of conducting business which may lead to a bad mark for the business.

Q2: Discuss the possible rational for including or not including the cost in an organization’s
productivity measures.
Ans: There is an inverse relationship between physical measures of productivity and the
cost of production.

1. Increasing the physical productivity of a resource that is used in a production

operation reduces the cost of production of a product or service.

2. Cost as a productivity measure

3. A driving objective of commercial organizations is generating profit. In a

competitive business environment, companies cannot afford to increase the price
of products and services to increase the margin of profit. Under such business
circumstances, increase in profit can only be achieved by increasing sales and
reducing the cost of production by the efficient use of resources.

Q3: Which guidelines are taken into consideration for the successful development and
management of the project?

Ans: 1. Involve the Right People in the Planning Process

Going back to the reference to systems, it's critical that all parts of the system continue to
exchange feedback in order to function effectively. This is true no matter what type of
system. When planning, get input from everyone who will responsible to carry out parts
of the plan, along with representative from groups who will be effected by the plan. Of
course, people also should be involved in they will be responsible to review and authorize
the plan.

2. Goals and Objectives Should Be SMARTER

SMARTER is an acronym, that is, a word composed by joining letters from different
words in a phrase or set of words. In this case, a SMARTER goal or objective is:

• Specific
• Measurable
• Acceptable
• Realistic
• Time frame
• Extending

3. Evaluate Planning Process and the Plan

During the planning process, regularly collect feedback from participants. Do they agree
with the planning process? If not, what don't they like and how could it be done better? In
large, ongoing planning processes (such as strategic planning, business planning, project
planning, etc.), it's critical to collect this kind of feedback regularly.

During regular reviews of implementation of the plan, assess if goals are being achieved
or not. If not, were goals realistic? Do responsible parties have the resources necessary to
achieve the goals and objectives? Should goals be changed? Should more priority be
placed on achieving the goals? What needs to be done?

Finally, take 10 minutes to write down how the planning process could have been done
better. File it away and read it the next time you conduct the planning process.

4. Project should be feasible

5. Project should be cost effective

Part-B

Q4: List the various techniques that can be used to gather the requirements of an
organization. Explain them with the help of an example.
Ans: 1. ASKING: this technique obtains information from user by simply asking them about the
requirements.
Comprises of methods:
• Questions may be open-ended or closed.

• Brainstorming
 • Group decisions
2. GETTING INFORMATION FROM EXISTING SYSTEMS
The analyst examines all reports, discusses with the user each piece of information
examined, and determines unfulfilled information needs by interviewing the user. In contrast
to this method is decision analysis.
3. PROTOTYPING:
This is used when the user cannot establish information needs accurately before the information
system is built.
Suitable for environments :
• Where it is difficult to formulate a concrete model for defining information requirements
and where information need of the user are evolving such as in DSS.

Q5: Is it beneficial to design a new system or cope up with the old system. Comment
Ans: I think it would be beneficial to cope up with the old system. An investigation and
questioning should be done how the system currently operates and to identify the requirements
the user have for a new or modified one. How the current systems are working and whether
adjustments are necessary or possible. Studies can be both manual and computer. We may add a
feature in the old system which we call as requirement. It includes a way of capturing or
processing data, producing information, controlling a business activity or supporting
management.

Q6: How can you differentiate decision tree and decision tables from each other . Discuss
the pros and cons of each.
Ans: Decision tree has as many branches as there are logical alternatives. It simply sketches the
logical structure based on the stated policy.
• Easy to read
• Easy to construct
• Easy to update
A decision table in contrast is a table of contingencies for defining a problem and actions to
be taken. It is a single representation of the relationship between conditions and actions.
Decision table consists of two parts:
1. Stub: it is divided into upper quadrant called the condition stub and a lower quadrant
called the action stub.
2. Entry: it is also divided into upper quadrant called the condition entry and a lower
quadrant called the action entry.
Standardized language must be used consistently and duplication of terms or meanings
should be eliminated.

Pros and cons:

• Decision trees are and decisions tables are best suited for dealing with complex
branching routines such as calculating discounts or sales commissions or inventory
control procedures.
• Decision trees are used to verify logic and in problems that involve a few complex
decisions resulting in a limited number of actions.