IEEE Industry Implementation of International Standard Iso/iec (iso/iec ) Standard for Information Technology – Software Life . ISO/IEC provides a common framework for developing and managing software. IEEE/EIA consists of the clarifications, additions, and changes . Provide an introduction to The IEEE Software Engineering. Standards Committee (SESC) . IEEE/EIA , Implementation. Considerations. ◇ Industry.
|Published (Last):||14 June 2013|
|PDF File Size:||8.47 Mb|
|ePub File Size:||11.53 Mb|
|Price:||Free* [*Free Regsitration Required]|
This harmonization of the two standards led to the removal of separate software development and software reuse processes, bringing the total number of processes from 43 down to the 30 processes defined in It also caused changes to the quality management and quality assurance process activities and outcomes.
Additionally, the definition of ” audit ” and related audit 12207.2 were updated. The standard establishes a set of 122077.2 for managing the lifecycle of software. The standard “does not prescribe a specific software life cycle model, development methodologymethod, modelling approach, or technique.
Stages aka phases are not the same as processes, and this standard only defines specific processes – it does not define any particular stages. Instead, the standard acknowledges that software life cycles vary, and may be divided into stages also called phases that represent major life cycle periods and give rise to primary decision gates.
No particular set of stages is normative, but it does mention two examples:. The life cycle processes the standard defines are not aligned to any specific stage in a software life cycle. Indeed, the life cycle processes that involve planning, performance, and evaluation “should be considered for use at every stage”.
In practice, processes occur whenever they are needed within any stage. Acquisition covers all the activities involved in initiating a project. The acquisition phase can be divided into different activities and deliverables that are completed 1220.2. During the supply phase a project management plan is developed.
This plan contains information about the project such as different milestones that need to be reached. Detailed here are life cycle model management, infrastructure management, portfolio managementhuman resource managementquality management, and knowledge management processes. Life cycle mode management helps ensure acquisition and supply efforts are supported, while infrastructure and portfolio management supports business and project-specific initiatives during the entire system life cycle.
The rest ensure the necessary iwee and quality controls are in place to support the business’ project and system endeavors. If an organization does not have an appropriate set of organizational processes, a project executed by the organization may apply those processes directly to the project instead.
These processes deal with planning, assessment, and control of software and other projects during the life cycle, ensuring quality along the way. The full list includes   :. These processes involve technical activities and personnel information technologytroubleshooters, software specialists, etc.
The analysis and definition processes early on set the stage for how software and projects are implemented. Additional processes of integration, verification, transition, and validation help ensure quality iewe readiness.
The operation and maintenance phases occur ieeee, with the operation phase consisting of activities like assisting users in working with the implemented software product, and the maintenance phase consisting of maintenance tasks to keep the product up and running.
ISO/IEC – Wikipedia
Clause 4 describes the document’s intended use and conformance requirements. It is expected that particular projects “may not need to use all of the processes provided by this document. This can be done through either “full conformance” or “tailored conformance”.
The latter permits more variation. From Wikipedia, the free encyclopedia. International Organization for Standardization. Retrieved 21 June Software Engineering Standards for Quality”. American Society for Quality.
Retrieved 22 June Standard for Information Technology”. Archived from the original on 30 December ISO standards by standard number.