You may use your own format or table, or a requirements document template as a starting point. Include all functional and non-functional requirements. Functional requirements are features / actions performed by the system (which you have expressed in the form of user stories) and non-functional requirements are known as "quality attributes" (described in slides #2). Update as needed your glossary of terms (analysis objects (slide 29- of slides#2)). When writing/revising your requirements, try to follow the S.M.A.R.T. criteria.
How to submit
Print your work (one copy per team) and give me a hard-copy in class.