This is a repository I will be using to show off my skills with GitHub Projects, Python, Web, MySQL, Azure, and Power BI
Version: 1.0
Last Updated: 2026‑05‑13
| Version | Last Updated | Description |
|---|---|---|
| 1.0 | 2026‑05‑13 | Initial creation of Standards folder README |
Your feedback helps improve the clarity, structure, and overall quality of this portfolio. If you're reviewing this project for hiring, collaboration, or professional interest, you’re invited to share your thoughts.
Please take a moment to sign the Visitor Log and optionally leave feedback about your experience.
What You Can Share:
- How you discovered this portfolio
- Which modules or diagrams you reviewed
- Any suggestions for clarity or improvement
- Opportunities for collaboration or follow‑up
Why This Exists
GitHub does not provide identity‑level analytics for repository views.
This Visitor Log offers a simple, professional way for reviewers to:
- Provide feedback
- Identify themselves
- Ask questions
- Connect for follow‑up
Your insights directly support the continuous improvement of this project.
Over the past eight or more years I have been on the weight loss fitness track. Over that time, I have used Fitbit, Samsung Health, and others to track both nutrition and fitness routines. Because of long term use of these types of applications, it made sense to use it as the basis for this portfolio. There are so many aspects of my experience over the years that align with this design.
Utilizing GitHub for the repository and project management of the project allows me to expand on the basics of project management and planning.
the fact that documentation has evolved quite a bit over the years from mostly Microsoft Office Documents (*.docx, *.xlsx) to the use of Markdown files ( *.md). This allowed me to upgrade my knowledge in these areas.
From the source control side if GitHub, I have used multiple Source Control software versions from Visual Source Safe to Team Foundation Server to Subversion and Azure Dev OPs and GitHub. This portfolio allows me to get further practice with GitHub Source Control.
As I have been a heavy SQL Server Integration Services programmer Python came into the mix. As such, the plan is to use Python for the APIs behind the Fitness App to be the interface between the Front End and the Azure hosted MySQL database.
Azure has so many possibilities starting with the Hosting of a MySQL database. Because this is a portfolio project I went with the lower cost database instead of staying with my comfort zone and the Azure SQL Database. Azure has so many possibilities starting with the Hosting of a MySQL database. Because this is a portfolio project I went with the lower cost database instead of staying with my comfort zone and the Azure SQL Database.
The APIs will be hosted in Azure because direct database access poses problems.
Reporting Models that support Power BI reports will have Pipelines to refresh the data on a schedule set to daily for now.
With a long history of web development before I was in data heavy positions, I want to update my skills a bit to provide a working front end. The plan is to use components that have minimal cost and are not JavaScript heavy to support browsers that limit JavaScript and or Http Cookies.
The backend support for the website it makes sense to update from my previous experience with C# .Net MVC applications to Razor and Node.
To round out the full cycle reports will provide the platform to transform OLTP data to Star Schema for optimized reporting.
This project includes full enterprise-grade documentation across Business Requirements, Functional Specifications, UI Specifications, API Contracts, Data Dictionary, Test Cases, Use Cases, and System Diagrams.
For reviewer convenience, curated Markdown samples are provided:
User Interface Specification Sample Section
Account Functional Specification
- Create Account
- Login
- MFA Enrollment
- Positive / Negative / Edge / Integration
- UC-LOGIN-01_UserLogin
- UC-MENU-03_NavigateDashboard
- UC-EP-02_ViewProgramDetail
- UC-LW-01_LogWorkout
- UC‑ANL‑06_LogFeatureUsage
- Context Diagram
- Sequence Diagram
- Data Flow Diagram
- Domain Model
Full documents (PDF , DOCX, XLSX) are available in /docs/
The Fitness App supports two primary system roles. These roles define how different actors interact with the application and determine the permissions, responsibilities, and system behaviors associated with each user type.
The App User is the core consumer of the Fitness App. This role represents individuals who use the application to track and improve their personal fitness journey.
Responsibilities:
- Create and manage their user profile
- Log workouts and daily activity
- Track progress over time
- View personalized analytics and insights
- Manage personal settings and preferences
Characteristics:
- Primary actor for all functional use cases
- Interacts exclusively through the mobile or web UI
- Has no administrative or system‑level permissions
The App Admin is responsible for maintaining the operational integrity of the system. This role does not represent a typical end‑user but an internal system operator.
Responsibilities:
- Manage user accounts (create, disable, reset passwords)
- Monitor system logs and error events
- Oversee data integrity and system health
- Perform administrative tasks through backend tools or APIs
Characteristics:
- Does not use the app for fitness tracking
- No dedicated UI in scope for this project
- Exists to support RBAC, logging, and system governance requirements