Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Supporting Software Development Teams with a Semantic Process- and Artifact-oriented Collaboration Environment <ul><li>Seb...
Motivation <ul><li>Many software projects are late, over budget, or fail due to complexity </li></ul><ul><li>Complexity re...
Research Questions <ul><li>How do we support SMEs with regards to mastering context activities? </li></ul><ul><li>They nee...
SPACE (Semantic Process- & Artifact-oriented Collaboration Environm.)  <ul><li>SE research has proposed many SE models </l...
Correlation between SPACE and SOP <ul><li>SPACE is domain and scenario independent </li></ul><ul><ul><li>Meta-model infras...
Mockup of SOP 2.0 Artifact Model Editor
Correlation between SPACE, SOP, and SOP 2.0
SPACE Process Model <ul><li>Basis for both modeling and execution platforms </li></ul><ul><li>Supports collaborative model...
SPACE Process Model (cont.) <ul><li>Personalized views enable roles to have minimal but sufficient view on processes </li>...
SPACE Artifact Model <ul><li>Artifact models are associated with process models or activities </li></ul><ul><li>Define the...
SPACE Artifact Model (cont.)
Related Work <ul><li>Related standards and concepts: </li></ul><ul><ul><li>ARIS (Architecture of Integrated IS) </li></ul>...
Related Work (cont.) <ul><li>SE process software </li></ul><ul><ul><li>V-Modell XT Projektassistent </li></ul></ul><ul><ul...
Feedback is Welcome <ul><li>Is this approach feasible/meaningful for  establishing process knowledge within SMEs? </li></u...
<ul><li>Backup </li></ul>
SOP 2.0 Architecture <ul><li>MediaWiki and Semantic MediaWiki as collaborative platform </li></ul><ul><li>Adobe Flex GUI <...
SOP 2.0 GUI Menu bar Accordion Tabbed Editor View
Example
Upcoming SlideShare
Loading in …5
×

Supporting Software Development Teams with a Semantic Process- and Artifact-oriented Collaboration Environment

1,115 views

Published on

"Supporting Software Development Teams with a Semantic Process- and Artifact-oriented Collaboration Environment" (Sebastian Weber, Andreas Emrich, Jörg Broschart, Eric Ras and Özgür Uenalan)

The focus of this paper is on how to support small software teams in
tailoring and following organization-specific process models by using a
lightweight and flexible approach to reduce the visible complexity of software
projects. We introduce the SPACE (Semantic Process- and Artifact-oriented
Collaboration Environment) concept, which describes working processes and an
associated approach. These models are integrated semantically, thereby enabling
various kinds of analytic techniques, and thus making it easier to cope with the
complexity of processes. Pre-defined templates can be configured to actual
working processes and artifacts exchanged in such processes. In this paper, we
adapt SPACE to the software engineering domain by using the domain-specific
Software Organization Platform (SOP). In this context, the templates contain
process and artifact descriptions of software process models, such as V-Model,
RUP, or agile development.

Published in: Business, Technology
  • Be the first to comment

