REQM TOOL 1

RESEARCH PAPER
ON
REQUIREMENTS MANAGEMENT TOOL
SITARA DAR, Member, IEEE
In its research to help organizations develop and maintain
Abstract— quality products and services, the Software Engineering
Despite decades of experience the effective development of Institute (SEI) has found several dimensions that an
software remains a difficult challenge. Most of the schedule organization can focus on to improve its business. Figure
delays in project delivery are caused by misunderstanding of the below illustrates the tree critical dimensions that
requirements from user and among development team. If organizations typically focus on: people, procedures and
requirements are taken properly, elucidated more clearly, methods, and tools and equipment.
analyzed and then implemented, it will reduce the delays in
project/product shipments. Therefore, I have selected this
process area to address the core issue in project delays. I hope
that my devised tool will help people to manage their
requirements more efficiently and unambiguously. I achieved
the sound understanding of process improvement discipline in
general and an organizational workflow to achieve process
improvement goals in particular. It will be according to the
CMMI Level 2 – REQM process area. This makes product more
qualitative

I.INTRODUCTION

Process improvement is a series of actions taken to identify,

analyze and improve existing processes within an
organization to meet new goals and objective. These actions
follow a specific methodology or strategy to create successful
results.
An essential aspect of software engineering is the discipline it
requires for a group of people to work together cooperatively
to sole a common problem. Defined processes set the bounds
for each person’s roles and responsibilities so that the
collaboration is successful and efficient one. Processes crop
up throughout software engineering efforts.
So, in all Software process provides the framework for the
development of software systems. Deficiencies in the
definition or execution of the activities which comprise the
process affect the quality and cycle time of the system under
production adversely. Hence, it is important to understand
how the errant activities may be corrected in-process, i.e.
during the course of development.
Several approaches to in-process improvement have been
developed over the years. Noteworthy examples include
Software Engineering Institute (SEI) approach, the Software
Engineering Laboratory (NASA/SEL) approach, the process
cycle approach and etc. these approaches address the entire
scope of software development and its improvement.
Effective processes also provide a vehicle for introducing and
using new technology in a way that best meets the business
objectives of the organization.

Figure 1: Organizations Development Model
Requirement Management (RM) is about organizing the
requirements and additional information gathered during the
Requirements Engineering (RE) process, and managing
changes of these requirements. Requirements Management
tool will be viewed as a two edged sword. On one hand it
views as productivity and a quality enhancer, on the other
hand it works as a mechanism to control routines’ and de-
skill work.
REQM Tool removes the guesswork from everyday
operations, creating consistency and predictability to help
organizations share information, streamline tasks, and
comply with mandates. Results are meaningful because the
data comes from a standardized process. It is consistent in the
way things are done so improvements are made over time.
Requirements Management is the process of establishing the
base capabilities of a project. This is more than a statement of
purpose for an applications - it is the specific goals that the
application must meet. As such, investigating and recording
Requirements is an important step in any project.
Thorough Requirements Management is effective in
improving workflow across the project lifecycle, from
Software Design to Cost Estimation and even creating User
REQM TOOL
Documentation.
Software development involves perhaps 50 percent computing
and 50 percent communication. Unfortunately, most teams
are better at the computing part, and requirements are almost
entirely about communication. There are many links in the
requirements communication chain, as illustrated in Figures
1 and 2. A breakdown in any of these links leads to
significant problems. For example, if an analyst
misunderstands stakeholder input about requirements, if
important requirements information does not surface or if an
analyst and developer do not share the same understanding
about requirements, the resulting product will not satisfy
customers.
Requirements Management (REQM) Tool is used to manage
the requirements of the project’s products and product
components and to identify inconsistencies between those
requirements.
It is all about balance, communication, and adjustment along
the way. To prevent one class of requirements from over-
riding another, constant communication among members of
the development team is critical. For example, in software
development for internal applications, the business has such
strong needs that it may ignore user requirements, or believe
that in creating use cases, the user requirements are being
taken care of
Figure 2: SDLC Phases Process
This document covers the all phases of requirements
management CMMI Level II. It contains scope of the project,
system requirement specification and interfaces. All the
requirements being gathered for the development of whole
application is explained in the said document with detail.
The devised tool helps development professionals to manage
their requirements more efficiently and unambiguously. The
formulated/developed tool is in compliance with CMMI, a
process improvement framework. Requirement Management,
a level 2 process area’s Special Goals, Generic Goals and sub
practices are implemented in the tool.
The System provides the following functionalities:
• Facility to specify different requirement
providers with requirement.
• Facility to trace each requirement or set of
requirement to a specific requirement provider
• Facility to trace a specific elicitation technique
used to gather specific requirement.
• Facility for analyzing the requirements coming
from different sources on a pre defined criteria
2
provided by the organization requirement
management process.
• Facility or maintaining history of all work
products related to requirement this includes:
o Files
o Use Cases
o GUI’S
o Feedback against each iteration
• Facility to follow the organizational process to
make change in the status of the requirement.
o Only authorized persons are allowed to
make change in the status of the
requirement.
• Facility to generate the SRS .doc
There are ultimate users that used or can be used this tool
Project Manager/Development Team Lead (PM/Dev
TL)
PM/Dev TL is the main punter of our intended
application. As requirement management is main task of
project manager and/or development team lead. Almost
all the functionality of this tool is explored or used by
this user. Like managing requirement provider’s
information, managing requirements itself, evaluating
requirements on acceptance criteria, conducting their
impact analysis, managing Change requests and
managing issues.
Development team lead helps the project manager to
maintain the bidirectional traceability among the
requirements.
Requirement Analyst
Requirement Analyst is able to manage requirements
through some proper channel of the particular project.
The role/user could be distributed among the project i.e.
every requirement analyst nominated any resource as a
project manager or it could be a central resource in the
entire organization. Moreover, requirement analyst
perform add, delete and modify the users and passwords
to the database.
II.SCOPE
The scope is to study of CMMI Level 2 processes area i.e.
Requirement Management and then to develop a tool in
compliance of the given process area. Since CMMI in
general and its level 2 in particular present a very large
canvas and demands a full time effort for its automation,
present circumstances do not allow us to work to
automate all process areas at Level 2. So, my project
scope has been narrowed down. REQM tool automate
only one process areas i.e. Requirements Management
and its related process areas of level 2. It is worthy to
note that related process areas will be partially automated
but not in their full terms. Only REQM process area is
automated.
REQM TOOL 3

