دوره‌ی آموزشی روش کاربردی تحلیل نیازمندی‌های نرم‌افزار مروری بر مفاهیم مرتبط با نیازمندی‌های نرم‌افزاری

1. ‫افز‬‫نرم‬ ‫های‬‫نیازمندی‬ ‫تحلیل‬ ‫کاربردی‬ ‫روش‬‫ار‬
‫مرور‬‫مفاهیم‬
‫بدری‬ ‫محمد‬
‫زمستان‬1398‫سماتک‬ ،
badri@software-academy.org
SOFTWARE ACADEMY 1

2. ‫مطالب‬ ‫سرفصل‬
o‫به‬ ‫توجه‬ ‫چرا‬«‫ها‬‫نیازمندی‬»‫است؟‬ ‫مهم‬
oِ‫ف‬‫تعری‬«‫نیازمندی‬»
o‫نیازمندی‬ ‫انواع‬
o‫پروژه‬ ‫مفاهیم‬ ‫سایر‬ ‫و‬ ‫ها‬‫نیازمندی‬ ‫میان‬ ‫ارتباط‬
o‫ها‬‫نیازمندی‬ ‫تحلیلگر‬
o‫ها‬‫نیازمندی‬ ‫با‬ ‫مرتبط‬ ‫مفاهیم‬ ‫سایر‬
SOFTWARE ACADEMY 2

3. ‫به‬ ‫توجه‬ ‫چرا‬«‫ها‬‫نیازمندی‬»‫است؟‬ ‫مهم‬
SOFTWARE ACADEMY 3

4. SOFTWARE ACADEMY 4

5. SOFTWARE ACADEMY 5

6. SOFTWARE ACADEMY 6

7. “It’s not the customer’s job to know
what they want” ____ Steve Jobs
SOFTWARE ACADEMY 7

8. ‫تعریف‬«‫نیازمندی‬»
Requirement
SOFTWARE ACADEMY 8

9. ‫تعریف‬ ‫جستجوی‬ ‫در‬«‫نیازمندی‬»-requirement
The dictionary defines requirements as:
‘‘a need’’, ‘‘a thing needed’’, ‘‘a necessary
condition’’, ‘‘a demand’’, ‘‘something essential to
the existence or occurrence of something else’’, and
‘‘something that is needed or that must be done’’.
Simply stated, a requirement is a need of some person or process. A requirement is capable of
being fulfilled. If we come across a requirement that cannot be fulfilled, it becomes a desire that
can perhaps be fulfilled at a later date or with a better technology or better set of
circumstances.
SOFTWARE ACADEMY 9
ِ‫ف‬‫تعری‬«‫نیازمندی‬»

10. ‫تعریف‬ ‫جستجوی‬ ‫در‬«‫نیازمندی‬»-2
Wikipedia defines requirements in the context of software engineering:
‘‘It is a statement that identifies a necessary attribute,
capability, characteristic, or quality of a system in
order for it to have value and utility to a user’’. In the
context of other engineering disciplines, it defines
requirements as ‘‘a singular documented need of
what a particular product or service should be or
perform’’.
SOFTWARE ACADEMY 10
ِ‫ف‬‫تعری‬«‫نیازمندی‬»

11. ‫تعریف‬ ‫جستجوی‬ ‫در‬«‫نیازمندی‬»-3
IEEE (Institute of Electrical and Electronics Engineers) standard 610 ‘‘Glossary of
Software Engineering Terminology’’ provides three definitions:
1. A condition or capability needed by a user to solve a
problem or achieve an objective,
2. A condition or capability that must be met/possessed by
a system or system component to satisfy a contract,
standard, specification or other formally imposed
documents.
3. A documented representation of a condition or a
capability as in (1) or (2) above.
SOFTWARE ACADEMY 11
ِ‫ف‬‫تعری‬«‫نیازمندی‬»

12. ‫تعریف‬ ‫جستجوی‬ ‫در‬«‫نیازمندی‬»-4
CMMI (Capability Maturity Model Integration) for Development version 1.3 also
gives three definitions almost similar to IEEE definitions:
1. A condition or capability needed by a user to solve a
problem or achieve an objective,
2. A condition or capability that must be met/possessed by
a product, service, product component or service
component to satisfy a supplier agreement, standard,
specification or other formally imposed documents.
3. A documented representation of a condition or a
capability as in (1) or (2) above.
SOFTWARE ACADEMY 12
ِ‫ف‬‫تعری‬«‫نیازمندی‬»

13. ‫تعریف‬ ‫جستجوی‬ ‫در‬«‫نیازمندی‬»-‫دی‬ ‫تعریف‬ ‫یک‬‫گر‬
A requirement is a need, expectation,
constraint or interface of any
stakeholders that must be fulfilled by
the proposed software product during
its development.
SOFTWARE ACADEMY 13
ِ‫ف‬‫تعری‬«‫نیازمندی‬»

14. ‫تعریف‬«‫نیازمندی‬»-‫تعریف‬ ‫اجزاء‬ ‫توضیح‬
1. Need—It is something basic without which the existence
becomes untenable. It is the absolute minimum necessity
if the system is to be useful. If a need is not met, the
system becomes unusable or less usable.
2. Expectation—Expectation is an unstated need. When
users entrust the development of software to a team (in-
house or outsourced) it is expected that the development
team brings expertise of software to bridge the gap in the
needs stated by the user.
SOFTWARE ACADEMY 14
ِ‫ف‬‫تعری‬«‫نیازمندی‬»

