1. Introduction (+ general description):

  - 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.

  - Explain the scope of the work to define boundaries and explain any constraints you will face during development.
 
2. Specific requirements:

  - Each requirement in 2.1~2.3 below should be categorized into functional or non-functional

  2.1. User requirements

    - Written from the point of view of end users

    - Usually expressed in narrative form

  2.2. System requirements
  
    - Detailed specifications describing the functions the system needs to do

    - More technical in nature; usually expressed as a list

  2.3. Interface requirements

    - How the interface (the part the user sees and interacts with) will look and behave
 
3. Summary:

  - Summarize the main functions of the work and list requirements with priority.

  - Explain the expectations of your work.


*** This is a guideline for writing a requirement analysis document. You can skip or add some items above depending on your work. (*** 2. Specific requirements is mandatory)

*** Reference material: http://www.cdl.edu/uploads/Qd/S6/QdS615B1DcnwRZlnSuTDnQ/writing-requirements.pdf

*** Please prepare the document as PPT around 10 pages and submit it through LMS.