Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC TR 29110-5-1-3: Systems and Software Engineering — VSE — Part 5-1-3: Management and Engineering Guide
ISO/IEC TR 29110-5-1-3 provides detailed management and engineering guidance for Very Small Entities (VSEs) implementing the ISO/IEC 29110 Basic profile. This Technical Report is the most operationally focused document in the 29110 family, offering step-by-step guidance for project management and software implementation processes. It translates the high-level process requirements from the framework into concrete, actionable practices that VSEs can apply directly to their projects.
💡 Key Insight: Unlike generic process standards that tell VSEs what to do without explaining how, ISO/IEC TR 29110-5-1-3 provides detailed implementation guidance including work product templates, activity descriptions, role assignments, and quality criteria — everything a VSE needs to operationalize the Basic profile.
1. Project Management Process
The project management process defined in ISO/IEC TR 29110-5-1-3 covers the full project lifecycle from initiation to closure. The process is organized into five key activities: Project Planning, Project Plan Execution, Project Assessment and Control, Project Closure, and Measurement. Each activity is described with specific tasks, work products, and quality criteria tailored for VSEs.
Project Planning includes defining project scope, identifying deliverables, estimating effort and cost, scheduling tasks, identifying risks, and allocating resources. The guide provides a simplified work breakdown structure (WBS) template appropriate for VSE projects, along with estimation guidelines based on historical data or analogy. Risk management is streamlined to focus on the top five to ten risks that typically affect VSE projects, such as staff turnover, requirement volatility, and technology uncertainty.
| Activity | Key Tasks | Work Products | Quality Criteria |
|---|---|---|---|
| Project Planning | Scope definition, estimation, scheduling, risk identification | Project Plan, Risk Register | Plan is reviewed and approved |
| Plan Execution | Task assignment, progress tracking, communication | Progress Records, Meeting Minutes | Tasks tracked against plan |
| Assessment & Control | Status reviews, corrective action, change management | Status Reports, Change Requests | Corrective actions defined |
| Project Closure | Delivery acceptance, lessons learned, archive | Acceptance Record, Lessons Learned | Customer acceptance obtained |
⚠️ Engineering Consideration: For VSEs, the project manager role is often combined with technical roles. The guide provides specific guidance on managing this role combination, including time allocation recommendations (e.g., 20-30% of effort dedicated to management activities for a typical VSE project manager) and techniques for switching context between management and technical tasks.
2. Software Implementation Process
The software implementation process covers the technical activities required to develop and deliver software products. It includes six activities: Software Requirements Analysis, Software Architectural Design, Software Detailed Design, Software Construction, Software Integration and Testing, and Product Delivery. The process is designed to be tailorable — VSEs can adjust the level of formality based on project criticality and size.
Software Requirements Analysis focuses on eliciting, analyzing, specifying, and validating requirements. The guide provides a simplified requirements specification template with sections for functional requirements, performance requirements, interface requirements, and quality attribute requirements. It also provides guidance on requirements prioritization using a simple MoSCoW (Must-have, Should-have, Could-have, Won’t-have) framework.
Software Architectural Design addresses the high-level structure of the software system. For VSEs, the guide recommends using informal architectural descriptions (e.g., box-and-line diagrams) supplemented by a component responsibility document. Detailed Design covers module-level design decisions, with the level of detail determined by the complexity of the module and the experience of the developer who will implement it.
| Activity | Inputs | Outputs | Typical Effort |
|---|---|---|---|
| Requirements Analysis | Customer needs, requirements | Software Requirements Specification | 10-20% |
| Architectural Design | Requirements specification | Architecture Description | 5-15% |
| Detailed Design | Architecture, requirements | Design Document | 10-20% |
| Construction | Design, coding standards | Source Code, Unit Tests | 30-40% |
| Integration & Testing | Software components, test plan | Test Reports, Integrated Software | 15-25% |
| Product Delivery | Tested software, user docs | Deployed Product, Delivery Note | 5-10% |
✅ Best Practice: Implement a simplified version of the software implementation process initially — focus on requirements analysis, construction with peer reviews, and product delivery. Add architectural design and formal integration testing in subsequent projects as the team matures. This incremental approach reduces the initial adoption barrier while building toward a complete engineering process.
3. Engineering Design Insights and Practical Applications
ISO/IEC TR 29110-5-1-3 is extensively used in VSE environments worldwide. The practical templates and checklists have been adopted by hundreds of small software companies, particularly in Latin America, Southeast Asia, and Eastern Europe where VSEs form the majority of the software industry. The guide’s emphasis on practicality over ceremony resonates with entrepreneurs and technical leads who need process benefits without process overhead.
One of the most valued aspects of the guide is its treatment of verification and validation in the VSE context. Recognizing that VSEs typically cannot afford dedicated test teams, the guide provides techniques for developer-led testing (unit testing, peer reviews), customer-involved validation (prototype demonstrations, acceptance testing), and automated testing where feasible. It also offers guidance on test documentation that scales from informal test notes for simple projects to structured test plans for critical projects.
From a continuous improvement perspective, the guide includes a lightweight measurement framework. Key metrics recommended for VSEs include: effort variance (planned vs. actual), schedule variance, defect density (defects per function point or per story point), and customer satisfaction. The guide provides simple data collection templates and guidance on using metrics for process improvement without creating a measurement bureaucracy.
🚨 Critical Warning: Do not treat the templates and checklists in ISO/IEC TR 29110-5-1-3 as rigid prescriptions. They are starting points that must be adapted to your VSE’s specific context. The most successful VSE adopters customize the templates after one or two project cycles, removing elements that do not add value and adding elements that address their specific challenges. Process ownership is more important than process compliance.
Frequently Asked Questions
Q1: Can ISO/IEC TR 29110-5-1-3 be used with Agile development methods?
Yes. The management and engineering guide is methodology-neutral. The project management activities can be mapped to Scrum events (sprint planning to Project Planning, sprint review to Assessment and Control, etc.), and the software implementation activities align well with Agile technical practices such as test-driven development, continuous integration, and iterative delivery.
Q2: How much effort is required to implement the Basic profile using this guide?
Based on reported case studies, VSEs typically require 4-8 weeks to implement the Basic profile for the first time, with approximately 200-400 person-hours of effort depending on the starting maturity level. Subsequent projects benefit from reusable templates and established practices, reducing implementation effort significantly.
Q3: Does the guide cover documentation requirements for regulatory compliance?
The guide provides baseline documentation that satisfies general quality management requirements. For domain-specific regulatory compliance (e.g., medical device software per IEC 62304, functional safety per IEC 61508), additional documentation beyond the guide’s recommendations will be necessary. However, the guide’s work products provide a solid foundation that can be extended for regulatory purposes.
Q4: What tools are recommended for implementing the management and engineering processes?
The guide is tool-agnostic. For VSEs, lightweight tools are recommended: spreadsheet-based project tracking, version control systems (Git), issue trackers, and documentation wikis. The key principle is that tools should support the process without adding overhead. The guide provides tool selection criteria rather than prescribing specific products.
