How to create

1. How to create software requirements

2. Part 1What are requirements and why do we have them?

3. Requirements are a sort of contract

4. between the client

5. and the project team.

6. The project team needs to determine the specific tasks for the project.

7. To start the project team writes down draft requirements.

8. Each requirement needs to start with:“The system will ….”

9. Each team member will go to VISTA and create at least 5 to 7 separate requirements inside the Module Requirement Discussion

10. In Vistago to the Home pagethen go to “Team Discussion”then “Module Requirement Discussion”(if you do not see this please contact Prof. Bernal)

11. Please create 5 requirements for your team project. Start with simple draft requirements in a separate threads

12. This is a required Participation Grade item of 20 points. Please create 5 different requirements for your team project.

13. Review the requirements already posted so that you do not duplicate! After you have posted your requirements, read and give advise to ten to fifteen other team member's requirements.

14. Check back frequently, and when someone gives you advise about your requirement, please take it into consideration and rewrite your requirement in the reply.

15. After a requirement has been reviewed by three different team members – then the requirement could be approve. A requirement can not be approve without some editting!

16. Once you have two members give you approval - you are done with your requirements.

17. Continue to help all your team members until all requirements are approve for the team.

18. Requirements come in two main flavours.

19. Traditional Agile

20. They look something like this;

22. Requirements are the way we (project people)

23. articulate what the client (business people)

24. … want to see out of a new software product.

25. to see out of

26. Requirements are not

27. typically what we want

28. to see in a software package.

29. to see in

30. Requirements are what the system wants to achieve

31. and why it is important.

32. Part 2Reading requirements

33. (By the way, the secret to this is all in the preparation.)

34. Remember these?

36. Step 1

37. Study the Ch. on requirements.

38. Step 2

39. Schedule a team meeting

40. Meeting goal: Team Project Requirements

41. All members prepare their requirements in sticky notes

42. Now add the things you do that are (a) important, and(b) not in your KPIs

43. Tasks that are reported on Important things not in usual task of the system Req # 1 Req # 2 Goal # 1 Req # 3 Goal# 2 Req # 4

44. Step 3

45. Write down all the major problems the new system wants to overcome

46. and attach them

47. to your list of tasks and important things (goals)

48. Req # 2 Available Rides Req # 1 Staff daily operations Goal# 1 Happy Customers Quality of service inconsistent Customer satisfaction heading south Staff attrition too high Goal# 2 Easy joining the club Req # 3 Financial Rewards Req # 4 Pending Rides Low membership Staying on Budget with unexpected expenses High volume of needed rides with low drivers

49. Step 4

50. Drop your problems into an important / urgent prioritisation grid