About me

Calendar

Search

Recent Articles

Recent Comments

Links

Statistics

Support


Except where otherwise noted, this site is licensed under a Creative Commons License.
除特别说明,本站所有内容都遵循创作共用协议.

About ADS

 

 
给我留言My Guestbook  我的照片My Photo  友情提示您,当前时间为:

关于CMMI 术语的翻译

[ 2006/7/3 14:19:00 | ]

最近研究CMMI总是遇到 stakeholder (n.赌金保管者;利害关系人)这个词,转了一篇介绍财务用词的文章。

 

stakeholder   n. 利害关系人
mock up  n. 模型(工程上的),原型(强调对目标的一个模拟)

 

ACCA Paper 2.4 Financial Management and Control Chapter 3Foulks Lynch)里面有这一段:A stakeholder is someone with an interest in what the organisation does。然后除了股东(Shareholder),课本还列举了一家公司的stakeholder通常还包含哪些:
The commnity at large
普罗大众
Company managers/directors
公司管理层
Company employees
公司员工
Customers
顾客
Suppliers
供货商
Finance providers
贷款人
The government 
政府
可以看出,stakeholder的中文应该翻译成利害关系人,也就是说一家公司的运作并不止涉及到它的股东的利益。

那么一家accounting firmstakeholder应该包含哪些呢?我认为至少有以下几个:
Parnters
合伙人,角色相当于股东
Investors 
投资者,主要针对上市公司而言,个人身份的投资者也就是股民
The commnity at large
普罗大众,这是对公共企业而言,例如电力、地铁等,涉及民众的日常生活
Company employees
公司员工,因为所有权和管理权没有分开,所以managerdirector也相当于一般员工
Clients
客户
The goverment
政府

但是公司的经营没可能同时满足所有stakeholder的要求,所以通常是以损害或牺牲其它stakeholder的利益为前提而达到个别stakeholder的目的。

以下是一篇伦敦金融时报的评论。在这个事件里面又是保护了谁的利益,而损害了谁的利益呢?

金融时报: 安永是否记得独立的重要

  安永(Ernst & Young)忘记独立的重要性了吗?这家国际会计师事务所本月发布的一份报告显示,中国四大国有银行的不良贷款已达令人瞠目的3580亿美元。中国政府对此予以驳斥。安永上周末撤回了报告。

  除了在北京之外,这份报告几乎没有引起什么波澜。安永得出的结论,与其它考察中国不良贷款的独立顾问机构(其中包括普华永道)得出的结论大同小异 。其实,就连温吞水般的国际货币基金组织(International Monetary Fund)也指出,中国银行分支机构的借贷标准有许多不足之处——这意味着,更多的不良贷款正在形成之中。正值此时,安永将总数算了出来。

  因此,可以说,撤回报告的意义更为重大。安永的辩词是,3580亿美元的总额实际上缺乏事实依据……该资料估计有误。这份报告没有经过全面的内部审查程序。这可不是小事一桩,因为它削弱了安永众多调查报告本身的可信度,也损害了这份报告作者的信誉。然而,考虑到该报告作者在业内受到普遍尊重,以及安永已发布成百上千份报告的事实,我们有理由认为,尽职调查(due diligence)过程几乎是理所当然的。

  这样,人们难免认为,作为中国工商银行的审计机构,安永是在采取一种绥靖政策。安永撤回报告必然会取悦北京,中国政府正打算通过下个月中国银行(Bank of China)的上市从外国投资者手中筹集100亿美元资金。但涉嫌扼制不同观点最终会对中国不利。在一个政府无处不在的国家里,独立报告为投资者提供了一种至关重要的安慰与把关。微软(Microsoft)和谷歌(Google)等科技公司已在中国签订了浮士德契约。如果顾问公司感到他们也不得不这样做的话,那就太令人遗憾了。

 

Project Stakeholder的权力和职责
 


Project Stakeholder Rights
The rights of project stakeholders are:
1)To have developers learn about their business and objectives.
2)To expect developers to learn and speak their language.
3)To expect developers to identify and understand their requirements.
4)To receive explanations of artifacts that developers use as part of working with project stakeholders, such as models they create with them (e.g. user stories or essential UI prototypes), or artifacts that they present to them (e.g. UML deployment diagrams).
5)To expect developers to treat them with respect.
6)To hear ideas and alternatives for requirements.
7)To describe characteristics which make the product easy to use.
8)To be presented with opportunities to adjust requirements to permit reuse, reduce development time, or to reduce development costs.
9)To be given good-faith estimates.
10)To receive a system that meets their functional and quality needs.
11)To determine how their resources will be spent by the project team, including the extent of the investment in permanent documentation.


Project Stakeholder Responsibilities
The responsibilities of project stakeholders are:
1)To provide resources (time, money, ? to the project team.
2)To educate developers about their business.
3)To spend the time to provide and clarify requirements.
4)To be specific and precise about requirements.
5)To make timely decisions.
6)To respect a developer's assessment of cost and feasibility.
7)To set requirement priorities.
8)To review and provide timely feedback regarding relevant work artifacts of developers.
9)To promptly communicate changes to requirements.
10)To own your organization's software processes, to both follow them and actively help to fix them when needed.


Re:关于CMMI 术语的翻译

[ 2006/7/3 14:37:00 | ]
权力和职责基本是平衡的
               
(重新配对^_^)
 

The rights and responsibilities of project stakeholders are:

To have developers learn about their business and objectives.
To expect developers to learn and speak their language.
Must educate developers about their business.

To expect developers to identify and understand their requirements.
Must spend the time to provide and clarify requirements.

To receive explanations of artifacts that developers use as part of working with project stakeholders, such as models they create with them (e.g. user stories or essential UI prototypes), or artifacts that they present to them (e.g. UML deployment diagrams).
Must be specific and precise about requirements.

To expect developers to treat them with respect.
Must respect a developer's assessment of cost and feasibility.

To hear ideas and alternatives for requirements.
Must make timely decisions.

To describe characteristics which make the product easy to use.
Must promptly communicate changes to requirements.

To be presented with opportunities to adjust requirements to permit reuse, reduce development time, or to reduce development costs.
Must review and provide timely feedback regarding relevant work artifacts of developers.

To be given good-faith estimates.
Must set requirement priorities. //有点牵强

To receive a system that meets their functional and quality needs.
Must own your organization's software processes, to both follow them and actively help to fix them when needed.

To determine how their resources will be spent by the project team, including the extent of the investment in permanent documentation.
Must provide resources (time, money, ? to the project team.


发表评论:

    昵称:
    密码:
    主页:
    标题:
  • 本博客由放飞思想提供免费服务
  • www.flyidea.cn 放飞思想,成就未来
  • 本博客内部所有文章如需转载,请联系原作者或转载前作者