Project Report 2 Responsibilities

Go ahead and post which items you will be working on. Be aware though, you will be expected to post progress on each item you assume.
Line Items:

• Paper Revisions
  
• Revised Interface Drawing
  
• Use Case Descriptions (tabular representation; only 2)
  
• Updated Class Diagram (solution description)
  
• Activity Diagrams (if accomplished; only 2)

Since I produced the first progress report, I will take the task of the second progress report.

I'll take care of the interface and class diagrams, but if anyone wants to help on either of these, let me know.

I can get the activity diagrams started.

I can do the use case. Also what do you mean by tabular representation? Do you have an example?

Thanks

I would say the use case description should be something like slide 11 from the 2/6 lecture slides. I am not really sure what the tabular representation means. Can anyone else help on this?

Tabular just means layed out in a grid, like a spreadsheet. If you google image result for "use case description" you'll get some good examples.

Like Scott said, tabular simply refers to the table format. That is, a form with fields, where columns are attributes(eg name, definition, usage, etc), and rows are entries.

Gotcha, Sounds good. Thanks for the input guys.

Use case is almost done. Just putting the final touches on it. I will have it posted before I go to work at 7 tonight

Sounds good!

ScottW wrote:Sounds good!

Hey Scott or anyone, I don't think I did exactly what we want. I think I just created a description of our use case, but instead do we want a use case flow chart where it shows the available paths that a user can take. Let me know what you think of this, I don't feel that I'm done, but let me know. Thanks guys

shagav wrote:

Hey Scott or anyone, I don't think I did exactly what we want. I think I just created a description of our use case, but instead do we want a use case flow chart where it shows the available paths that a user can take. Let me know what you think of this, I don't feel that I'm done, but let me know. Thanks guys

Paul has already created the use case diagram, see [You must be registered and logged in to see this link.] post. From what I understand, we need to update his use case diagram (right?) and then generate the tabular use case descriptions based off of that.

Yeah that's the correct understanding.

ScottW wrote:

shagav wrote:

Hey Scott or anyone, I don't think I did exactly what we want. I think I just created a description of our use case, but instead do we want a use case flow chart where it shows the available paths that a user can take. Let me know what you think of this, I don't feel that I'm done, but let me know. Thanks guys

Paul has already created the use case diagram, see [You must be registered and logged in to see this link.] post. From what I understand, we need to update his use case diagram (right?) and then generate the tabular use case descriptions based off of that.

Agreed, but am i basically creating a flow diagram through tabular representation? Because I feel that a flow diagram is different from a use case. Anyways, I will update this and try to repost it hopefully by tonight. I will do what the examples from google show even though that feels like a flow chart.

edit: I will see what I can add to the original use case, and clean it up to have a nice representation

Thanks for the feedback scott

A use case description is largely a technical statement, along the lines of a definition. Decision should not be represented at this level, only the 'best-case' operation of the scenario should.

Just to let everyone know, Progress Report 2 is due tomorrow (3/22/13). I need everyone to upload their completed work no later than 7 PM tonight so that I can put it in the report.

Also, I'm not sure if Paul mentioned it, but me and him are meeting at 8:30 PM tonight in Striebel to discuss the project (general discussion and address any questions). I encourage everyone to come. I know its kind of late notice, but if you can make it that would be awesome.