This document is applicable to Very Small Entities (VSEs). VSEs are enterprises, organisations, departments or projects having up to 25 people. The life cycle processes described in the set of International Standards (IS) and Technical Reports (TR) are not intended to preclude or discourage their use by organisations bigger than VSEs.<\/p>\n
The Advanced profile is the fourth profile of a four-profile software engineering roadmap (i.e. Entry, Basic, Intermediate and Advanced). This document describes processes targeted at VSEs that want to sustain and grow as an independent competitive software development business.<\/p>\n
ISO\/IEC 29110\u20114\u20111 identifies the requirements applicable to the tasks and work products described in this document.<\/p>\n
These guidelines apply to VSEs that develop non-critical software.<\/p>\n
Using these guidelines, VSEs can obtain the following benefits:<\/p>\n
management and monitoring of more than one project in parallel with more than one work team;<\/p>\n<\/li>\n
reuse of existing software components (e.g. code and document) in new projects;<\/p>\n<\/li>\n
continuous measurement and evaluation of projects;<\/p>\n<\/li>\n
continuous evaluation and improvement processes;<\/p>\n<\/li>\n
continuous sustainability and growth; and<\/p>\n<\/li>\n
support to customers in the disposal of software and installation of new software.<\/p>\n<\/li>\n<\/ul>\n
Once the software, developed by a VSE, has been accepted by their customer, the VSE that wants to provide after-delivery services can refer to ISO\/IEC TR 29110\u20115\u20113.<\/p>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 2<\/td>\n | National foreword <\/td>\n<\/tr>\n | ||||||
| 7<\/td>\n | Foreword <\/td>\n<\/tr>\n | ||||||
| 8<\/td>\n | Introduction <\/td>\n<\/tr>\n | ||||||
| 11<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
| 12<\/td>\n | 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
| 13<\/td>\n | 4 Conventions and abbreviated terms 4.1 Naming, diagramming and definition conventions <\/td>\n<\/tr>\n | ||||||
| 15<\/td>\n | 4.2 Notation used to document new processes, additions and modifications to the Intermediate profile processes <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | 4.3 Abbreviated terms 5 Overview <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | 6 Business Management (BM) process 6.1 BM purpose 6.2 BM objectives 6.3 BM input work products 6.4 BM output work products <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | 6.5 BM internal work products 6.6 BM roles involved 6.7 BM Process Description 6.7.1 BM Diagram <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | 6.7.2 BM activities <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | 6.7.3 BM incorporation to the Organisational Repository <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | 7 Project Management (PM) process 7.1 PM purpose 7.2 PM objectives <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | 7.3 PM input work products 7.4 PM output work products 7.5 PM internal work products <\/td>\n<\/tr>\n | ||||||
| 29<\/td>\n | 7.6 PM roles involved 7.7 PM Process Description 7.7.1 PM Diagram <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | 7.7.2 PM activities <\/td>\n<\/tr>\n | ||||||
| 36<\/td>\n | 7.7.3 PM incorporation to Project Repository <\/td>\n<\/tr>\n | ||||||
| 37<\/td>\n | 8 Software Implementation (SI) process 8.1 SI purpose 8.2 SI objectives 8.3 SI input work products <\/td>\n<\/tr>\n | ||||||
| 38<\/td>\n | 8.4 SI output work products 8.5 SI internal work products 8.6 SI roles involved <\/td>\n<\/tr>\n | ||||||
| 39<\/td>\n | 8.7 SI Process description 8.7.1 SI diagram 8.7.2 SI activities <\/td>\n<\/tr>\n | ||||||
| 47<\/td>\n | 8.7.3 SI incorporation to the Project Repository <\/td>\n<\/tr>\n | ||||||
| 48<\/td>\n | 9 Acquisition Management process (AM) 9.1 AM purpose 9.2 AM objective 9.3 AM input work products 9.4 AM output work products 9.5 AM internal work products 9.6 AM roles involved <\/td>\n<\/tr>\n | ||||||
| 49<\/td>\n | 9.7 AM Process description 9.7.1 AM Diagram 9.7.2 AM activities <\/td>\n<\/tr>\n | ||||||
| 51<\/td>\n | 9.7.3 AM incorporation to the Project Repository 10 Software Transition and Disposal process (STD) 10.1 STD purpose <\/td>\n<\/tr>\n | ||||||
| 52<\/td>\n | 10.2 STD objectives 10.3 STD input work products 10.4 STD output work products 10.5 STD internal work products 10.6 STD roles involved <\/td>\n<\/tr>\n | ||||||
| 53<\/td>\n | 10.7 STD process description 10.7.1 STD Diagram 10.7.2 STD activities <\/td>\n<\/tr>\n | ||||||
| 56<\/td>\n | 10.7.3 STD Incorporation to the Project Repository <\/td>\n<\/tr>\n | ||||||
| 57<\/td>\n | 11 Roles <\/td>\n<\/tr>\n | ||||||
| 58<\/td>\n | 12 Work product description <\/td>\n<\/tr>\n | ||||||
| 79<\/td>\n | 13 Software tools requirements 13.1 General 13.2 Business Management process <\/td>\n<\/tr>\n | ||||||
| 80<\/td>\n | 13.3 Project Management process 13.4 Software Implementation process 13.5 Acquisition Management (AM) process (conditional process) 13.6 Software Transition and Disposal (STD) process (conditional process) <\/td>\n<\/tr>\n | ||||||
| 81<\/td>\n | Annex A (informative) Software Engineering Deployment Packages <\/td>\n<\/tr>\n | ||||||
| 83<\/td>\n | Annex B (informative) Mapping between the objectives of ISO\/IEC TR 29110\u20115\u20111-4 and ISO\/IEC\/IEEE 12207 and ISO 9001:2015 <\/td>\n<\/tr>\n | ||||||
| 103<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Software and systems engineering. Lifecycle profiles for very small entities (VSEs) – Software engineering. Management and engineering guidelines. Generic profile group. Advanced profile<\/b><\/p>\n |