Software Process
ICS 225
Spring 2002		 <your project's name>

Project Title:

 

Team Members:

 

Abstract:

 

Introduction and Overview:

What is <your OSSD process/project> and why doe it need to be understood through an empirically grounded study?

Why is understanding <your OSSD process/project> important, an original research contribution, and a contribution to OSSD work practices?

Does existing knowledge of modern software engineering tools, techniques, and concepts already explain everything important to know about <your OSSD process/project>?

In any of the following sections, include examples of screenshots (and optionally, live Web links to relevant Web pages for <your OSSD process/project>) to help present or reveal what participants in <your OSSD process/project> actually see and interact with as their OSSD workspace or workplace.

Provide an overview of the sections that follow.
 

Problem Domain Characterization:

Mozilla/NetBeans/Apache

Classic software engineering view or characterization of <your OSSD process/project>
 

Process Modeling and Visualization:

Software production architecture for <your OSSD process/project>

Agent Roles

Role description or skill requirements, role hierarchy
 

Tools and Network Infrastructure

Tool description and network infrastructure requirements, tool hierarchy
 

Artifacts

Artifact description and (re)presentation requirements, artifact hierarchy
 

Processes

Processs description, process hierarchy

Rich Picture for <your OSSD process/project>

Agent Roles, Agent Concerns (non-functional requirements),  Process links
 

Use Cases for <your OSSD process/project>

Use case per Process (Relation)

UC provide process sequencing (control flow), tool invocation, resources input/output along the way, pre-conditions, post-conditions (goals/outcomes), and anticipated breakdown and recovery situations
 

Formal Model of <your OSSD process/project>

 

<other PLC activity>:

TBD
 

Discussion:

 

Conclusions:

 

Acknowledgements:

 

References: (sample)

  1. S. Bendifallah and W. Scacchi, Work Structures and Shifts: An Empirical Analysis of Software Specification Teamwork, Proc. 11th. Intern. Conf. Software Engineering, IEEE Computer Society Press, Pittsburgh, PA. 260-270, (May 1989).
  2. A. Brown and G. Booch, Reusing Open Source Software and Practices: The Impact of Open Source on Commercial Vendors, Proc. 7th International Conference on Software Reuse, 123-136, Austin, TX, USA, April 15-19, 2002. Appears in, C. Gacek (Ed.), Software Reuse: Methods, Techniques, and Tools, LNCS 2319, Spring-Verlag, May 2002
  3. T. Halloran and W. Scherlis, High Quality and Open Source Software Practices, Proc. 2nd Workshop on Open Source Software Engineering, Orlando, FL, May 2002.
  4. A. Mockus and J. Herbsleb, Why not improve coordination in distributed software development by stealing good ideas from Open Source?, Proc. 2nd Workshop on Open Source Software Engineering, Orlando, FL, May 2002.
  5. P. Mi and W. Scacchi,  A Knowledge-Based Environment for Modeling and Simulating Software Engineering Processes, IEEE Trans. Data and Knowledge Engineering, 2(3):283-294, September 1990. Reprinted in Nikkei Artificial Intelligence, 20(1):176-191, January 1991, (in Japanese). Reprinted in Process-Centered Software Engineering Environments, P.K. Garg and M. Jazayeri (eds.), IEEE Computer Society, 119-130, 1996.
  6. P. Mi and W. Scacchi, Articulation: An Integrated Approach to the Diagnosis, Replanning, and Rescheduling of Software Process Failures, Proc. 8th. Knowledge-Based Software Engineering Conference, Chicago, IL, IEEE Computer Society, 77-85, 1993.
  7. P. Mi, M.J. Lee, and W. Scacchi,  Knowledge-Based Software Process Library for Process-Driven Software Development , Proc. 7th. Knowledge-Based Software Engineering Conf., Washington, DC, IEEE Computer Society, 122-131, September 1992.
  8. A. Monk and S. Howard,  The Rich Picture: A Tool for Reasoning about Work Context, Interactions , March-April 1998.
  9. J. Noll and W. Scacchi,  Supporting Software Development in Virtual Enterprises, Journal of Digital Information, 1(4), February 1999.
  10. J. Noll and W. Scacchi,  Specifying Process-Oriented Hypertext for Organizational Computing, J. Network and Computer Applications, 24(1):39-61, 2001.
  11. C.R. Reis and R.P.M. Fortes, An Overview of the Software Engineering Process and Tools in the Mozilla Project, Proc. Workshop on Open Source Software Development, Newcastle, UK, February 2002.
  12. W. Scacchi,  Understanding Software Process Redesign using Modeling, Analysis and Simulation, Software Process--Improvement and Practice, 5(2/3):183-195, 2000.
  13. W. Scacchi,  Process Models in Software Engineering, in J. Marciniak (ed.), Encyclopedia of Software Engineering (Second Edition), 993-1005, Wiley, New York, 2002.
  14. W. Scacchi,  Understanding the Requirements for Developing Open Source Software Systems, to appear in IEE Proceedings--Software, 2002.
  15. W. Scacchi and P. Mi, Process Life Cycle Engineering, Intern. J. Intelligent Systems in Accounting, Finance, and Management, 6(1):83-107, 1997.