UML - Githubissues

vanbelle commented 9 years ago

Document your initial object-oriented analysis and design using a UML class diagram (or diagrams), focusing on the most important anticipated classes, interfaces, and relationships. Include detail on key attributes and methods. Include notes on the use of design patterns among the classes. Add notes if the purpose of a class or interface is likely not clear to an outsider. The diagram(s) may be reverse engineered from the code, but must be edited, arranged, and selective (not a raw dump). The diagram(s) must be neat and tidy, and drawn well using tools like eUML2 and dia and embedded as image(s) in your team wiki.

vanbelle commented 9 years ago

A list of the classes currently implemented in our code that I think needs to be in the UML:

[ ] User List - Jim is working on this
[ ] User - Jim is working on this
[ ] Claim list -Omar is working on this
[ ] Claim - Omar is working on this
[x] Sum List- Megan is working on this
[x] Expense List - Megan is working on this
[x] Expense Item - Sarah is working on this
[x] Amt - Currency - Sarah is working on this
[x] Tag List Just Added - Sarah is working on this
Any others???

qsjiang commented 9 years ago

FYI. I will be working on the UML for UserList and User class. The UML diagram will be created using DIA, and I will upload the dia files to the google drive once they are finished. (and I will also post the images to the wiki)

qsjiang commented 9 years ago

Since all the models inside an UML diagram are closely coupled, they need to be placed onto one single diagram if we want to draw connections between them.

The easiest way to merge all diagrams is to draw our models using the same software and later copy paste them onto one single diagram.

So make sure to use DIA, and we will merge the diagrams on Monday.

ViIIager commented 9 years ago

why don't we just use the built-in eclipse extension to make the diagram? it will do it for us and all we have to worry about is formatting it. i think it will be better. I can do it in 30 sec on my computer. I think it is better than having all different diagrams to merge. if we do it with eclipse, we can do it on Tuesday at our meeting( I will bring my laptop) and I can show you how to do it. we can then edit it and it will create a separate UML file. There is no need to complicate things. What do you guys think?

ViIIager commented 9 years ago

i will do Claim and ClaimList then.

Make sure we send everything to Jim so he can put everything together afterwards

qsjiang commented 9 years ago

My email: qsjiang@ualberta.ca

Jim

ViIIager commented 9 years ago

make sure we are not adding any unnecessary getters and setters in the UML. it should only include add/remove/boolean methods. otherwise it will get really cluttered

megsum commented 9 years ago

Should we worry about listeners in the UML?

LeahGabrielle commented 9 years ago

Uh, is there anything I can do with the UML?

vanbelle commented 9 years ago

Could you maybe do the storyboard? That would be useful.

LeahGabrielle commented 9 years ago

yep. I can work on that.

vanbelle commented 9 years ago

When I was rereading the USs about tags it seemed like the list of tags should be independent of each individual claim, so that when assigning tags to a claim they are just chosen from a previously created list of tags.To fit this model I added a button on the ClaimList page so that the user could add/remove tags from a tag list. This seems to fit better with US03.02. What do you think?

ViIIager commented 9 years ago

Just make a list as an attribute in the claim class. That would solve all the problems of not sharing tags On Feb 22, 2015 5:43 PM, "vanbelle" notifications@github.com wrote:

When I was rereading the USs about tags it seemed like the list of tags should be independent of each individual claim, so that when assigning tags to a claim they are just chosen from a previously created list of tags.To fit this model I added a button on the ClaimList page so that the user could add/remove tags from a tag list. This seems to fit better with US03.02. What do you think?

— Reply to this email directly or view it on GitHub https://github.com/CMPUT301W15T12/C301Project/issues/16#issuecomment-75475815 .

vanbelle commented 9 years ago

But that wouldn't work in the case where a tag is created but not associated with a claim

ViIIager commented 9 years ago

Why I mean is add a tag to the claim taglist every time you associate one with it. Other than that it stays in 'storage' in the taglist class On Feb 22, 2015 5:57 PM, "vanbelle" notifications@github.com wrote:

But that wouldn't work in the case where a tag is created but not associated with a claim

— Reply to this email directly or view it on GitHub https://github.com/CMPUT301W15T12/C301Project/issues/16#issuecomment-75476555 .

vanbelle commented 9 years ago

ok, that makes more sense. In that case though we will need to add a class Tag List to the UML, and attribute ArrayList tagList to the Claim.

CMPUT301W15T12 / C301Project

UML #16