A Methodology for Constructing User-Oriented Requirements Specifications for Large-Scale

Systems Using Electronic Hypermedia

DUC TUAN NGUYEN3565645

Agenda

• Problem• Author• Method• PDD• Example• Literature review• Question

Problem

• Requirement Specification for large-scale software system

• Text-based– Failed to support communication– Hard to understand– Unexpected result

The method

Define a method to help constructing user-oriented requirement specification for such large scale system using electronic hyper media

The author

• Scott P. Overmyer.• Current: a director, MSIS Program at Baker College • Past:

– associate Professor at South Dakota State University – associate Professor at Massey University – as an owner at Scotto's Italian/American Deli

• Education:– bachelor in Psychology at University of Colorado at

Colorado Springs – MSIE, Industrial Engineering/Human Factors at University

of Lowa– PhD in Information Technology (Info & Software Systems

Engineering) at George Mason University

The method was developed when he was an associate professor at Drexel University (from 1997 to 2000)

6 steps

PDD

• meta-modelling technique developed for the method engineering process (Weerd and Brinkkemper, 2008)

Example

• ID Description • 1 Search and identify camera agent using voice

command • 2 Search and identify camera agent using text input

(GPS location or street name) • 3 View camera observation • 4 Select object in the view and connect to backoffice

database by matching ID • 5 Matching ID can be given when object is selected • 6 Send command to camera agent to zoom, turn or

focus on object • 7 Automatically turn on and off or switch off led light

Example

• Perform analysis

Example

• 2. Establish Electronic Outline for Requirements Specification – Documentation for text-based requirements – Software and hardware supported for required

hypermedia requirement (2,3,4,6) – Repository for rapid prototypes product and animated

storyboard – Converting prototypes and animated storyboard to

document, diagrams

• 3. Decide if Multimedia Specifications is Useful or Necessary:

Example

4a. Choose requirement to represent with multimedia exhibits

Example

4b. Prioritise Selection of Multimedia Exhibits:

4c. Prepare Existing and Develop New Multimedia Exhibits

Example

4d. Describe requirements using conventions means: • - Requirement 2: A list of available most used camera agent

presented and a text field to input location data. Data can be input as GPS location or street name, after the location is given a list of matched camera is shown and each camera is selectable

• - Requirement 3: A clips of example camera turning around and viewing in a meeting mall where full view of the mall can be seen.

Example

• 5. Integrated with Electronic Outline

• 6. Review/Validate specification with Stakeholders: - Several meetings between all stakeholders are setup to review and validate the requirement specification. The requirement data is expanded after those meetings and the 6 steps processes are iterated.

Literature review

• Requirement Specification for software system• Text-based format and hard to understand by all stake

holder (Aiken, 1989)• Insufficient presentation method (Davis, 1990)• The written specifications have been judged essentially• unusable by the end-user community (US Accounting office,

1979)• hypertext/hypermedia is a better method for presenting

either factual or spatial information than either text or captioned pictures alone (Instone K, Brown E, Leventhal L, Teasley, B., 1993)

• Knowledge base requirement engineering for complex system (Ratchev, Urwin, Muller and Pawar, 2003)

Questions &

Feedback