BN Digital – Standard Software Development Procedures (Summary)
Scope & Objective
- Applies to hourly or budget-capped engineering engagements.
- Primary goal: convert business requirements into code, configurations, and assets.
- BN Digital adapts procedures to client needs and provides technical guidance.
General Engineering
BN Digital allocates focused professional time for:
- Reading and analysing documentation
- Problem-solving and architectural decisions
- Writing, reviewing, and testing code
- Team consultation on project topics
BN Digital ensures:
- Staff have appropriate skills
- Time is dedicated solely to the project while engaged
- Proper equipment and tools are used
Front-end Development
- Mockups are guidance unless explicitly stated as binding in writing.
- Wireframes are supplementary, not binding requirements.
- Where behaviour is unspecified, implementation follows professional judgement.
- Minor visual deviations due to browser constraints, rendering differences, or professional judgement are not considered defects.
Back-end Development
- Provided business logic is guidance unless explicitly stated as binding in writing.
- Non-functional requirements are implemented on a best-effort basis using professional capabilities and best practices.
- Technical limitations are communicated with proposed adaptations.
- No performance warranties (e.g. response time, throughput) unless explicitly defined, tested, and agreed in writing.
Client Responsibilities
Clients are responsible for:
- Providing clear, documented requirements before or during the engagement
- Reviewing and approving deliverables within agreed or reasonable timeframes
- Responding promptly to technical questions (unresponsiveness may cause billable idle time)
- Managing production environments, deployment pipelines, and live infrastructure
- Ensuring client-provided data, content, and business logic do not infringe third-party rights
Delays caused by the client’s failure to meet these responsibilities:
- Are not attributable to BN Digital
- Do not entitle the client to refunds or deadline adjustments
Acceptance of Deliverables
Deliverables (features, modules, codebases) are considered accepted when:
- The client approves them in writing, or
- Five (5) business days pass after delivery without documented objection, or
- The client continues to use the delivered software.
Post-acceptance:
- Changes are treated as new scope and estimated separately.
- BN Digital is not responsible for:
- Defects the client did not raise during the review period
- Issues introduced by client-side modifications after handover
Intellectual Property
Client-Owned Outcomes
- Upon full payment, the client owns all rights in original code and configurations created specifically for the client under the engagement.
Pre-existing IP
- BN Digital retains ownership of all pre-existing IP, frameworks, utilities, and internal tools.
- Where such IP is incorporated into deliverables, the client receives a non-exclusive, perpetual licence to use it as part of the delivered codebase.
Open-source & Third-party Components
- Deliverables may include open-source and third-party packages.
- These remain governed by their own licences (e.g. MIT, Apache 2.0, GPL).
- BN Digital uses commercially reasonable efforts to choose permissive licences but does not guarantee absence of licence restrictions.
- The client is responsible for any licence compliance review needed for their use case (including commercial distribution or SaaS).
Client-provided Materials
- The client warrants that all provided data, content, and third-party code are free of IP encumbrances or that they hold appropriate rights.
- The client indemnifies BN Digital against third-party claims arising from authorised use of client-provided materials.
Security
- BN Digital applies industry-standard security practices during development.
- No warranty that software is free of vulnerabilities.
- The client is responsible for:
- Security audits
- Penetration testing
- Ongoing security monitoring of production systems
If BN Digital identifies a material vulnerability during the engagement:
- It will notify the client in writing.
- Remediation of vulnerabilities identified after handover is out of default scope and billed separately.
What’s Not Included (by Default)
Outside default scope unless explicitly agreed in writing:
Content Management
- Content creation
- Initial and ongoing content population and management