Requirement Engineering for Web Applications

1

• Requirement Engineering for Web Applications
• Introduction
• -play important role in WA deve.
• Why there is need of RE?
• Because requirements are not properly described
• May be in ambiguoue or incorrect manner
• Sometimes poor requirements
• What is poor requirements?
• -No detail planning
• -inadequate software architectures
• What RE Do?
• -deals with principles, methods and tools .
• For What ?
• -to identify, describe, validadte and manage
  requirements
• Which are tools and methods?

2

• Then what such practioners do?
• -then they do RE process in ad-hoc manner
• How to do RE?
• -According software engg.
• What s/w engg says
• -s/w engineers tasks are collections of
  requirements and action of requirements.
• Is RE has really solved problem?
• Eventhough having several standars, approaches,
  models, description languages and tools, s/w
  industry still struggling for requirements.
• What do companies feel about?
• -major problem in deve. Process is requirement.
• -requirement management is another problem.
• Why these problems in requirements?
• -because poor user participation
• -incomplete or volatile requirements

3

• Survey say
• -16 of systems fully meet requirement
• -while 53 systems do not satisfy requirements.
• Fundamentals
• Where Do Requirements come From?
• -Comes from individual objectives
• -comes from expectations of stakeholders
• Who are stakeholders?
• -people or organization
• -they can have direct or indirecteffect on
  requirements.
• What are other typical stakeholders?
• -content authors,domain expert, usability
  experts, marketing professional
• E.g. Following are examples of requirements
• -WA should support 3000 concurrent user
• -j2EE should use as deve platform .

4
What is big challenge then? -to understand and
sttle down often conflicting objectves,
expectations, background and agendas e.g. may be
conflicts between capabilities and available
bugdets may be in project
schedule desired quality may be between desired
development technology and developers skill,
experience. What is solution then? -develop a
shared vision among stakeholders -derive more
detailed requirements ---why? -because
stakeholder objectives are often informal. What
requirement does? -it describes a property to met
or -it describes service to be providedby a
system. What is definition of requirement? -condi
tion or capability required by user to solve a
problem or to achive an objective.
5
What is definition of requirement? -condition or
capability required by user to solve a problem
or to achive an objective. Or -condition or
capability possd by ssyem to satisfy a contract,
standard, specification. How general
requirements are classified? -functional
requirements -non functional requirements -constra
ints What is functional requirements? -it
defines a systems capabilities and
services What non functional requirements
do -describes desired levels of quality. E.g. How
secure and how usable What are constraints? -non
negotiable conditions -e.g.skill level of deve.
Team, available budget, delivery date, existing
computer infrastructure at client.
6
What do you mean by requirement documents