Functional and Non-Functional Requirements Modeling for the Design of New Online Social Networks

Functional and Non-Functional Requirements Modeling for the Design of New Online Social Networks

Sarah Bouraga (University of Namur, Belgium), Ivan Jureta (Fonds de la Recherche Scientifique, Belgium & University of Namur, Belgium) and Stéphane Faulkner (University of Namur, Belgium)
DOI: 10.4018/978-1-5225-5715-9.ch002

Abstract

Online social networks (OSNs) such as Facebook and LinkedIn are now widely used. They count users in the hundreds of millions. This chapter surveys popular social networks in order to present a pattern of recurring functional requirements as well as non-functional requirements, and a model of that pattern in the i* requirements modelling language. The pattern can serve as a starting point for requirements engineering of new OSNs. The authors test their model by applying it to a popular OSN, namely Twitter.
Chapter Preview
Top

Introduction

Online Social Networks (OSNs) have grown to be popular over the last decade. They are systems that allow users to share content about any subject they wish, with anyone. To become a member, one has to create an account, and establish relationships with other users. OSNs allow then their users to connect online with their friends, communicate with each other, and share content. The most popular OSNs, such as Facebook, Twitter, or LinkedIn count hundreds of millions of members.

Considerable research has been carried out about OSNs. The literature mostly focuses on the structure of the networks, their topological characteristics, or on the user activity. Also, several studies explore the privacy and trust issues. Indeed, the OSNs have sparked a lot of interest, in part because of the volume of information they gather about their users. The latter give away a considerable amount of information (consciously and unconsciously) through their activity: their profile, their posts, their friends, their browsing activity, etc. This has led to various concerns.

However, as far as we know, researchers have not explored the patterns of features of the OSNs. What kind of features does an OSN have? What are the recurring features that we can find in several OSNs? Does a pattern of features exist that would be shared by OSNs? How important the features of OSNs are to users? Not much attention has been invested in Requirements Engineering (RE) for OSNs, either. What should be taken into account when designing an OSN? How should we model the recurring features? Can we define a requirements pattern for the design of OSNs?

We believe that these research questions are valuable because RE is one of the most important phases in the design of any Information System (IS). It is the first stage in the development of an IS, when the purpose of the IS is decided. RE is concerned with the elicitation, evaluation, specification, consolidation, and evolution of the objectives, functionalities, qualities, and constraints a software- based system should meet within some organizational or physical setting (van Lamsweerde, 2008).

In this paper, we propose to model a pattern of OSN features, using an existing RE modeling language, namely i* (Yu, 1997). More specifically, the goals and the corresponding contributions of this paper are twofold. Firstly, we seek to identify a pattern of features of OSNs. Secondly, we will model these features using an existing requirements engineering language, namely i*, and evaluate if it can represent accurately all the features present in the pattern.

In order to address these questions, we apply the following research methodology. Firstly, we identify features of various OSNs and compare them across those systems; as opposed to features specific to one particular OSN. Secondly, we analyze this list of features with regard to the selected OSNs: are the given features present in the OSN? Which form does the feature take? We will see if a pattern emerges from the discussion. We also discuss the implications of our findings for the design of future OSNs; and more specifically, the implications for the RE phase in the design of an OSN. Thirdly, we apply our modeling pattern to a specific OSN, namely Twitter. If a pattern of features common to several OSNs is found, we will know that one should pay attention to these particular features when designing an OSN.

The rest of this paper is structured as follows. First, Related Work is discussed in Section 2, as well as a brief summary of several popular OSNs. Then, we introduce the features we identified of OSNs, and analyze them in relation to the selected OSNs, in Section 3 Section 4 respectively. In Section 5, we turn to the modeling of the features using an existing RE language, namely i*; and we discuss the results in Section 6. Finally, Section 7 concludes the paper.

Complete Chapter List

Search this Book:
Reset