Software engineering is to create products, services, and processes that add value. People who contribute to the creation of these artifacts – analysts, process engineers, software engineers, testers, managers, executives – strive in their decisions and actions to maximize some simple or complex notion of value, whether consciously or unconsciously, and whether with respect to shared goals or to satisfy personal objectives. Alas, when value considerations remain implicit, the overall effect may very well be negative. Examples of undesirable consequences of implicit and clashing value perspectives abound. A good case in point is when developers value superior design, the marketing of new, nifty functionality, quality assurance “zero defects” and the management of short time-to-market. Value-based software engineering (VBSE) brings such value considerations to the foreground so that software engineering decisions at all levels can be optimized to meet or reconcile explicit objectives of the involved stakeholders, from marketing staff and business analysts to developers, architects, and quality experts, and from process and measurement experts to project managers and executives. In VBSE, decisions are not made in a setting blind to value perspectives, whether common or differing, of these project participants. Value-based software engineering (VBSE) brings such value considerations to the foreground so that software engineering decisions at all levels can be optimized to meet or reconcile explicit objectives of the involved stakeholders, from marketing staff and business analysts to developers, architects, and quality experts, and from process and measurement experts to project managers and executives. In VBSE, decisions are not made in a setting blind to value perspectives, whether common or differing, of these project participants.
Uploading links
Depositfiles links
Megaupload links
No comments:
Post a Comment