In the context of this Model, a Developer is a Stakeholder that

designs a solution Component or Dialog or Interface,
builds a solution Component and/or Dialog and/or Interface,
tests a solution Component and/or Dialog and/or Interface,
serves as an official Source of development Estimates.

Discussion

There are potentially several kinds of developer. They generally develop (or guide, or manage the development of) software solutions. Sometimes their responsibilities (and thus their interests) are combined in a single person or role within an organization. The following table lists representative solution developers, their Interests, and related quality Concerns.

Developers	Interests	Concerns
Component Developers	Usage, Knowledge, Behavior, Quality, Priority	Fitness, Simplicity, Flexibility, Adaptability, Modularity, Coverage, Completeness, Compatibility, Measurability, Efficiency
Component Designers	Usage, Knowledge, Behavior, Quality, Priority	Fitness, Simplicity, Flexibility, Adaptability, Modularity, Compatibility, Measurability, Efficiency
Interface Designers	Usage, Knowledge, Behavior, Quality, Priority	Intelligibility, Functionality, Usability, Sufficiency, Affordability, Efficiency
QA Engineers	Usage, Knowledge, Behavior, Quality, Priority	Sufficiency, Coverage, Completeness, Intelligibility, Alignment
Requirements Engineers	Needs, Usage, Knowledge, Behavior, Quality, Priority	Intelligibility, Sufficiency, Coverage, Completeness, Alignment
Solution Architects	Large-Scale Structures, Standards, Conventions, Compliance	Fitness, Flexibility, Adaptability, Modularity, Compatibility, Measurability, Scalability, Reliability, Availability, Efficiency
Project Managers	Priority, Schedules, Budgets, Resources, Knowledge	Feasibility, Availability, Scalability, Measurability, Affordability, Speed, Efficiency

---

Copyright 2003,2020 Nikolas S. Boyd.

Permission is granted to copy this document provided this copyright statement is retained in all copies.