Should be abstract (high-level) (Adapted from Dr. W. Spencer Smith's 4ZP6 Lecture Notes)
What problem does it solve?
Not how you are going to solve the problem! Do not make design descisions in the Problem Statement
Why is this an important problem?
What is the context of the problem you are solving? (stakeholders, environment for product, etc)
"People need to be entertained", "create game in which teamwork and tatical cooperation are rewarded" (fosters teamwork and commardarie in video game community)
(Notes from Meeting #1)
Should be abstract (high-level) (Adapted from Dr. W. Spencer Smith's 4ZP6 Lecture Notes)
For more information, refer to: https://gitlab.cas.mcmaster.ca/smiths/se3xa3/tree/master/Lectures/02-ProjectApprovalProbStateDevPlan