Bifalgorithm post · Infotech governance policy ethics and law · Appendix C: Common scenarios
Client Requirements
Client Requirements (Infotech governance policy ethics and law · Appendix C: Common scenarios) — "Software development companies with an idea for a software pr…
Ideas in this flowchart
- Client-financed software development creates obligations concerning reuse, requirements, and responsibility.
- A developer may seek a client to finance a product that will later be sold to the client’s competitors.
- The developer may offer a discount to secure the deal, although receiving full price would be preferable.
- The client understands that their funding may also benefit competing companies.
- The client may rely on a non-disclosure agreement, but that trust can prove misplaced.
- During development, the client may request additional or specific software requirements.
- The developer is likely to reject requests that do not fit the developer’s product strategy.
- A developer has explicitly rejected a client request on the grounds that it conflicted with development strategy.
- A client who pays for software is entitled to receive what they are paying for.
- If the developer chooses a different direction, that work should be done at the developer’s own expense and on their own time.
