In this chapter we talk about :-
mmmm …. but what exactly is a “requirement” mean ??
In this chapter we will learn how to satisfy our customers by making sure what
you deliver is actually what they asked for.
is a singular need detailing what a particular product or service should be or do.
1) Listen to customer:-
when it comes to requirements the best thing you can do is let the customer talk,and pay attention
to what the system needs to do,you can figure out how the system will do those things later.
2) Creating a requirement list:-
based on the custmer needs we create a requirement list.
is the steps that a system takes to make somthing happen,and it is a technique for
capturing the potential requirements of a new system.
- each use case provides one or more scenarios that convey how the system should
interact with the end user or another system to achive a specific goal.
There are three basic parts to a good use case:-
1) Clear value:
every use case must have a clear value to the system(which means it should help the customers to achive their goal)
2) Start and stop:
every use case must have a definit starting and stopping point.
3) External initiator:
every use case is started off by external initiator ,outside of the system. it could be a person or anything outside the system.
1- Working applications make customer happy. 🙂
2- Here are some key tools for making sure your customers are smiling when you show them the systems
you have built :-
3- Be careful! Good use cases make for good requirements, but a bad – or incomplete – use case can result in Bad requirements.
4- Your system must work in the real world … so plan and test for when things go wrong.
5- There are some important key words :-
Finally the source code for Dog Door System that he talk about it in this chapter you can find it Here . I implement it in C#.