1 / 17

Vrije Universiteit Faculty of Sciences Department of Computer Science

Goals are personal, requirements business – the requirements analysis twist. Johan F. Hoorn and Evelien Kok. Vrije Universiteit Faculty of Sciences Department of Computer Science Section Information Management & Software Engineering

sumana
Download Presentation

Vrije Universiteit Faculty of Sciences Department of Computer Science

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Goals are personal, requirements business – the requirements analysis twist Johan F. Hoorn and Evelien Kok Vrije Universiteit Faculty of Sciences Department of Computer Science Section Information Management & Software Engineering Subsection Human Computer Interaction, Multimedia & Culture

  2. Contents • Status • Problem • Goal • Theory • Model • Field study • Results • Discussion • Questions M M I 9 9 0 0 9 Johan F. Hoorn, 2005

  3. Status • Postdoc project: 2001-Aug 2005 • Supervisors:Gerrit van der Veer and Hans van Vliet • Four international publications, three pending • Industries involved • Mens-Machine Interactie Johan F. Hoorn, 2005

  4. Problem • Requirements change through business model change • Example: goes from non-profit to commercially oriented organization Johan F. Hoorn, 2005

  5. Politics demands change Work process slow Work process must be fast Supporting IT can leave much to the user Supporting IT leaves little to the user (control!) Business model Non-profit? Serves society Not self supporting Commercial? Serves own good Makes money Johan F. Hoorn, 2005

  6. Supporting IT can leave much to the user Supporting IT leaves little to the user (control!) Business model Non-profit Commercial • Capacity • Management • System (CMS) • Action planning • Shifts (day, night, special) • Holidays http://www.brilmanbouw.nl/images/verbouwing-planbord2.JPG Johan F. Hoorn, 2005

  7. Goal • Pinpoint the factors that lead to a change request so to anticipate them during system design Johan F. Hoorn, 2005

  8. Theory Requirements change Stakeholders Client Management Workfloor vs. vs. Sources of conflict, regarding goals vs. Business goals Personal goals egotistic vs. altruistic egotistic vs. altruistic Event Johan F. Hoorn, 2005

  9. Model Agreed requirements unexplained change Hypothesis: Changes in the relevance of goals, goal orientation (ego vs. altru), and business or personal view, change the agreement to the requirements Relevance Goals egotistic personal Profit Quality Career Loyalty business altruistic Adapted from Hoorn & Van der Veer, 2003a; 2003b Johan F. Hoorn, 2005

  10. Field study • Ethnography, task analysis by Evelien, who works at Concern Information Management Police - Goals (business and personal in the flavors egotistic and altruistic), categorized for relevance (relevant vs. irrelevant) - Requirements on the CMS (must and won’t) Johan F. Hoorn, 2005

  11. Four groups of police officers (novice CMS users) rated agreement to goals and requirements, each from a different point of view: Group 1 – Business egotistic goals Group 2 – Business altruistic goals Group 3 – Personal egotistic goals Group 4 – Personal altruistic goals Johan F. Hoorn, 2005

  12. Example items: BE Relevant scale (#items= 12) I find it important that my corps spends more money on allocating personnel completely disagree disagree agree agree completely disagreea little a little agree 0 -------------- 1 -------------- 2 -------------- 3 -------------- 4--------------5 Requirements Must scale (#items= 12) Schedules are definite 48 hours in advance completely disagree disagree agree agree completely disagreea little a little agree 0 -------------- 1 -------------- 2 -------------- 3 -------------- 4--------------5 Johan F. Hoorn, 2005

  13. Results Scale reliabilities Questionnaire version PE PA BE BA Cronbach’s  (#)  (#)  (#)  (#) Relevant scale .71 (2) .86 (3) .84 (4) .83 (3) Irrelevant scale .83 (3) .78 (2) .77 (2) .77 (3) Requirements Must .98 (3) .67 (2) .74 (2) .67 (2) Requirements Won’t .86 (3) .81 (4) .78 (3) .80 (2) N=33 n=8 n=8 n=9 n=8 Johan F. Hoorn, 2005

  14. Egotistic vs. altruistic is insignificant! F(1,30)= 10.19, p= .003, ηp2= .25. Parameter coefficient= .91, t= 3.19, p< .004

  15. Discussion (1) When stakeholders expressed their agreement to the goals to achieve with the system, they did this from a personal point of view However, the focus switched to the point of view of the business when it came to expressing agreement to the system’s requirements that were gathered to serve these goals Johan F. Hoorn, 2005

  16. Requirements change! Discussion (2) Tricky bit in requirements engineering and task analysis: - You ask for their goals - You specify requirements to serve these goals - You go back to the workfloor - They agree more or less to what you propose - And then while using the system they start complaining that it does not serve them well Johan F. Hoorn, 2005

  17. Questions? Johan F. Hoorn, 2005

More Related