• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Mileage Account - is it part of the system?

 
Roger Rustin
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,

As per the requirement, no aspect of the Frequent Flyer Mileage System(FFMS) is going to change. The proposed system will continue to interact with the existing web based FFMS.

I was trying to expand the existing business domain model to have a class diagram. Looking closely I found that as per the proposed system there will be no interact between customer class and mileage account since all interactions with FFMS will done through the web interface.

I have decided not to include mileage account in my class diagram and above snippet will be my explanation. Any thoughts! I would also like to know the point of view of the people who included mileage account in their class diagrams or are planning to include it.

thanks.
- Roger
 
Parag Doshi
Ranch Hand
Posts: 317
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Roger,
Your explanation makes sense. The only reason I might include it in my class diagram is to support future requirements/extensibility. If I have reasons to believe that the FFMS might be re-written (there is a mention of it in the interview) or integrated with this system, then I might keep the mileage account (though in a passive role currently) as part of my association with customer. Where the mileage account information is derived is immaterial at this point as it is going to be duely abstracted from the system.
So, it can go either way. I would say, go with what makes sense to you and more importantly, what you can justify in your documentation.

Hope this helps..

Parag
[ July 17, 2004: Message edited by: Parag Doshi ]
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic