Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Pourya Shaker

dblp:59/6080 · DBLP profile ↗
← Back
6ranked-venue papers
3as first author
0since 2021 · last 2015
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 6 · 3 first-authorArtificial intelligence and machine learning · 1 · 1 first-authorApplied, interdisciplinary, general and emerging computing · 1 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Requirements engineering and software design · 100%

Topics — the 1 heaviest of 1, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Requirements engineering and software design
requirements modeling
0.112010
Feature-oriented requirements modelling · ICSE (2) 2010

Methods — techniques the papers use, named apart from their topics

state machines · 0.1
YearPublicationVenuePosition
2015 Incremental and Commutative Composition of State-Machine Models of Features
abstract
In this paper, we present a technique for incremental and commutative composition of state-machine models of features, using the Feature House framework. The inputs to Feature House are feature state-machines (or state-machine fragments) modelled in a feature-oriented requirement modelling language called FORML and the outputs are two state-machine models: (1) a model of the whole product line with optional features guarded by presence conditions, this model is suitable for family-based analysis of the product line, and (2) an intermediate model of composition that facilitates incremental composition of future features. We discuss the challenges and benefits of our approach and our implementation in the Feature House.
Sandy Beidu, Joanne M. Atlee, Pourya Shaker
MiSE@ICSE3
2014 Behaviour interactions among product-line features
abstract
A software product line (SPL) is often constructed as a set of features, such that individual products can be assembled from a set of common features and a selection of optional features. Although features are conceptualized, developed, and evolved as separate concerns, it is often the case that, in practice, they interfere with each other -- called a feature interaction. In this paper, we precisely define what it means for one feature to have a behaviour interaction with another feature, where the behaviour of one feature is affected by the presence of another feature. Specifically, we use a form of bisimilarity to define when the behaviour of a feature in isolation differs from its behaviour in the presence of an interacting feature. We also consider the case where features are modelled in a language that allows the specification of intended interactions, and we adapt our use of bisimilarity to provide a formal definition for unintended behaviour interactions.
Pourya Shaker, Joanne M. Atlee
SPLC1
2012 A feature-oriented requirements modelling language
abstract
In this paper, we present a feature-oriented requirements modelling language (FORML) for modelling the behavioural requirements of a software product line. FORML aims to support feature modularity and precise requirements modelling, and to ease the task of adding new features to a set of existing requirements. In particular, FORML decomposes a product line's requirements into feature modules, and provides language support for specifying tightly-coupled features as model fragments that extend and override existing feature modules. We discuss how decisions in the design of FORML affect the evolvability of requirements models, and explicate the specification of intended interactions among related features. We applied FORML to the specification of two feature sets, automotive and telephony, and we discuss how well the case studies exercised the language and how the requirements models evolved over the course of the case studies.
Pourya Shaker, Joanne M. Atlee, Shige Wang
RE1
2012 Code generation for a family of executable modelling notations
Adam Prout, Joanne M. Atlee, Nancy A. Day, Pourya Shaker
Softw. Syst. Model.4
2010 Feature-oriented requirements modelling
abstract
Our goal is to develop a method for creating models of functional software requirements in which features are explicit, with a focus on the automotive software domain. In the current state of our proposed method, feature requirements are modelled using state machines that describe changes to a shared domain model.
Pourya Shaker
ICSE (2)1
2008 Semantically Configurable Code Generation
Adam Prout, Joanne M. Atlee, Nancy A. Day, Pourya Shaker
MoDELS4