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

Non-Use case Driven?

 
Tristan Zeta
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Non-Use case Driven?

Hi guys, I am one of those silent readers in this forum.

I am writing assumption and i found one question, here it is.

Normally, we use OOD to design the system and so, it should be use case driven. The use case diagram has just 2 users as we all get very very very familiar with. One of my assumption is that we will not consider other uses such as administrators, backup operators etc, however it feels kinda weird in a lot of cases. For example, when designing Booking Subsystem (in my design), there will be no manager session beans maintaining information about itineraries, segment etc, because there is no use cases metioning those interactions. So, am i supposed to just leave it alone? Where would those info be maintained? Yeah, it is easy to say that when one seat is booked, then the status will be set to booked or sth like that, but what about others? Like equipment, where'd we know if it is one 737 or jet? As FBN's gonna purchase more planes, it is in the requirement, so how could we address these non-use case driven requirements?

Thanks for any thought.
 
Tristan Zeta
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Oh, sorry, the sentence "there will be no manager session beans maintaining information about itineraries, segment etc," should be "there will be no manager session beans maintaining information about flight, equipment etc,"
 
James Wang
Ranch Hand
Posts: 102
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Tristan Zeta,

I am preparing the PART 2, I dont think that you need take care administrators and backup operators. The usecase diagram dont mention it,I think the requirement is not requred to complement it. Is what I said right? welcome to any suggestion.
 
Frank Silbermann
Ranch Hand
Posts: 1408
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
My assumption is that we are architecting a system, not designing it. That means we draw out a few architecturally significant use cases with the assumption that this will exemplify the structure into which all remaining functionality will be implemented.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic