From this page you can:
| Home |
Descriptors
Add the result to your basket Make a suggestion Refine your search Apply to external sourcesSIU IS. Administering Mis (Sing) Information a Comparative Study of Traditional and Agile Requirements Methods / Hussein Ahmed Abdulle / Bangkok: Shinawatra University - 2017
Collection Title: SIU IS Title : Administering Mis (Sing) Information a Comparative Study of Traditional and Agile Requirements Methods Material Type: printed text Authors: Hussein Ahmed Abdulle, Author ; Mason, Paul, Associated Name ; Aekavute Sujarae, Associated Name Publisher: Bangkok: Shinawatra University Publication Date: 2017 Pagination: vii, 90 p. Layout: ill, Tables Size: 30 cm. Price: 500.00 General note: SIU IS: SOST-MSIT-2017-03
Independent Study. [MS[Information Technology]]. -- Shinawatra University, 2017Languages : English (eng) Descriptors: [LCSH]Requirements engineering Keywords: Requirements engineering, Missing information, Requirements elicitation, Traditional and agile methods Abstract: Software requirements engineering is the most critical phase in developing software systems, because success or failure of system development depends more than anything else on the requirements which 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.
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.
Traditional methods user requirements are often misunderstood because the system analyst may misinterpret the user’s needs. In addition to requirements collecting, standards and constraints play an important role in systems development. Absence of appropriate requirements validation with the user involvement typically results in requirements that are incomplete because they fail to specify important customer needs or they are incorrect because of misunderstandings between the requirements engineers and the customers. That is why project failure is ongoing process over thirty years which comes from missing information.
More recently to lightweight techniques designed to deliver products on time, on budget, and with high quality and customer satisfaction. Agile team tried to solve the problems existing in traditional, 50% of failure they reduced and adaptation is 69% which is better than traditional methods.
However; this independent study we focus on the problem of missing information or incorrect requirement with four examples of Major IT project failures blamed (at least in part) on poor requirements.Curricular : BSCS/MSIT Record link: http://libsearch.siu.ac.th/siu/opac_css/index.php?lvl=notice_display&id=27605 SIU IS. Administering Mis (Sing) Information a Comparative Study of Traditional and Agile Requirements Methods [printed text] / Hussein Ahmed Abdulle, Author ; Mason, Paul, Associated Name ; Aekavute Sujarae, Associated Name . - [S.l.] : Bangkok: Shinawatra University, 2017 . - vii, 90 p. : ill, Tables ; 30 cm.
500.00
SIU IS: SOST-MSIT-2017-03
Independent Study. [MS[Information Technology]]. -- Shinawatra University, 2017
Languages : English (eng)
Descriptors: [LCSH]Requirements engineering Keywords: Requirements engineering, Missing information, Requirements elicitation, Traditional and agile methods Abstract: Software requirements engineering is the most critical phase in developing software systems, because success or failure of system development depends more than anything else on the requirements which 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.
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.
Traditional methods user requirements are often misunderstood because the system analyst may misinterpret the user’s needs. In addition to requirements collecting, standards and constraints play an important role in systems development. Absence of appropriate requirements validation with the user involvement typically results in requirements that are incomplete because they fail to specify important customer needs or they are incorrect because of misunderstandings between the requirements engineers and the customers. That is why project failure is ongoing process over thirty years which comes from missing information.
More recently to lightweight techniques designed to deliver products on time, on budget, and with high quality and customer satisfaction. Agile team tried to solve the problems existing in traditional, 50% of failure they reduced and adaptation is 69% which is better than traditional methods.
However; this independent study we focus on the problem of missing information or incorrect requirement with four examples of Major IT project failures blamed (at least in part) on poor requirements.Curricular : BSCS/MSIT Record link: http://libsearch.siu.ac.th/siu/opac_css/index.php?lvl=notice_display&id=27605 Hold
Place a hold on this item
Copies
Barcode Call number Media type Location Section Status 32002000596906 SIU IS: SOST-MSIT-2017-03 c.1 SIU Independent Study Graduate Library Thesis Corner Available 32002000597078 SIU IS: SOST-MSIT-2017-03 c.2 SIU Independent Study Graduate Library Thesis Corner Available
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 -- DevelopmentKeywords: Requirements Engineering
Requirements Elicitation
Requirements Extraction rulesAbstract: 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 -- DevelopmentKeywords: Requirements Engineering
Requirements Elicitation
Requirements Extraction rulesAbstract: 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 Hold
Place a hold on this item
Copies
Barcode Call number Media type Location Section Status 32002000580488 SIU THE: SOIT-MSIT-2014-02 c.1 SIU Thesis and Dissertation Graduate Library Thesis Corner Available
