• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

scope of the project

 
Ranch Hand
Posts: 68
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The use case diagram for the project has 7 use cases.
However only 4 use cases are detailed. The "Log in", "Create Profile" and "View Frequent Flyers Miles" use cases are not detailed.
Do we have to do sequence diagrams for these too? If so, how? There are no descriptions!
Also, should the class diagram and component diagram contemplate these functionalities?
Regards,
Leo
 
Ranch Hand
Posts: 72
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Do we have to do sequence diagrams for these too?
As I remember correctly you have to provide a sequence diagram for each detailed (!) use case.

Also, should the class diagram and component diagram contemplate these functionalities?
These diagrams should reflect the architecture according to both the functional (all) and non-functional (all) requirements.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic