Case studies in just-in-time requirements analysis
- Neil A. Ernst, G. Murphy
- Computer ScienceSecond IEEE International Workshop on Empirical…
- 1 September 2012
The need to better understand the context of practice, and the need to properly evaluate the cost of decisions is seen, and a taxonomy is proposed to describe the requirements practices spectrum from fully formal to just-in-time.
Measure it? Manage it? Ignore it? software practitioners and technical debt
- Neil A. Ernst, S. Bellomo, I. Ozkaya, R. Nord, I. Gorton
- Computer ScienceESEC/SIGSOFT FSE
- 30 August 2015
It is found that architectural decisions are the most important source of technical debt, and while respondents believe the metaphor is itself important for communication, existing tools are not currently helpful in managing the details.
Jambalaya: Interactive visualization to enhance ontology authoring and knowledge acquisition in Protégé
- M. Storey, M. Musen, Natasha Noy
- Computer Science
- 2001
This paper describes the integration of an interactive visualization user interface with a knowledge management tool called Protege. Protege is a general-purpose tool that allows domain experts to…
Alternative splicing, methylation state, and expression profile of tropomyosin-related kinase B in the frontal cortex of suicide completers.
- C. Ernst, V. Deleva, G. Turecki
- BiologyArchives of General Psychiatry
- 2009
A reduction of TrkB.T1 expression in the frontal cortex of a subpopulation of suicide completers is associated with the methylation state of the promoter region, and this downregulation is mediated by an epigenetic process.
Automated topic naming to support cross-project analysis of software maintenance activities
- Abram Hindle, Neil A. Ernst, M. Godfrey, J. Mylopoulos
- Computer ScienceIEEE Working Conference on Mining Software…
- 21 May 2011
The case studies show that labelled topic extraction can produce appropriate, context-sensitive labels relevant to these projects, which provides fresh insight into their evolving software development activities.
Techne: Towards a New Generation of Requirements Modeling Languages with Goals, Preferences, and Inconsistency Handling
- Ivan Jureta, Alexander Borgida, Neil A. Ernst, J. Mylopoulos
- Computer ScienceIEEE International Requirements Engineering…
- 27 September 2010
The need for Techne is motivated, the need is introduced through examples, and its formalization is sketched.
A Framework for Empirical Evaluation of Model Comprehensibility
- Jorge Aranda, Neil A. Ernst, Jennifer Horkoff, S. Easterbrook
- Computer ScienceInternational Workshop on Modeling in Software…
- 20 May 2007
A flexible framework to evaluate the comprehensibility of model representations that is grounded on the underlying theory of the language to be evaluated, and on theoretical frameworks in cognitive science is presented.
The who, what, how of software engineering research: a socio-technical framework
- M. Storey, Neil A. Ernst, Courtney Williams, Eirini Kalliamvakou
- Computer ScienceEmpirical Software Engineering
- 30 May 2019
A socio-technical research framework is developed to capture the main beneficiary of a research study, the main type of research contribution produced, and the research strategies used in the study ( how the authors methodologically approach delivering relevant results given the who and what of their studies).
Toward Design Decisions to Enable Deployability: Empirical Study of Three Projects Reaching for the Continuous Delivery Holy Grail
- S. Bellomo, Neil A. Ernst, R. Nord, R. Kazman
- Computer Science44th Annual IEEE/IFIP International Conference on…
- 23 June 2014
This paper interviews three project teams striving to practicing continuous delivery and summarizes the deploy ability goals, design decisions, and deploy ability tactics derived from the interviews in the form of an initial draft version hierarchical deploy ability tactic tree.
On the role of requirements in understanding and managing technical debt
- Neil A. Ernst
- Computer ScienceThird International Workshop on Managing…
- 5 June 2012
This position paper defines technical debt in requirements as the distance between the implementation and the actual state of the world, and highlights how a requirements modeling tool, RE-KOMBINE, makes requirements, domain constraints and implementation first-class concerns.
...
...