1

REQUIREMENTS ENGINEERING

FOR

WEB BASED INFORMATION SYSTEMS

CONTENTS

What is WBIS? Existing methods of requirements analysis for WBIS The pre-eminent importance of stakeholder analysis Identification of stakeholder views and concerns The processes governing elicitation of web systems

requirements Derivation of a model of concern-driven requirements

evolution

3

4

WHAT IS WBIS??? Web information system, or web-based information system, is

an information system that uses internet web technologies to deliver information and services, to users or other information systems / applications. It is a software system whose main purpose is to publish and maintain data by using hypertext-based principles.

A web information system usually consists of one or more web applications, specific functionality-oriented components, together with information components and other non-web components. Web browser is typically used as front-end whereas database as back-end.

5

WEB-BASED INFORMATION

SYSTEMS

6

Web-based information systems (WBIS) are often claimed to have a development process quite different to that of traditional software systems.

7

WHAT MAKES WEB SYSTEMS SO DIFFERENT FROM THE TRADITIONAL SOFTWARE SYSTEMS THAT THEIR PLANNING AND CONSTRUCTION REQUIRES A UNIQUE DEVELOPMENT PROCESS?

8

To deliver advertising and promotion. To assist business workflows. To facilitate inter-organizational interaction. To support multi-participant trading.

LAWRENCE, MILETSKY AND THEIR COLLEAGUES IDENTIFY FOUR MAJOR TYPES OF WBIS MODELS

9

MARKETING ISSUES ARE DOMINATING

FACTORS IMPACTING WEB SITE’S DESIGN

10

APART FROM THE OBVIOUS PROJECT STAKEHOLDERS, SUCH AS SPONSORS, CUSTOMERS AND USERS, THE PARTIES INVOLVED ALSO INCLUDE

Contents developers and copyright consultants, Marketing and public relation specialists, Media planner and strategies, Creative and art directors, Graphic designers, Multimedia and interaction developers, and great many others, who are not often considered by

requirements engineers as having input into the specification of a traditional software system.

11

The fact that project stakeholders commonly hold conflicting opinions is well-known to the requirements engineering community.

IS THAT REALLY SO IN WBIS????

12

THE DELIVERY CYCLE FOR WEB-ENABLED APPLICATIONS IS COMMONLY VERY SHORT, I.E. LESS THAN 3 MONTHS WHICH LEAVES VERY LITTLE TIME FOR ANY FORMAL REQUIREMENTS GATHERING AND THEIR CONSOLIDATION.

13

DEVELOPMENT OF WEB-BASEDINFORMATION COMMONLY RELIES ON A STEP-WISE PROTOTYPING APPROACH

The iterative process of design, prototyping and evaluation is observed, and it commonly involves following activities

Exploration Refinement Production Implementation Launch Maintenance Discovery

APPROACHES TO REQUIREMENT ENGINEERING FOR DEVELOPMENT OF WBIS

15

APPROACHES TO REQUIREMENT ENGINEERING FOR DEVELOPMENT OF WBIS

oWEB ENGINEERING

oRELATIONSHIP MANAGEMENT METHODOLOGY

oHOWCROFT’S METHODOLOGY

oINTERNET COMMERCE DEVELOPMENT METHODOLOGY

oWEB INFORMATION SYSTEMS DEVELOPMENT METHODOLOGY

16

WEB ENGINEERING

17

WEB ENGINEERING

According to Ginige Web development should be recognized as a process

with all its structure and complexity, and not just as an atomic event considered by many web practitioners.

18

WEB ENGINEERING FOUNDERS EMPHASIZE ON

Importance of addition of new functionality, information resources and their addition to the system iteratively to the system over time.

19

Difficulties related to Development of large Web Sites. Lack of suitable models for the development teams to

follow. Suitable Architecture. A product model for the Web Enabled Applications

WEB ENGINEERING FOUNDERS EMPHASIZE ON

20

A good practice in this technique is to treat the users of the system as an integral part of the system

WEB ENGINEERING

21

22

ONE OF THE MOST SIGNIFICANTPOINTS, AT LEAST FROM THE POINT OF VIEW OF THIS WORK, PRESENTED BY GINIGE AS ANEW AND EMERGING TREND ASSOCIATED WITH THE DEVELOPMENT AND EVOLUTION OF WEB-ENABLEDSERVICES, IS THE ACKNOWLEDGEMENT OF THE IMPORTANCE FOR PROJECT TEAMS TOIMPROVE BY LEARNING THROUGH EXPERIENCE

