On the public citation graph
A scenario‐based approach for requirements engineering: Experience in a telecommunication software development project
0 signed · 28 inferred · view as graph
Inferred edges come from two machine sources: sweeps of open repository metadata (mostly SSRN and Zenodo), and a bulk OpenAlex citation snapshot. Every row below is labelled with the one it came from. Neither is a complete citation index — absence here is not evidence of absence.
Is this your work? Sign in with ORCID and put your name on the
claims that are yours.
Reference health. See whether every reference in this work resolves to a
known work and none has been retracted — and get a dated CiteStamped
badge you can embed.
What this work says
Outgoing claims: the papers this work cites, builds on, or argues with.
inferredcites →https://doi.org/10.1002/sys.10057openalex-snapshot
Case studies of systems engineering and management in systems acquisition
inferredcites →https://doi.org/10.1002/sys.20013openalex-snapshot
The hybrid process that combines traditional requirements and use cases
inferredcites →https://doi.org/10.1006/ijhc.1994.1058openalex-snapshot
Binding objects to scenarios of use
inferredcites →https://doi.org/10.1007/s00766-004-0192-6openalex-snapshot
Scenario-based requirements analysis techniques for real-time software systems: a comparative evaluation
inferredcites →https://doi.org/10.1016/0167-6423(93)90021-gopenalex-snapshot
Goal-directed requirements acquisition
inferredcites →https://doi.org/10.1023/a:1018954425162openalex-snapshot
A practical approach to combining requirements definition and object‐oriented analysis
inferredcites →https://doi.org/10.1109/3468.867861openalex-snapshot
A design process based on a model combining scenarios with goals and functions
inferredcites →https://doi.org/10.1109/52.663783openalex-snapshot
Scenarios in system development: current practice
inferredcites →https://doi.org/10.1109/ms.2002.1003459openalex-snapshot
Tracing all around in reengineering
What points at this work
Incoming claims: where this work appears in other papers’ reference lists and arguments.
inferred← citeshttps://doi.org/10.1002/j.2334-5837.2007.tb02896.xopenalex-snapshot
4.1.0 Panel 4.1.0: Requirements Engineering for Software vs. Systems in General?
inferred← citeshttps://doi.org/10.1002/sys.20086openalex-snapshot
Using parameters and discriminants for product line requirements
inferred← citeshttps://doi.org/10.1002/sys.21231openalex-snapshot
Strategic requirements engineering for complex sustainable systems
inferred← citeshttps://doi.org/10.1002/sys.21560openalex-snapshot
Toward a better integration of requirements and model‐based specifications
inferred← citeshttps://doi.org/10.1007/978-3-030-01042-3_11openalex-snapshot
A Comparative Analysis of ITU-MSC-Based Requirements Specification Approaches Used in the Automotive Industry
inferred← citeshttps://doi.org/10.1007/978-3-540-74800-7_93openalex-snapshot
How to Combine Requirements and Interaction Design Through Usage Scenarios
inferred← citeshttps://doi.org/10.1007/978-3-642-03658-3_117openalex-snapshot
Combining Requirements and Interaction Design through Usage Scenarios
inferred← citeshttps://doi.org/10.1007/978-3-642-23768-3_126openalex-snapshot
Scenario-Based Requirements Engineering Facilitating Interaction Design
inferred← citeshttps://doi.org/10.1007/978-3-642-31063-8_33openalex-snapshot
Requirements Meet Interaction Design
inferred← citeshttps://doi.org/10.1007/978-3-642-39259-7_36openalex-snapshot
Model-Based Transition from Requirements to High-Level Software Design
inferred← citeshttps://doi.org/10.1007/s00766-009-0095-7openalex-snapshot
On confusion between requirements and their representations
inferred← citeshttps://doi.org/10.1016/j.is.2018.01.011openalex-snapshot
On the relevance of a business constraint to an event log
inferred← citeshttps://doi.org/10.1017/pds.2024.5openalex-snapshot
Introducing a framework to translate user scenarios into engineering specifications with “action steps”
inferred← citeshttps://doi.org/10.1109/apsec.2013.117openalex-snapshot
Model-Based Transition from Requirements to High-Level Software Design
inferred← citeshttps://doi.org/10.1109/icebe68123.2025.00017openalex-snapshot
From Scenario to Case Model: Generating CMMN Models from Natural Language with Large Language Models
inferred← citeshttps://doi.org/10.1109/icsea.2009.16openalex-snapshot
A Unification of the Essence of Goal-Oriented Requirements Engineering
inferred← citeshttps://doi.org/10.1109/syscon.2017.7934808openalex-snapshot
A language proposition for system requirements
inferred← citeshttps://doi.org/10.2201/niipi.2008.5.8openalex-snapshot
Feature interaction: the security threat from within software systems
Editorial review for independent work. ICSAC — the Institute for Complexity
Science and Advanced Computing — runs a structured editorial panel for researchers
publishing outside journals, and publishes on CiteStamp rails. Submission is free
and goes through ORCID: icsacinstitute.org/submit.