III.METHODOLOGY and testing information is needed.

For developing REQM Tool I used Visual Studio 2005, SQL • Impact Analysis
Server 2005. The features of both softwares are The purpose of given requirement to analyze the
existing requirements. If the requirement is entered first
The features of Visual Studio 2005 are the following: time then there is no need to impact analysis and if the
• Reliability and Scalability will also be requirement is not new then the maintenance of the
significantly improved through support for 64- history is needed.
bit processors from Intel and AMD.
• Improved ASP .NET caching and page • GUI
processing. The purpose of the given requirement is to maintain the
• Improved working set and startup-time. graphical user interface.
• No-Touch deployment strategy will improve -
Click Once • Acceptance Criteria
• Simplified Implementation of Multithreaded The purpose of the given requirement is to analyze the
applications. requirements according to the organization.
The features of SQL Server 2005 are the following: Requirements shall be analyzed by the developer
according to the criteria of the organization. If the
• Web Services requirement is not fine then the developer asked for
• Reporting Services description according to that requirement.
• ADO.NET version 2.0
• SRS
• Security Enhancements
• Transact-SQL Enhancements
The purpose of the given requirement is to generate the
• Visual Studio Integration SRS.
It is used to gather, analyze, maintain, process and
We have many tools that are using for Management of change all the requirements spawn the System
Requirement over internet but there was not any specific tool Requirement Specification.
that rally the CMMI level II.-
There are different operation of Administrator and Project
I analyzed different type of tools before implementation of my
Manager/Development Team Lead (PM/Dev TL)
REQM TOOL.
• Gatherspace
Administrator
• TRUEreq
• Create Database for a new project
• WIBNI
• Add users to database
• SoftREQ
• Delete users from database
• Tracer
• Modify user’s information in database
After analyzing this tool we developed our REQM tool that is • Delete any database
following the CMMI Level II. • Change password

REQM Tool helps to manage the requirements and their Project Manager/Development Team Lead (PM/Dev TL)
various phases. Follow is the broad list of activities which our
tool helps to do. • Manage requirement provider’s information
• Manage requirements
• Log Requirements • Manage issues
The purpose of the given requirement log data of • Evaluate requirements on Acceptance Criteria
requirement. The log files are entered by the user in the • Conduct Impact Analysis
system. • Manage requirements traceability
• Manage Change Requests
• Use Cases
The purpose of the given requirement is to define the use • Get various Reports
case from the statements that is entered by the user. For • Generate SRS
this purpose I write a Algorithm that obtained verb from
the entered list by user and generate its use cases.
• Maintain Traceability
The purpose of the given requirement is to maintain the
traceability in a bidirectional way. For traceability of the
requirements designing information, coding information
REQM TOOL 4

