Feasibility Study and Requirement Gathering

Mir Yousuf
Assistant Professor: CSE

Lovely Professional University
 Process of defining, documenting and maintaining the documents.
 Requirement analysis done in a systematic way
 7 steps
1. Inception define overall objectives, functionality and
constraints
2. Elicitation Detail the problems (scope, understanding,
volatility)
3. Elaboration we refine and expand
4. Negotiation conflicting requirements, resolve
5. Specification above mentioned steps are put in a diagrammatic
notation or template
6. Validation To validate against customer requirements
7. Management Manage the changes in the software.
 4 step process
1. Feasibility Process
2. Requirement gathering
3. Software requirement specification
4. Software requirement validation
 An important phase on which the management decides on the
feasibility report that “Whether or not the proposed system is
worthwhile”
 Main focus in on the organizational goal
 The main aim
◦ “not thinking how to solve a problem but to determine whether the
problem is worth solving”
Features and functions
that the user expects
from a software
ROUGH
IDEA
CLIENT Organization
Does a detailed study
about whether the
software is feasible to
develop
ANALYLSTS >>Can we practically
implement
Implementation
Contribution
of the project Cost
to the estimated
organization and objective
OUTPUT OF THIS PHASE

Generate a report that contains comments and
recommendations for management about whether or not to
consider the project
1. If the system contributes to the organizational objectives?
2. If the system can be engineered using the current technology
and within budget?
3. If the system can be integrated with the other systems that
are used?
It contributes to the following features

 Technical feasibility
 Economic feasibility
 Operational feasibility
 Feasibility study leads to the decision
 GO AHEAD
 DO NOT GO AHEAD
 THINK AGAIN
 Based upon the information assessment (what is required) and
report writing we get a list of Questions
1. What if the system was not implemented?
2. What are the current process problems?
3. How will the proposed system help?
4. What will be the integration problems?
5. Is new technology needed?
6. Is new skill (staff team members) required?
7. What facilities must be supported by the proposed system?
 The format
 Product  brief description of the proposed system will do.
 Technical feasibility output the technical system option you propose to use
which will give a technical solution satisfying the requirements
 Social feasibility whether the proposed system would prove acceptable to the people
who would be affected by its introduction
 Describe the effect on users by the new system
 Economic feasibility  consider the costs/benefits of the system
 Consider development cost and running cost
 Market research detail market research you carried out
 Justify the conclusions you have drawn from your research
 Describe how you propose to compete with the similar products in the market
 Alternative solution consider the alternate solutions to be documented
 Consider that you have been asked by your team leader to
write a feasibility report for your next project. The project
requires a website to be developed that will allow online
booking for the local squash club. The club has an unlimited
budget due to a big lottery grant. You have six months to
complete the project.
 If the feasibility report is positive towards understanding the
project, the next phase starts with the requirement gathering
 Clients/ users may not be able to define their problems
requirements
 System developers gather the client requirement to
understand the problem that needs to be resolved.
 The analysts and the engineers communicate with the end
users to know their ideas on what the software should
provide.
 Some questions that help in understanding a business include
What is being done?

How its being done?
What is the frequency of a task?
What is the volume of the decisions or transactions?
What are the problems being encountered?
 Some techniques that help in requirement gathering
 Interviews
 Questionnaires
 Studying the existing documents
 Analysing business data
 Specific
 Measurable
 Agreed upon
 Realistic
 Time based
 Failure can result in
1. Incomplete problem definition

2. Incorrect problem goals
3. Rework to deliver required outcome
4. Delayed delivery
Due to the depth of information required , the requirement

gathering is also known as “detailed investigation”.
 Various other objectives of feasibility study are listed
below.
 To analyze whether the software will meet organizational
requirements
 To determine whether the software can be implemented
using the current technology and within the specified
budget and schedule
 To determine whether the software can be integrated with
other existing software
 Technical Feasibility
 Econonomic Feasibility
 Operational feasibility
 Technical feasibility assesses the current resources (such as
hardware and software) and technology, which are required to
accomplish user requirements in the software within the allocated
time and budget.
 Analyzes the technical skills and capabilities of the software

development team members
 Determines whether the relevant technology is stable and
established
 Ascertains that the technology chosen for software development
has a large number of users so that they can be consulted when
problems arise or improvements are required.
 Operational feasibility assesses the extent to which the
required software performs a series of steps to solve business
problems and user requirements.
 Determines whether the problems anticipated in user
requirements are of high priority
 Determines whether the solution suggested by the software
development team is acceptable
 Analyzes whether users will adapt to a new software
 Determines whether the organization is satisfied by the
alternative solutions proposed by the software development
team.
 Economic feasibility determines whether the required software
is capable of generating financial gains for an organization.
 Focuses on the issues listed below.
◦ Cost incurred on software development to produce long-term gains for
an organization
◦ Cost required to conduct full software investigation (such as
requirements elicitation and requirements analysis)
◦ Cost of hardware, software, development team, and training.

Feasibility Study and Requirement Gathering

Uploaded by

Copyright:

Available Formats

Feasibility Study and Requirement Gathering

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Feasibility Study and Requirement Gathering

Uploaded by

Copyright:

Available Formats

Mir Yousuf

Assistant Professor: CSE

OUTPUT OF THIS PHASE

It contributes to the following features

What is being done?

1. Incomplete problem definition

Due to the depth of information required , the requirement

 Analyzes the technical skills and capabilities of the software

You might also like