Software Engineering Body of Knowledge (v3) (2014) (811503), страница 92
Текст из файла (страница 92)
IDEF1X 97 is formallydefined in terms of first order logic. A procedureis given whereby any valid IDEF1X 97 modelcan be transformed into an equivalent theory infirst order logic. That procedure is then applied toa metamodel of IDEF1X 97 to define the valid setof IDEF1X 97 models.In recent years, the UML notation has becomepopular for modeling software-intensive systems.The next two standards provide two versions ofthe UML language.ISO/IEC 19501:2005 Information Technology—Open Distributed Processing—Unified ModelingLanguage (UML) Version 1.4.2ISO/IEC 19501 describes the Unified Modeling Language (UML), a graphical language forvisualizing, specifying, constructing, and documenting the artifacts of a software-intensive system. The UML offers a standard way to write asystem’s blueprints, including conceptual thingssuch as business processes and system functionsas well as concrete things such as programminglanguage statements, database schemas, and reusable software components.ISO/IEC 19505:2012 [two parts] Information Technology—Object Management Group Unified Modeling Language (OMG UML)ISO/IEC 19505 defines the Unified ModelingLanguage (UML), revision 2.
The objective ofUML is to provide system architects, softwareengineers, and software developers with tools foranalysis, design, and implementation of softwarebased systems as well as for modeling businessand similar processes.Two more standards build on the base of UMLto provide additional modeling capabilities:ISO/IEC 19506:2012 Information Technology—Object Management Group Architecture-DrivenModernization (ADM)—Knowledge DiscoveryMeta-Model (KDM)ISO/IEC 19506:2012 defines a metamodel for representing existing software assets, their associations, and operational environments, referred to asthe knowledge discovery metamodel (KDM). Thisis the first in the series of specifications related tosoftware assurance (SwA) and architecture-drivenmodernization (ADM) activities.
KDM facilitatesAppendix B B-19projects that involve existing software systemsby insuring interoperability and exchange of databetween tools provided by different vendors.ISO/IEC 19507:2012 Information Technology—Object Management Group Object Constraint Language (OCL)ISO/IEC 19507:2012 defines the Object Constraint Language (OCL), version 2.3.1. OCL version 2.3.1 is the version of OCL that is alignedwith UML 2.3 and MOF 2.0.Some organizations invest in software engineering environments (SEE) to assist in theconstruction of software. An SEE, per se, is nota replacement for sound processes.
However, asuitable SEE must support the processes thathave been chosen by the organization.ISO/IEC 15940:2006 Information Technology—Software Engineering Environment ServicesISO/IEC 15940:2006 defines software engineeringenvironment (SEE) services conceptually in a reference model that can be adapted to any SEEs to automate one or more software engineering activities.It describes services that support the process definitions as in ISO/IEC 12207 so that the set of SEEservices is compatible with ISO/IEC 12207. ISO/IEC 15940:2006 can be used either as a general reference or to define an automated software process.The selection of tooling for a software engineeringenvironment is itself a difficult task.
Two standardsprovide some assistance. ISO/IEC 14102:2008defines both a set of processes and a structured set ofcomputer-aided software engineering (CASE) toolcharacteristics for use in the technical evaluationand the ultimate selection of a CASE tool.IEEE Std. 14102-2010 Standard Adoption of ISO/IEC 14102:2008 Information Technology—Guideline for the Evaluation and Selection of CASE ToolsWithin systems and software engineering, computer-aided software engineering (CASE) toolsrepresent a major part of the supporting technologies used to develop and maintain information technology systems. Their selection must becarried out with careful consideration of both thetechnical and management requirements.ISO/IEC 14102:2008 defines both a set of processes and a structured set of CASE tool characteristics for use in the technical evaluation andthe ultimate selection of a CASE tool. It followsthe software product evaluation model defined inISO/IEC 14598-5:1998.ISO/IEC 14102:2008 adopts the general modelof software product quality characteristics andsubcharacteristics defined in ISO/IEC 91261:2001 and extends these when the softwareproduct is a CASE tool; it provides product characteristics unique to CASE tools.The next document provides guidance on howto adopt CASE tools, once selected.IEEE Std.
14471-2010 Guide—Adoption of ISO/IECTR 14471:2007 Information Technology—SoftwareEngineering—Guidelines for the Adoption of CASEToolsThe purpose of ISO/IEC TR 14471:2007 is toprovide a recommended practice for CASE adoption. It provides guidance in establishing processes and activities that are to be applied forthe successful adoption of CASE technology.The use of ISO/IEC TR 14471:2007 will helpto maximize the return and minimize the risk ofinvesting in CASE technology.
However, ISO/IEC TR 14471:2007 does not establish compliance criteria.It is best used in conjunction with ISO/IEC14102 for CASE tool evaluation and selection. Itneither dictates nor advocates particular development standards, software processes, design methods, methodologies, techniques, programminglanguages, or life cycle paradigms.B-20 SWEBOK® Guide V3.0Within a software engineering environment, itis important for the various tools to interoperate.The following standards provide a scheme forinterconnection.IEEE Std.
1175.1-2002 Guide for CASE Tool Interconnections—Classification and DescriptionIEEE Std. 1175.2-2006 Recommended Practice forCASE Tool Interconnection—Characterization ofInterconnectionsIEEE Std. 1175.3-2004 Standard for CASE ToolInterconnections—Reference Model for SpecifyingSoftware BehaviorIEEE Std. 1175.4-2008 Standard for CASE ToolInterconnections—Reference Model for SpecifyingSystem BehaviorThe purpose of this family of standards is to specify a common set of modeling concepts basedon those found in commercial CASE tools fordescribing the operational behavior of a softwaresystem. These standards establish a uniform,integrated model of software concepts related tosoftware functionality. They also provide a textual syntax for expressing the common properties(attributes and relationships) of those concepts asthey have been used to model software behavior.SOFTWARE QUALITYOne viewpoint of software quality starts withISO 9001, Quality Management Requirements,dealing with quality policy throughout an organization.
The terminology of that standard maybe unfamiliar to software professionals, andquality management auditors may be unfamiliarwith software jargon. The following standarddescribes the relationship between ISO 9001 andISO/IEC 12207. Unfortunately, the current version refers to obsolete editions of both; a replacement is in progress:IEEE Std. 90003-2008 Guide—Adoption of ISO/IEC 90003:2004 Software Engineering—Guidelinesfor the Application of ISO 9001:2000 to ComputerSoftwareISO/IEC 90003 provides guidance for organizations in the application of ISO 9001:2000 to theacquisition, supply, development, operation, andmaintenance of computer software and relatedsupport services.
ISO/IEC 90003:2004 does notadd to or otherwise change the requirements ofISO 9001:2000.The guidelines provided in ISO/IEC90003:2004 are not intended to be used as assessment criteria in quality management systemregistration/certification.The application of ISO/IEC 90003:2004 isappropriate to software that is• part of a commercial contract with anotherorganization,• a product available for a market sector,• used to support the processes of anorganization,• embedded in a hardware product, or• related to software services.Some organizations may be involved in allthe above activities; others may specialize inone area. Whatever the situation, the organization’s quality management system should coverall aspects (software related and nonsoftwarerelated) of the business.ISO/IEC 90003:2004 identifies the issueswhich should be addressed and is independentof the technology, life cycle models, development processes, sequence of activities, andorganizational structure used by an organization.
Additional guidance and frequent references to the ISO/IEC JTC 1/SC 7 softwareengineering standards are provided to assist inthe application of ISO 9001:2000: in particular, ISO/IEC 12207, ISO/IEC TR 9126, ISO/IEC 14598, ISO/IEC 15939, and ISO/IEC TR15504.The ISO 9001 approach posits an organization-level quality management process pairedwith project-level quality assurance planningto achieve the organizational goals. IEEE 730describes project-level quality planning. It isAppendix B B-21currently aligned with an obsolete edition of12207, but a revision is being prepared.IEEE Std. 730-2002 Standard for Software QualityAssurance PlansThe standard specifies the format and content ofsoftware quality assurance plans.Another viewpoint of software quality beginswith enumerating the desired characteristics of asoftware product and selecting measures or otherevaluations to determine if the desired level ofcharacteristics has been achieved.
The so-calledSQuaRE (software product quality requirementsand evaluation) series of SC 7 standards coversthis approach in great detail.ISO/IEC 25000 through 25099 Software Engineering—Software Product Quality Requirements andEvaluation (SQuaRE)A few of the SQuaRE standards are selectedbelow for particular attention. The first is theoverall guide to the series.ISO/IEC 25000:2005 Software Engineering—Software Product Quality Requirements and Evaluation(SQuaRE)—Guide to SQuaREISO/IEC 25000:2005 provides guidance for theuse of the new series of international standardsnamed Software product Quality Requirementsand Evaluation (SQuaRE).
The purpose of thisguide is to provide a general overview of SQuaREcontents, common reference models, and definitions, as well as the relationship among the documents, allowing users of this guide a good understanding of those international standards. Thisdocument contains an explanation of the transition process between the old ISO/IEC 9126 andthe 14598 series and SQuaRE, and also presentsinformation on how to use the ISO/IEC 9126 and14598 series in their previous form.SQuaRE provides• terms and definitions,• reference models,• guides• standards for requirements specification,planning and management, measurement,and evaluation purposes.The next SQuaRE standard provides a taxonomy of software quality characteristics that maybe useful in selecting characteristics relevant to aspecific project:ISO/IEC 25010:2011 Systems and Software Engineering—Systems and Software Quality Requirements and Evaluation (SQuaRE)—System and Software Quality ModelsISO/IEC 25010:2011 defines the following:1.A quality in-use model composed of fivecharacteristics (some of which are furthersubdivided into subcharacteristics) thatrelate to the outcome of interaction when aproduct is used in a particular context of use.This system model is applicable to the complete human-computer system, includingboth computer systems in use and softwareproducts in use.2.A product quality model composed of eightcharacteristics (which are further subdividedinto subcharacteristics) that relate to staticproperties of software and dynamic properties of the computer system.
![](https://s.studizba.com/z.php?f=/templates/si/i/noavatar.png&w=100&h=100&t=1"){kind=avatar}
