How will objects in the application be stored in the database?
We will use one database table for each class, and one row in
the database for each persistent instance of that class.
We will use a library to do our
object-relational mapping. (E.g., torque, castor, JDO, ADO,
What database access controls will be used?
A database user account has been created that has access to the
needed application database tables. The username and password for
this account is stored in a configuration file read by the
application server. The database limits login by that user to only
the IP-address used by the application server.
Is this application's central database accessible to other
Yes. The database is an important point of interoperability for new
applications to be added later. The database itself provides
support for access controls and checks validity constraints so that
a defective application cannot corrupt the database.
No. This database should always be accessed through this
application. All relevant pieces of information are available
through the application interfaces. The database itself does not
protect against data corruption that could be caused by other
What data needs to be stored in files?
Nothing is stored in files, everything is in the database.
The server stores most data in the database, but mailing list
attachments are written to files on the server hard disk.
All user documents are stored in files on their computer hard
What are the conventions for directory structure and file naming?
Files are stored on the server as
Users store files anywhere on their computer, with the filename
What file system access controls will be used?
Files for message attachments are only readable and writable by
the mailing list archiving process that runs as operating system
Users can use whatever file permissions they like.
What information (if any) will be stored on client machines?
For how long?
A cookie will be stored on the user machine for the purpose of
identifying a user session. When the user logs out or closes their
web browser, the cookie is deleted. Most browsers will not even
write this cookie to the disk.
The a cookie is stored on the user's computer that is equivalent
to their password (but it is NOT actually their password). This
cookie is needed for the auto-login feature. The cookie lasts a
maximum of 30 days, and it can only be used from the same IP
User preferences for color scheme are stored in cookies in their
browser. This information is not at all sensitive, so it is kept
All the user data will be stored on files on their
Persistence Mechanisms Checklist
Expressiveness: To what extent has this been achieved?
Ease of access: To what extent has this been achieved?
Reliability: To what extent has this been achieved?
Capacity: To what extent has this been achieved?
Security: To what extent has this been achieved?
Performance: To what extent has this been achieved?
Interoperability: To what extent has this been achieved?
Has the persistence design been communicated to the development
team and other stakeholders?