15. ‫تعریف‬«‫نیازمندی‬»-‫تعریف‬ ‫اجزاء‬ ‫توضیح‬-2
1. Constraint—It is a hurdle that the user has to live with. It
may be in terms of a limitation on the leverage of the
software design or development.
2. Interface—It is the basis for interaction with the
customers, suppliers, and peers (in the forward chain or
backward chain) of the user.
SOFTWARE ACADEMY 15
ِ‫ف‬‫تعری‬«‫نیازمندی‬»

16. ‫تعریف‬«‫نیازمندی‬»-‫تعریف‬ ‫اجزاء‬ ‫توضیح‬-3
5. Stakeholders—A stakeholder is someone who is affected
by the outcome of a human endeavor. A software
development project has multiple stakeholders, namely,
a. The end user who is the ultimate user of the product
b. The project team that is going to develop the product to fulfill
the need
c. The marketing team, if the resultant product is a COTS product
so that they can find customers and sell it
d. The managements of both the supplier and the customer as
both derive ROI (Return on Investment) from the endeavor
SOFTWARE ACADEMY 16
ِ‫ف‬‫تعری‬«‫نیازمندی‬»

17. ‫تعریف‬«‫نیازمندی‬»-‫تعریف‬ ‫اجزاء‬ ‫توضیح‬-4
6. That must be fulfilled—The need must be fulfilled. If it cannot be
fulfilled either due to limitations of technology or finance, it
becomes a future requirement. If the need cannot be fulfilled by
the present endeavor, then the endeavor itself becomes
unnecessary
7. The proposed software product—It is the place where the need is
expected to be fulfilled. It is the end result of the present endeavor
8. During its development—This specifies the timeline when the
need shall be fulfilled. If it is not being fulfilled during present
development, then the need remains unfulfilled or a future need.
SOFTWARE ACADEMY 17
ِ‫ف‬‫تعری‬«‫نیازمندی‬»

18. ‫تعریف‬ ‫مرور‬«‫نیازمندی‬»
‫ینف‬ ‫از‬ ‫یاک‬ ‫هار‬ ِ‫ط‬‫واسا‬ ‫یاا‬ ‫ییاد‬ ،‫انتظاار‬ ،‫نیاز‬ ‫از‬ ‫عبارتست‬ ‫نیازمندی‬‫هاه‬ ‫عاان‬
‫برآور‬ ،‫پیشنهادی‬ ِ‫ی‬‫افزار‬‫نرم‬ ‫محصول‬ ‫ی‬‫توسعه‬ ‫حین‬ ‫در‬ ‫بایست‬‫می‬‫شود‬ ‫ده‬.
A requirement is a need, expectation, constraint or interface of any
stakeholders that must be fulfilled by the proposed software product
during its development.
SOFTWARE ACADEMY 18
ِ‫ف‬‫تعری‬«‫نیازمندی‬»

19. ‫ها‬‫نیازمندی‬ ‫سطوح‬ ‫و‬ ‫انواع‬
SOFTWARE ACADEMY 19

20. SOFTWARE ACADEMY 20

21. SOFTWARE ACADEMY 21

22. SOFTWARE ACADEMY 22
Requirements Exist at Many Levels

23. SOFTWARE ACADEMY 23
‫انواع‬
‫ها‬‫نیازمندی‬:
‫هارهردی‬
‫غیرهارهردی‬

24. ‫نیازمند‬ ‫بندی‬‫طبقه‬‫ها‬‫ی‬
SOFTWARE ACADEMY 24
Categories of requirements (from BABoK)

25. ‫ها‬‫نیازمندی‬ ‫سطوح‬
SOFTWARE ACADEMY 25

26. SOFTWARE ACADEMY 26

27. SOFTWARE ACADEMY 27
‫های‬‫نیازمندی‬ ‫انواع‬
‫غیرهارهردی‬

28. ‫پروژه‬ ‫مفاهیم‬ ‫سایر‬ ‫و‬ ‫ها‬‫نیازمندی‬ ‫میان‬ ‫ارتباط‬
SOFTWARE ACADEMY 28

29. SOFTWARE ACADEMY 29

30. ‫و‬ ‫ها‬‫نیازمندی‬ ‫میان‬ ‫ارتباط‬
‫پروژه‬ ‫فرایندهای‬ ‫سایر‬
SOFTWARE ACADEMY 30

31. ‫نیازمندی‬ ‫خصوص‬ ‫در‬ ‫مختلف‬ ‫نفعان‬‫ذی‬ ‫مشارکت‬‫ها‬
SOFTWARE ACADEMY 31

32. ‫می‬ ‫ارتباط‬‫ان‬
‫انواع‬
‫اطالعات‬
‫با‬ ‫مرتبط‬
‫ها‬‫نیازمندی‬
SOFTWARE ACADEMY 32

33. ‫ها‬‫نیازمندی‬ ‫تحلیلگر‬
SOFTWARE ACADEMY 33

34. SOFTWARE ACADEMY 34

35. SOFTWARE ACADEMY 35

36. ‫ها‬‫نیازمندی‬ ‫با‬ ‫مرتبط‬ ‫مفاهیم‬ ‫سایر‬
SOFTWARE ACADEMY 36

37. SOFTWARE ACADEMY 37

38. SOFTWARE ACADEMY 38

39. SOFTWARE ACADEMY 39

40. ‫در‬ ‫ها‬‫نیازمندی‬ ‫فرایند‬
‫محصول‬ ‫ی‬‫توسعه‬ ‫ی‬‫چرخه‬
SOFTWARE ACADEMY 40

41. SOFTWARE ACADEMY 41

42. ‫شما‬ ‫توجه‬ ‫از‬ ‫تشکر‬ ‫با‬
SOFTWARE ACADEMY 42