Currently, our class diagram only shows a few important data models. We should create a comprehensive class diagram, which will help us in parts C and D.
Requirements:
Show all Services and Controllers (other than MongoTest) (unless it gets too cluttered, in which case show some)
Don't show all the models, that's way too cluttered. Show a subset of which are critical to illustrate (maybe just the ones we already have in our current diagram).
Show db-related services as holding a collection of its models through association
Show Program.cs as a class with a main()
Show Program.cs holding on to services via a singleton manager (see here for the single-service case, called IServiceA)
Show Controllers associated to services through dependency injection (see above link)
Show most important methods in services and controllers. aggregate if necessary for brevity (e.g., show all database fetchers in a service as a single method called Get())
jaczhi
commented
6 months ago
Currently, our class diagram only shows a few important data models. We should create a comprehensive class diagram, which will help us in parts C and D.
Requirements:
main()Get())