Why an understanding of work context helps to identify the real stakeholder needs (beyond what they are telling). 5 reason ?

Step 2: Determine the work context Based on the identified domain, you should then determine the work context, which defines the work that you intend to study and the work's responsibilities. For example, let us assume that you are required to build a system to manage a library's collections and members. The domain of interest here is 'Library'. The work within the 'Library' domain may include acquisition, cataloguing, serials, Online Public Access Catalogue (OPAC), member management and circulation. Usually, a work exists to produce something such as data, documents or almost anything. In addition, things also move from one work to another. Based on this information, you can say that a simple library management system has the following work processes: Manage the process of purchasing library materials; Built catalogue of materials and manage the catalogue; Manage subscriptions of serials such as journals and magazines; Allow searching capability of library materials via OPAC; Allow member management capability (manage profile, register new member, bill member, block member, etc); and Allow circulation capability (check-in, check-out, reserve, and renew materials, etc). Step 3: Build a work context model Next, you can build a diagram called a work context model to show the work in its context. Figure 1.5 shows a sample work context model that depicts all the work involved in managing the library's collection and its members. With understanding and knowledge of the work, you may then decide how much of it you can automate (i.e. build a product to support that work). orders Purchase Request People Registration Suppliers people Invoice The work to manage a library's collection and members Subscription Circulation Magazine/ journal Materials details Images Catalogue materials Books OPAC Cataloque Figure 1.5: A sample work context model