1. The document discusses requirements engineering approaches for developing web-based information systems (WBIS). WBIS have unique characteristics compared to traditional software systems. 2. Stakeholders in WBIS projects have a wider scope than traditional projects, including marketing and design specialists. Requirements engineering must account for conflicts between diverse stakeholder needs. 3. The document reviews several methodologies for WBIS development, including web engineering, relationship management, and internet commerce development methodologies. All emphasize the importance of involving stakeholders and adapting to their changing needs.

1. 1
Requirements Engineering for Web-
Based Information Systems

2. 2
Internet
• Internet is a network of networks
• It is a huge network providing various kinds of information in various
forms
• We use internet in our daily life to send an email, to get information
about a particular topic and even to chat with our friends

3. 3
Web-Based Information Systems (WBIS)
• What makes web systems so different from the traditional
software systems that their planning and construction
requires a unique development process?
• First, we need to understand different types of web-based
information systems

4. 4
Types of WBIS Models
• Those that deliver advertising and promotion
• Those that assist business workflow
• Those that facilitate inter-organizational interaction
• Those that support multi-participant trading

5. 5
Differences in WBIS Models
• Each kind of WBIS model emphasizes distinct aspects of site design
depending on its purpose
• Some focus on supporting business to business transactions, the
construction of online metaphors for business activity, and customer
assistance

6. 6
Differences in WBIS Models
• Others look at promoting organizational brand, building market trust
and credibility
• While some simply accentuate web contents, layout, navigation and
search for organizational information

7. 7
E-What?
• E-commerce
• E-banking
• E-auctioning
• E-government
• E-voting
• E-healthcare
• E-insurance
• E-everything

8. 8
WBIS and Requirements Engineering
• In the richness of web design issues, many directly concern WBIS
customers and thus necessarily absorb requirements engineers

9. 9
Stakeholders in WBIS
• Apart from the obvious project stakeholders, such as sponsors,
customers, and users, the parties involved also include content
developers and copyright consultants, marketing and public relation
specialists, media planner and strategists, creative and art directors,
graphic designers, multimedia and interaction developers, and many
others, who are not often considered by requirements engineers as
having input into the specification of a traditional software system

10. 10
Stakeholders in WBIS
• It is a fact that stakeholders’ opinion conflict with each other
• In WBIS, these conflicts are firmly embedded not only in the needs of
the software systems to be developed but rather in the business
processes and objectives of online buyers and sellers, and in the
constraints imposed on the system by agencies regulating the
financial transactions or determining compliance with the laws of the
land and international treaties

11. 11
Key facts
• The scope of concerns to be considered in the earliest stages of web
site construction can be significantly enlarged, due to the marketing-
driven development process

12. 12
Key facts
• The delivery cycle for web-enabled applications is commonly very
short, i.e., 3 months, which leaves very little time for any formal
requirements gathering and their consolidation

13. 13
Key facts
• Current requirements engineering practices for WBIS projects are
inadequate, failing requirements engineers in identification and
characterization of the potential system users, their needs and
preferences, and the features required of the web systems under
development

14. 14
Key facts
• There is need to emphasize on the stakeholder views and
opinions on requirements evolution in web development
• A stakeholder in this context is considered to be any
individual, group, or organization whose actions can
influence or be influenced by the development and use of
the system whether directly or indirectly

15. 15
RE Approaches for Development of WBIS
• Web engineering
• Relationship management methodology
• Internet commerce development methodology
• Web information systems development methodology

16. 16
Web Engineering
• Web development should be recognized as a process with all
its structure and complexity
• Most of the difficulties with respect to development of large
web sites can be attributed to a lack of suitable process
models for the project teams to follow, suitable architecture,
or a project model for the development of web-enabled
application

17. 17
Web Engineering
• One of the most significant points, as a new and emerging trend
associated with the development and evolution of web-enabled
services, is the acknowledgement of the importance for project teams
to improve by learning through experience

18. 18
Relationship Management Methodology (RMM)
• RMM was introduced as a methodology for the development of
hypermedia systems
• While acknowledging the importance of requirements analysis, RMM
sheds little light on its mechanism

19. 19
Internet Commerce Development Methodology
(ICDM)
• ICDM combines the elements of business analysis as well as
system development
• Internet commerce is one of those fields, that necessitate
intense business activity as part of their systems
development, and thus it requires a thorough analysis of its
place in the overall business strategy

20. 20
Internet Commerce Development Methodology
(ICDM)
• Customers and suppliers (users of the systems) are encouraged to be
involved at various stages of the e-Business operations, and
participate in periodic reviews

21. 21
Internet Commerce Development Methodology
(ICDM)
• The two commonly used requirements gathering techniques in ICDM
are:
• Brainstorming
• Group Requirements Sessions (GRS)

22. 22
Internet Commerce Development Methodology
(ICDM)
• Although clearly acknowledging the importance of stakeholder issues
and “learning from experience” in requirements establishment for
WBIS, ICDM is not prescriptive as to the use of any specific model or a
process where these issues could be addressed

23. 23
Web Information Systems Development
Methodology (WISDM)
• WISDM is employed with the aim for evaluating the effectiveness of a
pre-web methodology to the web-based methodology
• RAD and prototyping are effective approaches for WISDM project
development

24. 24
Non-Functional Requirements
• Special focus on non-functional requirements
• Security
• Efficiency
• Scalability
• User-interface design