• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Login/Authentication Module and Component Diagram

 
Kumar Amit
Ranch Hand
Posts: 103
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi There

I am planning to put in the assumption section that Authentication/Login module already exists for the SuD and is therefore out of scope for this assignment. In this case, do I need to show Login, Logout JSPs, Authetication Backing Bean, User Business Logic and LDAP in the component diagram?

Is it safe to put such an assumption?
 
Sharma Ashutosh
Bartender
Posts: 346
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I had BSCS assignment and i also made the same assumption but i provided the components in the component diagram. Remember you might not be expected to architect and design full end to end system but your component or system context diagram(big picture diagram) should contain everything.
 
Kumar Amit
Ranch Hand
Posts: 103
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sharma Ashutosh wrote:I had BSCS assignment and i also made the same assumption but i provided the components in the component diagram. Remember you might not be expected to architect and design full end to end system but your component or system context diagram(big picture diagram) should contain everything.

Many thanks Ashutosh.
 
Saket Mittal
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Amit/Ashutosh

If we include components in the component diagram which we think already exist for the SuD and are out of scope we don't have to include the corresponding classes / JSPs etc in the class diagram correct ?

For e.g. in your case below you wouldn't have included Login, Logout JSPs, Authetication Backing Bean, User Business Logic in your class diagrams right ?
If we do not have to include the corresponding classes then the component diagram would just contain the name of the Component ?

Thanks,
 
Unni Pillai
Ranch Hand
Posts: 35
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

I also did the same way.

Mittal,

You are correct. You can define it as a component without giving any internal details. But clearly write that in the assumptions, that is very important.

Unni
 
Kumar Amit
Ranch Hand
Posts: 103
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Saket Mittal wrote:Hi Amit/Ashutosh

If we include components in the component diagram which we think already exist for the SuD and are out of scope we don't have to include the corresponding classes / JSPs etc in the class diagram correct ?

For e.g. in your case below you wouldn't have included Login, Logout JSPs, Authetication Backing Bean, User Business Logic in your class diagrams right ?
If we do not have to include the corresponding classes then the component diagram would just contain the name of the Component ?

Thanks,

Hi Saket

I did the same. Please note that my result is NOT declared as yet.

Cheers
Amit
 
Saket Mittal
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Unni / Amit.
 
Sharma Ashutosh
Bartender
Posts: 346
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have assumed that Authentication and Authorization module already exists. In the class and component diagram- i have displayed Authentication Service and the User detached entity as this is the way my rest of the system will interact with A&A module.
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic