* <b>CSED 499 Requirement Analysis Document Guideline</b> </br></br>

1. Introduction (+ general description): </br>
&nbsp;&nbsp; - State any technical background that is needed to understand the requirements and point less-technical readers to overview sections which will be easier to understand </br>
&nbsp;&nbsp; - Explain the scope of the work to define boundaries and explain any constraints you will face during development </br></br>
 
2. Specific requirements: </br>
&nbsp;&nbsp; - Each requirement in 2.1~2.3 below should be categorized into functional or non-functional</br>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2.1. User requirements </br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Written from the point of view of end users </br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Usually expressed in narrative form</br>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2.2. System requirements</br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Detailed specifications describing the functions the system needs to do </br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - More technical in nature; usually expressed as a list </br>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2.3. Interface requirements</br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - How the interface (the part the user sees and interacts with) will look and behave</br></br>
 
3. Summary:</br>
&nbsp;&nbsp; - Summarize the main functions of the work and list requirements with priority</br>
&nbsp;&nbsp; - Explain the expectations of your work.</br></br>


*** This is a guideline for writing a requirement analysis document. You can skip or add some items above depending on your work. <b>(*** 2. Specific requirements is mandatory) </b> </br>
*** Reference material: <a href="http://www.cdl.edu/uploads/Qd/S6/QdS615B1DcnwRZlnSuTDnQ/writing-requirements.pdf">http://www.cdl.edu/uploads/Qd/S6/QdS615B1DcnwRZlnSuTDnQ/writing-requirements.pdf</a> </br>
*** Please prepare the document as PPT around 10 pages and submit it through LMS. </br>