In such instances, the system analyst might decide to validate only those features whose sureness factor is at or above a specific limit — say 80 percent — as firm requirements.
在这样的实例中,系统分析人员可能会决定只确认那些确信因子在或高于一个具体限制——比方说80%——的特性作为确定的需求。
The system analyst is 75 percent sure that the marketing analyst actually wants to join the customer company, and therefore might be promoting this feature for her future benefit.
系统分析人员75%确定,市场分析人员实际上想要加入客户公司,并因此可能为她的未来利益而促进该特性。
A system analyst refers to an information specialist who performs system analysis, design, and implementation.
系统分析员是指从事系统分析、设计和执行的信息专业人士。
Its basic function is to assist system analyst to analyze the requirement of the developed system, and to get an intact and accurate software requirement specification which is made up of Data Fl.
需求分析工具用于软件工程的需求分析阶段,它的基本功能是辅助系统分析人员对开发的系统需求进行分析,最终得到由数据流图和数据字典组成的完整而准确的软件需求规约。
The system Analyst converts business requirements into requirements on the IT systems.
系统分析人员将业务需求转换为对IT系统的要求。
The Enterprise Architect, Business Analyst, and System Analyst are the roles that identify, prioritize, and group these needs into projects.
企业架构师、业务分析人员和系统分析人员就是对这些需求进行标识、确定优先级并将其分组为项目的角色。
This requires a change to the it systems, so the Business Analyst works with the system Analyst to look at the feasibility of supporting this new offering.
这需要对IT系统进行更改,因此业务分析人员与系统分析人员一起分析支持此新服务的可行性。
After talking to the Business Analyst, the System Analyst realizes that this new offering requires a consistent means to access the organization's customer data.
与业务分析人员交流之后,系统分析人员认识到,这个新服务要求采用一致的方式访问组织的客户数据。
To effectively integrate PBR with RUP, we elaborate new scenarios corresponding to the actors in the RUP's Requirements discipline: System Analyst, Requirements Specifier, and Software Architect.
为了有效地整合PBR和RUP,我们在 RUP的需求规程中精心制作了新的与参与者相应的场景:系统分析师,需求阐释员和软件构架师。
To effectively integrate PBR with RUP, we elaborate new scenarios corresponding to the actors in the RUP's Requirements discipline: System Analyst, Requirements Specifier, and Software Architect.
为了有效地整合PBR和RUP,我们在 RUP的需求规程中精心制作了新的与参与者相应的场景:系统分析师,需求阐释员和软件构架师。
应用推荐