01
Business brief
Goals & acceptance
SOFTWARE DEVELOPMENT
Software built for business.
A team for what comes next.
From requirements to production, we help organizations design, build and deliver software with a clear process—and a team with more than 10 years of experience caring for customer websites.
SDLCISO/IEC 29110Code & documentation
FROM BUSINESS NEED TO OPERABLE SOFTWARE
Delivery overview · Illustrative process
02
Engineering
Design · build · test
03
Production
Approved release & handover
04
Long-term care
Operate & improve
Evidence travels with the workRequirement → Review → Test → Release
10+ years
Experience caring for customer websites, through launch and the changes that follow.
ISO/IEC 29110
Guides project management and software implementation, with reviewable work and deliverables.
Build → Run → Improve
Plan handover and care from the start, so the system has clear owners and a path forward.
BUILT AROUND YOUR BUSINESS
Software that fits
how your organization works.
Start with the work that needs to improve. Choose scope and technology around your users, data and the team that will operate it.
01
Business applications
Connect fragmented workflows
Internal tools, approval workflows and shared business data, with less duplicate work and role-based access.
02
Customer platforms
Serve customers and partners
Customer portals, business websites and service applications connected to back-office data and designed for the devices people use.
03
Integration & modernization
Evolve existing systems deliberately
Connect APIs and data across systems, assess legacy code and break improvements into testable, deliverable increments.
THE DELIVERY SYSTEM
Every phase has a purpose.
Every handover has evidence.
Ruk-Com’s six-phase service framework makes work, responsibilities and decisions visible. Adapt the delivery cadence to the project and iterate as needed.
SDLC process · Illustrative process
Select a phase to see its owners and deliverables below.
DeliveryFeedback & reworkApproval step
01
Discover & Plan
Align on the problem first
02
Architecture & Design
Design for the work and the existing systems
03
Build & Review
Build in increments with a clear trail
04
QA & UAT
Validate quality and business acceptance
05
Release & Handover
Release with a plan and a usable handover
06
Operate & Improve
Improve from real operational needs
Normal route: agree requirements → design → build → test → hand over → operate. Production release follows the agreed approval.
01
Discover & Plan
Understand users, workflows and constraints. Turn the brief into requirements and a backlog with acceptance criteria, then agree scope, risks and a delivery plan.
- Owner
- Business owner + PM / BA
- Deliverables
- Requirements · Scope · Acceptance criteria
- Review point
- Client confirms priorities, requirements and initial scope
02
Architecture & Design
Design user flows, UX/UI, data models and API contracts. Review integrations, access controls and architecture choices before implementation.
- Owner
- Product owner + Designer / Architect
- Deliverables
- UX flow · Data model · API contract
- Review point
- Review design and integration constraints together
03
Build & Review
Implement prioritized backlog items using branches, peer-reviewed pull requests, unit tests and change records. Link work back to its originating requirement.
- Owner
- Engineer + Code reviewer
- Deliverables
- Source code · Pull requests · Unit tests
- Review point
- Review code and test results before merging
04
QA & UAT
Run risk-based integration and regression tests. Business users perform UAT against agreed criteria. Record defects, return them for fixes and retest before acceptance.
- Owner
- QA + Business users
- Deliverables
- Test results · Defect log · UAT record
- Review point
- Accountable owners review UAT and outstanding issues
05
Release & Handover
Prepare release checklists, data migration and rollback plans appropriate to the system. Hand over repositories, documentation and knowledge. Production changes require the agreed approver.
- Owner
- Release owner + Client approver
- Deliverables
- Release notes · Runbook · Handover record
- Review point
- Approve the release, validation and rollback plan
06
Operate & Improve
Monitor and gather feedback within the support scope. Distinguish incidents, defects and change requests. Scope changes return to requirements, impact assessment and approval before a new iteration.
- Owner
- Service owner + Support / Engineering
- Deliverables
- Service log · Maintenance plan · Change request
- Review point
- Agree improvements and approve impacts before proceeding
Adapt agile or iterative delivery to your project while keeping requirements and deliverables traceable throughout.
PROCESS WITH ACCOUNTABILITY
ISO/IEC 29110.
From guidance to working practice.
Use Basic profile guidance to connect project management with software implementation, keeping business decisions and engineering work aligned.
PM
Project Management
Know what is being done, who owns it and which decisions need attention.
- Agree scope, plans and responsibilities.
- Review progress, risks and pending decisions.
- Assess change impacts before approval.
- Review deliverables and record acceptance.
Project plan · Progress record · Change log
SI
Software Implementation
Turn requirements into software that can be verified and handed over.
- Analyze requirements and design system components.
- Build, review code and control versions.
- Test against criteria and manage defects methodically.
- Prepare the software configuration and delivery package.
Requirements · Design · Code · Tests · Delivery
A traceable path through the work
Example evidence chain, not customer project data.
- Requirement
- Design
- Pull request
- Test result
- Release
Explore the official ISO/IEC 29110 series guidance.
QUALITY IS PART OF THE WORK
Quality and security.
Built into the process.
Agree risk-appropriate review criteria and retain evidence that business and technical teams can assess together.
Clear acceptance
Define expected behavior, data boundaries and error cases before development so UAT uses shared criteria.
Requirements → Test casesReviewed changes
Use version control and code review, separate environments and apply automated tests to important system behavior.
Pull request → Review → TestSecurity by scope
Consider access control, secret handling, dependencies and data flows. Define separate scope and authorization for deeper security assessments.
Access · Secrets · DependenciesRelease readiness
Review release checklists, backup and rollback arrangements for the work, with an approver and post-deployment validation plan.
Approve → Deploy → VerifyBUILT TO BE LOOKED AFTER
Launch is the beginning
of long-term care.
More than 10 years of experience caring for customer websites informs how we plan handover and maintenance alongside development—from access to ownership when issues arise.
Ongoing care · Illustrative process
01
Monitor
Signals & requests
02
Triage
Impact & ownership
03
Fix
Agreed-scope changes
04
Verify
Test & check impact
05
Approved deploy
Approve → deploy → validate
↳ After deployment, return to monitoring to validate and continue care.
Define routine care
and change work clearly.
Choose a care plan appropriate to your system. Agree environments, coverage hours, contact channels and responsibilities before service begins.
- Monitoring and request intake, prioritized by impact.
- Updates, backup and restore under an agreed, testable plan.
- Runbooks, access inventory and clear handover owners.
- Separate defect warranty from maintenance and new features.
People and Ruk-Com Agent work together
Ruk-Com Agent Agent assistance helps monitor and gather information for team review. Access and remediation follow agreed permissions, scope and approvals; production changes are not automatic.
A HANDOVER YOU CAN USE
Hand over more than features.
Give your team a way forward.
Define deliverables, source code rights and usage terms in the agreement, including open-source and third-party license constraints.
Code & configuration
Repositories, delivered versions and dependencies, with build and configuration instructions that keep secrets separate.
Documentation & evidence
Architecture, API and user documentation within scope, with test and UAT results, release notes and outstanding issues.
Knowledge & continuity
Transfer knowledge, runbooks and access records to accountable owners. Agree warranty terms and onward care before closure.
Start where you are
Whether you have a new idea, a project needing delivery capacity or an existing system needing care, we clarify the problem before proposing the work.
- DiscoverShare goals, current systems and constraints
- AgreeAgree scope, milestones, budget and acceptance
- DeliverReview regularly, hand over and support to plan
BEFORE WE BEGIN
Get aligned
before you build.
Clear agreements help business and technical teams make decisions from the same information.
What does ISO/IEC 29110 mean for our project?
We use Project Management and Software Implementation guidance to connect scope, requirements, reviews and deliverables, adapting the SDLC to the size and delivery approach of your project.
Do we need complete requirements before talking?
No. Start with your goals, users, existing systems and the problems you want to solve. Discovery helps identify priorities, constraints and acceptance criteria before estimating scope.
How are changes handled during delivery?
Record a change request and assess its impact on design, time, budget and testing together. After approval, update the backlog and plan. Added features are not automatically part of the original scope.
Who owns the source code, and what documents are delivered?
Agree code rights, repository access and deliverables in the contract before work starts, including open-source, library and third-party terms. Documentation and knowledge transfer are scoped around the receiving team.
What happens if UAT does not pass?
Record defects against agreed acceptance criteria, prioritize them and return them to engineering. Retest before the accountable owner considers acceptance. New requirements follow the change-request process.
Can you take over a system built by another team?
Begin by reviewing source code, stack, dependencies, access and documentation to assess risk and readiness before accepting scope. The engagement may start with an assessment or phased improvements.
What do warranty and ongoing care cover?
Define the duration, conditions and scope of the defect warranty. Monitoring, updates, backups, support and new features are agreed in the relevant service plan; they are not all included for the life of the system.
LET’S BUILD THE NEXT CHAPTER
Tell us what you need.
Let’s plan the way forward.
Share your systems, goals and timeline. We can assess a development and care scope that fits your organization.