My thoughts on Database

All the enterprise applications keep the data base and the application separately for the ease of maintenance. Even the menu, drop down lists were referred from the database tables. It would be easy to maintain the database more consistent, if we specify the following four data sets during the database design/architect phase:

Application master data: The application would respond well, if the data is not exposed to the end user

Business level master data: This would be part of the application master data; whereas we have to add additional information based on  the Government rules and regulation (less coding effect) - the data is exposed to the end user; with restricted access

Customer master data: This would be the part of application deployment at the customer environment; better to get sign-off from the customer once the environment is ready for production. Authorized persons would update the data instead of entire end uses

Transaction data: This would be the final set of data for the application and should have hierarchy of approval.

1. In the SaaS Model application we would have the below stakeholders:
2. The product would be owned by the Independent Software Vendor (ISV)
3. The actual product development would be done by a different set of team based on the requirement provided by the ISV 
4. The product sold to the end customer
5. The end customer’s data would be handled by the BPO; which may be done by the product development team.

The customer requires runtime reports which would not be the part of the application. The application customization would take long time; whereas the customer requires the report in advance. 

Generate the report outside the application by referring the database directly would be the idle solution. During that phase, it is recommended that use the temporary tables, which would hold the required data set instead of just joining the entire table.