As QA Analysts our primary function is to find ways to break a given piece of software, but this is not something we do randomly, rather there is an efficient process to be followed. When we are given the requirements for the Software Under Test (SUT) we have to intimately study each requirement and ask ourselves, “How can we test this?” and then “Under what conditions can this test fail?”. Thus we plan out testing scenarios which wil then lead to us writing out a series of test cases which will help us validate whether the SUT does or does not meet the given requirements. Here is a good article that discusses how to write Test Cases in detail, including giving you a visual on how to structure the TC matrix.
Hope you guys find it helpful.