Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Creating a Class Diagram

 
Asif Fraz
Greenhorn
Posts: 17
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello friends,

I am working on making the class diagram for assignment.

I want to know a few details regarding it.

1. The case study narrates about a few items which will interact with each other during system functioning. I want to know whether my classes should be restricted to only those few items or i can add my own classes those i perceive fit for the job at hand?

2. Do i need to include exhaustive list of all the classes needed for the system to work?

 
Simon Roberts
Author
Ranch Hand
Posts: 170
7
Java Linux Netbeans IDE
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You're creating an architecture. Absolutely that will involve realizing some components.

You should, however, restrict yourself to architecture, which is a high-level view addressing "Architecturally Significant" items. What things are Architecturally Significant? Well, anything that you can't trust the designer to get right Typically, anything that relates to transactions, network messaging, persistence, integration of stuff you don't own/control (either at a code or sysadmin level), novel functionality, security, critical performance, and the like. In general, assume that anything that isn't the purview of "regular design" (functional correctness, extensibility, maintainability) is probably relevant to address.

HTH,
Simon
 
Asif Fraz
Greenhorn
Posts: 17
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thank you Simon Roberts.

Here I have attached a test class diagram with following characteristics.

1. Customer and Investor are two actors (roles) for a business.
2. Both are users of the portal.
3. The user of the portal must be authorized and authenticated before it can access the portal features.
4. The FinancialReport can only be viewed by the Investor.



A) My question is does this attached class diagram rightly presents the above facts?
B) If i am not missing anything still what else i can add to it to make it better?

Regards,
Asif

[NOTE: I do not want to create so many individual threads/topics. Therefore putting all my questions and understandings for class diagram in this same thread.]
TestExample.jpg
[Thumbnail for TestExample.jpg]
Test Class Diagram
 
K. Tsang
Bartender
Posts: 3585
16
Android Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Diagram does satisfy the points you stated.

The only thing wrong is that Customer and Investor should have inherited User.

As for the relationship, 1 Investor to M FinancialReports.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic