Titlebook: Rationale-Based Software Engineering; Janet E. Burge,John M. Carroll,Ivan Mistrik Book 2008 Springer-Verlag Berlin Heidelberg 2008 Design

Asphyxia

書目名稱Rationale-Based Software Engineering影響因子(影響力)




書目名稱Rationale-Based Software Engineering影響因子(影響力)學(xué)科排名




書目名稱Rationale-Based Software Engineering網(wǎng)絡(luò)公開度




書目名稱Rationale-Based Software Engineering網(wǎng)絡(luò)公開度學(xué)科排名




書目名稱Rationale-Based Software Engineering被引頻次




書目名稱Rationale-Based Software Engineering被引頻次學(xué)科排名




書目名稱Rationale-Based Software Engineering年度引用




書目名稱Rationale-Based Software Engineering年度引用學(xué)科排名




書目名稱Rationale-Based Software Engineering讀者反饋




書目名稱Rationale-Based Software Engineering讀者反饋學(xué)科排名

nutrients

Mhc-Molecule

開花期女

Evaluationviding a process for analyzing use scenarios via Scenario-Claims Analysis (SCA) (Carroll and Rosson 1992; Carroll 2002). In this chapter, we discuss a number of approaches for using rationale to evaluate the alternatives to assist with decision-making and also how SCA supports usability evaluation.

Flatter

nt the decision-making process itself, can best be documented as the rationale for the system, which will reveal not only what was done during development but the reasons behind the choices made and alternatives considered and rejected. This information becomes increasingly critical as software deve

忙碌

What is Rationale and Why Does It Matter?sses and failures of the past. It can facilitate coordination and collaboration within development teams, aid in identification and analysis of requirements, as well as design, testing and maintenance. It can even help users to understand the systems they use.

Thyroid-Gland

Learning from Rationale Research in Other Domains All of this work provides potentially valuable lessons for SE researchers and developers. This chapter will look at some examples of this work that could have important implications for rationale research in SE.

反復(fù)拉緊

Rationale and Software Maintenancehanges might be needed during maintenance if design goals change and help the maintainer avoid repeating earlier mistakes by explicitly documenting alternatives that were tried earlier that did not work. In this chapter we will look at these and other ways that rationale can assist with software maintenance.

Definitive

Book 2008best be documented as the rationale for the system, which will reveal not only what was done during development but the reasons behind the choices made and alternatives considered and rejected. This information becomes increasingly critical as software development becomes more distributed and encomp

偶然