PACE
PACE is an architectural style for trust management in
decentralized applications. An architectural style is a set of
guidelines, constraints and principles that define how components and
connectors are composed together in an architecture, how they behave
and the nature of their interaction. PACE similarly provides a set of
principles and constraints that provide comprehensive guidance on what
trust components to include, how to place these components
appropriately within the architecture of a decentralized entity, and
how these components should interact for effective trust management.
ScenarioGraph
ScenarioGraph is a tool for specifying,
visualizing, and analyzing temporal relations of events in complex
scenarios written in ScenarioML. ScenarioML is a language for
writing scenarios in XML. It
provides syntax for expressing the semantic distinctions that are
present in scenarios, and semantics for the things that people use and
respond to consistently in scenarios. ScenarioGraph
provides graphical editing of scenarios, computation of the relations
between events, consistency analysis of scenarios, comparison of
scenarios, and matching graphical scenarios against concrete
occurrences. ScenarioGraph has been implemented in Java and given
initial evaluation on a group of scenarios, including the real-world
scenario used in this study as an example.
Scenario Workbench
The Scenario Workbench is an Eclipse plug-in for editing and working with scenarios in ScenarioML.
ScenarioML is a language for writing scenarios in XML. It
provides syntax for expressing the semantic distinctions that are
present in scenarios, and semantics for the things that people use and
respond to consistently in scenarios. Scenario Workbench is
currently under development.
Scenario and Ontology based Software Architecture Evaluation (SOSAE)
SOSAE is an approach to architecture evaluation that aids software
architecture designers. The approach takes requirements-level scenarios
described in ScenarioML
and evaluates them against the architecture of the system described
with components and connectors. The scenarios describe the functional
and non-functional requirements that are important to the stakeholders.
The approach is based on explicit mappings between eventTypes in the
ontology and components in the architecture. The mapping is created by
examining in conjunction the meaning of the event in the scenarios and
the roles played by different components in the architecture. A tool
supporting the approach is under development.