Strengths -give specific detail show how about system work and how system interact with server; -give specific requirement in good detail for reader can understand The strength of SG1 is the performance. (Measurable performance) The description of System perspective is not clear.; The requirements written are clear.; The System Perspective and System Function diagrams are clear.; Some technical terms should be elaborated.; Some requirements are measurable, some are non-measurable e.g.in I2, the word 'easily' which is non-measurable and in F7, it should specify the maximum number of multiple files allowed.; The performance requirements should specify the display format. They explain clearly and understand about how the system work Weaknesses -wrong format in part2 (requirement) SG1 They explain every things not cleary and in some part i don't understand why do they these thing and what it is about.They should explain ; more and explain some technical word. Unclear explanation in most part of report. 1.clear requirement -System funtion is confused, the description of funtion is not get along with it. Their requirement did not explain the function clearly so I do not know which function provide each requirement. It is hard to understand. They did not tell what type of file that they use to encrypt. First, by reading the system description, I don’t really understand what is it and what does it use for because the system description only describe how does it work.; Second, the functional requirement should be separate into each function. For example, which function should be able to do what, not mix them all together.; Third, the requirement should not be separate into Interface, Functional, and Performance requirement yet as it has been said in the instruction of the draft requirement.