2015 Tenth International Conference on Computer Engineering &Amp; Systems (ICCES) 2015
DOI: 10.1109/icces.2015.7393045
|View full text |Cite
|
Sign up to set email alerts
|

Automatic framework for requirement analysis phase

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
7
0

Year Published

2017
2017
2022
2022

Publication Types

Select...
3
3

Relationship

1
5

Authors

Journals

citations
Cited by 7 publications
(7 citation statements)
references
References 4 publications
0
7
0
Order By: Relevance
“…Therefore, preparing a session for all selected stakeholders to collect and classify requirements is not trivial task. One of the efficient and formal requirement elicitation techniques that can deal with different schedules and different locations is the online questionnaire [14]. The online questionnaire is used as a formal tool that helped in describing, specifying, and prioritising (based on stakeholders preference) requirements well.…”
Section: Overview Of the Proposed Frameworkmentioning
confidence: 99%
See 3 more Smart Citations
“…Therefore, preparing a session for all selected stakeholders to collect and classify requirements is not trivial task. One of the efficient and formal requirement elicitation techniques that can deal with different schedules and different locations is the online questionnaire [14]. The online questionnaire is used as a formal tool that helped in describing, specifying, and prioritising (based on stakeholders preference) requirements well.…”
Section: Overview Of the Proposed Frameworkmentioning
confidence: 99%
“…After studying and analysing the complaints gathered previously about the faculty website, a number of existing requirements want to be enhanced/upgraded and a number of new requirements want to be added. An online questionnaire is set up only to help the requirement elicitation and release planning modelling phase based on the steps in [14]. The questionnaire comprises of three parts: the first part is for gathering each stakeholder personal information including name, faculty job position, last certificate, and so on.…”
Section: Phase 1: Requirement Elicitation and Release Planning Modellingmentioning
confidence: 99%
See 2 more Smart Citations
“…Basically, these processes are bound to vary at different levels depending on the kind of people that will be involved, organisational requirements and the application domain that is being employed. RE-E is a process that is used to determine and discover the needs of the clients or customers to find application domain [4], RA declares exactly what the software project is aimed to achieve [5], RS is used to document and presents a blueprint to the stakeholders for the process of software development [6], RVV acts as a proof that the software product may meet the needs of the stakeholders or customers [2] and finally RM is responsible for ensuring the existing requirements' modification are done in a controlled manner [7]. Figure 1 shows the activities involved in RE.…”
Section: Requirement Engineeringmentioning
confidence: 99%