♂ Person: Anthony Finkelstein

DBLP: Finkelstein:Anthony

Facilitated 3 volumes:

Ed

GCh

Ed

Contributed to:

2013

2013

2012

2011

2011

2011

2010

2010

2009

2008

2008

2008

2008

2007

2005

2005

2004

2003

2003

2002

2001

2001

2001

2001

2000

2000

1999

1997

1995

1994

1994

1993

1993

1991

1989

Wrote 40 papers:

ER-BR-2013-Finkelstein #re-engineering #what

The Next 10 Years: the shape of software to come and what if means for software engineering (AF).

ESEC-FSE-2013-ZervoudakisREF #model checking #verification

Cascading verification: an integrated method for domain-specific model checking (FZ, DSR, SGE, AF), pp. 400–410.

SEKE-2012-PimentelSDCF #architecture #evolution #model transformation #towards

Towards Architectural Evolution through Model Transformations (JP, ES, DD, JC, AF), pp. 448–451.

CAiSE-2011-Finkelstein #bound #challenge #information management #re-engineering

Ten Open Challenges at the Boundaries of Software Engineering and Information Systems (AF), p. 1.

ICSE-2011-LimDF #identification #network #requirements #social #using

StakeSource2.0: using social networks of stakeholders to identify and prioritise requirements (SLL, DD, AF), pp. 1022–1024.

RE-2011-FitzgeraldLF #feature model #predict

Early failure prediction in feature request management systems (CF, EL, AF), pp. 229–238.

ICSE-2010-BencomoWSFL #requirements #runtime

Requirements reflection: requirements as runtime entities (NB, JW, PS, AF, EL), pp. 199–202.

ICSE-2010-LimQF #named #network #scalability #social #using

StakeNet: using social networks to analyse the stakeholders of large-scale software projects (SLL, DQ, AF), pp. 295–304.

ICSE-2010-LimQF10a #analysis #crowdsourcing #named #network #power of #social

StakeSource: harnessing the power of crowdsourcing and social networks in stakeholder analysis (SLL, DQ, AF), pp. 239–242.

RE-2010-SawyerBWLF #adaptation #research #self

Requirements-Aware Systems: A Research Agenda for RE for Self-adaptive Systems (PS, NB, JW, EL, AF), pp. 95–103.

HCI-VAD-2009-BolchiniFP #architecture #design

Designing Usable Bio-information Architectures (DB, AF, PP), pp. 653–662.

ASE-2008-EgyedLF #consistency #design #generative #modelling #nondeterminism #uml

Generating and Evaluating Choices for Fixing Inconsistencies in UML Design Models (AE, EL, AF), pp. 99–108.

ICSE-2008-BunyakiatiFSC #standard #testing #uml #using

Using JULE to generate a compliance test suite for the UML standard (PB, AF, JS, CC), pp. 827–830.

RE-2008-FinkelsteinHMRZ #analysis #requirements

“Fairness Analysis” in Requirements Assignments (AF, MH, SAM, JR, YZ), pp. 115–124.

REFSQ-2008-ZhangFH #challenge #optimisation #requirements

Search Based Requirements Optimisation: Existing Work and Challenges (YZ, AF, MH), pp. 88–94.

RE-2007-Finkelstein #in the large

Modelling-in-the-Large (AF).

ICSE-2005-CourbisF #aspect-oriented #towards #weaving

Towards aspect weaving applications (CC, AF), pp. 69–77.

RE-2005-BerryDFGHW #question #requirements #why

To do or not to do: If the requirements engineering payoff is so good, why aren’t more companies doing it? (DMB, DD, AF, DCG, RH, AW), p. 447.

EDOC-2004-YoshiokaHF #coordination #performance #security

Security Patterns: A Method for Constructing Secure and Efficient Inter-Company Coordination Systems (NY, SH, AF), pp. 84–97.

ICSE-2003-NentwichEF #consistency

Consistency Management with Repair Actions (CN, WE, AF), pp. 455–464.

ICSE-2003-NuseibehKF #exclamation #named

ViewPoints: meaningful relationships are difficult! (BN, JK, AF), pp. 676–683.

RE-2003-BushF #assessment #requirements #using

Requirements Stability Assessment Using Scenarios (DB, AF), pp. 23–32.

SEKE-2002-AlvesF #challenge #off the shelf #perspective #requirements

Challenges in COTS decision-making: a goal-driven requirements engineering perspective (CFA, AF), pp. 789–794.

ASE-2001-NentwichEF #consistency #distributed #specification

Static Consistency Checking for Distributed Specifications (CN, WE, AF), p. 115–?.

EDOC-2001-PiccinelliEF #component

Mapping Service Components to EJB Business Objects (GP, WE, AF), pp. 169–173.

ICSE-2001-MascoloEF #re-engineering #xml

XML Technologies and Software Engineering (CM, WE, AF), pp. 775–776.

RE-2001-FarbeyF #analysis

Software Acquisition: A Business Strategy Analysis (BF, AF), pp. 76–83.

FoSE-2000-FinkelsteinK #re-engineering #roadmap

Software engineering: a roadmap (AF, JK), pp. 3–22.

ICSE-2000-EmmerichMF #implementation #incremental #migration #xml

Implementing incremental code migration with XML (WE, CM, AF), pp. 397–406.

ICSE-2000-TakahashiEFG #development #using

System development using application services over the Net (KT, WE, AF, SG), p. 830.

RE-1999-ZismanF #xml

XML for Software Engineers (AZ, AF), p. 193–?.

RE-1997-FinkelsteinS #requirements #traceability

Requirements Traceability (AF, RS), p. 265.

RE-1997-GotelF #case study #industrial #requirements #traceability

Extended Requirements Traceability: Results of an Industrial Case Study (OG, AF), p. 169–?.

RE-1995-GotelF #requirements

Contribution structures (Requirements artifacts) (OG, AF), pp. 100–107.

ICRE-1994-GotelF #analysis #problem #requirements #traceability

An analysis of the requirements traceability problem (OCZG, AF), pp. 94–101.

ICSE-1994-Finkelstein #education #question #re-engineering

Software Engineering Education: A Place in the Sun? (AF), pp. 358–359.

ESEC-1993-FinkelsteinGHKN #consistency #multi #nondeterminism #specification

Inconsistency Handling in Multi-Perspective Specifications (AF, DMG, AH, JK, BN), pp. 84–99.

ICSE-1993-NuseibehKF #multi #requirements #specification

Expressing the Relationships Between Multiple Views in Requirements Specification (BN, JK, AF), pp. 187–196.

ESEC-1991-Finkelstein #requirements

A (Neat) Alphabet of Requirements Engineering Issues (AF), pp. 489–491.

ICSE-1989-Finkelstein #development #modelling #quote #representation

“Not Waving but Drowning”: Representation Schemes for Modelling Software Development (AF), pp. 402–404.