Start by reviewing what FIS is supposed to do: use cases and
domain models, etc..

Invent your own packaging using the ideas we have
looked at in class.  Look at the previous work for inspiration
and the web site.  Draw a diagram showing the packages
and how they depend on each other. KISS!

For each package there should be a class diagram that
describes the classes in the package and how they are related.
These are classes that will appear in the FIS Software(Design
classes) rather than the domain model from earlier iterations.
You should show all the classes/interfaces/attributes/operations
needed to support what SIS does.

One special case:  if a package is referring to software that is bought
(rather than built)
then you only need to show the classes/interfaces you are interacting with.
And you don't need to show all the detail.

Now you know all the classes of objects in your program: which of
them are persistent and which transient?  Make list of names of
classes that will need external storage.

Finally: how might you get persistent storage for your data,
without too much hassle.  Be creative!  Write this up in a
short paragraph.   Note: you don't want to get into all the detailed
stuff in chapter 34: YAGNI.  You should look for an alternatives.
Perhaps in the problem, or on the net, or in magazines, or...
Is there a solution?  I'm not sure.