Today is the second day when I spend some evident time on preparing to my knowledge evaluation. For today I had Engineering Management, Requirements and OOD.
Engineering Management is something that I read few articles on wikipedia and OOD is something that is not possible to learn per one night. So regarding Requirements I noted only few things.

Requirements

Requirements is very important part of the process of building software. The better and cleaner requirements you get – the better understanding of the system and its design you create; the better you communicate requirements to development team – the better product will be built. And what is the most important as per me – you can evaluate requirements before you started developing something and find out if it is feasible.

So how can requirements look like?

• Business Requirement – defines needs from software that can help reach goal of the business.
• User Requirement – defines how people (users) will interact with system and what should it do from their perspective.
• Functional Requirements – define functional specification to the system, developers must build to satisfy the other requirements.
• Quality of Service Requirement – performance, scalability 

Evaluating the Requirements for the Application

• Requirement perspectives
• Unambiguous
• Complete
• Necessary
• Feasible