We know the requirements include functional requirements and non-functional requirements, in "Mastering the requirements process," the authors also explain the contents of this part, also it made me understand the true meaning of demand.
The sixth chapter is about the functional requirements. What are the functional requirements? That specific functional requirements of the completion of the content needs. The author expressly set forth in this chapter: To be considered as the functional business requirements demand. So what is the business need? Business needs of the organization expressed or high levels of customer goals. It usually comes from project investors, customers buy products, the actual user's manager, marketing department or product planning department. Specifically, the business needs is to describe why the organization to develop a system that hopes to achieve organizational goals, that if we talk to users or a clerk would they describe the product in order to complete the work they must do some part of some of the things. Here, we think of brainstorming fifth chapter the author mentioned (before suddenly found a lot of things have come into contact with, but not too much care about), and we on this semester for the development of Android is the same, in the minds of after the storm, the more we can determine what is good and we expect users of the system goal is to better the needs to improve, he also aims to improve the function it functional requirements. In these terms, the functional requirements is a real job, or had a description of the business, it is done with his work is irrelevant. Remember, requirements specification will be referred to the contract to build the product. Therefore functional requirements must complete description of the action desired product can perform. Therefore, a requirement for requirements specification is product development sting can use it to build our customers expect products.
Chapter VII, the author tells of a non-functional requirements. In a certain sense, it refers to a non-functional requirements of the information system needs to ensure that the appropriate elements of performance, reliability, scalability requirements. Generally will not be made clear in the user's business needs, the need to analyze the need to conduct research summarized based on actual business. Non-functional requirements is a must-have product attributes. These attributes can be seen as some of the features or attributes that make the product attractive, easy to use, fast or reliable. Relative to the length of the sixth chapter, the author non-functional requirements for the presentation and discussion is more specific and detailed. Author introduced from eight types, so I deeply understand the basic meaning of the non-functional requirements: "The non-functional requirements define constraints on the services or functions provided by the system, including time constraints, space constraints, constraints and development process standards should be followed and so on. it originated from the user's restrictions, including budget constraints, institutional policies, and among other software and hardware systems interoperability, as well as safety regulations, privacy protection legislation and other external factors. "nonfunctional requirements it is easy to say we ignore these rookie, so later in the development process must be analyzed non-functional requirements.
"Mastering the requirements process." This book is really a good book, in a lot of places I've solved the doubts in the learning process.