Supporting Software Development Teams with a Semantic Process- and Artifact-oriented Collaboration Environment

  1. 1. Supporting Software Development Teams with a Semantic Process- and Artifact-oriented Collaboration Environment <ul><li>Sebastian Weber </li></ul><ul><li>(sebastian.weber@iese.fraunhofer.de) </li></ul><ul><li>Andreas Emrich, Jörg Broschart, Eric Ras, </li></ul><ul><li>Özgür Ünalan </li></ul><ul><li>SOFTEAM </li></ul><ul><li>2009 Kaiserslautern, March 3rd 2009 </li></ul>
  2. 2. Motivation <ul><li>Many software projects are late, over budget, or fail due to complexity </li></ul><ul><li>Complexity results from </li></ul><ul><ul><li>Distributed development settings </li></ul></ul><ul><ul><li>Different stakeholders involved </li></ul></ul><ul><li>Core (i.e., creating artifacts) and context activities </li></ul><ul><li>Context activities (CA): </li></ul><ul><ul><li>Ratio of CA continuously increasing </li></ul></ul><ul><ul><li>Mastering CAs is key factor for success </li></ul></ul><ul><ul><li>Especially SMEs not acquainted with CAs </li></ul></ul><ul><ul><li>CAs often skipped by SMEs </li></ul></ul>Source: Standish Group, 2007
  3. 3. Research Questions <ul><li>How do we support SMEs with regards to mastering context activities? </li></ul><ul><li>They need to establish a process- and technique-specific knowledge </li></ul><ul><li>How do we get SMEs to follow certain process models? </li></ul><ul><li>And how do we support them handling the overall complexity arising from software development? </li></ul><ul><li>Our approach: SPACE (Semantic Process- and Artifact-oriented Collaboration Environment) </li></ul>
  4. 4. SPACE (Semantic Process- & Artifact-oriented Collaboration Environm.) <ul><li>SE research has proposed many SE models </li></ul><ul><li>Practice shows that SMEs often assume effort for modeling & tailoring high </li></ul><ul><li>Often follow their own “chaotic” process </li></ul><ul><li>Solution approach: SPACE </li></ul><ul><ul><li>Supports flexible process & artifact models </li></ul></ul><ul><ul><li>Models describe overall processes from different perspectives </li></ul></ul><ul><li>Apply to software domain: Software Organization Platform (SOP) </li></ul>
  5. 5. Correlation between SPACE and SOP <ul><li>SPACE is domain and scenario independent </li></ul><ul><ul><li>Meta-model infrastructure </li></ul></ul><ul><ul><li>Creation / execution of process & artifact models from different perspectives </li></ul></ul><ul><ul><li>Pro-active information delivery (PID) </li></ul></ul><ul><li>SOP aims at supporting software teams </li></ul><ul><ul><li>Lifecycle Artifact & Process Management </li></ul></ul><ul><ul><li>Knowledge Management </li></ul></ul><ul><ul><li>Stakeholder Collaboration </li></ul></ul>
  6. 6. Mockup of SOP 2.0 Artifact Model Editor
  7. 7. Correlation between SPACE, SOP, and SOP 2.0
  8. 8. SPACE Process Model <ul><li>Basis for both modeling and execution platforms </li></ul><ul><li>Supports collaborative modeling and execution of processes  “prosumer” idea </li></ul><ul><li>Soft and flexible processes allow the user to diverge from the modeled process </li></ul><ul><li>Semantic relationships between processes and artifacts allow for traceability </li></ul>
  9. 9. SPACE Process Model (cont.) <ul><li>Personalized views enable roles to have minimal but sufficient view on processes </li></ul><ul><li>Perspectives reduce complexity and improve reusability and modularity </li></ul><ul><li>Consistency checks help to evaluate whether working-process conforms to modeled-process  chances to improve processes </li></ul>
  10. 10. SPACE Artifact Model <ul><li>Artifact models are associated with process models or activities </li></ul><ul><li>Define the different artifact types that are transformed throughout process execution </li></ul><ul><li>Internal artifact structure consists of attributes representing data or relations </li></ul><ul><li>Transformation of artifact descriptions and relations on the meta-level into templates </li></ul><ul><li>Pro-active information delivery (PID) </li></ul>
  11. 11. SPACE Artifact Model (cont.)
  12. 12. Related Work <ul><li>Related standards and concepts: </li></ul><ul><ul><li>ARIS (Architecture of Integrated IS) </li></ul></ul><ul><ul><li> ARIS views show what kind of models could be considered within SPACE </li></ul></ul><ul><ul><li>SPEM (Software Process Engineering Metamodel) </li></ul></ul><ul><ul><li> Standardized language may reduce high coordination efforts </li></ul></ul>
  13. 13. Related Work (cont.) <ul><li>SE process software </li></ul><ul><ul><li>V-Modell XT Projektassistent </li></ul></ul><ul><ul><li> Might be to static for agile scenarios </li></ul></ul><ul><ul><li>IRIS Process Author </li></ul></ul><ul><ul><li> Similar to SOP 2.0 but lacks deeper semantic support </li></ul></ul><ul><li>SE phase specific software </li></ul><ul><ul><li>NetBeans collaboration project </li></ul></ul><ul><ul><li>Teamserver </li></ul></ul><ul><li>SEE </li></ul><ul><ul><li>Jazz Project + Rational product portfolio </li></ul></ul><ul><ul><li> Restriction to tool family, no transparent semantic connection between artifacts of different tools </li></ul></ul>
  14. 14. Feedback is Welcome <ul><li>Is this approach feasible/meaningful for establishing process knowledge within SMEs? </li></ul><ul><li>Why are “traditional” wikis only rarely used for SE activities by the target group? </li></ul>
  15. 15. <ul><li>Backup </li></ul>
  16. 16. SOP 2.0 Architecture <ul><li>MediaWiki and Semantic MediaWiki as collaborative platform </li></ul><ul><li>Adobe Flex GUI </li></ul><ul><li>Hybrid extension mechanism </li></ul><ul><li>SOP 2.0-own hook mechanism allows sophisticated integration </li></ul>
  17. 17. SOP 2.0 GUI Menu bar Accordion Tabbed Editor View
  18. 18. Example

×