ISO IEC 29110-4-1 pdf download

ISO IEC 29110-4-1 pdf download.Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs)
1 Scope
The ISO/IEC 29110 series is applicable to Very Small Entities (VSEs). VSEs are enterprises, organizations, departments or projects having up to 25 people. The lifecycle processes described in the ISO/IEC 29110 series are not intended to preclude or discourage their use by larger organizations than VSEs. The lifecycle processes defined in the ISO/IEC 29110 series can be used by VSEs when using, as well as when creating and supplying, a software system. They can be applied at any level in a software system’s structure and at any stage in the lifecycle. The processes described in the ISO/IEC 29110 series are not intended to preclude or discourage the use of additional processes that VSEs find useful. This document is not intended to preclude the use of different life cycles such as: waterfall, iterative, incremental, evolutionary or agile. This document provides a profile specification for the Basic profile. The Basic profile applies to VSEs involved in software development. It selects ISO/IEC/IEEE 12207 project management and software implementation process elements from the single project perspective. This document provides the normative and informative links to the subset of ISO/IEC/IEEE 12207.
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions For the purposes of this document, the terms and definitions given in ISO/IEC 29110-2-1 apply. ISO and IEC maintain terminological databases for use in standardization at the following addresses: — IEC Electropedia: available at http: //www .electropedia .org/ — ISO Online browsing platform: available at https: //www .iso .org/obp
4 Conformance
4.1 Conformance situations This document can be implemented by organizations or projects implementing and using the processes required by this document. Therefore, organizations can claim conformance to this document. This document does not contain any requirements applicable to products that facilitate its implementation and its use within organizations. Therefore, conformance cannot be claimed by developers of products. NOTE Examples of such products are methods, courses, teaching aids, tools, and forms. This document can be attested by a third party. It can be mandated as part of procurement and contractual processes. 4.2 Conformance to this document A VSE that claims conformance to the profile specified in this document shall identify the Software Engineering Basic Profile as the profile it has implemented. It can claim conformance to the process part of the profile if it meets all the mandatory profile process requirements as identified in its specification Clause 7, and the associated properties and requirements as described in the base standards when applicable. NOTE Requirements of this document are mandatory and use the word “shall”.
7 Basic profile specifications
7.1 Introduction This clause contains the specification of the standardized profile requirements. It contains the specification for the following profile elements: — in 7.2, Project Management process; and — in 7.3, Software Implementation process. The requirements are expressed in the form of process descriptions following ISO/IEC 29110-2-1 and ISO/IEC 33004 requirements. NOTE The process outcomes are not declared in present tense so they can be used for different conformity assessment schemas, e.g. auditing purposes or process capability and organizational maturity. These requirements are the result of Project Management and Software Implementation purpose achievement. Annex A specifies the references between the standardized profile elements and the source standards. Annex B gives additional information on the Process Reference Model for the VSE Basic Profile. 7.2 Project Management process specification 7.2.1 Project Management purpose The purpose of the Project Management process is to establish and carry out in a systematic way the tasks of the software implementation project, which allows complying with the project’s scope, in the expected quality, time and costs.