Domain Processes

1. Domain Processes Know your customer.

2. Last Class - • "Life Cycles" • the process we will use to create the software product • This Class - • "Domain Processes" • how a company works • "Project Team" • what kinds of experts do we need help from

3. Why consider the Corporate Process? • The Critical Point of View is the End-User • the best software solutions come from understanding the customer's view of the world and addressing the customer's problems • war stories o'plenty

4. Why consider the Corporate Process? • Perceived Value is based on how well the software solves the customer's problem in their domain • Value is not entirely based on Quality • for example - Microsoft software crashes • Perceived Value ≠ Value • for example - Microsoft security holes costs millions of dollars

5. Why consider the Corporate Process? • Customer's take the Business View ($), not the computer science view • The system should revolve around the Company's Objectives

6. Question… • So who are the key players? • Who should we try to make happy?

7. People in the Process • Managers • Employees / Users • Company's Stock Holders • Consumers

8. Managers' Motivations • Return On Investment • Intangible Benefits • Market Strategy • meeting existing or expected demand • being the first to market • securing our niche in the market

9. Types of Software Products • business • biggest class • includes services • consumer • mass market / shrink wrap • price sensitive • industrial • real-time • really timely • scientific

10. Project Types • new software product • component integration • re-engineered product • heroic maintenance

11. Summary • We must understand the Company Process • We must recognize the key players and know their objectives • The type of product we are to produce dictates a lot of how we will produce it • Now that we have a good idea of the environment that we are dealing with, it is time to build a team and start planning