form of SRS that is in .doc and .pdf format.

<<include>>

<<include>>
Create project Add User
<<include>>
<<include>>
New Req SQLServer2005
Modify User
Modify Req <<include>> <<include>>
Delete User <<include>>
Open Project
suggest usecase
Administrator Set Password

Requirement Mainpulation
Login
DataBase
Sever
Define attribute
Define Req provider info Acceptance Criteria Define Crit eria
Delete Project
.NetFramework
InternetExplorer
New Issue
Logout <<include>>
<<include>> Impact Ananlysis
Generate Log report
Delete Issue
Project Manager
issue Managemnt Web Client
Sever Machine

<<include>>
<<include>>
<<include>> Reports Change Request GUI

Revision History Report

<<include>> <<in clude>>
<<include>>

<<include>> SRS IIS

Baseline reports Delete GUI REQM(pakage)
Req Modify report Manipulation usecase
<<include>> Add GUI
<<include>>
<<include>>
<<include>> <<include>>
Impact Analysis report <<include>>
Modify GUI
.PDF
Figure 4: Deployment Diagram
Add Usecase

.DOC Modify Usecase IV.DOMAIN

Issue Management Report
Delete Usecase As there is trend to publish research papers on Software
Project Management in Software Engineering. Typical
researchers need to know about Software Engineering. Our
domain is SE. Because is concerned with developing and
maintaining software systems that behave reliably and
Figure 3: Overall System Flow Diagram
efficiently, are affordable to develop and maintain, and satisfy
all the requirements that customers have defined for them. It
REQM Tool based on two applications one is Client site and is important because of the impact of large, expensive
second is Administrator site. It is a 2-tier and web-based software systems and the role of software in safety-critical
application. And I used SQL server 2005 as a database tool. applications. It integrates significant mathematics, computer
This devised tool is well-matched with all other databases science and practices whose origins are in engineering.
also because of database factory model that is used in this Analyzing domain knowledge is possible once a declarative
application. specification of the terms is available. Formal analysis of
terms is extremely valuable when both attempting to reuse.
In Administrator site all the information about Users, Projects
Because of this, other syntactic forms for OWL have also been
and Log- File reports are handled. Administrator had rights defined.
to create user for the specific project.
In Client Site user authenticate and entered the project that is V.CONCLUSION
assigned to that user and then start work on it and perform In this paper, I have described web based-development
the specification for that specific project. Here user generated methodology for REQM Tool. We listed the steps in the
the report files and at the end final output is generated in the REQM-development process and addressed the complex
issues.
The devised tool will help development professionals to
manage their requirements more efficiently and
unambiguously. The formulated/developed tool will be in
compliance with CMMI, a process improvement framework.
REQM TOOL 5

Requirement Management, a level 2 process area’s Special

Goals, Generic Goals and sub practices will be implemented
in the tool.
However, after following all the rules and suggestions, one of
the most important things to remember is the following: there
are many Tools for this purpose but none is compliance with
CMMI level II. The potential applications of the Tool and the
designer’s understanding and view of the domain will
undoubtedly affect Tool design choices. “The proof is in the
pudding”—we can assess the quality of our Tool only by
using it in applications for which we designed it

ACKNOWLEDGMENT
Allah Almighty for his guidance and help to complete
this project
Wish to acknowledge our appreciation to all those who
assisted in the preparation of this project References
Wish to acknowledge my parents who support me in
every field of my life.

REFERENCES
[1] http://www.sparxsystems.com.au/platforms/requirements_management.htm
l
[2] Leffingwell, Dean. 1997. “Calculating the Return on Investment from
More Effective Requirements Management.” American Programmer 10(4):
13–16.
[3] 2 Grady, Robert B. 1999. “An Economic Release Decision Model: Insights
into Software Project Management.” In Proceedings of the Applications of
Software Measurement
[4] http://computingcareers.acm.org/?page_id=12
[5] Bell, T., E., Bixler, D. C. et al. (1997) an extendable approach to computer
aided software requirements engineering. IEEE Tran. On Software
Engineering, SE-3(1),
[6] “CMMI v1.2 for Development” Guide, Software Engineering Institute,
2006
[7] Software Engineering Institute, www.sei.com
[8] www.Wekipedia.com/Requirements Management
[9] www.sourceproject.com
[10] www.requirementsManagement.com
[11] www.crossroads.com
[12] http://www.processimpact.com/articles/rm_tools.html