Capturing Web Application Requirements through Goal-Oriented Analysis

Presented by Chin-Yi Tsaicyt@pmlab.iecs.fcu.edu.tw

http://140.134.26.25/~cyt

2

Outline

• Introduction and Motivation

• Background

• UWA Requirements a model for the analysis of web application requirements

• Closing Remarks

3

Introduction and Motivation

• A number of comprehensive models, methodologies and notations for managing the analysis of software requirements have been developed and assessed in the last decade.Web Application?

• Conceptual tools for effectively supporting the activity of requirements analysis of web application are needed. InteractiveHypermedia-intensive

HDMOOHDM

domain analysis object modeling view design navigation design implementation design construction

domain analysis object modeling view design navigation design implementation design construction

4

Introduction and Motivation (cont’d)

• Web application are today first and foremost articulated means of communication between the end-user and the stakeholders who conceived the site.Stakeholder-centeredOffer content and interaction capability which best meet

the goal of the usersSatisfy the business and communication objectives of the

site itself

complexitycomplexity

5

Introduction and Motivation (cont’d)

• Specific needs of requirement management for web applicationManaging complexity

High-level communication and business goal

Requirement-design gapGap between requirements and hypermedia specification

AccessibilityNeed informal, lightweight, straightforward method

TraceabilitySuspension of commitment

Requirement analysis

6

Introduction and Motivation (cont’d)

• EU-funded UWA projectA light-weight methodologyAn intuitive UML-based notationA set of heuristic principlesA Rational Rose-based analysis tool

Goal-oriented Scenario-based

7

Background• RE framework/methodology

KAOS NFR framework i*

• RE and web application Goal-based analysis

• KAOS seems to be not sufficient for analyzing the goal and the expectations of the stakeholders of web application Communication and business goal Software component and modules Formal

Goal-orientedRefinement

Goal-orientedRefinement

8

UWA Requirements

• Banca121Web-based credit-card serviceProduct manager, salesman, end-users

9

From Goals to Requirements

10

A Taxonomy for Requirements

• Categories of requirementsContentStructure of contentAccess paths to contentNavigationPresentationUser operationSystem operation

• A requirement belongs to exactly one dimensionRequirement specifications are the input for design activit

y (HDM, OOHDM, WebML, RMM, WSDM)

11

A Taxonomy for Requirements (cont’d)

• Navigational (N)Effectiveness, orientation, accessibility, self-evidence,

predictability

• Content (C)Completeness, authority, accuracy

• Presentation (P)Clearness, animation control, consistency

NFR

12

Goals and Scenarios as Mutually Supportive

• The power of scenarios is their capability of representing goals more concretely and easy to understand

• Scenario It can help to refine the high-level goals into sub-goal and

then into requirements It can help to assess and validate the goal graph

13

Closing Remarks• The basis elements of UWA Requirement model

StakeholderGoalSub-goalRequirementRequirement dimensionRefinement process

• The model can be complemented by other techniquesUML use caseHypermedia design model Interface design methodologies

the lower-level function specification and interaction design

the lower-level function specification and interaction design

14

Closing Remarks (cont’d)

• Requirement modeling primitiveThe hypermedia taxonomy for requirement It allows capturing hypermedia and web high-level

specification It helps to smoothly indicate design suggestions