Collection Title:	SIU Thesis
Title :	Reducing the Gap between Users and Developers: A Problem Oriented Approach to Understanding Requirements Using Natural Language Processing
Material Type:	printed text
Authors:	Salah Ali Hassan, Author ; Mason, Paul, Associated Name ; Sivadon Chaisiri, Associated Name
Publisher:	Bangkok: Shinawatra University
Publication Date:	2014
Pagination:	vi, 60 p.
Layout:	ill, tables
Size:	30 cm.
Price:	500.00
General note:	SIU THE: SOIT-MSIT-2014-02 Thesis. [M.S. [Information Technology]]. -- Shinawatra University, 2014.
Languages :	English (eng)
Descriptors:	[LCSH]Requirements engineering [LCSH]Software -- Development
Keywords:	Requirements Engineering Requirements Elicitation Requirements Extraction rules
Abstract:	Software requirements engineering is defined as all the activities devoted to identification of user requirements, analysis of the requirements to derive additional requirements, documentation of the requirements as a specification, managing requirements, and validation of the documented requirements against actual user needs. Requirements elicitation is often regarded as the first step in the requirements engineering process. Hence the most important goal of requirements elicitation is to ‘discover’ precisely what problem needs to be solved and to identify the system boundaries. These boundaries define, at a high level, where the final delivered system will fit into the current operational environment. Without a well-written requirements specification, developers do not know what to build, users do not know what to expect, and there is no way to validate the target system against the original user needs. Our belief is that traditional approaches to establishing user requirements employing popular techniques such as interview, questionnaire, or even ethnography is at odds with the customers’ actual perspective which in turn leads to so called ‘air gaps’ between developers and customers understanding of requirements. Hence in this research we focus on addressing this customer/developer air gap problem by developing a process-model that transforms user problem statements into acceptable user requirements - with the stakeholders always central to the process - by generating requirements automatically in the form of Use Case and Sequence Diagrams. To substantiate our argument, we use real world case study from Airline Reservation System and turn the problem statement of the case study into requirement in the form of unified modeling language (use case and sequence diagrams).
Curricular :	BSCS/MSIT
Record link:	http://libsearch.siu.ac.th/siu/opac_css/index.php?lvl=notice_display&id=26223

SIU Thesis. Reducing the Gap between Users and Developers: A Problem Oriented Approach to Understanding Requirements Using Natural Language Processing [printed text] / Salah Ali Hassan, Author ; Mason, Paul, Associated Name ; Sivadon Chaisiri, Associated Name . - [S.l.] : Bangkok: Shinawatra University, 2014 . - vi, 60 p. : ill, tables ; 30 cm.
500.00
SIU THE: SOIT-MSIT-2014-02
Thesis. [M.S. [Information Technology]]. -- Shinawatra University, 2014.
Languages : English (eng)

Descriptors:	[LCSH]Requirements engineering [LCSH]Software -- Development
Keywords:	Requirements Engineering Requirements Elicitation Requirements Extraction rules
Abstract:	Software requirements engineering is defined as all the activities devoted to identification of user requirements, analysis of the requirements to derive additional requirements, documentation of the requirements as a specification, managing requirements, and validation of the documented requirements against actual user needs. Requirements elicitation is often regarded as the first step in the requirements engineering process. Hence the most important goal of requirements elicitation is to ‘discover’ precisely what problem needs to be solved and to identify the system boundaries. These boundaries define, at a high level, where the final delivered system will fit into the current operational environment. Without a well-written requirements specification, developers do not know what to build, users do not know what to expect, and there is no way to validate the target system against the original user needs. Our belief is that traditional approaches to establishing user requirements employing popular techniques such as interview, questionnaire, or even ethnography is at odds with the customers’ actual perspective which in turn leads to so called ‘air gaps’ between developers and customers understanding of requirements. Hence in this research we focus on addressing this customer/developer air gap problem by developing a process-model that transforms user problem statements into acceptable user requirements - with the stakeholders always central to the process - by generating requirements automatically in the form of Use Case and Sequence Diagrams. To substantiate our argument, we use real world case study from Airline Reservation System and turn the problem statement of the case study into requirement in the form of unified modeling language (use case and sequence diagrams).
Curricular :	BSCS/MSIT
Record link:	http://libsearch.siu.ac.th/siu/opac_css/index.php?lvl=notice_display&id=26223