分享兴趣，传播快乐，增长见闻，留下美好！
亲爱的您，这里是LearningYard学苑。
今天小编为大家带来“信息系统开发课程笔记（十三）|需求获取（2）”，欢迎您的访问。
Share your interests, spread your joy, grow your insights, and leave your beauty behind!
Dear you, this is LearningYard Academy.
Today I bring you "Information Systems Development Course Notes (XIII) | Requirements Acquisition (2)", welcome to visit.
需求获取阶段可以通过各种途径收集所需的信息，如访谈手稿；观察和分析文档的笔记；表格、报告、工作描述和其他文档的集合；计算机产生的输出，如系统原型等。
The requirements acquisition phase allows for the collection of the required information through various means, such as interview manuscripts; notes from observation and analysis documents; collections of forms, reports, job descriptions, and other documents; and computer-generated outputs, such as system prototypes.
1
需求获取的途径
需求获取的途径主要有以下3点：
（1）通过与用户对话或者观察用户收集的信息，如访谈手稿、观察和分析文档的笔记、会议纪要等；
（2）现有的书面信息：业务使命和战略陈述、业务表格、报告和计算机演示范例，规程手册、工作描述、培训手册、流程图和现有系统的文档、咨询报告；
（3）基于计算机的信息：来自于联合应用设计会议的结果、组群支持系统会议的手稿或者文件、现有系统的CASE资料库和报告、来自系统原型的显示和报告。
Requirements are obtained through the following three main means: (1) Information gathered through conversations with or observation of users, such as interview manuscripts, notes from observation and analysis of documents, meeting minutes, etc.
(2) Existing written information: business mission and strategy statements, business forms, reports and examples of computer presentations, protocol manuals, job descriptions, training manuals, flow charts and documentation of existing systems, consulting reports.
(3) Computer-based information: results from joint application design meetings, manuscripts or documents from cluster support system meetings, CASE libraries and reports from existing systems, displays and reports from system prototypes.
2
需求获取的过程
（1）了解用户需求。通过与客户的交互了解客户对系统功能和性能的期望。
（2）分析用户需求。需求分析包括提炼、分析和仔细审查已经收集到的需求，以确保所有相关方都明白其中的含义，并找出其中的错误、遗漏或不足之处。
（3）编写需求文档。需求文档是需求获取阶段的主要成果，系统需求需要以正式的方式记录，以便与主要关联人员沟通。
（4）评审需求文档。选择客户代表评审文档并纠正存在的误解或者错误。
（5）需求管理。主要指需求变更以及需求跟踪。
了解用户需求、分析用户需求、需求文档编写等环节不遵循线性的顺序，这些活动可以并行并且可以循环迭代。
(1) Understand user requirements. Understand customer expectations of system functionality and performance through interaction with customers.
(2) Analyze user requirements. Requirements analysis involves distilling, analyzing, and carefully reviewing the requirements that have been gathered to ensure that all parties involved understand what is meant and to identify errors, omissions, or deficiencies.
(3) Prepare requirements documentation. Requirements documentation is the main outcome of the requirements acquisition phase, and system requirements need to be documented in a formal manner for communication with key associates.
(4) Review the requirements document. The customer representative is selected to review the document and correct any misunderstandings or errors.
(5) Requirements management. Mainly refers to requirement changes and requirement tracking.
Understanding user requirements, analyzing user requirements, and writing requirements documents do not follow a linear sequence; these activities can be parallel and iterative.
3
需求获取的方法
分析员可以使用不同的技术来从客户手中获得需求。比较传统的包括访谈、观察、名义团体技术、文档与报告、联合应用设计、原型等。
There are different techniques that analysts can use to get requirements from customers. The more traditional ones include interviews, observations, nominal group techniques, documentation and reporting, joint application design, prototyping, etc.
今天的分享就到这里，如果您对今天的文章有独到的见解，欢迎给我们留言，让我们相约明天，祝您今天过得开心快乐！
Today's share is over here, if you have unique views on today's article, welcome to leave a message for us, let us meet tomorrow, I wish you a happy and happy today!
参考资料：文字：百度；图片：微博；翻译：百度翻译
本文由LearningYard新学苑原创，部分图片文字来自网络，如有侵权请联系。