Đơn giản chỉ cần JavaScript bởi Kevin Yank và Cameron Adams. Trích đoạn đóng gói Tóm tắt Nội dung, Thông tin về các Tác giả và SitePoint, lục, Lời nói đầu, ba chương của cuốn sách, và chỉ số. Chúng tôi hy vọng bạn tìm thấy thông tin | 28 4 s Process analysis and modelling 675 Interviews with the people involved in the process are more open ended than questionnaires. You start with a prepared script of questions but adapt these according to the responses that you get from different people. If you give participants an opportunity to discuss issues more widely you may find that the process participants talk about process problems the ways that the process is changed in practice etc. Ethnographic analysis is more likely to discover the true process used. However it is a prolonged activity that can last several months. It relies on external observation of the process as it is being enacted. To do a complete analysis you have to be involved from the initial stages of a project through to product delivery and maintenance. For large projects this could take several years so it is clearly impractical in those situations. Ethnographic analysis therefore is most useful when an in-depth understanding of process fragments is required. You carry out a smaller-scale study focusing on process details. Process models are simplified views of software processes that show the activities and outputs of the process. The process models used in this book present a high-level view of the processes concerned. At this abstract level these processes are the same in many organisations. However these generic models have different instantiations in different companies depending on the type of software being developed and the organisational environment. Detailed process models are not usually the same across organisations. Abstract or generic process models are a useful basis for discussing processes. However they do not include enough information for process analysis and improvement. Process improvement needs information about activities deliverables people communications schedules and other organisational processes that affect the software development process. Figure explains what might be included in a detailed process
