Titlebook: Managing Software Engineering Knowledge; Aybüke Aurum,Ross Jeffery,Meliha Handzic Book 2003 Springer-Verlag Berlin Heidelberg 2003 capabil

門牙

書目名稱Managing Software Engineering Knowledge影響因子(影響力)




書目名稱Managing Software Engineering Knowledge影響因子(影響力)學科排名




書目名稱Managing Software Engineering Knowledge網(wǎng)絡公開度




書目名稱Managing Software Engineering Knowledge網(wǎng)絡公開度學科排名




書目名稱Managing Software Engineering Knowledge被引頻次




書目名稱Managing Software Engineering Knowledge被引頻次學科排名




書目名稱Managing Software Engineering Knowledge年度引用




書目名稱Managing Software Engineering Knowledge年度引用學科排名




書目名稱Managing Software Engineering Knowledge讀者反饋




書目名稱Managing Software Engineering Knowledge讀者反饋學科排名

隼鷹

An Investigation into Software Development Process Knowledge knowledge. In order to provide a better understanding of the most serious software project risks and the interrelations among risks, we collected software project data from developers. This data includes information about senior management, customers and users, requirements, estimation and scheduli

MUT

Decrepit

implore

A Dynamic Model of Software Engineering Knowledge Creationng stability, they should focus on creating software engineering knowledge and mind sets that embrace environmental change. The model developed in this chapter supports this shift by directing attention to the need for ., ., and .. The key to successful knowledge creation is continuous and simultane

Valves

anarchist

Eliciting and Maintaining Knowledge for Requirements Evolutionwe focus on how to manage knowledge about a software system with respect to change, so that changes can be evaluated and realized with less effort and without reducing quality. We use a rationale-based approach for making explicit change knowledge and the knowledge activities that need to occur duri

syring

Emergent Knowledge in Web Developmentcteristics that lead to changes in the development approach. Among other factors, there is substantial volatility in clients’ articulation of their requirements, particularly as their understanding evolves of the way in which the systems under development might affect their client and stakeholder in

藕床生厭倦

Case-Based Reasoning and Software Engineeringith adaptation where necessary, to solve new problems. It is argued that CBR as a technology has a number of strengths, since it deals well with poorly understood problem domains, does not require explicit knowledge elicitation and supports collaboration with users. This chapter provides some genera

Melodrama

A Process for Identifying Relevant Information for a Repository: A Case Study for Testing Techniquesues, products, processes, tools, and so on). But how does one package each artifact so that the package contains the appropriate information to understand and use the artifact? What is the appropriate characterization schema? This chapter proposes an empirical and iterative process to identify the i