Software Publico / articles

Commit 6e93ca71c600909cd3caa0cf7c8fa24f91acb3e0

Authored by Rafael Reggiani Manzo 2017-07-05 18:39:59 -0300

Exists in master and in 3 other branches

[icse2018] Add first introduction draft

It needs to be reviewed by a second pair of eyes.

Missing a review on similar work.

Showing 3 changed files with 45 additions and 68 deletions Show diff stats

icse2018/bibliography.bib

Wrap text Diff comments View file @6e93ca7

1		-@ARTICLE{bowman:reasoning,
2		- author = {Bowman, Mic and Debray, Saumya K. and Peterson, Larry L.},
3		- title = {Reasoning About Naming Systems},
4		- journal = {ACM Trans. Program. Lang. Syst.},
5		- volume = {15},
6		- number = {5},
7		- pages = {795-825},
8		- month = {November},
9		- year = {1993},
10		- doi = {10.1145/161468.161471},
	1	+@article{anthopoulos2016government,
	2	+ title={Why e-government projects fail? An analysis of the Healthcare. gov website},
	3	+ author={Anthopoulos, Leonidas and Reddick, Christopher G and Giannakidou, Irene and Mavridis, Nikolaos},
	4	+ journal={Government Information Quarterly},
	5	+ volume={33},
	6	+ number={1},
	7	+ pages={161--173},
	8	+ year={2016},
	9	+ publisher={Elsevier}
11	10	}
12	11
13		-@ARTICLE{braams:babel,
14		- author = {Braams, Johannes},
15		- title = {Babel, a Multilingual Style-Option System for Use with LaTeX's Standard Document Styles},
16		- journal = {TUGboat},
17		- volume = {12},
18		- number = {2},
19		- pages = {291-301},
20		- month = {June},
21		- year = {1991},
	12	+@article{goldfinch2007pessimism,
	13	+ ISSN={00333352, 15406210},
	14	+ URL={http://www.jstor.org/stable/4624644},
	15	+ abstract={The majority of information systems developments are unsuccessful. The larger the development, the more likely it will be unsuccessful. Despite the persistence of this problem for decades and the expenditure of vast sums of money, computer failure has received surprisingly little attention in the public administration literature. This article outlines the problems of enthusiasm and the problems of control, as well as the overwhelming complexity, that make the failure of large developments almost inevitable. Rather than the positive view found in much of the public administration literature, the author suggests a pessimism when it comes to information systems development. Aims for information technology should be modest ones, and in many cases, the risks, uncertainties, and probability of failure mean that new investments in technology are not justified. The author argues for a public official as a recalcitrant, suspicious, and skeptical adopter of IT.},
	16	+ author={Shaun Goldfinch},
	17	+ journal={Public Administration Review},
	18	+ number={5},
	19	+ pages={917-929},
	20	+ publisher={[American Society for Public Administration, Wiley]},
	21	+ title={Pessimism, Computer Failure, and Information Systems Development in the Public Sector},
	22	+ volume={67},
	23	+ year={2007}
22	24	}
23	25
24		-@INPROCEEDINGS{clark:pct,
25		- AUTHOR = "Malcolm Clark",
26		- TITLE = "Post Congress Tristesse",
27		- BOOKTITLE = "TeX90 Conference Proceedings",
28		- PAGES = "84-89",
29		- ORGANIZATION = "TeX Users Group",
30		- MONTH = "March",
31		- YEAR = {1991} }
32		-
33		-@ARTICLE{herlihy:methodology,
34		- author = {Herlihy, Maurice},
35		- title = {A Methodology for Implementing Highly Concurrent Data Objects},
36		- journal = {ACM Trans. Program. Lang. Syst.},
37		- volume = {15},
38		- number = {5},
39		- pages = {745-770},
40		- month = {November},
41		- year = {1993},
42		- doi = {10.1145/161468.161469},
43		-}
44		-
45		-@BOOK{Lamport:LaTeX,
46		- AUTHOR = "Leslie Lamport",
47		- TITLE = "LaTeX User's Guide and Document Reference Manual",
48		- PUBLISHER = "Addison-Wesley Publishing Company",
49		- ADDRESS = "Reading, Massachusetts",
50		- YEAR = "1986" }
51		-
52		-@BOOK{salas:calculus,
53		- AUTHOR = "S.L. Salas and Einar Hille",
54		- TITLE = "Calculus: One and Several Variable",
55		- PUBLISHER = "John Wiley and Sons",
56		- ADDRESS = "New York",
57		- YEAR = "1978" }
58		-
59		-@MANUAL{Fear05,
60		- title = {Publication quality tables in {\LaTeX}},
61		- author = {Simon Fear},
62		- month = {April},
63		- year = 2005,
64		- note = {\url{http://www.ctan.org/pkg/booktabs}}
	26	+@article{mcilroy1968software,
	27	+ title={Software Engineering: Report on a conference sponsored by the NATO Science Committee},
	28	+ author={McIlroy, MD},
	29	+ year={1968},
	30	+ publisher={NATO Scientific Affairs Division}
65	31	}
66	32
67		-@Manual{Amsthm15,
68		- title = {Using the amsthm Package},
69		- organization = {American Mathematical Society},
70		- month = {April},
71		- year = 2015,
72		- note = {\url{http://www.ctan.org/pkg/amsthm}}
	33	+@article{dybaa2008empirical,
	34	+ title={Empirical studies of agile software development: A systematic review},
	35	+ author={Dyb{\aa}, Tore and Dings{\o}yr, Torgeir},
	36	+ journal={Information and software technology},
	37	+ volume={50},
	38	+ number={9},
	39	+ pages={833--859},
	40	+ year={2008},
	41	+ publisher={Elsevier}
73	42	}
74		-
...	...

icse2018/content/01-introduction.tex

Wrap text Diff comments View file @6e93ca7

1	1	\section{Introduction}
2		-Same SPB introduction from OSS articles plus a related work review and brief relevance to this article?
	2	+%Same SPB introduction from OSS articles plus a related work review and brief relevance to this article?
	3	+
	4	+The difficulty of writing software is an old subject on computer science that dates back to 1968 \cite{mcilroy1968software} when the term software crisis has been first used. This refers to recurrent problems on software development such as exceeding time and budget expectations, inefficiency, low quality and maintainability among many others that usually culminate in the software not meeting the user expectations or not even being delivered.
	5	+
	6	+Specially in the public sector the pessimism and failure ratios are even deeper than in the general industry \cite{goldfinch2007pessimism,anthopoulos2016government}. This is due governments having rigid processes and organizational structures for which is hard to apply techniques that have been achieving success on software development in the private sector such as the broad spectrum of agile methods \cite{dybaa2008empirical}.
	7	+
	8	+Here we report our experiences on a three years long development project with the Brazilian government in a scenario with low budget, high political instability and a mostly unexperienced team formed mostly by students but, despite all that risks and many others, has been kept under active development for three years and since its final delivery one year ago has been maintained online.
	9	+
	10	+We will give a more detailed context at section \ref{sec:problem_context} for later detailing which development practices were adopted during the project and what were the observed results for each one. This report is not expect to be the final recipe on working with public sector software development, but has the objective to report on which techniques have been successful, what adaptations were necessary and what has failed as means to provide other developers a reference when they meet similar situations.
...	...

icse2018/content/02-context.tex

Wrap text Diff comments View file @6e93ca7

1	1	\section{Problem Context}
	2	+\label{sec:problem_context}
2	3	The public sector employees are chosen by a contest process that values most their knowledge of specific development processes and management techniques. Thus this generates a strong culture around documents, formal meetings and processes, long term planning and closed contracts among other practices that go against agile values.
...	...