Using Nsia For Large Scale Requirement Elicitation

Published Date: 02 Nov 2017

Abstract:

Requirement elicitation is the software engineering activity in which it requires involvement with client domain experts and end users in order to establish a client’s needs. For large scale projects several methods has been used to identify and prioritize the requirement using techniques. Various social network measures are used for prioritization process. Stakeholders are asked to rate an initial set of requirements; they can also suggest other requirements. The requirements are then prioritized using their ratings weighted by their influence in project. The method which is used for prioritization assumes that stakeholder provide recommendation honestly. But malicious stakeholder may provide responses for their personal benefits such as recommending no stakeholders exclude some stakeholder’s. This in turn affects the quality of stakeholders and requirements. Thus to reduce the malicious stake holder’s requirement ranking, based on the changing behavior of their requirement specification rating an algorithm is developed to identify the non-stakeholders.NSIA-Non stakeholder identification algorithm is an algorithm which identifies the Non stakeholders.

Index terms-Requirements/specification, elicitation methods, requirements prioritization, recommender system, social network analysis, stakeholder analysis.

INTRODUCTION:

Nowadays growth in software system is increasing. Large-scale projects include more number of stakeholders and they all are diverse in their needs

Requirement elicitation is the practice of collecting the requirements from users, customers and other stakeholders [16]. It includes practices such as interviews, questionnaires, user observation,

Workshops and role playing. It consists of process such as identifying stakeholders, requirements from these stakeholders and prioritizing their requirements.

Requirement prioritization is used in Software product management for determining which candidate requirements of a software product should be included in a certain release [15] [4] [5].

Stake Rare is the method which is used for identifying and prioritizing the requirements. It can be done using social networks and collaborative filtering.StakeRare stands for –Stakeholder Recommender assisted method for requirements elicitation.

It can be used for large scale projects in which it holds more number of stakeholders. Due to large numbers they were unable to meet, because they are diverse by their locations and time constraint [9].

Stake rare uses social network to identify and prioritize stakeholders and their roles in the project. Then, it asks the stakeholders to rate an initial set of requirements using their ratings weighted by their project influence derived from their position on the social network. The process involves construction of social network with stakeholders as nodes and their recommendations as links.

A social network measure [7] [8] [10] such as Betweenness centrality is used for prioritization process. Stakeholders are asked to rate an initial set of requirements; they can also suggest other requirements.

The requirements are then prioritized using their ratings weighted by their influence in project. Collaborative filtering is the process of filtering for information or patterns using techniques involving collaboration among multiple agents, viewpoints, data sources [11] [12] [13]. This is used for prediction of user information. The prediction can be done by using variety of algorithms such as KNN.K-Nearest Neighbor algorithm [11] is used to find like-minded users.

Social network measures [16] [7] [8] [10] such as Betweeness centrality, Load centrality, Degree centrality, In-degree centrality, and Out-degree centrality.

Stake Rare assumes that stakeholder provide recommendation honestly. But malicious stakeholder may provide responses for their personal benefits such as recommending no stakeholders exclude some stakeholders [9].

The system is resilient against stakeholders who misuse their signature power, since their only obligation is not to sign conflicting blocks, the only way they could double spend is if they first sign one block so it achieves a majority, then sign a different one so that it achieves a greater majority.

Thus to reduce the malicious stake holder’s requirement ranking, based on the changing behavior of their requirement specification rating an algorithm is developed to identify the non-stakeholders. The Malicious Stakeholder can be identified based on number of clicks they used for rating the requirements.

RELATED WORK:

An algorithmic framework for performing collaborative filtering and new algorithmic elements that increase the accuracy of collaborative filtering algorithms has been proposed[12].Requirement-driven collaboration is the collaboration during the management and development of requirements.

(1)Constructs a requirement-centric social network which represents the membership and relationships among members working on a requirement and its associated downstream artifacts.

(2)Outlines a number of social network analysis techniques to study collaboration aspects such as communication, awareness, and the alignment of technical dependencies driven by development of requirements and social interactions.

Prioritizing requirement is an important activity in product development [1]. It generally requires complex context-specific decision-making and it has to be performed iteratively during the development [13].

A network is usually defined as a set of actors (or agents, or nodes, or points, or vertices) that may have relationships (or links, or edges, or ties) with one another [9].Networks can have few or many actors, and one or more kinds of relations between pairs of actors.

Requirement prioritization necessarily relies on the specified requirements and on predictions of benefit and cost of individual requirements [15].

PROPOSED WORK:

The NSIA algorithm is proposed to identify the Non–Stakeholders. The architecture for the proposed system is illustrated in Figure1

FIGURE 1

The architecture describes the steps identifying, prioritizing stakeholders and their requirements.

Identify and Prioritize Stakeholder

Stakeholders have to be prioritized. As their level of influence in the project affects the priority of the requirements.

Stake net is a stakeholder analysis method used to identify initial Stakeholders. It then asks to recommend other Stakeholders [9].

It uses various social network measures to prioritize the Stakeholders.

Collect Profile from stake holders

Stakeholders identified from previous step can provide their preferences on the Requirements which are in the form of [9]:

<Stakeholder, requirement, rating>.

Elicitation methods such as interviews can be used to identify initial set of requirements.

TABLE 1

Concept

Description

Stakeholder

An Individual or a group who can influence or influenced by the project success or failure of a project.

Stakeholder role

The Stakeholder’s position in the Project[18]

Requirement

The goals,funtions and constraints on software systems.[13]

Rating

Numerical Importance given in terms of values Range from 1-5[11]