FOR YOUR INFORMATION !!!

23

WHEN DEVELOPING SUCH SYSTEMS, IT IS ESSENTIAL TO HAVE APPROPRIATE MEASURES BUILT INTO THE DEVELOPMENT PROCESS THAT ALLOW DEVELOPERS TO CATER FOR USER RELATED ISSUES.

24

RELATIONSHIP MANAGEMENT METHODOLOGY

25

RELATIONSHIP MANAGEMENT METHODOLOGY

Involves seven steps Shed light on the mechanisms of requirements analysis The steps require a high level of specialized technical

skills Does not even linger near the establishment of

requirements

26

27

HOWCROFT’SMETHODOLOGY

28

HOWCROFT’S METHODOLOGY Phase One: Analysis

Step One: Development of a Web Strategy Step Two: Defining Objectives Step Three: Objectives Analysis

Phase Two: Design Step One: Design Step Two: Design Testing

Phase Three: Generation Step One: Resource Selection Step Two: Design Review Step Three: Code Generation & Installation Step Four: Testing

Phase Four: Implementation Step One: Implementation Step Two: Maintenance Step Three: Objectives Review

Evaluation

29

As part of the Objectives Analysis (Phase One, Step Three) include: Time Analysis to assist with the management of the project. Training Analysis to assess the cost of training staff to

maintain the site Ongoing Cost Analysis to assess the running costs of the site

search Ongoing Maintenance Analysis to assess the frequency of

updates and the frequency of the Objectives Review (Phase Four, Step Three).

As part of Phase Two, supply a prototype or screenshots of the site to be built.

Ensure each Phase is signed off with the Client.

30

Despite its thorough coverage of organizational objectives, business needs and user needs, the methodology does not propose any concrete means of how web developers could incorporate stakeholder issues into their work.

31

INTERNET COMMERCE DEVELOPMENT METHODOLOGY (ICDM)

32

INTERNET COMMERCE DEVELOPMENT METHODOLOGY (ICDM)

It emphasizes the formulation of business strategy which can be translated into an Internet commerce strategy. Techniques and approaches for capturing requirements in a group setting are explained as well as frameworks for functional and physical requirements. At the lower level ICDM deals with formal engineering methods which are part of an overall aim of organizational change.

33

WEB INFORMATION SYSTEMS DEVELOPMENT METHODOLOGY

34

WEB INFORMATION SYSTEMS DEVELOPMENT METHODOLOGY

WISDM is a framework and methodology for the development of web-based information systems. The framework recognizes that a methodology in practice emerges from the triad of situation, human agents, and methods.

35

36

COMPARISON OF APPROACHES

37

KEY POINTS

38

WBIS are acquired by organizations, from vendors, in order to web-enable (both intra-and inter-organizational) workflows.

WBIS are developed or configured in an incremental manner using the evolutionary prototyping approach.

New features are added to the WBIS with each development cycle iteration.

The time frame for the development of WBIS is very short, i.e. about 3 months.

A diverse and broad base of stakeholders are the potential users of web services, but it is not always possible to anticipate the constituent groups.

The stakeholders are external to and thus beyond control of the project initiator.

Due to this unanticipated large and relatively heterogeneous groups of stakeholders, system requirements for web applications are often “created from scratch”, rather than elicited.

The existence of a mechanism that enables web teams to learn from past experience, can aid the establishment of system requirements.

39

ISSUES INADEQUATELY COVERED BY THE CURRENT APPROACHES

Identification and description of stakeholders and their needs

in the process of development and implementation of WBIS.

Dealing with the needs and concerns expressed by a diverse

and relatively large WBIS stakeholder base.

Impact of the stakeholder needs and concerns on the

requirement-driven features associated with the WBIS.

Explanation of how the needs of the various potential users

are inculcated in the further evolution and roll-over of web

services.

SIGNIFICANCE OF CONCERNS IN REQUIREMENTS ENGINEERING

41

What is stakeholder?Stakeholder analysis?Benefits of stakeholder analysis?

STAKEHOLDER ANALYSIS

42

