STT App Framework
This is an Overview page
Please review:
This is an Overview page
Typically the need for further automation has grown from the use a variety of spreadsheets (often developed by a manager or user in an office) that are:
interconnected (whether users knew it not)
and that have outgrown their functionality in terms of scope and access
The Framework allows a variety of Multi-user Applications to be built within it.
Users login into the Framework and based on a managed permission model, users are given access to specific aspects of any given applications as needed. This allows, for example certain user/managers to be given read only permissions for report purposes.
Log Tracking, when turned, on allows all data changes to a particular data table, to be logged. Error Log tracking can be used during development to track system or data entry errors, causing issues in the final numbers.
The Application Framework includes an extensive Maintenance system that facilitates a reliable methodology to implement specific data base applications that need to used/shared by a variety of people in a common work environment.
The system runs on local area network based environment and the Backend Database is usually stored on a share common server drive. It can also be implemented using Microsoft Azure for a wide area solution.
Applications typically, have several data entry points and management points.
Change Management:
Very often, these applications are developed (conceptualised) as a result of reviewing (White Boarding) a variety of spreadsheets used by employees to track specific elements of a production or office process.
The Framework has important update tools & methodology in it. Theses tools facilitate Change Management within a production process that is seeking to upgrade and seek more efficiencies.
This is a critical element to an effective Change Management process as managers and user typically do not understand how the efficiency will work, and/or what the screens will look, despite the general requirement of those users telling the development team what it is that they need or want. Hence the Maintenance methodology must allows for regular upgrades, without interruption to the Data Entry and Data Review.
Table Maintenance
Event Logs
User Level Security
Data Maintenance
Data Manipulation
Error Log Tracking
Other, as needed