Java知识分享网 - 轻松学习从此开始!    

Java知识分享网

        
AI编程,程序员挑战年入30~100万高级指南 - 职业规划
SpringBoot+SpringSecurity+Vue权限系统高级实战课程        

IDEA永久激活

Java微信小程序电商实战课程(SpringBoot+VUe)

     

AI人工智能学习大礼包

     

PyCharm永久激活

66套java实战课程无套路领取

     

Cursor+Claude AI编程 1天快速上手视频教程

     
当前位置: 主页 > Java文档 > Java基础相关 >

Software Engineering,9th Edition PDF 下载


时间:2024-03-01 09:57来源:http://www.java1234.com 作者:转载  侵权举报
Software Engineering,9th Edition
失效链接处理
Software Engineering,9th Edition PDF 下载
 
 
相关截图:
 


主要内容:


Requirements elicitation and analysis may involve a variety of different kinds of
people in an organization. A system stakeholder is anyone who should have some
direct or indirect influence on the system requirements. Stakeholders include end
users who will interact with the system and anyone else in an organization who will
be affected by it. Other system stakeholders might be engineers who are developing
or maintaining other related systems, business managers, domain experts, and trade
union representatives.
A process model of the elicitation and analysis process is shown in Figure 4.13.
Each organization will have its own version or instantiation of this general model
depending on local factors such as the expertise of the staff, the type of system being
developed, the standards used, etc.
The process activities are:
1.
Requirements discovery This is the process of interacting with stakeholders of the
system to discover their requirements. Domain requirements from stakeholders and
documentation are also discovered during this activity. There are several comple
mentary techniques that can be used for requirements discovery, which I discuss
later in this section.
2.
Requirements classification and organization This activity takes the unstruc
tured collection of requirements, groups related requirements, and organizes
them into coherent clusters. The most common way of grouping requirements is
to use a model of the system architecture to identify sub-systems and to associ
ate requirements with each sub-system. In practice, requirements engineering
and architectural design cannot be completely separate activities.
3.
Requirements prioritization and negotiation Inevitably, when multiple stake
holders are involved, requirements will conflict. This activity is concerned with
prioritizing requirements and finding and resolving requirements conflicts
through negotiation. Usually, stakeholders have to meet to resolve differences
and agree on compromise requirements.

 

 
 
------分隔线----------------------------


锋哥推荐