Software Requirements Engineering Lecture Notes, Slides of Software Engineering

Download Software Requirements Engineering Lecture Notes and more Slides Software Engineering in PDF only on Docsity! SOFTWARE REQUIREMENTS ENGINEERING LECTURE# 4,5 TEAM SKILL2: UNDERSTANDING USERAND STAKEHOLDER NEEDS REQUIREMENTS ELICITATION TECHNIQUES l – & ll Engr. Dr. M SohailApr, 2022 Software Requirement Engineering What is software requirement Functional vs Non Functional Requirement Source of Requirement Goal of Software Development Root Causes of Project Success and Failures The High Cost of Requirement Errors The Problem Domain The solution domain Problem Domain defines the environment where the solution will come to work, the solution domain defines the abstract environment where the solution is developed ❑ The Challenge of Requirement Elicitation ❑ Requirement Elicitation ❑ The Requirement Elicitation Process ❑ Requirement Elicitation Techniques- l ✓ Interviews ✓ Questionnaires ✓ Background Reading ✓ Introspection ✓ Social Analysis TEAM SKILL 2: UNDERSTANDING USER AND STAKEHOLDER NEEDS REQUIREMENTS ELICITATION TECHNIQUES l –& ll The Challenge of Requirements Elicitation ❑ Requirements elicitation is complicated by three endemic syndromes. ✓ The "Yes, But" syndrome ❑ users' reactions after checking software for the first time are: "Wow, this is so cool; we can really use this, and so on ….. "Yes, but, hmmmm, now that I see it, what about this . . . ? Wouldn't it be nice if . . . ? And soon . . . ” ✓ The "Undiscovered Ruins“ Syndrome ❑ In many ways, the search for requirements is like a search for undiscovered ruins: the more you find, the more you know remain. ✓ The "User and the Developer" syndrome ❑ The third syndrome arises from the communication gap between the user and the developer. 4 Requirements Elicitation In requirements engineering, requirements elicitation is the practice of researching and discovering the requirements of a system from users, customers, and other stakeholders. ✓ Interviews ✓ Questionnaires ✓ Background Reading ✓ Introspection ✓ Social Analysis ✓ Requirements Workshops ✓ Brainstorming and Idea Reduction ✓ Story Boarding ✓ Role Playing ✓ Prototyping ✓ Requirements Reuse Requirements Elicitation Techniques8 Social Analysis ❑ Social Analysis is a process of collecting requirements ❑ By observing the people doing their normal work. ❑ Find the additional requirements needed by the user, when the user is unable to explain ❑ This Social Analysis can be of the following types:: ✓ Passive Observation ✓ Active Observation ✓ Explanatory Observation 25 Social Analysis Passive Observation ❑ This social analysis is carried out without the direct involvement of the observer in the society ❑ The observation of the peoples work is carried out by recording using videotapes, video cameras and surveillance cameras 26 Active Observation ❑ The observer provides the domain knowledge and encourage to the userand makesthe report of the requirements of the people by observing their day to day work with the product. 10 Closed Interviews ❑ In closed interviews the requirements engineer prepares some predefined questions and he tries to get the answers for these questions from the stakeholder’s Open Interviews ❑ In open interviews the requirements engineer does not prepares any predefined questions and he tries to get the information from the stakeholder’s in open discussions Closed ended Question ❑ A close-ended question is one that demands mostly a brief yes or no response. [3,4] Open ended Question ❑ An open-ended question is one that demands far more than a brief yes or no response. [3,4] Interviews Questionnaires [1] 15 ❑ Questionnaires are one easy methods of gathering requirements from a large number of people only in lesser time. ❑ Can be manual (paper form) or electronic (soft form distributed through e-mail) ❑ The resultsextracted fromthe Questionnairesmust be clearly analyzed ❑ A well designed and effective questionnaire canbe usedto decide the actual user requirements, objectives and the constraints The steps involved in designing and conducting the Questionnaires are:: ❑ The purpose of survey should be clearly defined ❑ The Sampling group (respondents of the survey) should be decided ❑ Clearly state Why the respondent was selected for questionnaire ❑ Provide clear instructions on how to complete the questionnaire ❑ Avoid asking two questions in one ❑ Do not ask questions that give cluesto answers ❑ Keep the questionnaire brief and user friendly ❑ Preparing and developing the questionnaire ❑ Conducting the questionnaire process ❑ Gathering and analyzing the results 16 The Designing of Questionnaires ▪Introspection is an easier technique to apply Introspection can be very inaccurate at times because Requirement Analyst imagines what is required rather than asking from the user what he requires This technique is unlikely to reflect the stakeholder’s goals and actual user experiences 24 Introspection SOFTWARE REQUIREMENTS ENGINEERING LECTURE# 5 TEAM SKILL2: UNDERSTANDING USERAND STAKEHOLDERNEEDS REQUIREMENT ELICITATION TECHNIQUES-II Engr. Dr. M. SohailApril 2022 ✓ Interviews ✓ Questionnaires ✓ Background Reading ✓ Introspection ✓ Social Analysis ✓ Requirements Workshops ✓ Brainstorming and Idea Reduction ✓ Story Boarding ✓ Role Playing ✓ Prototyping ✓ Requirements Reuse Requirements Elicitation Techniques4 Preparing for the Workshop ❑ “Proper preparation for the workshop is critical to success.” ❑ Sending the workshop concept to stakeholders ❑ Ensuring the Participation of the Right Stakeholders ❑ Preparation of Warm-up materials ✓ Project-specific information ✓ Out-of-box thinking preparation 10 Warm-up Materials 11 ❑ Project-specific information ✓ This might include drafts of requirements documents, suggested features, copies of interviews, analyst's reports on industry trends, bug reports from existing system, new management orders, new marketing data, and so on. Although it's important not to bury the attendees in data, it's also important to make sure they have the right data. ❑ Out-of-box thinking preparation ✓ Simply bring your insights on the features of this new project, and be prepared to think 'out of the box.'" Role of the Facilitator 12 ❑ Establish professional and objective tone to the meeting. ❑ Start and stop the meeting on time. ❑ Establish and enforce the “rules” for the meeting. ❑ Introduce the goals and agenda for the meeting. ❑ Manage the meeting and keep the team “on track.” ❑ Facilitate a process of decision and consensus making, but avoid participating in the content. ❑ Make certain that all stakeholders participate and have their input heard. ❑ Control troublesome or unproductive behavior. ❑ Every team member is allotted a certain time interval to express and explain their ideas ❑ Notepads are provided to all members to write their ideas and suggestions ❑ The team of Brainstorming will then decides the best idea by voting from the group and that idea is selected as the solution to the issue discussed in the conference Brainstorming 18 It can be used to help ✓ elicit new ideas and features for the application ✓ define what project or problem to work on, ✓ to diagnose problems , ✓ Identify possible solutions and resistance to proposed solutions 19 Brainstorming Roles 20 There are three roles for participants in a brainstorming session: ❑ Leader -This person needs to be a good listener, ❑ Scribe -This person needs to write down EVERY idea – clearly and where everyone in the group can see them and ❑ Teammember - participants 23 ❑ First, all the significant stakeholders gather in one room, and supplies are distributed. ❑ Then the facilitator explains the rules for brainstorming. Rules of Brainstorming Ascending to a level markedly higher than the usual Change Or Modify ❑ The facilitator also explains the the process. Theobjective of following questions are a few ways to state the objective. ✓ What features would you like to seein the product? ✓ What servicesshould the product provide? ✓ What opportunities are wemissingin the product or the market? ❑ After stating the objective of the process, the facilitator asks participants to share their ideas aloud and to write them down, one per sheet Objective of Brainstorming 24 HOW ….. ? Idea Generation25 1. Pruning Ideas 2. Grouping Ideas 3. Defining Features 4. Prioritizing Ideas Idea Reduction 29 1. Pruning Ideas ❑ The first step is to "prune" those ideas that are not worthy of further investment by the group. ❑ The facilitator asks the participants whether each idea is worthy of further consideration and then removes an invalid idea. Idea Reduction 30 2. Grouping Ideas ❑ It may be helpful during this process to start grouping similar ideas ❑ Name the groupsof related ideas. For example, ✓ New features ✓ Performance issues ✓ Enhancements to current features ✓ User interface and ease-of-use issues Idea Reduction 33 4. Prioritizing Ideas ❑ Cumulative Voting: The Hundred- Dollar Test ✓ Each member of the group is given $100 in “idea money” to be spent on purchasing ideas. ✓ All participants write down on a piece of paper how much they are willing to spend on each idea they think is important (i.e., they vote with dollars). ✓ Theresults are tabulated and the ideas are ordered based onthe results. Idea Reduction 34 4. Prioritizing Ideas ❑ "Critical, Important, Useful” Categorization ✓ Each participant is given a number of votes equal to the number of ideas, one-third of which are “critical”, one-third are “important” and one-third are “useful”. ✓ Each participant assigns one vote (critical, important, or useful) to each of the ideas. ✓ The results are tabulated where a critical vote is given a value of 9, an important vote is 3, and a useful vote is a 1. ✓ The ideas are prioritized based on the computed sums. Idea Reduction References 29 1. Managing Software Requirements: A Use Case Approach, Second Edition By Dean Leffingwell, Don Widrig, Addison- Wesley http://www.redstarresume.com/content/cms/Open-Ended+and+Closed- Ended+Job+Interview+Questions/3525/ http://blog.simplyhired.co.uk/2011/07/open-vs-closed-tips-for-answering-these- interview-questions.html http://examples.yourdictionary.com/examples/examples-of-open-ended-and-closed- ended-questions.html 2. 3. 4.