Titlebook: Domain Knowledge for Interactive System Design; Alaistair Sutcliffe,David Benyon,Frans Assche (Ind Book 1996 IFIP International Federation

postpartum

书目名称Domain Knowledge for Interactive System Design影响因子(影响力)




书目名称Domain Knowledge for Interactive System Design影响因子(影响力)学科排名




书目名称Domain Knowledge for Interactive System Design网络公开度




书目名称Domain Knowledge for Interactive System Design网络公开度学科排名




书目名称Domain Knowledge for Interactive System Design被引频次




书目名称Domain Knowledge for Interactive System Design被引频次学科排名




书目名称Domain Knowledge for Interactive System Design年度引用




书目名称Domain Knowledge for Interactive System Design年度引用学科排名




书目名称Domain Knowledge for Interactive System Design读者反馈




书目名称Domain Knowledge for Interactive System Design读者反馈学科排名

aquatic

VAN

消散

EXUDE

Unknown Values and Stakeholdersn from a semiformal to a formal specification and further on to design is achieved as all the description techniques rely on the same conceptual model to describe the functional and non-functional aspects of the system. Thus, the system is thoroughly documented at different description levels, each

Blatant

Social Disparities in Health and Health Cared possible extensions are discussed. By introducing the domain context, several additional models of the work task by the user, as well as the designer, occur. If the dynamic iterative system development process is regarded, additional models and dynamic changes in the models over time can be traced

Blatant

Urban Structure in Hot Arid Environmentsow an integrated model supports problem diagnosis is presented. The problem diagnosed is a discrepancy between the worksystem operator’s mental categorisations of domain objects (aircraft), and the actual state of the domain objects being categorised. The model supports reasoning about the consequen

扫兴

Seeding, Evolutionary Growth and Reseeding: Constructing, Capturing and Evolving Knowledge in Domainterative process of collaboration among multiple stakeholders. Requirements cannot be completely specified before system development occurs. Our research focuses on the following claims: software systems (I) must evolve because they cannot be completely designed prior to use, (2) must evolve to some

易发怒

Diary of a domain analyst: a domain analysis case-study from avionicsis, such as domain structuring, modelling complex forms of commonality and optionality, rationale capture and multiple-perspectives. Adopting an analysis method provided some lessons and an introduction to more complex issues. However, we feel that our experience points to a number of areas which ar

截断

Modelling domain knowledge with nd to . descriptions are shown by means of a real-world example. The main features of the .-centred approach are compared with the corresponding features of two popular structural and behavioural modelling approaches.