User Story What?

Just so people know what they are looking at. User stories are used as a way to capture requirements for a system. The reason we do it this way is, often it's hard for someone to describe how exactly a system should be, but it's much easier to sit down and think about what the people who would be using the system would be doing with it. The list is not a sequence of events but 20 discrete "stories" on what someone or something would be doing with the system. Ultimatey the objective is capture all the things that people would be doing into User Stories, and from that I can create my requirements. If I have a system that lets people do all the things that are described in the User Stories, the system will be "fully featured".

Entities are basically "things" that exist in the context of what needs to get done in the User Stories. Some of the "things" are what begin the action and are called "actors". Hope this helps!