7 citations found. Retrieving documents...
C Seaman, Qualitative Methods in Empirical Studies of Software Engineering, IEEE Transactions on Software Engineering ,25.4, July/August 1999, pages 557-572

 Home/Search   Document Details and Download   Summary   Related Articles   Check  

This paper is cited in the following contexts:
Qualitative Studies of XP in a Medium Sized Business - Gittins, Hope, Williams (2001)   (1 citation)  (Correct)

....benefits of a flexible management approach to XP methodology, and records the experiences of both management and staff, as initial practices matured and new practices emerged. Keywords: Extreme Programming, Qualitative methods, Software Methodology. 1 RELATED WORK Previous qualitative research [11] [12] 3] has concentrated on non judgmental reporting, with the intent of provoking discussion within the culture being studied by providing observations and evidence, collaborators deciding for themselves whether any changes were required. This fieldwork study follows the format of [6] ....

....collaborators deciding for themselves whether any changes were required. This fieldwork study follows the format of [6] whereby the researcher is immersed for a period in the software developer team; thereby the active researcher becomes instrumental in the development and improvement of XP. In [11] Seaman describes an empirical study that addresses the issue of communication among members of a software development organization. Sharp et al. 12] use combined ethnography and discourse analysis, to discover implicit assumptions, values and beliefs in a software management system. In [3] ....

Seaman, C.B. `Qualitative methods in empirical studies of software engineering', IEEE Trnsctns on Software Engineering, Vol.25 (4):557-572 Jul/Aug 99.


Quantitative and Qualitative Methods in Process Improvement - And Product Quality (2001)   (Correct)

....the results are more subjective and more difficult to process, and thus require more work during analysis. But they give richer and more informative results. Quantitative methods can be applied to theory generation and improvement, problem identification and removal, and cross case analysis [8]. They are necessary in the situations when better reality or system understanding is required, and complexity, not reductions and quick processing are a value. Searching for reasons of things and non technical aspects are good fields for them. Although they seem to be intuitive their application ....

Seaman C. B., "Qualitative methods in Empirical Studies of Software Engineering.", Transactions on Software Engineering volume 25, 1999, pages 557-572.


Interpretation of Qualitative Data in XP using Fuzzy Logic - Hope, Gittins (2002)   (Correct)

....in Soft Computing Ludmila Kuncheva [5] introduces the fundamentals of fuzzy set recognition and fuzzy set theory. Ludmila defines fuzzy if then classifiers and in a chapter on multiple classifier combination discusses fuzzy and non fuzzy models for fusion selection. Carolyn B. Seaman [1] describes an empirical study that addresses the issue of communication among members of a software development organization. In recent papers Carolyn has presented several qualitative methods for data collection and analyses, and described them in terms of how they might be incorporated into ....

Seaman, C.B. `Qualitative methods in empirical studies of software engineering', IEEE Transactions on Software Engineering, Vol.25 (4):557- 572, July/August 1999.


EPiCS: Evolution Phenomenology in Component-intensive Software - Lehman, Ramil (2001)   (2 citations)  (Correct)

....[fesbp] hypotheses of interest [leh00d] Once collected, such data will provide a basis for both black box [e.g. cle93,han96] and white box modelling. As in FEAST, system dynamics process modelling [for61,sen90] will be applied to the latter wherever possible. The second, qualitative data [sea99], will include results of interviewing key personnel, natural language descriptions of the evolution processes from their inception, etc. Such data will provide a set of qualitative descriptions of the phenomena and facilitate the identification of evolutionary mechanisms and of the major drivers ....

SEAMAN, C: 'Qualitative Methods in Empirical Studies of Software Engineering', IEEE Trans. on Softw. Eng, vol. 25, n. 4, July/Aug. 1999, pp. 557 - 572


An Experience Management System for a Software.. - Seaman, Mendona.. (1999)   (3 citations)  Self-citation (Seaman)   (Correct)

....it was essential to get user feedback on the basic paradigms we had chosen before we proceeded further. 5. 1 Study design The interface evaluation study was based on qualitative methods [10] The importance of such methods in validating software engineering technology is discussed by Seaman in [12]. The goals of the interface evaluation study were: 1. To evaluate the current set of attributes (in both the projects and documents taxonomies) in terms of completeness, usefulness, and clarity. 2. To evaluate the visual query search and retrieval interface in terms of usefulness, usability, ....

Seaman, C.B. Qualitative Methods in Empirical Studies of Software Engineering. IEEE Transactions on Software Engineering, 25(4):557-572, July/August 1999.


A Prototype Experience Management System for a Software.. - Neto, Seaman, al. (2001)   (2 citations)  Self-citation (Seaman)   (Correct)

No context found.

Seaman, C.B. Qualitative Methods in Empirical Studies of Software Engineering. IEEE Transactions on Software Engineering, 25(4):557-572, July/August 1999.


An Initial Study of Attitudes to CASE Tools in Agile - Cowling Karn Dept   (Correct)

No context found.

C Seaman, Qualitative Methods in Empirical Studies of Software Engineering, IEEE Transactions on Software Engineering ,25.4, July/August 1999, pages 557-572

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC