Today read "Mastering the requirements process," the book, the book from the basic fact that the process needs to determine the scope of business issues, business use cases, research work, scene, understand the real problem begins solutions, today business strategy analysis, function requirements, non-functional requirements, acceptance criteria and rationale, quality, demand and iterative development, reuse needs, communication needs, demand respect the integrity of seventeen explain in detail the need for the process. Currently read the fourth chapter, the first record your own thoughts read for content.
This book in the beginning of time, the basic facts, tell us something about our past misunderstandings thing - "The demand is actually not talking about demand", these words say, demand is not to talk, and you are going to discover by keen sense of. In the past, we are caught in a cycle of death, if not always think the depth of the conversation, they will not understand the needs of users, however, even if the user needs to express himself more specific, it is still an unknown because users do not know if it was right, so we have a lot of time for users to create demand through their own discovery, provided that you understand the depth of these needs. Second, the demand must be found before building products, if only to find after the building, which will bring us very great trouble.
The first chapter, the author also emphasized the importance of demand, good requirements gathering and system analysis is necessary. Like us, you have to understand when shopping to buy what customers need is great demand for those, to get the maximum profit by analyzing talent. The article mentions the use of the process model to describe the requirements, the functional requirements that the process found by modeling verify its correctness, and the demand will go through some changes. Requirements include functional requirements, non-functional requirements, constraints and so on. At the same time, requirements gathering and analysis system also has a certain degree of overlap, the relationship between them is - needs analysis collectors use models to help identify needs, systems analyst needs to help the modeling of functions and data.
The second chapter, the author from the start of the project, to the quest for knowledge, prototyping and modeling scene, wrote needs, quality control, identification requirements specification, and the subsequent analysis and tailoring to tell an example for us, but also by this example, allow us to deeply understand the basic methods and conditions to make a demand, but also can deeply appreciate the question if we really want to develop a project to ensure its entire run, is particularly important when the needs analysis.
The third chapter, the author focuses on the issues related to aspects of the project started, he stressed that the process be started in a project, we must first determine the needs of users down, we must understand our clients, customers, understanding what they want, understand the customer's problems and expectations for clients and customers who know what acceptable what unacceptable. Different users will request made products are different, so we have to know the characteristics of users, in order to write the correct usability requirements. At the same time, I have to be good at what you find potential customers, to know the powerful resources of potential users, from all areas to determine our audience, in order to maximize the value and benefits of the product to the limit in the future.
The first three chapters, the biggest aspects of my harvest is that these, in the fourth chapter is also being read. Read from the current point of view, and I learned in the classroom knowledge of many complementary roles, understanding is not in place in terms of the current reading is also have a preliminary understanding in the classroom and look forward to the next reading can be harvested to more.