![Page 1: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/1.jpg)
![Page 2: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/2.jpg)
Journal of Software &
Systems Development
Vol. 2011 (2011), Article ID
742200, 253 minipages.
DOI:10.5171/2011.742200
www.ibimapublishing.com
![Page 3: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/3.jpg)
Copyright © 2011 Noraini Che Pa and
Abdullah Mohd Zain. This is an open
access article distributed under the
Creative Commons Attribution License
unported 3.0, which permits
unrestricted use, distribution, and
reproduction in any medium, provided
that original work is properly cited.
![Page 4: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/4.jpg)
A Survey of
Communication Content
in Software
Requirements Elicitation
involving Customer and
Developer
![Page 5: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/5.jpg)
Authors
Noraini Che Pa1
and Abdullah Mohd Zain2
![Page 6: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/6.jpg)
1Department of Information
System, Faculty of Computer
Science and Information System,
Universiti Putra Malaysia, Malaysia
![Page 7: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/7.jpg)
2Programming and Software
Technology Research Group,
Faculty of Information Science and
Technology, Universiti
Kebangsaan Malaysia, Malaysia
![Page 8: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/8.jpg)
Abstract
At the heart of software
requirements elicitation
lies the communication
between customer and
![Page 9: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/9.jpg)
developer. There are
several valuable
components of
communication such as
medium, sender, receiver,
and messages, which
![Page 10: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/10.jpg)
relates to the input and
output from both parties.
Most of these messages are
delivered through
incompletely,
inconsistently or
![Page 11: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/11.jpg)
inaccurately defined
communication medium.
This study has been done to
look into the
communication content of
the current communication
![Page 12: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/12.jpg)
practices between
developer and customer in
Malaysia. The results of this
study revealed some
important notes on the
practices of communication
![Page 13: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/13.jpg)
content during software
requirements elicitation
process in Malaysia.
![Page 14: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/14.jpg)
Keywords: requirements
elicitation; software
requirements specification;
communication content.
![Page 15: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/15.jpg)
Introduction
In general, organization is
complex, hence identifying
the requirements are
especially difficult. In
![Page 16: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/16.jpg)
addition, software
requirements always
change from time to time.
Requirements elicitation
involves the
communication process
![Page 17: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/17.jpg)
between customer and
developer during the
analysis phase in software
engineering. There are
several important
components under
![Page 18: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/18.jpg)
consideration during
communication, such as the
medium, sender, receiver,
and the content of
messages, which relates to
the input and output from
![Page 19: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/19.jpg)
both parties. Such
information by the
customer, which is often
delivered verbally and not
in writing, will be used to
produce Software
![Page 20: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/20.jpg)
Requirements Specification
document (SRS). At
present, several studies
have been conducted on the
practices of requirements
elicitation but none has
![Page 21: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/21.jpg)
looked into the
communication content
between customer and
developer.
![Page 22: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/22.jpg)
In practice, communication
activity involves messages
transmission from sender
to receiver, whreby the
discussion topic revolves
around domain application
![Page 23: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/23.jpg)
(Drake et al 1993), business
requirements, system
barrier and others
problems (Paetsch et
al.2003). While messages
are in the form of
![Page 24: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/24.jpg)
information and
knowledge, knowledge is
difficult to transmit
because it belongs to a
person who manages the
particular knowledge.
![Page 25: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/25.jpg)
According to Stary (2002),
knowledge of an
organisation covers tasks
and processes that are
carried out by customers.
Such information and
![Page 26: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/26.jpg)
knowledge are in turn used
to produce the software
requirements document,
which is traditionally
viewed as a document that
communicates the
![Page 27: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/27.jpg)
requirements of the
customer to the developer
who is responsible to build
the system. The collection
of requirements and its
representation must be
![Page 28: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/28.jpg)
understandable by both
customer and developer.
The remainder of this
paper is organized as
follows. Section two will
![Page 29: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/29.jpg)
describe in detail the
software requirements
elicitation process and the
related works. Section
three will present the
survey results from the
![Page 30: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/30.jpg)
requirements elicitation
between customer and
developer as practiced in
Malaysia. Finally, Section
four will conclude the
![Page 31: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/31.jpg)
findings with some
indications for future work.
![Page 32: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/32.jpg)
Literature Review
Software Requirements
Elicitation
According to Coulin et al
(2005), requirements
![Page 33: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/33.jpg)
elicitation is the process of
searching, revealing,
acquiring, and detailing of
requirements for
computer-based systems.
This process is complex as
![Page 34: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/34.jpg)
it involves various
activities, techniques,
approaches, and support
tools. More often, these
processes are carried out
repeatedly (Aurum &
![Page 35: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/35.jpg)
Wohlin 2005).
Requirements elicitation is
also looked as a negotiation
process among
stakeholders in order to
achieve an agreement on
![Page 36: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/36.jpg)
the system to be developed.
Sommerville (2001)
identifies activities
involved during
requirements elicitation as
discovered, negotiation,
![Page 37: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/37.jpg)
and documentation.
According to Haywood and
Dart (1996), these activities
may be implemented using
bottom-up or top-down
approach, based on specific
![Page 38: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/38.jpg)
customer problem. Aurum
and Wohlin (2005) state
that in general, the
processes are made up by
four principle activities,
which are communication,
![Page 39: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/39.jpg)
set priorities, negotiation
and cooperation with the
stakeholder.
Various techniques have
been used for requirements
![Page 40: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/40.jpg)
elicitation such as
interviews, document
analysis, group work,
ethnography, prototyping,
questionnaires, scenarios,
and viewpoint. These
![Page 41: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/41.jpg)
techniques may be divided
into two categories: the
interaction between an
individual and the
interaction between groups
(Duran et al 2004).
![Page 42: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/42.jpg)
Interactions between
individuals are divided into
two types: local and
distributed. Local
interaction includes
prototype, group meetings,
![Page 43: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/43.jpg)
and interviews. Whereas
distributed interaction
involve interaction of
interviews, conferences,
and meetings through
video. Non-personal
![Page 44: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/44.jpg)
interaction consists of
observation, document
analysis and
questionnaires. According
to Coulin et al (2005), most
of these techniques are
![Page 45: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/45.jpg)
adapted from various
disciplines such as social
science and engineering.
Requirements elicitations
techniques may also be
![Page 46: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/46.jpg)
classified into traditional,
group, formal, semi formal,
and natural language. In
traditional ways,
requirements elicitation
process are performed face
![Page 47: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/47.jpg)
to face such as through
interviews, whether
individually or in a group
among customer or
manager. There have been
several difficulties
![Page 48: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/48.jpg)
conducting interview
session such as:
(i) it is time consuming;
![Page 49: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/49.jpg)
(ii) there may exists
conflict between user
and manager with
regards of perception,
assumption, problem
defined, and even
![Page 50: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/50.jpg)
objective of a system
and
(iii) different personalities
and behavior (Bahn
1995), as well as
![Page 51: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/51.jpg)
background and
terminology used
during communication
between both parties
(Liou & Chen 1993).
![Page 52: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/52.jpg)
Nonetheless, this technique
requires direct interaction
between both parties; the
interviewer and the
respondent, which results
in quick information
![Page 53: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/53.jpg)
exchange. The quality of the
information obtained is
closely related to the skills
of the interviewer.
Basically, there are three
forms of interview, which
![Page 54: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/54.jpg)
are unstructured,
structured, and semi-
structured. Unstructured
interviews give the
respondent the freedom to
express opinions, feelings,
![Page 55: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/55.jpg)
position, goals, and beliefs
of an issue. This form can
be used if the interviewer
has little knowledge of the
domain. The weakness of
unstructured interview is
![Page 56: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/56.jpg)
the tendency of both
parties to focus discussion
on only specific topics. A
structured form of
interview allows the parties
to involve and determine
![Page 57: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/57.jpg)
the topic in advance. The
results from structured
interviews are easily
analyzed, the process only
takes a considerable short
time, and best carried out
![Page 58: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/58.jpg)
by a new analyst. However,
interviewing techniques
actually involve high costs
and time consuming to
prepare the interviews,
performing the interviews
![Page 59: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/59.jpg)
and analyzing the results of
the interview. In some
situations, an interview has
to be conducted over time
and involve several
individuals, with different
![Page 60: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/60.jpg)
needs and requirements.
Finding by Hickey et al
(1999) reveals that this
technique is not efficient if
the number of respondent
![Page 61: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/61.jpg)
involves the public and
consists of different groups.
Document analysis
technique is conducted by
reviewing documents and
![Page 62: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/62.jpg)
application of an existing
system. This technique is
most suitable for the
renovation of obsolete
systems or by a new
analyst. The documents
![Page 63: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/63.jpg)
involved include design
documents, manual
systems, as well as forms
and files used in the
business processes.
However, more often the
![Page 64: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/64.jpg)
documents involved
contain outdated or
incomplete, and
inconsistent with the
current business
![Page 65: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/65.jpg)
requirements (Hoffer et al
2008).
Elicitation techniques that
involve public participation
or occur at the same time
![Page 66: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/66.jpg)
for instance meetings, focus
groups, and workshops
require a designated
working group. Hickey et al
(1999) and Drake et al
(1993) have categorized
![Page 67: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/67.jpg)
meeting techniques that
involve time and high cost
as it requires the
involvement of many
parties at one time. Focus
group is one of the
![Page 68: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/68.jpg)
techniques performed in a
group interview. This
technique involves
participation of the
customer representatives
and the developer to
![Page 69: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/69.jpg)
exchange information
through discussions
(Sommerville 2007). A
facilitator will be appointed
to ensure that the
discussions are conducted
![Page 70: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/70.jpg)
smoothly, hence the
technique is less suitable
for requirement
specifications of complex
software systems.
Meanwhile, workshop is
![Page 71: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/71.jpg)
conducted in collaboration
consisting of five stages of
development, critique,
understanding and support,
implementation, and delay
(Gottesdiener 2003),
![Page 72: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/72.jpg)
whereby all participants
play a role in every stage of
the workshop conducted.
This technique is able to
produce high quality
![Page 73: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/73.jpg)
requirements within a
short time.
Prototyping is another
requirements elicitation
technique that allows user
![Page 74: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/74.jpg)
feedback and considers in-
depth information, which is
considered the most
suitable technique for
developing the user
interface requirements that
![Page 75: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/75.jpg)
have not been identified in
full. The prototype
responds better to
uncertain or changing of
requirements (Satzinger et
al 2002). Two prototype
![Page 76: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/76.jpg)
approaches are incremental
and throw away.
Incremental prototype is
the prototype that is built
in a small module from the
overall user requirements.
![Page 77: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/77.jpg)
Unlike incremental,
throwaway prototyping
does not preserve the
prototype that has been
developed. There is never
any intention to convert the
![Page 78: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/78.jpg)
prototype into a working
system (Hoffer et al 2008).
This technique is used to
encourage user to
participate in developing
the customer requirements
![Page 79: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/79.jpg)
and benefits the
discussions with customers
because it involves a
system that is already in
existence.
![Page 80: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/80.jpg)
Meanwhile, elicitation
through questionnaire
requires a clear focus to
ensure the information
obtained is appropriate.
Questionnaires are used to
![Page 81: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/81.jpg)
gather information when
the project involves many
respondents and is to be
completed within a short
time period. The
information obtained is
![Page 82: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/82.jpg)
usually lack in depth, less
authentic, and less
interactive. Normally, this
technique is best used to
obtain information on
attitudes, beliefs, and basic
![Page 83: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/83.jpg)
features for a system. Other
than questionnaire,
observations may be
performed by observing
how users work out the
actual business process
![Page 84: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/84.jpg)
without their intervention.
This technique involves
high costs and requires skill
to interpret and understand
human actions. Often, users
tend to change how they
![Page 85: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/85.jpg)
work after finding out that
they are being observed In
addition, interpretation of
the observations made by
the analyst is subject to
influence and personal bias.
![Page 86: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/86.jpg)
Scenario-based elicitation
technique is basically a
summarized description of
the system as described in
the beginning of the
process, along the process,
![Page 87: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/87.jpg)
and at the end of the
process. The scenario is
served in the form of a
story and contains
information on the process,
actions and interactions of
![Page 88: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/88.jpg)
users with the system.
However, this technique
does not show the internal
structure of a system
although it may be used to
![Page 89: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/89.jpg)
understand and to validate
the requirements.
The most commonly used
communication type during
requirements elicitation
![Page 90: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/90.jpg)
processes are verbal,
written, and mediator
(Saiedian & Dale 2002,
Coughlan et al 2003). The
medium chosen is
important to assure the
![Page 91: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/91.jpg)
types of messages received
are similar to the actual
messages that were
delivered. Usually, the
chosen method is in favors
of communication with fast
![Page 92: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/92.jpg)
feedback time, clear, no
conflict, and easy to
understand. Many
customers and developers
alike use natural language
to communicate during
![Page 93: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/93.jpg)
requirements elicitation
process. However, this
method poses some
problems such as
differences in
pronunciation, expression,
![Page 94: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/94.jpg)
human emotion, and
ambiguous information.
(Loucopoulos and
Champion 1992).
![Page 95: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/95.jpg)
Communication Content
among Software
Developers in Malaysia
The general objective of
this survey is to identify
![Page 96: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/96.jpg)
communication content
that relates to
requirements elicitation
activities between
customer and developer
specifically in Malaysia. The
![Page 97: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/97.jpg)
questionnaire encompasses
questions on
communication content
and the appropriate tools
used to support the
elicitation activities.
![Page 98: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/98.jpg)
The specific objectives of
this study are:
(1) to determine the input
and output of requirements
elicitation process and
![Page 99: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/99.jpg)
(2) to recognize the actual
processes involved during
requirements elicitation. To
achieve the above
objectives, the following
are some research
![Page 100: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/100.jpg)
questions that need to be
addressed:
1. What is the source of
requirements
elicitation for
![Page 101: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/101.jpg)
communicating
requirements during
requirements
elicitation in Malaysia?
![Page 102: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/102.jpg)
2. What are the method
and support tools used
in preparing for
software requirements
specification
document?
![Page 103: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/103.jpg)
3. What are the roles of
users’ involvement
when performing
requirements
elicitation?
![Page 104: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/104.jpg)
Stakeholder Background
The methods of data
collection in this survey are
through postal, e-mail, and
interviews. The
![Page 105: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/105.jpg)
respondents involved are
software developers from
various sectors in Malaysia.
Questionnaires are
appropriate because our
data collection involves
![Page 106: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/106.jpg)
public respondents where
the distribution of the
respondents is scattered.
The selection of
respondents is determined
based on their position and
![Page 107: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/107.jpg)
experience in requirements
elicitation activity during
system development.
Participations came from
various agencies that are
categorized as government,
![Page 108: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/108.jpg)
semi-government, private
agencies with Multimedia
Super Corridor (MSC)
status and without. Table 1
shows the background of
![Page 109: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/109.jpg)
the respondents who
participated in this study.
![Page 110: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/110.jpg)
Table 1: Background
Respondent Selection
Please see Table 1 in full
PDF version
![Page 111: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/111.jpg)
In the following sections,
we will present the
analyses performed on the
information gathered from
42 responses. The results of
![Page 112: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/112.jpg)
the survey were then
analyzed using SPSS.
Results
Table 2 shows the content
and criteria investigated in
![Page 113: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/113.jpg)
the survey. There are 5
categories of content, which
are the requirements
sources, analysis and
modeling, prototype, SRS,
and user involvement.
![Page 114: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/114.jpg)
Table 2: Content and
Criteria Investigated
Please see table 2 in full
PDF version
![Page 115: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/115.jpg)
Requirements Sources Requirements sources are
information that are
gathered from the
customers. These refer to
![Page 116: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/116.jpg)
customer needs for new
implementations or even
upgrades. From the
analysis, it is found that
numerous sources from
customers were used in
![Page 117: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/117.jpg)
process identification
requirements. The survey
result shows 69.0% of
respondents chose the
work process as their main
information source to
![Page 118: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/118.jpg)
identify the software
requirements. Other
sources used are based
from existing system
(50.0%), 50.0% from the
organization rules, 50.0%
![Page 119: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/119.jpg)
from expert knowledge,
42.9% from documents,
and 4.8% from others
source (refer to Table 3).
![Page 120: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/120.jpg)
Table 3: Sources of
Requirements
Please see Table 3 in
full PDF version
![Page 121: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/121.jpg)
Many organizations choose
and modify their
requirements sources in
accordance with technology
changes. Besides, sources of
project are also influenced
![Page 122: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/122.jpg)
by changes of external
factors such as economic,
politic, social, regulations,
financial, psychology,
history, and geography. For
example, an organization
![Page 123: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/123.jpg)
that practices a
bureaucratic system often
faces difficulty in gathering
requirements as compared
to other non-bureaucratic
organizations. Changes of
![Page 124: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/124.jpg)
management and political
pattern in an organization
also influence in delivering
the requirements sources.
Such new changes may
cause customer to feel
![Page 125: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/125.jpg)
unhappy and unable to
accept. Nonetheless,
changes in requirements
and scope will rarely affect
the information delivered
![Page 126: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/126.jpg)
as delivered through email,
telephone or interview.
![Page 127: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/127.jpg)
Analysis and Modeling
Requirements
This process includes
refining and modeling
the requirements. From
![Page 128: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/128.jpg)
the analysis, (see Fig. 1)
the results of the study
show that respondents
prefer to use Structured
System Analysis and
Design Method
![Page 129: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/129.jpg)
(SSADM) as compared
to Object Oriented
Analysis (OOA) with
small percentage of
preference on internal
methodology. This is
![Page 130: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/130.jpg)
probably because the
traditional method is
easy to understand and
represent the actual
customer requirements.
The survey shows that
![Page 131: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/131.jpg)
although 71.4% of
developers do not use
any specific software to
analyze and model the
requirements, 28.6% of
them have considered
![Page 132: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/132.jpg)
using the Rational Rose,
Enterprise Architect or
Microsoft Visio.
![Page 133: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/133.jpg)
Fig 1. Methodology Used
for Software
Requirements Analysis
and Modeling
Please see Figure 1 in full
PDF version
![Page 134: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/134.jpg)
Prototype Normally in practice, a tool
is used to get feedbacks on
software requirements as
specified by the developer.
![Page 135: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/135.jpg)
This type of feedback is
used to examine and
guarantee the consistency,
completeness, reality and
accuracy of software
requirements. According to
![Page 136: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/136.jpg)
Sommerville (2001), this
includes checking the
requirements document.
From the analysis, it is
shown that 71.4% of
![Page 137: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/137.jpg)
developers used prototype
techniques to validate their
requirements and 28.6%
chose other techniques
(refer Table 4).
![Page 138: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/138.jpg)
Table 4: Techniques
of Prototype
Please see Table 4 in full
PDF version
![Page 139: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/139.jpg)
Feedback from respondents
who used prototype is 30
from 42 persons, whereby
prototype parts involve
user interface, schedule,
process flow, and work
![Page 140: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/140.jpg)
system. Table 5 shows the
use of prototype techniques
to communicate system
requirement that were
developed in effort to seek
feedback from customer.
![Page 141: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/141.jpg)
Implementation of the
prototype involves the
programming language and
specified software. From
the analysis, it is shown
that 86.7% of developers
![Page 142: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/142.jpg)
used programming
language to implement the
prototype but 13.3% chose
Macromedia Dreamweaver,
Microsoft Visio or Microsoft
PowerPoint.
![Page 143: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/143.jpg)
Also, most respondents
stated that they used
combination of
requirements part to show
the prototype. Study found
out as much as 86.7%
![Page 144: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/144.jpg)
presented their prototype
for interface, 26.7% for
schedule, 80% for process
Ilow, and 3.3% for working
system.
![Page 145: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/145.jpg)
Table 5: Parts of
Requirements that
Demonstrate in a
Prototype
Please see Table 5 in full
PDF version
![Page 146: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/146.jpg)
Software Requirements
Specification (SRS)
Documentation Because software
requirements are often
![Page 147: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/147.jpg)
seen as abstract statements
of the services provided or
the constraints of a system,
they are defined in various
ways. Software
requirements document
![Page 148: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/148.jpg)
can also be viewed as a
detailed statement that
defines the process using
formal mathematics of a
functional system.
According to IEEE (Yang &
![Page 149: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/149.jpg)
Tang 2003), SRS
documentation is a term
referring to software
requirements with:
![Page 150: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/150.jpg)
(i) the capacity required by
users to solve a problem
or to achieve certain
objectives,
![Page 151: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/151.jpg)
(ii) the ability of the system
to fulfill the contract,
standards, specifications
or other and
![Page 152: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/152.jpg)
(iii) a document that
reflects the ability to
satisfy objective (i) and
(ii). Chirinos et al
(2004) report that there
is actually no consensus
![Page 153: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/153.jpg)
on the meaning of
software requirements.
Yadav et al (1988) and
Whitten et al (2001)
present how a requirement
![Page 154: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/154.jpg)
is described, which are
through:
(i) activities,
(ii) input and output,
![Page 155: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/155.jpg)
(iii) data definition, and
(iv) processing
requirements.
![Page 156: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/156.jpg)
In subsequent research,
Gregoriades et al (2004)
define software
requirements as goals to be
achieved and consider the
implementation through
![Page 157: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/157.jpg)
software operating
processes, machines, and
humans. Software
requirements are divided
into two types, which are
the functional
![Page 158: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/158.jpg)
requirements and non-
functional requirements.
Functional requirements
refer to the functions or
services provided by the
system. This requirement
![Page 159: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/159.jpg)
highly depends on the
software, potential users,
and the type of systems. It
is also known as the
behavior of the system
(Chirinos et al 2004).
![Page 160: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/160.jpg)
Meanwhile, non-functional
requirements refer to the
constraints of the system
(Paetsch et al 2003).
The process of
documenting the software
![Page 161: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/161.jpg)
requirements includes
activities such as creating
the software requirements
specifications (SRS),
reviewing the SRS content,
and checking the resulting
![Page 162: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/162.jpg)
SRS. These activities are
carried out to ensure the
document that is created
adheres to the quality
standard and satisfies the
customer. Basically,
![Page 163: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/163.jpg)
software requirements
document is a group of
statements that needs to be
written by developer
(Sommerville 2001). The
details of software
![Page 164: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/164.jpg)
requirements document
depends on the kind of
system to be developed and
the software development
process (Sommerville
2001). There are various
![Page 165: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/165.jpg)
standards in existence for
requirements document
such as the IEEE, ISO 9000,
and others. Basic issues in
IEEE standard 830-1998
![Page 166: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/166.jpg)
pertaining the SRS
document include:
1. Functionality
What is the software
supposed to do?
![Page 167: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/167.jpg)
2. External interfaces
How does the software
interact with people, the
system’s hardware,
other hardware, and
software?
![Page 168: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/168.jpg)
3. Performance
What are the functions
of speed, availability,
response time and
recovery time of various
software , etc?
![Page 169: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/169.jpg)
4. Attributes
What are the portability,
correctness,
maintainability, security
issues under
consideration?
![Page 170: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/170.jpg)
5. Design constraints
imposed on an
implementation
Are there any required
standards in effect,
implementation
![Page 171: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/171.jpg)
language, policies for
database integrity,
resource limits,
operating environment?
![Page 172: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/172.jpg)
The survey results show
that respondents did follow
some standard in preparing
SRS documentation, among
which are from the
Institute of Electrical and
![Page 173: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/173.jpg)
Electronics Engineers
(IEEE), International
Standards Organization
(ISO) 9000-3, National
Standards or internal
organization. Analysis of
![Page 174: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/174.jpg)
data showed that 53%
respondent follows their
own organization standard
or at least refer to similar
organization in writing the
SRS document. While 28%
![Page 175: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/175.jpg)
of respondents do not
adopt any formal standard,
13% of respondents
adhered to standard set by
IEEE, 3% adhered to ISO
standard 9000-3, while the
![Page 176: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/176.jpg)
remaining 3% adhered to
the National Standards.
Further analysis reveals
that most of the SRS
document content includes
![Page 177: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/177.jpg)
the following items:
• Introduction
• Content
![Page 178: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/178.jpg)
• Project background
• System cope and
business
• System summary
![Page 179: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/179.jpg)
• Interface
• Output and input
• Process
![Page 180: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/180.jpg)
• Procedure
Meanwhile, only a small
number of organizations
incorporated the following
additional items:
![Page 181: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/181.jpg)
• Change control
• Storage data
• Review
![Page 182: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/182.jpg)
• Validation
As for the tools, software
that is used to prepare the
SRS document is mainly
word processor or specific
![Page 183: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/183.jpg)
software. Findings show
that 90.5% respondents
used word processor to
write SRS and 7.1% use
other specific software,
while the remaining 2.4%
![Page 184: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/184.jpg)
use both types of software.
Examples of specific
software are Microsoft
Visio, Microsoft Excel and
Microsoft Project.
![Page 185: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/185.jpg)
User Involvement
Findings from the survey
show that most customers
are involved in checking the
SRS document. Analysis of
![Page 186: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/186.jpg)
data shows that 88.1 %
respondent claimed
customer involvement in
checking on SRS document
while 11.9% claimed
![Page 187: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/187.jpg)
otherwise (indicated in
Table 6).
![Page 188: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/188.jpg)
Table 6: User
Involvement
Please see Table 6 in
full PDF version
![Page 189: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/189.jpg)
Table 7 shows the
itemized content of SRS
document that are
validated by customer.
This information is
gained after the
![Page 190: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/190.jpg)
respondents were
requested to list the
section of SRS
document that requires
confirmation by
customers. Analysis of
![Page 191: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/191.jpg)
data shows that 89.2%
respondents claimed
involvement of
customer in functional
part, 73% in system
scope and business
![Page 192: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/192.jpg)
part, 73% in interface
part, 73% in input and
output part, and 73%
other parts. All
respondents state that
they do not use any
![Page 193: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/193.jpg)
specific software to
check the SRS
document.
![Page 194: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/194.jpg)
Table 7: Parts of SRS
that Validate by User
Please see Table 7 in full
PDF version
![Page 195: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/195.jpg)
Consolidation of the
Result
Based on the survey
findings reported in Section
3, the content of
![Page 196: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/196.jpg)
communication between
the customer and
developer during
requirements elicitation are
investigated in effort to
further understand the
![Page 197: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/197.jpg)
common practices during
the elicitation process.
While previous researchers
look for technique and
sources that is used to
generate SRS, there is also
![Page 198: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/198.jpg)
researcher that focuses on
support tools to facilitate
communication between
customer and developer
during the requirements
elicitation process. While
![Page 199: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/199.jpg)
previous studies only look
into user involvement for
requirements validation,
this study includes source
of communication, user
involvement and support
![Page 200: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/200.jpg)
tool that are used in
performing requirements
elicitation.
Overall, the survey
conducted is able to
![Page 201: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/201.jpg)
provide insights on current
communication practices
during requirements
elicitation activity among
software developers in
Malaysia. The sources for
![Page 202: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/202.jpg)
generating the software
requirements were
identified by this study. The
study also showed that
software developers do not
use any specific tools to
![Page 203: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/203.jpg)
support all activities for
requirements during the
requirements elicitation
process. Survey also shows
that there is no specific
methodology adopted by
![Page 204: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/204.jpg)
the developers to
implement the
requirements elicitation
process. In addition, it is
found only a handful of
developers who use tools to
![Page 205: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/205.jpg)
support requirements
elicitation.
![Page 206: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/206.jpg)
Conclusion and Future
Research
This paper discusses
communication content
between the customer and
![Page 207: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/207.jpg)
developer during
requirements elicitation
process in preparing the
Software Requirement
Specification (SRS)
document. The findings
![Page 208: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/208.jpg)
show that most developers
do not use any support tool
in implementing activities
during the requirements
elicitation process nor do
they follow any
![Page 209: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/209.jpg)
methodology to perform
requirement elicitation.
Requirement document is
important because it is
always taken as the basis
for software development,
![Page 210: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/210.jpg)
hence a software tool is
needed in creating the
software requirements
document.
![Page 211: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/211.jpg)
One obvious limitation of
this study is the use of only
one set of questionnaire to
be distributed to the
developers. In this case, the
information gathered is
![Page 212: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/212.jpg)
limited to the questions
asked. More in-depth
information and deeper
understanding may be
gained if other research
methods are used in
![Page 213: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/213.jpg)
combination such as focus
group and interview. Our
future work intend to
increase the number of
participating companies
and to use additional data
![Page 214: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/214.jpg)
gathering techniques with
the objectives of getting
wider and more accurate
representation of
requirements elicitation
![Page 215: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/215.jpg)
practices among industrial
practitioners in Malaysia.
There are other interesting
issues in communication
for requirements to be
![Page 216: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/216.jpg)
explored. The issues
include medium,
personalities, procedures,
and communication skill. At
the end, our main aim in
this endeavor is to facilitate
![Page 217: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/217.jpg)
customer and developer to
consciously manage future
communication during
requirements elicitation by
looking in-depth of
considering the
![Page 218: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/218.jpg)
communication content.
Effective and clear
communication will
produce the best software
requirement documents,
![Page 219: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/219.jpg)
which in turn will produce
good software.
![Page 220: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/220.jpg)
References
Aurum, A. & Wohlin, C.
(2005). “Engineering and
Managing Software
Requirements,” Springler-
![Page 221: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/221.jpg)
Verlag Berlin Heidelberg.
Germany.
Bahn, D. L. (1995).. “System
Designer User Interaction:
An Occupational
![Page 222: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/222.jpg)
Subcultures Perspective,”
Proceeding of ACM SIGCPR
Conference on Supporting
teams, groups, and learning
inside and outside the IS
function reinventing, 72-80.
![Page 223: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/223.jpg)
Chirinos, L., Losavio, F. &
Matteo, A. (2004).
“Identifying Quality-Based
Requirements,” Information
![Page 224: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/224.jpg)
System Management Winter
41(8), 15-26.
Coughlan, J., Lycett, M. &
Macredie, R. D. (2003).
“Communication Issues in
![Page 225: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/225.jpg)
Requirements Elicitation: A
Content Analysis of
Stakeholder Experiences,”
Information and Software
Technology 45, 525-537.
![Page 226: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/226.jpg)
Coulin, C., Sahraoui, Abd El
Kader & Zowghi, D. (2005).
'Towards a Collaborative
and Combination Approach
to Requirements Elicitation
within a Systems
![Page 227: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/227.jpg)
Engineering Framework,'
Proceeding of 18th
International Conference
on System Engineering,
456–461.
![Page 228: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/228.jpg)
Dawson, L. & Swatman, P.
(1999). “The Use Object-
Oriented models in
requirements Engineering:
A Field Study,” Proceeding
of. 20th International
![Page 229: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/229.jpg)
Conference on Information
System, 260-273.
Drake, J. M., Xie, W. W., Tsai,
W. T. & Zualkernan, I. A.
(1993). “Approach and Case
![Page 230: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/230.jpg)
Study of Requirement
Analysis Where End Users
Take an Active Role,”
Proceeding of 15th
International Conference
![Page 231: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/231.jpg)
on Software Engineering,
177-186.
Duran, A., Benavides, D. &
Bermejo, J. (2004).
Applying System Families
![Page 232: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/232.jpg)
Concepts to Requirements
Engineering Process
Definition, Lecture Notes in
Computer Sciences 3014, 1-
12.
![Page 233: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/233.jpg)
http://www.lsi.us.es/~dbc
/dbc_archivos/pubs/benav
ides07-phd.pdf. [10 Julai
2008].
![Page 234: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/234.jpg)
Gottesdiener, E. (2003).
"Requirements by
Collaboration: Getting It
Right the First Time," IEEE
Software 20(2), 52-55.
![Page 235: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/235.jpg)
Haywood, E. & Dart, P.
(1996). “Analysis of
Sofware Requirements
Models,” Proceeding of
Australian Software
![Page 236: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/236.jpg)
Engineering Conference,
131-138.
Hickey, A. M. Dean D. L. &
Nunamaker, J. F. (1999).
"Setting a Foundation for
![Page 237: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/237.jpg)
Collaborative Scenario
Elicitation," Proceedings of
the Hawaii International
Conference on System
Sciences, 26-30.
![Page 238: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/238.jpg)
Hoffer, J. A., George. J. F. &
Valacich, J.S. (2008).
Modern Systems Analysis
and Design, Fifth Edition.
New Jersey, Pearson
International Edition.
![Page 239: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/239.jpg)
Lio, Y.I. & Chen, M. (1993).
“Using Group Support
Systems and Joint
Application Development
for Requirements
Specification,” Journal of
![Page 240: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/240.jpg)
Management Information
Systems 10(3), 25-41.
Loucopoulos, P. &
Champion, R. E. M. (1992).
“Concept Acquisition and
![Page 241: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/241.jpg)
Analysis for Requirements
Specification,” Software
Engineering Journal March
1990, 116-123.
![Page 242: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/242.jpg)
Paetsch, F., Eberlein, A. &
Maurer, F. (2003).
"Requirements Engineering
and Agile Software
Development,” Proceeding
of 12th IEEE International
![Page 243: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/243.jpg)
Workshops on Enabling
Technologies:
Infrastructure for
Collaborative Enterprise,
308-313.
![Page 244: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/244.jpg)
Saiedian, H. & Dale, R.
(2000). “Requirements
Engineering: Making the
Connection between the
Software Developer and
Customer,” Information and
![Page 245: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/245.jpg)
Software Technology 42(6),
419-428.
Satzinger, J. W., Jackson R.
B. & Burd S. D.
(2002). Systems Analysis
![Page 246: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/246.jpg)
and Design. Second Edition,
Course Technology Thomson
Learning.
![Page 247: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/247.jpg)
Sommerville, I. (2001).
Software Engineering. Sixth
Edition. Addision Wesley.
Sommerville, I. (2007).
Software Engineering.
![Page 248: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/248.jpg)
Eighth Edition.
Edinburgh,Addision Wesley.
Stary, C. (2002). “Shifting
Knowledge from Analysis
to Design: Requirements
![Page 249: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/249.jpg)
for Contextual User
Interface Development,”
Behaviour & Information
Technology 21(6), 425-440.
![Page 250: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/250.jpg)
Whitten, J. L., Bentley, L. D.
& Dittman, K. C. (2001).
System Analysis and Design
Methods. 5th Edition.
Boston, McGraw-Hill Higher
Education.
![Page 251: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/251.jpg)
Yadav, S. B., Bravoco, R. R.,
Chatfield, A.T. & Rajkumar,
T. M. (1988). “Comparison
of Analysis Techniques for
Information Requirement
Determination,”
![Page 252: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/252.jpg)
Communications of the ACM
31(9), 1090-1096.
Yang, H.-L. & Tang, J.-H.
(2003). "A Three-Stage
Model of Requirements
![Page 253: Journal of Software & Systems Developmentibimapublishing.com/articles/JSSD/2016/742200/m742200.pdf · Abdullah Mohd Zain. This is an open access article distributed under the Creative](https://reader035.vdocument.in/reader035/viewer/2022070822/5f28cd91477a4f265e5789be/html5/thumbnails/253.jpg)
Elicitation for Web-based
Information System,"
Industrial Management &
Data System 103(6), 398-
409.