Clustering technique for information requirement prioritization in specific CMSs

Setiani, Novi; Dirgahayu, Teduh

doi:10.1109/icodse.2016.7936107

Cited by 7 publications

(8 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…There were four clusters representing the level of importance i.e. very important, important, less important and not necessary [8]. [27] Proposed the use of Case-based Ranking (CBR), which combines stakeholders' preferences with requirement ordering approximations computed through machine learning approaches.…”

Section: Related Workmentioning

confidence: 99%

“…Existing techniques from the literature have shown that they are not scalable for large set of requirements especially in dealing with dependency issues between the functional requirements. When one requirement is dependent on other requirements, prioritization on the basis of internal structure of the implementation becomes necessary [7] [8]. There are three types of requirements; (1) business requirements which deals with benefits and cost issues of requirements along with time constraint, (2) functional requirements which are necessary for software system to develop, and (3) non-functional requirements that are not directly demanded but are necessary for ensuring quality product such as security and performance issues.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Untitled

2020

Int. j. comput. sci. softw. engr.

View full text Add to dashboard Cite

Requirements prioritization plays important role for a successful requirements implementation. Functional requirements, in specific, represents the specification of behavior between the inputs and outputs. They are prioritized based on the high-level requirements of the system and subsystems functionalities, as well as the type of software, expected users and the type of system where the software is used. Nonetheless, prioritization of functional requirements is very challenging considering a project where the requirements are huge. In practice, prioritization of functional requirements highly depends on stakeholders' preference for giving priorities in features selection instead of based on its internal structure and characteristics. This is because the key information in functional requirements concern on business processes, security, performance, data migration and conversion. This paper proposes a graph-based approach for prioritizing functional requirements using directed acyclic graphs for relating requirements with one another on the basis of its importance to overall project and how much it is required for other requirements. The proposed approach is then evaluated in terms of total time estimation to project completion. The experimental results showed that the graph-based approach is able to effectively prioritize functional requirements with lower estimated project completion time as compared to non-prioritized requirements. The approach will help software vendors to deliver projects well within the total project duration.

show abstract

Section: Related Workmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Untitled

2020

Int. j. comput. sci. softw. engr.

View full text Add to dashboard Cite

show abstract

“…Although most of the techniques like AHP work well for small size requirements, they are not scalable and suitable to apply on large requirements. While machine learning techniques and intelligent based techniques such as Artificial Neural Networks (ANN) and SNIPR are suitable for prioritizing large-sized FRs, but they are not suitable techniques to prioritize FRs from developer's perspective where requirements are distributed in parallel development team [20][21] [22].…”

Section: Introductionmentioning

confidence: 99%

Prioritization of Software Functional Requirements from Developers Perspective

Yaseen¹,

Ibrahim²

2020

IJACSA

View full text Add to dashboard Cite

Prioritizing software requirements is important and difficult task during requirements management phase of requirements engineering. To ensure timely delivery of project, software developers have to prioritize functional requirements. The importance of prioritization increases when size of requirements is big. Software for large enterprises like the Enterprise Resource Planning (ERP) systems are more likely to be developed by a team of software developers where large size requirements are distributed in parallel team members. However, requirements are dependent on each other, therefore development of pre-requisite requirements must be carefully timed and should be implemented first. Therefore, assigning importance and priority to some requirements over others is necessary so that requirements can be available on time to developers. This paper proposes a prioritization approach for functional requirements on the basis of their importance during implementation. The design of research method consists of Analytical Hierarchical Process (AHP) technique based on spanning trees. Through spanning trees, dependent requirements were linked in hierarchical structure and then AHP were applied. As a result of prioritization, requirements were distributed in such a way that dependency among requirements of developers were kept minimum as much as possible so that waiting time of requirements for their pre-requisite were reduced. With reduced effect of dependency in requirements of parallel developers, timely delivery of software projects can be assured.

show abstract

“…In a large software development projects such as an Enterprise Resource Planning (ERP), requirements are huge and prioritization process becomes much difficult [11]. When the stakeholder wishes to implement each and every requirement within a limited time and a limited budget, prioritization of the requirements become necessary [12] [13] [14]. As all types of requirements are inter-dependent with each other, there is critical need of collaboration among software developers and stakeholders during requirements prioritization especially when requirements [13].…”

Section: Introductionmentioning

confidence: 99%

Prioritization of Software Functional Requirements: Spanning Tree based Approach

Yaseen¹,

Ibrahim²

2019

IJACSA

View full text Add to dashboard Cite

Requirements prioritization shows significant role during effective implementation of requirements. Prioritization of requirements is not easy process particularly when requirements are large in size. The current methods of prioritization face limitations as the current prioritization techniques for functional requirements rely on the responses of stakeholders instead of prioritizing requirements on the basis of internal dependencies of one requirement on other requirements. Moreover, there is need to classify requirements on the basis of their importance i.e. how much they are needed for other requirements or dependent on other requirements. Requirements are first represented with spanning trees and then prioritized. Suggested spanning tree based approach is evaluated on requirements of ODOO ERP. Requirements are assigned to four developers. Time estimation with and without prioritization are calculated. The difference in time estimation with prioritization and without prioritization shows the significance of prioritization of functional requirements.

show abstract

Clustering technique for information requirement prioritization in specific CMSs

Cited by 7 publications

References 8 publications

Untitled

Untitled

Prioritization of Software Functional Requirements from Developers Perspective

Prioritization of Software Functional Requirements: Spanning Tree based Approach

Contact Info

Product

Resources

About