SENG 611

1
SENG 611
Requirements Engineering
Group 5 Final Presentation
October 18, 2001
2
Group 5
Guy Davis Mohamed S. Shehata
3
Presentation Overview

• Introduction
• Process
• Personality Factors
• Interview
• Repertory Grid
• Concept Mapping

4
Presentation Overview (cont.)

• Prioritizing Requirements
• Software Life Cycle (SLC)
• Software Requirement specifications (SRS)

5
Introduction

• Objective of the system
• Real estate system.
• Tasks
• Keep track of properties with their amenities,
  selling, and rental prices.
• can execute queries for potential customers with
  different priorities.
• develop a web catalogue for web browsers.
• generate different reports on demand.
• Techniques
• Different techniques will be used to evaluate the
  SRS for this project.
• Goals
• Develop an SRS document for the real estate
  project
• Prioritize these SRS using AHP technique

6
Process for evaluating the SRS
Final SRS
Concept Mapping
Personality Factors
Repertory Grid
Interviewing
Prioritizing Requirements
7
Personality Factors

• An interesting way to explore your personality
• An interesting way to get the team members into
  discussion

8
Personality Factors (cont.)

• We used the Keirsey Temperament Sorter Test
• Mohamed and Guy are E S T J.
• Comments
• Good way to break the Ice between team members
• Good way to discover the points of strength and
  weakness
• in the team.
• This test is not that reliable as it can depend
  on
• the mood of the person on the test day.
• It is only one test. It cant be fully proven to
  give accurate results

9
Interviewing

• We used both structured and unstructured
  interviewing. We concluded
• the following for the structured
  interview

• It is more effective in extracting detailed
  information about the project
• It allows the interviewer to guide the interview
  to the direction he wants
• The purpose of this interview is clear to the
  interviewee.
• Needs a lot of preparation
• Needs an extensive study on the project domain
  and materials.

• We also concluded the following for the
  unstructured interview

• It is effective when the RE wants to scope the
  domain of an issue.
• The goal is to be established later.
• The data acquired is unclear.
• Very time consuming
• Repeatable questions from the interviewer

10
Repertory Grid
11
Concept Mapping
12
Prioritizing Requirements
13
Prioritizing Requirements

• R1 The system shall store up to date
  information about each property in
  a robust database.
• R8 The system will provide daily, weekly, and
  monthly reports about the agency activities
  during the period each report covers.
• R3 The system shall provide searching and
  browsing access to customers.
• R4 The system should recognize the various
  "states" that a property may be in such
  as "unlisted", "listed", "conditionally sold",
  and "sold.
• R9 The system shall provide windows-format
  graphical interface. 
• R2 The system shall provide advanced searching,
  browsing, and editing functionalities to real
  estate agents and agency office staff. This will
  require differing levels of access and controls.
• R5 The system will support internet access to
  the web page of the agency.
• R6 The system will provide on-line
  transactions.
• R7 The system will run on Windows platform and
  use standard communication protocols.

14
Software Life Cycle

• We decided to use the incremental model for the
  REC

15
Software Requirement Specification (SRS)
Software Requirement Specification (SRS)

• SRS writers should
• be unambiguous
• be funny
• be understandable
• be simple
• review and revise

• SRS docs should
• be kept up-to-date
• contain audience notes
• for developers
• for management
• for quality assurance
• for tech writers

Adapted from Painless Functional Specifications
by Joel Spolsky