Process Modeling Across the Web Information Infrastructure

1
Process Modeling Across the Web Information
Infrastructure

• Chris Jensen and Walt Scacchi
• Institute for Software Research
• School of Information and Computer Science
• University of California, Irvine
• cjensen, wscacchi_at_ics.uci.edu

2
ProSim 2003

• Discovering and modeling of open source software
  development processes
• Phase1 reference model
• Phase2 project history development in context
• Phase3 process-fragment mining
• relevancy issues
• Phase4 multi-technique process modeling, and
  simulated/remote process re-enactment
• Phase5 analysis

3
Rich Picture
Funds, support, Promote Java/Open source
Sun Microsystems
Download and use free software
Share knowledge and ensure all community issues
are addressed
Ensure that the netbeans community is being run
in a fair and open manner
Configure and maintain CVS
Community Manager
Start new release phase, propose schedule/plan
respond to tech issues, unanswered questions
Release Manager
make decisions for the community, on high level
download new release
The Board
Users
release proposal, release updates, branch for
current release, release post mortem, review
release candidates (2) decide final release
report bugs
grant access
CVS Manager
Mailing Lists
Manage website
Website
Tools
deploy builds
download development builds and test, release
Q-builds
SourceCast
CVS
IssueZilla
decide features for the project and merge
patches/bug fixes, create module web page
Site Administrator
select feature to develop, bug to fix, download
netbeans, commit code
QA Team
Produce Q- builds and ensure quality of the
software
Maintain a project/ module, manage a group of
developers
Contribute to community, meet time constraints
for the release
grant CVS commit privilege to developers
Maintainer
Developers/ Contributors
Link to all Use Cases
Links to all Agents
Link to Tools
4
ProSim 2004

• ProSim 2003 study addresses single case
  NetBeans.org
• Now reporting on what we have since discovered
  and modeled by examining multiple cases of OSSD
  processes in interrelated OSSD projects.
• NetBeans.org, Mozilla.org, Apache.org

5
ProSim 2004
6
Objects of Interaction

• Development artifacts (software informalisms)
• Protocols
• HTTP, RPCs
• Shared data formats
• HTML, XML, CGI
• Community infrastructure tools
• Defect repositories (e.g. Bugzilla),
  Collaborative development tools (e.g. WIKI, CVS,
  mail list managers)
• Product infrastructure
• Plugins, Modules

7
Direct Interaction
Tomcat
8
Indirect Interaction
9
Interaction Patterns

• These appear to be ad hoc, however patterns can
  be detected and include
• Integration of a tool or support for a technology
  created by another community
• Defect detection and reduction
• Organizations contribute defect reports/patches
  detected in another organization's tool or
  technology implementation
• Infrastructure evolution planning
• Researching contributing to discussions of
  future/changes in tools and technologies
• Discovery, assessment of effects on ones own
  community
• These interactions give rise to additional
  opportunities for coordination and conflict

10
Conclusions

• OSSD processes occur within and across multiple
  projects spanning the Internet infrastructure
• Multiple project/organizational interaction may
  be coordinative or conflictive
• Interaction is driven by ongoing synchronization
  and stabilization of objects of interaction
  across the Internet infrastructure
• Interaction patterns are emerging, detectable,
  modeled, and suitable for simulated re-enactment
• Modeling processes within and across multiple
  dependent projects is new, challenging, and
  important.

11
Mozilla
Provide Resource and Manpower
Collaborate and provide Mozilla working
environment
Help to prioritize checkin patches
Sheriff
Drivers
Developers (Module Owners, Module Peers)
Staff Staff Associates
Reviewing patch
Contact the hook and Monitor Build Status
Develop manage Mozilla
Provide code enhancements and bug fixes
Close Tree Approve Build
Fix bugserrors Coding Check-in CM
Code Development LXR, Gnu, Emacs
CM CVS, Tinderbox, Bonsai
Build Engineers
Ok given to Download Invite testers for smoketest
Close Tree Generate Build Approve Build
Mozilla Tools
Determine Compilation Problems
Smoke Test Coordinators
Communicate with Testers for smoke test
Communication Bugzilla, IRC, News Server,
Mozilla.org
QA Contacts Owners
Open Bugzilla Account Research Finding/Report
Perform bug triage Run test cases
Input Bug Report
ReviewerSuper Reviewers
Ensure Nightly build pass Smoke test
Review code
Volunteer Testers
Bugzilla Component Owners
Ensure high quality of enhancement and bug fixes
Open Bugzilla Account Research Finding/Report
Perform bug triage Run test cases
Input Bug Report
Acceptance assignment
Help to assign bugs
Help to reveal bugs
12
Apache
13
NetBeans