Comp 523 Group M Project Site
Team
Client: Ernie Ward, DVM, CVFT
Dr. Ernie Ward is an internationally recognized award-winning veterinarian known for his work in the areas of general small animal practice, pet obesity and nutrition, life extension and longevity, practice management and leadership, and the special needs of senior dogs and cats.
He has authored three books, including “The Clean Pet Food Revolution: How Better Pet Food Will Change the World,” “Better You, Better Dog, Better Life: 30 Days to Happiness with Your Best Friend,” “Chow Hounds: Why Our Dogs Are Getting Fatter.” Dr. Ward has been a frequent guest on television programs and served as the resident veterinarian for the “Rachael Ray Show” from 2007 until 2014.
Dr. Ward has authored and been featured in more than 100 practice management and peer-reviewed medical journal articles in 11 countries, co-authored the American Animal Hospital Association (AAHA) Weight Management Guidelines, co-authored the peer-reviewed Veterinary Clinics of North America Small Animal Obesity textbook, and is a 1992 graduate of the University of Georgia College of Veterinary Medicine. He is also a certified veterinary food therapist (CVFT), dedicated to preserving health, extending longevity, and improving quality of life through better nutrition.
Professor: Jeff Terrell
Prof. Terrell is Professor of the Practice at UNC since 2018, specializing in software and app development.
Mentor: Jim Fletcher
Team Rules
1. Communication
More is better, so ask for help and advice when needed.
Use email for communication outside of the developer team unless urgent.
Clearly acknowledge the expectations of an assignment and follow up as needed.
Always message when merging or pushing change to avoid integration errors or oversight.
2. Meetings
Meeting attendance is expected but not required.
Communicate any forseen absence as soon as possible.
3. Code style
Clean looking code with emphasis on relevant naming and spacing.
Comment with the intention of helping others during code review.
4. Git style
Name your commits/branches relevantly.
Separate branches for features.
Prioritize merging to master upon completion to fix integration errors instead of focusing development in one branch.