You are on page 1of 6

REQUIREMENTS ELICITATION

RMT
DOCUMENT

PROFESSOR LYNNCARTER
REQUIREMENTS ELICITATION DOCUMENT MSIT-2010

Risk Management Tool

Requirements Elicitation Document


Version 1.2

Prepared By: Team- MSIT2010

Team Members Roll No. E-mail Address

Chinnaiah Gopineni 1209A015 chinnag.linus@gmail.com


Chakradhar Katta 1209A023 ckatta23@gmail.com
Murali Krishna Tejaswy M 1209A029 teja.music16@gmail.com

Date: 8th march, 2010

Version History:

Version
Date Changed By Changes Made
No.
1.0 07-05-2010 Chakradhar K Creating the document

Modifications in
1.1 07-05-2010 Chinnaiah G
Requirements

Modifications in Scope and


1.2 08-05-2010 M K Tejaswy M
Requirements

MSIT -2010 RMT Team Page: 2


REQUIREMENTS ELICITATION DOCUMENT MSIT-2010

Table of Contents

Contents
Table of Contents .................................................................................................................3
Contents ......................................................................................................................................3
Introduction ................................................................................................................................4
Overview ....................................................................................................................................4
Stakeholders........................................................................................................................................ 4

Purpose ............................................................................................................................................... 4

Scope .................................................................................................................................................. 4

Requirements ..............................................................................................................................4
Functional Requirements: .................................................................................................................... 4

Requirements Elicitation Problems ..............................................................................................6


Problem of understanding: .................................................................................................................. 6

Rules: ..........................................................................................................................................6
Definition: ...................................................................................................................................6
Reference: ...................................................................................................................................6

MSIT -2010 RMT Team Page: 3


REQUIREMENTS ELICITATION DOCUMENT MSIT-2010

Introduction
Risk management tool (RMT) is a stand-alone tool for an
individual to manage a set of risks identified. It helps in
prioritizing the risks and providing effective solutions.

Overview

St
akehol
der
s
1. TEAM MSIT-2010

2. Prof. Lynn Robert Carter, PhD, C.M.U

3. Smt G Swetha Padma, MSIT, IIIT-H

4. Software Developers

Pur
pos
e
It is software’s nature to exhibit a list of issues whose
addressing is sporadically effective using naïve techniques. As
software is prone to such issues, there should be a way of
recording them before they occur, analyze them and eliminate or
confront them with solutions.

Scope
This Document contains various functional and non-functional
requirements of the RMT, assuming that the end user knows how to
frame a risk statement.

Requirements

Funct
ionalRequi
rement
s:
The tool takes risk statements as its input. The duty of the RM
Tool is to

• Build and maintain a list of risks


• Calculate the Exposure of risks

MSIT -2010 RMT Team Page: 4


REQUIREMENTS ELICITATION DOCUMENT MSIT-2010

• Put the risks in a Prioritized order


• Calculate the Impact of risks in terms of Money
• Calculate the Impact of risks in terms of Time
• Follow a resolution Approach for ignoring/considering a
risk
• Manage Risks by
o Mitigation
o Contingency
• Provide a risk status

Non-Funct
ionalRequi
rement
s:
Usability

The RMT

• Should be easy to start and user friendly


• Should provide a help file on how to use
• Should provide a detailed documentation on different
types of risks

Reliability

The RMT

• Should be reliable. It should not fail to show the


output
• If the tool fails, the risk data should be recoverable

Performance

The RMT should

• Use minimal resources (CPU time and memory)


• Be accurate in results as it is dealing with risks
o Status of the risk is either 0 or 1

Supportability

The RMT should

• Be adaptable to various hardware and software


platforms

MSIT -2010 RMT Team Page: 5


REQUIREMENTS ELICITATION DOCUMENT MSIT-2010

• Work successfully in different operating Systems


• Be adaptable to changes in the requirements
• Be easily configurable

Supplementary Requirements

• Implementation constraints of using python or java


• Internationalization concerns in both writing the
software and using the Impact units in terms of money
(as US dollars, Indian Rupees, Dinars and etc.)
• Documentation Standards

Requirements Elicitation Problems

Pr
obl
em ofunder
standi
ng:
1. Internationalization

Rules:
1. Must be implemented in Object Oriented Programming

Definition:
RMT – RISK MANAGEMENT TOOL

References:
1. Spring 2010: MSIT/ Hyderabad topics in
http://IvoryTower.Qatar.cmu.edu/

2. Della 04.jar

MSIT -2010 RMT Team Page: 6

You might also like