Updated grades table- Part1

[yaeli]

Hi all,

I attached the updated grades table.

Please send your works to my personal mail address.

You may send me one diargram from the fisrt part (only one) for rechecking (Please send it together with your second part)

 

	Use Case Diagram	Deployment Diagram	Activity Diagram	Total garde (part 1)
320517105 316982461	There are arrows that should point from the customer actor to tasks (as to "Buy Ticket"). - those task should be done directly by the customer. 28/33	Good 33/33	Good 34	95
66062712	You didn't completely understand the purpose of this diagram. A use case is a written description of how users will perform tasks. You don't supposed to include decision results ("no", "yes") as part of the systems tasks. 20/33	there is a lack of explanations.What is the "Despatcher operator service" is it the Client side of the operator? 30/33	You didn't compltly understand the purpose of this diagram. For example- what is the different between the result of "yes" and "not". Also the option should exit from one diamond decisions (as you did in the next diamonds decisions) 20/34	70
037093788 021574264	A few comments: 1. the user doesn't supposed to be responsible on "Approve transcation by confirmation code". 2.what is "seats details"- is supposed to describe the user task (same regarding to "date") 3. the system part is much better 25/33	Missing protocols and communication details between the components 25/33	Good 34	84
37559192 300396843	Missing arrow between the passenger to the "Login" task. Also there were supposed to be  between the passenger and the tasks after the login. 28/33	Good 33/33	Good 34	95
302751854	Some of the arrows to the system are unnecessary. The arrows should reflect the actions (tasks) that the actor executes . 30/33	Good 33/33	Good 34	97
312064892 302941646	You didn't completely understand the purpose of this diagram. A use case is a written description of how users will perform tasks. For example "phone", "website", "phone application" are not tasks. A few more points: 1. what is the different between "Cancel ticket reservation" and "Cancel reservation" 2. I don't think there supposed to be an "include" line between the "Book a ticket" and "Pay" task. in this case the arrow should be from the use to "Pay". 23/33	Missing protocols and communication details between the components, included sub components and files/applications inside the main component 23/33	Missing payment validation 32/34	78
201627742 301193513	Good, but please notice that the reservation center doesn't supposed to "Buy ticket" 32/33	A few points: 1. missing protocols between the components 2. what are those "consoles"? Where is the user interface? 20/33	Missing a few main flows. For example, playment validation. 30/34	82
026490060 200212777	The "Check out" tasks should be execute by the Client. Missing the operations from the server/order center side 25/33	Good 33/33	Good 34	92
038054664 062877832	Too high level. notice that the teller doesn't supposed to "Buy ticket" 28/33	Missing some protocols and communication details 30/33	Missing payment validation 32/34	90
300000098 305777799	Good 33/33	Missing some protocols and communication details. Also you defined actors and tasks as sub components 25/33	Good 34	92
066364811 300154390 316760172	Missing arrows between the customer to the "order ticket", payment task. Missing tasks, for example, payment validation task 26/33	Good but missing some protocols and communication details 30/33	good 34	90
320517105 316982461	Notice that some of the tasks are not operations. As "face to face" 30/33	Good 33/33	Good 34	97
301483731 302928726	Good 33/33	Good 33/33	Good 34	100
066105693 304795644	Missing tasks as credit card validation. The tasks should describe the actors action. No need to use a line between the customer and the receptionist 25/33	Good 33/33	Missing payment validation flow 32/34	90
300906815 200067775	The tasks should describe the actors action. No need to use a line between the customer and the receptionist 28/33	too high level 29/33	Good, but Missing payment validation 32/34	89
204729107	Most of the tasks should be perform by the customer (as paymnt, chosing seat...) 28/33	too high level, mising component types (as which DB are you going to use) 29/33	Not so clear, let's talk about it in the next practice 26/34	83