Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (19)
Andere mochten auch
Andere mochten auch (20)
Ähnlich wie Requirements engineering
Ähnlich wie Requirements engineering (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Requirements engineering
- 1. Requirements Engineering For business analyst Doug Vucevic, P. Eng M. Eng
- 3. System Requirement Engineering Lifecycle
- 6. Top 10 Success Factors
- 8. Top 10 Proprieties of Challenged Projects
- 9. Proprieties of Challenged Projects
- 10. Top Ten Impaired Projects Factors
- 11. Proprieties of Impaired Projects
- 12. Requirements Elicitation Understanding Requirements © ISE Toronto
- 14. Outcome of good Elicitation
- 15. Outcome of Poor Elicitation
- 16. What is Facilitation? A highly structured, intensive workshop in which participants are guided by a skilled and impartial facilitation team to develop a high-quality, draft work product and/or deliverable.
- 49. What do all of these have in common?
Hinweis der Redaktion
- These are the five activities involved in sw req engineering.
- We have all been part of projects where developers say things like “When will marketing (or user) supply us with the requirements that we need. That way we can do what we like to do, code.” In the real world I have never seen this happen. In fact with experience I have found that this is undesirable. Rather a successful project will find a way for both users (marketing) and engineers to work together to elicit and manage requirements.
- Each of these is explained on subsequent slides. Don’t spend time on THIS one.
- Dilbert – “Work is very rewarding”
- Examples of context-free questions?
- These are on the course web site. Each section on slide has several questions under it in the document. Establish Customer or User Profile Name: Company: Industry: Job Title: What are your key responsibilities? What outputs do you produce? For Whom? How is success measured? Which problems interfere with your success? What, if any, trends make your job easier or more difficult? Assessing the Problem For which problems do you lack good solutions? What are they? (Hint: Keep asking, “Anything else?”) For each problem ask: Why does the problem exist? How do you solve it know? How would you like to solve it? Understanding the User Environment Who are the users? What is their educational background? What is their computer background? Are users experienced with this type of application? Which platforms are in use? What are your plans for future platforms? What are your expectations for usability for this type of product? What are your expectations for training time? What kinds of user help do you need? Recap the Understanding You have told me: (List customer described problems in your own words.) Analyst’s Inputs on Customer’s Problems (Validate or Invalidate assumptions) For each problem ask, Is this a real problem? What are the reasons for the problem? How do you currently solve the problem? How would you like to solve the problem? How would you rank solving these problems in comparison to others you’ve mentioned? Assessing Your Solution (if applicable) What if you could How would you rank the importance of these?
- What does this have to do with engineering? Everything. So far, the only creatures we have found to use as engineers are people. Same goes for marketing, testing, strategic planning, etc. The engineer’s tendency to shy away from actions needed to encourage, cajole, and motivate humans to be productive leads to unproductive meetings.
- Banning criticism and banning debate is not just an attempt to “be nice”. It is necessary to not squelch creative thinking.
- Weakness of Use Cases -- we miss the “ilities”, the quality attributes. Those must be addressed explicitly eventually.
- Out loud Envision actually using Multi-sensory involvement ??