There is so much information to share that we needed a resource area for all the information that will be shared with our clients and the community. Within each of the sub pages in these areas, there will be several software development areas covered.
This includes, but not limited to the following area(s):
| Area | Description | | Process and Data Modeling | Modeling is a clean and effective way to represent an organizations business needs and desires. It provides information in a graphical style interface so that stakeholders better can understand and relate the business rules and processes. This area encompasses business process modeling and data modeling. | | SQL | | | Reporting | | | Analytics | | | Troubleshooting | | | Performance Tuning | | | Code Snippets | | | Presentations | These are the presentations that I have given at various meetings. | Certifications
| This refers to the confirmation of certain characteristics of an object, person, or organization. This confirmation is often, but not always, provided by some form of external review, education, or assessment. One of the most common types of certification in modern society is professional certification, where a person is certified as being able to competently complete a job or task, usually by the passing of an examination
| | Documentation | |
Database Development Life Cycle| Phase | Function | | Analysis | In this phase, system requirements are determined for both application and central database servers. A mission statement defines the required objective of your database design. Available forms, reports, and software applications used can be analyzed, and potential users of the database can be interviewed to collect information, such as required queries to be run, reports to be generated,. This can enable a better estimation of the system requirements. | | Design | In this phase, the designer makes a preliminary list of tables and identifies field(s) in a table that uniquely identify each record in a table. The requirements determined in the analysis phase are transformed into a system design normally using the Entity Relational Diagram (ERD) principals. The designer examines the tables for redundant or inconsistent data types and normalizes the tables to prevent loss of information and unintentional results. The design is finalized after incorporating the clients feedback into the design. | | Development and Documentation | The physical structure of the database is built based on the ERD. While the developer focuses on programming an application. The database administrator (DBA) works with the developer to build efficient queries that will run on the database. Further all aspects and functionality of the system are well documented to enable developers to track bugs and bottlenecks. | | Transition | The system in intentionally subjected to a variety of rigorous inspections and tests, to ensure that it is ready for production. The database administrator (DBA) monitors and checks the system as it runs and also tests the system back up and recovery plan to ensure the system can be recovered from failure. This is also called Quality Assurance phase. | | Production | The tested database design moves into the production phase, goes live, and end users begin using the system. Further the DBA maintains and tunes the production database when needed. |
|
|