A review of literature in information systems development (ISD) and project management reveals that one of the major causes of project failures can be attributed to the dissatisfaction of stakeholders with either the way the project is undertaken or the final product of the project.

43

44

Stakeholder analysis in conflict resolution, project management, and business administration, is the process of identifying the individuals or groups that are likely to affect or be affected by a proposed action, and sorting them according to their impact on the action and the impact the action will have on them.

45

Benefits of stakeholder analysis helps with the identification of

the following: Stakeholders' interests Potential risks Key people to be informed about the project during the

execution phase Negative stakeholders as well as their adverse effects on the

project.

46

What is viewpoint? Stakeholder viewpoint? Multi view?

VIEW POINT ANALYSIS

47

The concept of viewpoints was first introduced by Mullery in his Controlled Requirement Specification (CORE)method.

The viewpoint approaches recognize that the development of a system involves the participation (in the form of expressing requirements) of multiple stakeholders with different perspectives, and conflict may erupt between these different perspectives.

48

Preview is an entity which encapsulates some but not all information about a system’s requirements.

WHAT IS PREVIEW (PROCESS & REQUIREMENTS ENGINEERING VIEWPOINTS)?

49

Preview viewpoints are flexible, generic entities which can be used in different ways and in different application domains.

Preview provides an iterative process, based on the spiral model by Boehm of identifying essential viewpoints, emergence of new requirements, and fine tuning of existing ones with each cycle of the process.

50

With the concept of multiple stakeholders a number of different perspectives reveal, namely technical (system analysts), organizational (societal), and personal (individual).

51

What are concerns?Stakeholder concerns?

CONCERN ANALYSIS

52

Any project could only be successful in terms of stakeholder satisfaction when the needs and expectations of the distinct (and non-homogenous) stakeholder groups could be complied with. Should the compliance not be achieved, the stakeholders will claim this situation as of great concern to them and perceive it as a serious problem.

53

Importance of stakeholder concerns in IS projects by maintaining that the perceptions of stakeholders with regards to the proposed information system are formed on the basis of their concerns.

54

DEFINITION OF STAKEHOLDER CONCERNS A concern is an issue voiced by a particular stakeholder

with regards to some aspect of the proposed information system, which impacts the stakeholder’s involvement in this system and which when addressed will determine the need for further evolution of the system.

A MODEL OF CONCERN-DRIVEN REQUIREMENTS EVOLUTION

CONCERNS BASED ADOPTION MODEL (CBAM)

STAGES OF CONCERN (SOC)- FEELINGS AND MOTIVATIONS

58

ANALYSIS OF THE WBIS REQUIREMENTS EVOLUTION PROCESS IN TERMS OF SOC STAGES

• Stakeholders’ awareness of change• Stakeholders’ informational pursuits• Personal engagement in the implementation• Management engagement in the implementation• Dealing with the consequences of change• Collaborative improvement over change• Possible refocusing

NATURE OF WBIS PROJECTS

60

61

SUMMARY

• Participation of stakeholders with multiple viewpoints can lead to conflicts in requirements engineering for WBIS.

• The model of concern-driven web requirements evolution can be used as a solid basis for development of WBIS.

• New generation of software systems include enterprise-wide systems, commercial off-the-shelf systems, and reuse/component-based systems.

• New generation of software systems commonly involve the sophisticated enabling infrastructure, high business impact, short time to market and high level of stakeholder concerns.

• These new generation of software systems redefine the role of a requirements engineer and shift his or her attention from requirements management to stakeholder and concern management.

62

NEW REQUIREMENTS ENGINEER

The new requirements engineer now must spend a considerable amount of effort in dealing with non-requirements. His traditional province - stakeholders’ expression of what they wanted, what they needed, what would make their work improve - deals with those same needs, yet most of these things are now concerns.

SO ENTER THE NEW GENERATION OF REQUIREMENTS ENGINEERS!

QUESTIONS ???

63

64

REFERENCES

http://www.cs.toronto.edu/~eharley/340F/RQ/Gajenslide1.htm

http://aisel.aisnet.org/ecis2000/73/ http://webcache.googleusercontent.com/search?

q=cache:KFbOFuOIIyEJ:ftp://ftp.computer.org/MAGS/MULTIMED/mms/webEng/112113.doc+internet+commerce+development+methodology&cd=1&hl=en&ct=clnk&gl=pk

65