@article {895,
	title = {Multi-Modal Modeling, Analysis and Validation of Open Source Software Development Processes},
	journal = {Intern. J. Internet Technology and Web Engineering},
	volume = {1},
	number = {3},
	year = {2006},
	pages = {49-63},
	abstract = {Understanding the context, structure, activities, and content of software development processes found in practice has been and remains a challenging problem. In the world of free/open source software development, discovering and understanding what processes are used in particular projects is important in determining how they are similar to or different from those advocated by the software engineering community. Prior studies have revealed that development processes in F/OSSD projects are different in a number of ways. In this paper, we describe how a variety of modeling perspectives and techniques are used to elicit, analyze, and validate software development processes found in F/OSSD projects, with examples drawn from studies of the software requirements process found in the NetBeans.org project.},
	keywords = {empirical studies of software engineering, open source software development, process modeling, requirements processes, software process},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Scacchi-Jensen-Noll-Elliott-OSSC05.pdf},
	author = {Walt Scacchi and Chris Jensen and Noll, J. and Elliott, M.}
}
@conference {Twidale:2005:SBF:1062455.1062468,
	title = {Silver bullet or fool{\textquoteright}s gold: supporting usability in open source software development},
	booktitle = {Proceedings of the 27th international conference on Software engineering},
	series = {ICSE {\textquoteright}05},
	year = {2005},
	pages = {35{\textendash}35},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {At first glance it can look like Open Source Software development violates many, if not all, of the precepts of decades of careful research and teaching in Software Engineering. One could take a classic SE textbook and compare the activities elaborated and advocated in the various chapters with what is actually done in plain sight in the public logs of an OSS project in say SourceForge. For a Professor of Software Engineering this might make for rather depressing reading. Are the principles of SE being rendered obsolete? Has OSS really discovered Brooks{\textquoteright} Silver Bullet? Or is it just a flash in the pan or Fool{\textquoteright}s Gold.In this talk I will mainly look at one aspect of Open Source Development, the {\textquoteright}problem{\textquoteright} of creating usable interfaces, particularly for non-technical end-users. Any approach involves the challenge of how to coordinate distributed collaborative interface analysis and design, given that in conventional software development this is usually done in small teams and almost always face to face. Indeed all the methods in any HCI text just assume same-time same-place work and don{\textquoteright}t map to distributed work, let alone the looser mechanisms of OSS development. Instead what is needed is a form of participatory usability involving the coordination of end users and developers in a constantly evolving redesign process.},
	keywords = {course project, education, lifecycle model, pedagogical, software engineering education, software process},
	isbn = {1-58113-963-2},
	doi = {10.1145/1062455.1062468},
	url = {http://doi.acm.org/10.1145/1062455.1062468},
	author = {Twidale, Michael}
}
@article {capiluppi:23,
	title = {Improving comprehension and cooperation through code structure},
	journal = {IEE Seminar Digests},
	volume = {2004},
	number = {908},
	year = {2004},
	note = {"In this study we measured source code size in three different forms (LOCs, SLOCs, and Kbs of code)."

"Pilot Project: The ARLA System"
},
	pages = {23-28},
	publisher = {IEE},
	abstract = {Defining a relationship between a software system{\textquoteright}s architecture and the process{\textquoteright} efforts is one of the most fascinating questions of software engineering. Apparently, when a system{\textquoteright}s architecture is complex, the process to improve and evolve it will be more difficult. We try to tackle this question from a different point of view: given an open source system, in all the phases of its evolution, we focus on both the aspects of software developers, and the obtained software product. More we observe one of the possible architectures of this system, based on the tree structure derived from source components. First conclusions show that some patterns of tree evolution are recognizable: some branches may appear more promising than other, and are extensively evolved, while other remains in the same status for all the life cycle. More, when the tree structure reaches some status, the process of joining as a core developer seems to forestall. },
	keywords = {arla, code structure, contributors, developers, open source system, scm, software development, software engineering, software process, software product, software system architecture, source code, source components, tree evolution, tree structure},
	doi = {10.1049/ic:20040260},
	url = {http://link.aip.org/link/abstract/IEESEM/v2004/i908/p23/s1},
	attachments = {https://flosshub.org/sites/flosshub.org/files/capiluppi2004.pdf},
	author = {A. Capiluppi}
}
