@article{knodel08, title = {An experiment on the role of graphical elements in architecture visualization}, author = {Jens Knodel and Dirk Muthig and Matthias Naab}, journal = {Empirical Software Engineering}, note = {online only currently}, pages = {--}, year = 2008, url = {http://dx.doi.org/10.1007/s10664-008-9069-5}, description = {SpringerLink - Journal Article}, abstract = {Abstract  The evolution and maintenance of large-scale software systems requires first an understanding of its architecture before delving into lower-level details. Tools facilitating the architecture comprehension tasks by visualization provide different setsof configurable, graphical elements to present information to their users. We conducted a controlled experiment that exemplifiesthe critical role of such graphical elements when aiming at understanding the architecture. In our setting, a different configurationof graphical elements had significant influence on program comprehension tasks. In particular, a 63% gain in effectivenessin architectural analysis tasks was achieved simply by changing the configuration of the graphical elements of the same tool.Based on the results, we claim that significant effort should be spent on the configuration of architecture visualizationtools and that configurability should be a requirement for such tools.}, biburl = {http://www.bibsonomy.org/bibtex/2e846680d25043dcbe72580caad7991ce/neilernst}, keywords = {empirical visualization should-read} } @article{dzidek08tose, title = {A Realistic Empirical Evaluation of the Costs and Benefits of UML in Software Maintenance}, author = {James Dzidek and Erik Arisholm and Lionel Claude Briand}, journal = {IEEE Transaction on Software Engineering}, month = {June}, year = 2008, url = {http://doi.ieeecomputersociety.org/10.1109/TSE.2008.15}, abstract = {The Unified Modeling Language (UML) is the de facto standard for object-oriented software analysis and design modeling. However, few empirical studies exist that investigate the costs and evaluate the benefits of using UML in realistic contexts. Such studies are needed so that the software industry can make informed decisions regarding the extent to which they should adopt UML in their development practices. This is the first controlled experiment that investigates the costs of maintaining and the benefits of using UML documentation during the maintenance and evolution of a real, non-trivial system, using professional developers as subjects, working with a state-of-the-art UML tool during an extended period of time. The subjects in the control group had no UML documentation. In this experiment, the subjects in the UML group had on average a practically and statistically significant 54\% increase in the functional correctness of changes (p=0.03), an insignificant 7\% overall improvement in design quality (p=0.22) - though a much larger improvement was observed on the first change task (56\%) - at the expense of an insignificant 14\% increase in development time caused by the overhead of updating the UML documentation (p=0.35).}, biburl = {http://www.bibsonomy.org/bibtex/2861899e60b360da6a2fad6dcd36f2d99/neilernst}, keywords = {empirical uml should-read} } @article{pikkarainen08ese, title = {The impact of agile practices on communication in software development}, author = {M. Pikkarainen and J. Haikara and O. Salo and P. Abrahamsson and J. Still}, editor = {Tore Dybå}, journal = {Empirical Software Engineering}, year = 2008, url = {http://dx.doi.org/10.1007/s10664-008-9065-9}, abstract = {Agile software development practices such as eXtreme Programming (XP) and SCRUM have increasingly been adopted to respond to the challenges of volatile business environments, where the markets and technologies evolve rapidly and present the unexpected.In spite of the encouraging results so far, little is known about how agile practices affect communication. This article presents the results from a study which examined the impact of XP and SCRUM practices on communication within software development teams and within the focal organization. The research was carried out as a case study in F-Secure where two agile software development projects were compared from the communication perspective. The goal of the study is to increase the understanding of communication in the context of agile software development: internally among the developers and project leaders and in the interface between the development team and stakeholders (i.e. customers, testers, other development teams). The study shows that agile practices improve both informal and formal communication. However, it further indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication. The study highlights the fact that hurdles and improvements in the communication process can both affect the feature requirements and task subtask dependencies as described in coordination theory. While the use of SCRUM and some XP practices facilitate team and organizational communication of the dependencies between product features and working tasks,the use of agile practices requires that the team and organization use also additional plan-driven practices to ensure the efficiency of external communication between all the actors of software development.}, biburl = {http://www.bibsonomy.org/bibtex/251b0ef8b8fa0269a593e586063d5048f/neilernst}, keywords = {should-read empirical software agile} } @article{gregor06, title = {The nature of theory in information systems}, author = {Shirley Gregor}, journal = {MIS Quarterly}, month = {September}, note = {referenced in Hannay et al}, number = 3, pages = {491-506}, volume = 30, year = 2006, url = {http://www.google.ca/url?sa=t&ct=res&cd=1&url=http%3A%2F%2Fwww.ise.canberra.edu.au%2Fun6797%2FShirley%2FNo6-MISQ%2520RA%25203828%2520theory%2520sub%25205%2520260705%2520final-f.pdf&ei=l3H-R7emCZfIhgK7892rCg&usg=AFQjCNHMTOpHZL4j5b_gnMHfCnPz8kpuYA&sig2=eGeqZsqZ-yfWjO0OXW_Gqw}, abstract = {he aim of this research essay is to examine the structural nature of theory in information systems. Despite the importance of theory, questions relating to its form and structure are neglected in comparison with questions relating to epistemology. The essay addresses issues of causality, explanation, prediction, and generalization that underlie an understanding of theory. A taxonomy is proposed that classifies information systems theories with respect to the manner in which four central goals are addressed: analysis, explanation, prediction, and prescription. Five interrelated types of theory are distinguished: (1) theory for analyzing, (2) theory for explaining, (3) theory for predicting, (4) theory for explaining and predicting, and (5) theory for design and action. Examples illustrate the nature of each theory type. The applicability of the taxonomy is demonstrated by classifying a sample of journal articles. The paper contributes by showing that multiple views of theory exist and by exposing the assumptions underlying different viewpoints. In addition, it is suggested that the type of theory under development can influence the choice of an epistemological approach. Support is given for the legitimacy and value of each theory type. The building of integrated bodies of theory that encompass all theory types is advocated.}, biburl = {http://www.bibsonomy.org/bibtex/268d4e2635a5ab93fdd83f021c799251f/neilernst}, keywords = {empirical theory information system} } @article{hannay08tose, title = {The Role of Deliberate Artificial Design Elements in Software Engineering Experiments}, author = {Jo Hannay and Magne Jørgensen}, journal = {IEEE Transactions on Software Engineering}, month = {March/April}, number = 2, pages = {242-259}, volume = 34, year = 2008, url = {http://dx.doi.org/10.1109/TSE.2008.13}, abstract = {Increased realism in software engineering experiments is often promoted as an important means to increase generalizability and industrial relevance. In this context, artificiality, e.g., the use of constructed tasks in place of realistic tasks, is seen as a threat. In this article, we examine the opposite view, that deliberately introduced artificial design elements may increase knowledge gain and enhance both generalizability and relevance. In the first part of the article, we identify and evaluate arguments and examples in favor of, and against, deliberately introducing artificiality into software engineering experiments. In the second part of the article, we summarize a content analysis of articles reporting software engineering experiments published over the ten-year period 1993-2002. The analysis reveals a striving for realism and external validity, but little awareness of for what and when, various degrees of artificiality and realism are appropriate. We conclude that an increased awareness and deliberation in these respects is essential. However, arguments in favor of artificial design elements should not be used to justify studies that are badly designed or that have research questions of low relevance.}, biburl = {http://www.bibsonomy.org/bibtex/20dc83b000a90b34f14dc2800e754d88b/neilernst}, keywords = {empirical software} } @techreport{ellis08, title = {Business Analysis Benchmark: The Impact of Business Requirements on the Success of Technology Projects}, author = {Keith Ellis}, institution = {IAG Consulting, Inc.}, month = {January}, year = 2008, url = {http://www.iag.biz/images/resources/iag%20business%20analysis%20benchmark%20-%20full%20report.pdf}, abstract = {The Business Analysis Benchmark report presents the findings from surveys of over 100 companies and definitive statistics on the importance and impact of business requirements on enterprise success with technology projects. The survey focused on larger companies and looked at development projects in excess of $250,000 where significant new functionality was delivered to the organization. The average project size was $3 million. The study has three major sections: 1. Assessing the Impact of Poor Business Requirements on Companies: Quantifying the cost of poor requirements. 2. Diagnosing Requirements Failure: A benchmark of the current capability of organizations in doing business requirements and an assessment of the underlying causes of poor quality requirements 3. Tactics for Tomorrow: Specific steps to make immediate organizational improvement. In addition to this full text report, these sections and an executive summary have also been published as stand-alone white papers for ease of use. All can be accessed from www.iag.biz . The study provides a comprehensive analysis of business requirements quality in the industry and the levers for making effective change. The following issues are addressed in the report: the financial impact of poor quality requirements; the information needed to identify underlying issues critical to success; and, the data necessary to target specific recommendations designed to yield performance improvement.}, biburl = {http://www.bibsonomy.org/bibtex/242329b68e7667a9894629c1dbf843ba4/neilernst}, keywords = {requirements empirical} } @book{easterbrook07empirical, title = {Selecting Empirical Methods for Software Engineering Research}, author = {Steve Easterbrook and Janice Singer and Margaret-Anne Storey and Daniela Damian}, booktitle = {Guide to Advanced Empirical Software Engineering}, editor = {F. Shull and J. Singer}, publisher = {Springer}, year = 2007, abstract = {Selecting a research method for empirical software engineering research is problematic because the benefits and challenges to using each method are not yet well catalogued. Therefore, this chapter describes a number of empirical methods available. It examines the goals of each and analyzes the types of questions each best addresses. Theoretical stances behind the methods, practical considerations in the application of the methods and data collection are also briefly reviewed. Taken together, this information provides a suitable basis for both understanding and selecting from the variety of methods applicable to empirical software engineering.}, biburl = {http://www.bibsonomy.org/bibtex/2a029b7aa2273424b4606723f672d4da6/neilernst}, keywords = {empirical research software methods} } @inproceedings{jorgensen04, title = {Generalization and Theory-Building in Software Engineering Research}, author = {M. Jørgensen and D. I. K. Sjøberg}, booktitle = {Empirical Assessment in Software Engineering (EASE2004)}, pages = {29--36}, year = 2004, url = {http://simula.no/research/engineering/publications/SE.5.Joergensen.2004.c/downloadPdfFile}, isbn = {0 86341 435 4}, totalpages = {7}, abstract = {The main purpose of this paper is to generate discussions which may improve how we conduct empirical software engineering studies. Our position is that statistical hypothesis testing plays a too large role in empirical software engineering studies. The problems of applying statistical hypothesis testing in empirical software engineering studies is illustrated by the finding: Only 3 out of the 47 studies in Journal of Empirical Software Engineering which applied statistical hypothesis testing, were able to base their statistical testing on well-defined populations and random samples from those populations. The frequent use of statistical hypothesis testing may also have had unwanted consequences on the study designs, e.g., it may have contributed to a too low focus on theory building. We outline several steps we believe are useful for a change in focus from ?generalizing from a random sample to a larger population? to ?generalizing across populations through theory-building?}, biburl = {http://www.bibsonomy.org/bibtex/2b02e8bee2917e9da9871404be59dca4c/neilernst}, keywords = {methods empirical research} } @article{hoorn07, title = {Requirements change: Fears dictate the must haves; desires the won't haves}, author = {Johan F. Hoorn and Elly A. Konijn and Hans van Vliet and Gerrit van der Veer}, booktitle = {Selected papers from the 1st International Workshop on Requirements Engineering for Business Need and IT Alignment (REBNITA'05), 1st International Workshop on Requirements Engineering for Business Need and IT Alignment}, journal = {Journal of Systems and Software}, month = {#mar#}, number = 3, pages = {328--355}, volume = 80, year = 2007, url = {http://www.sciencedirect.com/science/article/B6V0N-4K71638-1/2/650a0f72639b8b73407464b7e470c91c}, abstract = {We attempt to contribute to a general theory of requirements change from a goal-oriented and viewpoints-driven angle. To practitioners, this knowledge is relevant to anticipate changes in certain types of requirements, which may shorten the project's timeline, reduce costs, and increase product quality. Initially, we followed the common assumptions that what should be on a system is demanded by goals to achieve and what should not be on a system is demanded by goal states to avoid. However, requirements engineering of a diversity of systems (capacity and warehouse management, COTS PCs, and a Braille mouse) revealed that must requirements are predicted by goals to avoid (!) and won't requirements by goals to approach (!). Expectations about the positive or negative impact (valence) of requirements on goals played a moderating role. We unfold the gradual discovery of this "goals-to-requirements chiasm" (CHI-effect or [chi]-effect), claiming that variability in agreement to positive or negative requirements is predicted by goals of opposite polarity. We found that whether the [chi]-effect occurred or not, depended on the alignment of stakeholder viewpoints on goals and requirements. Comments from practitioners are included.}, biburl = {http://www.bibsonomy.org/bibtex/22796b941aecba62f3f86013eb3d37b23/neilernst}, keywords = {engineering RE validation Viewpoints software Requirements questionnaires change Structured Empirical Goal-driven} } @article{cao08, title = {Agile Requirements Engineering Practices: An Empirical Study}, author = {Lan Cao and Balasubramaniam Ramesh}, journal = {IEEE Software}, month = {Jan}, number = 1, pages = {60-67}, volume = 25, year = 2008, url = {http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=4420053&arnumber=4420071}, issn = {0740-7459}, doi = {10.1109/MS.2008.1}, abstract = {An analysis of data from 16 software development organizations reveals seven agile requirements-engineering practices, along with their benefits and challenges. These practices include face-to-face communication, iterative RE, extreme prioritization, constant planning, prototyping, test-driven development, and reviews and tests.}, biburl = {http://www.bibsonomy.org/bibtex/25abe9de6a4e1f928528988b841ef0854/neilernst}, keywords = {agile empirical requirements} } @article{basili84, title = {Software Errors and Complexity: An Empirical Investigation.}, author = {Victor R. Basili and Barry T. Perricone}, journal = {Commun. ACM}, number = 1, pages = {42-52}, volume = 27, year = 1984, url = {http://portal.acm.org/citation.cfm?id=2085}, description = {dblp}, biburl = {http://www.bibsonomy.org/bibtex/22dc15c7416ad9dcde10ea1e949787c90/neilernst}, keywords = {software could-read complexity empirical} } @inproceedings{moody04, title = {Cognitive Load Effects on End User Understanding of Conceptual Models: An Experimental Analysis}, address = {Budapest, Hungary}, author = {D. L. Moody}, booktitle = {Proceedings of 8th East European Conference on Advances in Databases and Information Systems, ADBIS 2004}, editor = {G. Gottlob and A. A. Benczur and J. Demetrovics}, month = {September}, note = {22-25}, pages = {129-143}, publisher = {Springer}, series = {LNCS 3255}, year = 2004, url = {http://dblp.uni-trier.de/db/conf/adbis/adbis2004.html#Moody04}, abstract = {According to Cognitive Load Theory (CLT), presenting information in a way that cognitive load falls within the limitations of working memory can improve speed and accuracy of understanding, and facilitate deep understanding of information content. This paper describes a laboratory experiment which investigates the effects of reducing cognitive load on end user understanding of conceptual models. Participants were all naïve users, and were given a data model consisting of almost a hundred entities, which corresponds to the average-sized data model encountered in practice. One group was given the model in standard Entity Relationship (ER) form and the other was given the same model organised into cognitively manageable ldquochunksrdquo. The reduced cognitive load representation was found to improve comprehension and verification accuracy by more than 50%, though conflicting results were found for time taken. The practical significance of this research is that it shows that managing cognitive load can improve end user understanding of conceptual models, which will help reduce requirements errors. The theoretical significance is that it provides a theoretical insight into the effects of complexity on understanding of conceptual models, which have previously been unexplored. The research findings have important design implications for all conceptual modelling notations.}, biburl = {http://www.bibsonomy.org/bibtex/2c1b7167c531c08540cd3335f9e1b4eb5/neilernst}, keywords = {cognition empirical analysis} } @inproceedings{herbsleb93, title = {Preserving knowledge in design projects: what designers need to know}, address = {Amsterdam, The Netherlands}, author = {James D. Herbsleb and Eiji Kuwana}, booktitle = {CHI '93: Conference on Human factors in computing systems}, pages = {7--14}, publisher = {ACM}, year = 1993, url = {http://portal.acm.org/citation.cfm?doid=169059.169061}, location = {}, isbn = {0-89791-575-5}, doi = {http://doi.acm.org/10.1145/169059.169061}, description = {Preserving knowledge in design projects}, abstract = {In order to inform the design of technology support and new procedural methods for software design, we analyzed the content of real design meetings in three organizations, focusing in particular on the questions the designers ask of each other. We found that most questions concerned the project requirements, particularly what the software was supposed to do and, somewhat less frequently, scenarios of use. Questions about functions to be performed by software components and how these functions were to be realized were also fairly frequent. Rationales for design decisions were seldom asked about. The implications of this research for design tools and methods are discussed.}, biburl = {http://www.bibsonomy.org/bibtex/22fb0378edddebb0c737393f4808e9ab9/neilernst}, keywords = {design empirical} } @article{kitchenham02, title = {Preliminary Guidelines for Empirical Research in Software Engineering}, author = {B. A. Kitchenham and S. L. Pfleeger and D. C. Hoaglin and J. Rosenberg}, journal = {IEEE Trans. Software Engineering}, month = {August}, number = 8, pages = {721 -- 734}, publisher = { IEEE Computer Society Press }, volume = 28, year = 2002, url = {http://www.ehealthinformation.ca/documents/1082.pdf}, description = {software evolution bibliography}, abstract = {Empirical software engineering research needs research guidelines to improve the research and reporting processes. We propose a preliminary set of research guidelines aimed at stimulating discussion among software researchers. They are based on a review of research guidelines developed for medical researchers and on our own experience in doing and reviewing software engineering research. The guidelines are intended to assist researchers, reviewers and meta-analysts in designing, conducting and evaluating empirical studies. Editorial boards of software engineering journals may wish to use our recommendations as a basis for developing guidelines for reviewers and for framing policies for dealing with the design, data collection and analysis and reporting of empirical studies.}, biburl = {http://www.bibsonomy.org/bibtex/2bce139322738527bd4620e058f776779/neilernst}, keywords = {should-read empirical engineering software} } @article{mockus02, title = {Two case studies of open source software development: Apache and Mozilla}, address = {New York, NY, USA}, author = {Audris Mockus and Roy T. Fielding and James Herbsleb}, journal = {ACM Trans. Softw. Eng. Methodol.}, number = 3, pages = {309--346}, publisher = {ACM}, volume = 11, year = 2002, url = {http://portal.acm.org/citation.cfm?id=567795}, issn = {1049-331X}, doi = {http://doi.acm.org/10.1145/567793.567795}, description = {Two case studies of open source software development}, abstract = {According to its proponents, open source style software development has the capacity to compete successfully, and perhaps in many cases displace, traditional commercial development methods. In order to begin investigating such claims, we examine data from two major open source projects, the Apache web server and the Mozilla browser. By using email archives of source code change history and problem reports we quantify aspects of developer participation, core team size, code ownership, productivity, defect density, and problem resolution intervals for these OSS projects. We develop several hypotheses by comparing the Apache project with several commercial projects. We then test and refine several of these hypotheses, based on an analysis of Mozilla data. We conclude with thoughts about the prospects for high-performance commercial/open source process hybrids.}, biburl = {http://www.bibsonomy.org/bibtex/26abef027845ec3a3f9043d3fe3c46aa6/neilernst}, keywords = {empirical software open-source} } @article{jamieson06, title = {Ecological Interface Design for Petrochemical Process Control: An Empirical Assessment}, author = {Greg A. Jamieson}, editor = {Donald E. Brown}, journal = {IEEE Transactions on Systems, Man and Cybernetics (A)}, number = 6, volume = 37, year = 2007, description = {citeulike sept 4}, abstract = {Abnormal events in process plants cost the petrochemical industry billions of dollars annually. In part, these events are difficult to deal with because contemporary interfaces do not adequately inform operators about the state of the process. Laboratory simulator studies have shown that, in comparison with contemporary interfaces, ecological interfaces can lead to more effective monitoring and control behavior. However, ecological interfaces derived from work domain analysis differ from more traditional human-centered interfaces that use a task analysis to inform the design process. A companion article demonstrated an ecological interface that integrates both work domain- and task-based information. A second ecological interface was created, drawing exclusively from the traditional work domain-based analysis. Professional operators used the novel interfaces in an industrial petrochemical process simulator to monitor for, diagnose, and respond to several types of process events. Operators using the work domain-based ecological interface completed trials more quickly and executed fewer control actions than their counterparts using the current process displays. Operators using the integrated (task- and work domain-based) ecological interface also showed these benefits, and in addition, showed improved fault diagnoses and better performance scores. The implications and opportunities for introducing ecological interfaces into industrial control rooms are discussed.}, biburl = {http://www.bibsonomy.org/bibtex/292ab3f9130d247f8147a7514470d368f/neilernst}, keywords = {cwa empirical hci complexity} } @article{viller00, title = {Ethnographically informed analysis for software engineers}, author = {Stephen Viller and Ian Sommerville}, journal = {International Journal of Human-Computer Studies}, month = {#jul#}, number = 1, pages = {169--196}, volume = 53, year = 2000, url = {http://www.sciencedirect.com/science/article/B6WGR-45FC2BT-11/2/a05dc8100479ce15a72336abe6235d97}, description = {ScienceDirect - International Journal of Human-Computer Studies : Ethnographically informed analysis for software engineers}, abstract = {It is increasingly recognized that human, social, and political factors have a significant impact on software systems design. To address this, ethnographic studies of work have been used to inform the systems design process, especially in cooperative work settings where systems support several users working together. Based on our experience of these studies, we have investigated the integration of social analysis into the systems design process by developing an integrated approach to social and object-oriented analysis. New methods are unlikely to be adopted in industry unless they can be integrated with existing practice. Our approach, called Coherence, addresses this issue by helping identify use cases, generating initial use case models, and by using the Unified Modelling Language (UML) to represent social aspects of work that may have an impact on the design of computer-based systems. Coherence is the fusion of two well-established strands of research on ethnographically informed design and viewpoint-oriented requirements engineering. This paper introduces Coherence, and focuses on the support provided for social analysis. We have identified three social viewpoints, namely a distributed coordination viewpoint, a plans and procedures viewpoint and an awareness of work viewpoint. Coherence is illustrated using a case study based on an air traffic control system.}, biburl = {http://www.bibsonomy.org/bibtex/2ffc244d4ad457448d6ce93c85b4aac26/neilernst}, keywords = {ethnography empirical seminal} } @article{robinson07, title = {Ethnographically-informed empirical studies of software practice}, author = {Hugh Robinson and Judith Segal and Helen Sharp}, booktitle = {Qualitative Software Engineering Research}, journal = {Information and Software Technology}, month = {jun}, number = 6, pages = {540--551}, volume = 49, year = 2007, url = {http://www.sciencedirect.com/science/article/B6V0B-4N1JRNN-6/2/e1f0049e9be25bef553a44e3badc3ccd}, description = {ScienceDirect - Information and Software Technology : Ethnographically-informed empirical studies of software practice}, abstract = {Over the past decade we have performed a sustained series of qualitative studies of software development practice, focusing on social factors. Using an ethnographically-informed approach, we have addressed four areas of software practice: software quality management systems, the emergence of object technology, professional end user development and agile development. Several issues have arisen from this experience, including the nature of research questions that such studies can address, the advantages and challenges associated with being a member of the community under study, and how to maintain rigour in data collection. In this paper, we will draw on our studies to illustrate our approach and to discuss these and other issues.}, biburl = {http://www.bibsonomy.org/bibtex/286e8be5a722e3e0d96a18d6d8c4323db/neilernst}, keywords = {software empirical} } @inproceedings{roblesGMA06, title = {Mining large software compilations over time: another perspective of software evolution.}, author = {Gregorio Robles and Jesús M. González-Barahona and Martin Michlmayr and Juan Jose Amor}, booktitle = {MSR}, crossref = {conf/msr/2006}, editor = {Stephan Diehl and Harald Gall and Ahmed E. Hassan}, pages = {3-9}, publisher = {ACM}, year = 2006, url = {http://dblp.uni-trier.de/db/conf/msr/msr2006.html#RoblesGMA06}, ee = {http://doi.acm.org/10.1145/1137983.1137986}, isbn = {1-59593-397-2}, date = {2006-09-21}, description = {dblp}, biburl = {http://www.bibsonomy.org/bibtex/267d07d73645607b29c87df869cf89d0b/neilernst}, keywords = {empirical software} } @article{pettigrew90, title = {Longitudinal Field Research on Change: Theory and Practice}, author = {Andrew M. Pettigrew}, journal = {Organization Science Special Issue: Longitudinal Field Research Methods for Studying Processes of Organizational Change }, number = 3, pages = {267-292}, volume = 1, year = 1990, url = {http://links.jstor.org/sici?sici=1047-7039(1990)1%3A3%3C267%3ALFROCT%3E2.0.CO%3B2-8#abstract}, description = {Longitudinal Field Research Methods for Studying Processes of Organizational Change (1990), pp.}, abstract = {This paper reveals the author's theory of method for conducting longitudinal field research on change. The paper also discusses a range of practical problems in carrying out time-series research in organisational settings. The practical problems include dealing with time in longitudinal research; issues of site selection; choices about data collection and degrees of involvement; the importance of clarifying research outputs, audience, and presentation; and finally handling problems of complexity and simplicity associated with longitudinal comparative case study research on change. The paper concludes by discussing some ethical issues of longitudinal research field research, and managing a community of researchers}, biburl = {http://www.bibsonomy.org/bibtex/2bd96936ccaca966387d831acaaa27e44/neilernst}, keywords = {change empirical seminal} }