ABSTRACT
Requirements analysis is the activity of analyzing requirements for problems. Requirements agreement is the process of reconciling differences in the same requirement derived from different sources. Various techniques can be used to describe functionality in any system, including use cases, user stories, natural languages, formal languages, stylized (restricted natural) languages, and a variety of formal, semiformal, and informal diagrams. Performance requirements are static and dynamic requirements placed on the software or on human interaction with the software as a whole. The functional requirements should capture all system inputs and the exact sequence of operations and responses (outputs) to normal and abnormal situations for every input possibility. Object-oriented representations involve highly abstract system components called objects, and their encapsulated attributes and behavior. Engineers (of all types) have acquired an unfair reputation for poor communications skills, particularly writing. There are few studies covering the statistics of requirements specification document size in terms of number of requirements, page length, and other measures.
