3 research outputs found
Requirement patterns: an approach for streamlining requirements engineering in software product families
Reusable structure is essential in all reuse-based software
development processes. This provides a solid foundation
for seamless management of reusable artefacts especially
in software product line engineering (SPLE). One of the
potential benefits provided by a well-defined structure is
systematic reuse of these artefacts. Requirements pattern
approach provides guidelines for requirement engineers to
reuse and specify requirements. Although a plethora of
research on requirements pattern have been reported in the
literature, no research available focuses on requirement
engineering (RE) activities of SPLE. In this paper, we
present an anatomy of software requirement pattern (SRP)
for SPLE with a structured example from e-learning
domain. To enable practitioners, understand the concept of
requirement pattern more, we present a meta-model for the
SRP concepts and their relationships. In addition, we
describe how the requirement pattern approach,
streamlines RE activities, design for and with reuse in both
domain and application engineering processes of SPLE.
The requirement pattern approach thus helps in achieving
systematic requirements reuse (RR) and generation of
structured software requirement specification (SRS) for
individual applications
Modelling Requirements for Content Recommendation Systems
This paper addresses the modelling of requirements for a content
Recommendation System (RS) for Online Social Networks (OSNs). On OSNs, a user
switches roles constantly between content generator and content receiver. The
goals and softgoals are different when the user is generating a post, as
opposed as replying to a post. In other words, the user is generating instances
of different entities, depending on the role she has: a generator generates
instances of a "post", while the receiver generates instances of a "reply".
Therefore, we believe that when addressing Requirements Engineering (RE) for
RS, it is necessary to distinguish these roles clearly.
We aim to model an essential dynamic on OSN, namely that when a user creates
(posts) content, other users can ignore that content, or themselves start
generating new content in reply, or react to the initial posting. This dynamic
is key to designing OSNs, because it influences how active users are, and how
attractive the OSN is for existing, and to new users. We apply a well-known
Goal Oriented RE (GORE) technique, namely i-star, and show that this language
fails to capture this dynamic, and thus cannot be used alone to model the
problem domain. Hence, in order to represent this dynamic, its relationships to
other OSNs' requirements, and to capture all relevant information, we suggest
using another modelling language, namely Petri Nets, on top of i-star for the
modelling of the problem domain. We use Petri Nets because it is a tool that is
used to simulate the dynamic and concurrent activities of a system and can be
used by both practitioners and theoreticians.Comment: 28 pages, 7 figure