I can suggest a way to structure the Use Case Model.
Under Use Case Model I create two packages:
Repository
Views.
Under Repository package, I create one package per use case. This is useful for version control purposes, and a package called Actors in which I put my actors obviously.
Under Views I create packages structures, as needed, for instance, one package per subsystem. In this packages I model actors, use cases and the relations between them:
Actor ------> use case
Use case ---> extended Use Case
Use Case <----- included use case
Under Views package I feel free to organize use cases under different point of views depending on the audience: stakeholders, developers, project managers etc.
For analysis and design model, I'm still working on finding the best structure that fits my organization.
Component model should be easier because must correspond to the organization of the software artifacts (.jsp, .asp, .dll, .class etc).