Predict Requirements:

In this step requirements are predicted based on the collected Stakeholder’s profile. Collaborative filtering systems use KNN algorithm to find Stakeholder’s and measure the similarity between their profiles; it then generates predicted level of interest.

Finally rating can be given to the predicted requirements. [9]

Finding malicious stake holders

To reduce the malicious stake holder’s requirement ranking, based on the changing behavior of their requirement specification rating an algorithm can be proposed.

Using the algorithm, the no of clicks made for rating the requirement can be calculated. If the clicks made by stakeholders for rating the requirements exceeds more than threshold value, then resultant is a non stakeholder.

The algorithm for identifying Non-Stakeholder is as follows,

Input data:

Where(i =1 to N)

/*N=Total number of stakeholder

Compute

/*=Clicks made by user

/*TR=Total number of Requirements

If ≤(TR ± α),1<α<3

then

ξ Stakeholders

else

ξ Non-Stakeholders

Prioritize Requirements

The requirements are then prioritized based on the influence of Stakeholder role in the project, influence of Stakeholder role.

The influence of stakeholder i’s role in the project

Using these project influence and importance are calculated. Finally based on importance their requirements are prioritized [9].

CONCLUSION:

Large-scale projects include more number of stakeholders and they all are diverse in their needs. Requirement elicitation is the practice of collecting the requirements from users, customers and other stakeholders. It consists of process such as identifying stakeholders, requirements from these stakeholders and prioritizing their requirements.

Requirements rated by malicious stakeholders affect the quality of product. We have proposed an algorithm for identifying Non-Stakeholders. Future work can be extended in the direction of finding a tool for automatic identification of Non-Stakeholders.

RFERENCE:

[1] L. Lehtola, M. Kauppinen, and S. Kujala, "Requirements Prioritization Challenges in Practice," Proc. Int’l Conf. Product Focused

[2] S.L. Lim, "Social Networks and Collaborative Filtering for Large-Scale Requirements Elicitation," PhD thesis, Univ. of New South Wales,//www.cs.ucl.ac.uk/staff/S.Lim/phd/thesis_soolinglim.pdf, 2010.

[3] A. van Lamsweerde, "Goal-Oriented Requirements Engineering: A Guided Tour," Proc. Fifth IEEE Int’l Symp. Requirements Eng., pp. 249-262, 2001.

[4] J. Karlsson and K. Ryan, "A Cost-Value Approach for Prioritizing Requirements," IEEE Software, vol. 14, no. 5, pp. 67-74, Sept. /Oct. 1997.

[5] J. Azar, R.K. Smith, and D. Cordes, "Value-Oriented Requirements Prioritization in a Small Development Organization," IEEE Software, vol. 24, no. 1, pp. 32-37, Jan. /Feb. 2007.

[6] N.R. Mead, Requirements Prioritization Introduction. Software Eng. Inst., Carnegie Mellon Univ., 2006.

[7] S. Wasserman and K. Faust, Social Network Analysis: Methods and Applications. Cambridge Univ. Press, 1994.

[8] J. Scott, Social Network Analysis: A Handbook. Sage, 2000.

[9]S.L. Lim, and A. Finkelstein"StakeRare: Using Social Networks andCollaborative Filtering forLarge-Scale Requirements Elicitation", IEEE transactions on software engineering, vol. 38, no. 3, may/June 2012

[10]R.A. Hanneman and M. Riddle, Introduction to Social Network Methods. Univ. of California, Riverside, 2005.

[11] J. Schafer, D. Frankowski, J. Herlocker, and S. Sen., "Collaborative Filtering Recommender Systems," The Adaptive Web: Methods and Strategies of Web Personalization, pp. 291-324, Springer, 2007.

[12] J.L. Herlocker, J.A. Konstan, A. Borchers, and J. Riedl, "An Algorithmic Framework for Performing Collaborative Filtering," Proc. 22nd Ann. Int’l ACM SIGIR Conf. Research and development in Information Retrieval, pp. 230-237, 1999.

[13]D. Damian, I. Kwan, and S. Marczak, "Requirements-Driven Collaboration: leveraging the Invisible Relationships between Requirements and People," Collaborative Software Engineering, Springer, 2010.

[14] N. Lathia, "Computing Recommendations with Collaborative Filtering," Collaborative and Social Information Retrieval and Access: Techniques for Improved User Modeling, Information Science Reference, 2008.

[15] A. Herrmann and M.Daneva, "Requirements Prioritization Based on Benefit and Cost Prediction: An Agenda for Future Research,"Proc. 16th IEEE Int’l Conf. Requirements Eng., pp. 125-134, 2008.

[16] S.L. Lim, D. Damian, and A. Finkelstein, "Stake Source: Harnessing the Power of Crowd sourcing and Social Networks in Stakeholder Analysis," Proc. 32nd ACM/IEEE Int’l Conf. Software Eng. vol. 2, pp. 239-242, 2010.

[17] S.L. Lim, D. Damian, and A. Finkelstein, "StakeSource2.0: Using Social Networks of Stakeholders to Identify and Priorities Requirements," Proc. 33rd ACM/IEEE Int’l Conf. Software Eng., 2011.

[18]H. Sharp, G.H. Galal, and A. Finkelstein, "Stakeholder Identification in the Requirements Engineering Process," Proc. Database and Expert System Applications Workshop, pp. 387-391, 1999.

[19] B. Nuseibeh and S. Easterbrook, "Requirements Engineering: A Roadmap," Proc. Conf. Future of Software Eng., pp. 35-46, 2000.