This document discusses requirements gathering for software development projects. It defines what requirements are, including business, functional, and technical requirements. It emphasizes the importance of gathering accurate and complete requirements through techniques like interviews, questionnaires, and prototyping. A good requirement is described as being complete, correct, clear, verifiable, necessary, feasible, prioritized, consistent, traceable, modular, and design-independent. The document provides an assignment with questions to help gather requirements for various goals and problems.

1. LEAN CANVAS
REQUIREMENT
GATHERING
HUMAN COMPUTER INTERACTION
AND

2. INDEX
1. Introduction
2. Definition
3. Gathering Requirements
4. Lean canvas
5. Workshops & Assignment

3. INTRODUCTION

4. Idea Design Process Result

6. SOFTWARE DEVELOPMENT
THE WATERFALL MODEL AGILE METHODS

7. DEFINITIONS

8. requirement
[ri-kwahyuh r-muh nt]
Noun
1.that which is required; a thing demanded or
obligatory:
One of the requirements of the job is accuracy.
2.an act or instance of requiring.
3.a need or necessity:
to meet the requirements of daily life.
re·quire·ment
http://dictionary.reference.com/

9. REQUIREMENTS
There are a number of types of requirements:
• Business Requirements- what is the business
need
• Functional Requirements- how should the
system meet the business requirement or user
requirement
• Technical Requirements- how should the
system technically meet the functional
requirement or system requirement

10. สิ่งที่ลูกค้าอยากได้
สิ่งที่ Creative
เข้าใจ
สิ่งที่ Programmer
เข้าใจ
Cr. FB ลูกค้าผู้น่ารัก

11. THE IMPORTANCE OF REQUIREMENTS
www.softwork.co.il

12. • Complete (express a whole idea or statement)
• Correct (technically and legally possible)
• Clear (unambiguous and not confusing)
• Verifiable (it can be determined that the system meets
the requirement)
• Necessary (should support one of the project goals)
• Feasible (can be accomplished within cost and
schedule)
• Prioritized (tracked according to business need levels)
• Consistent (not in conflict with other requirements)
• Traceable (uniquely identified and tracked)
• Modular (can be changed without excessive impact)
• Design-independent (do not pose specific solutions on
design)
A GOOD REQUIREMENT

13. REQUIREMENTS GATHERING

14. Requirements gathering is an essential part of any
project and project management. Understanding fully
what a project will deliver is critical to its success. This
may sound like common sense, but surprisingly it's an
area that is often given far too little attention.
By Duncan Haughey
Requirement gathering is often a challenging exercise
as you need to work with stakeholders who have day jobs
and competing demands. Often the business expect you
to create the requirements but without the business input
you will not create an end product which is fit for the
business purposes.
By Amy Slater
IT Programme Manager

16. GATHERING TECHNIQUES
1. One-on-one interviews
2. Group interviews
3. Facilitated sessions
4. Joint application development (JAD)
5. Questionnaires
6. Prototyping
7. Use cases
8. Following people around
9. Request for proposals (RFPs)
10.Brainstorming

18. LEAN CANVAS

21. WORKSHOP & ASSIGNMETS

22. Assignment
1. ทำอย่ำงไรให้แต่งตัวไม่เรียบร้อยมำเรียน แต่งตัวถูกระเบียบ
2. ทำอย่ำงไรให้คนอยำกมำบริจำคเลือด
3. ทำยังไงให้อยำกคนแข่งไตรกีฬำ กำรเตรียมควำมพร้อมสำหรับกำรไปแข่ง
ไตรกีฬำ
4. ทำยังไงให้คนอยำกทำควำมดี
5. ทำยังไงให้คนไม่ฆ่ำตัวตำย
6. ทำยังไงให้คนอยำกเข้ำวัด สวดมนต์ ทำบุญ ( ไม่ได้จำกัดศำสนำ)
7. ทำยังไงให้คนเก่งภำษำอังกฤษ
8. ทำยังไงให้คนไม่ชอบเล่นกีฬำ อยำกจะมำออกกำลังกำย
9. ทำยังไงให้คนหลับยำก นอนหลับง่ำย
10. ทำไงให้คนรู้จักประหยัดไฟประหยัดน้ำ