Presentation on theme: "ISO/IEC JTC1 SC7 Sintesi delle attività in SC7 Roma 8-5-2002 A.Jeanrenaud (Tecnopolis CSATA)"— Presentation transcript:
ISO/IEC JTC1 SC7 Sintesi delle attività in SC7 Roma A.Jeanrenaud (Tecnopolis CSATA)
2 Tecnopolis Sintesi delle attività in SC7 ISO/IEC JTC1/SC7 Sottocomitato SC 7 :Ingegneria del software (Software Engineering) Chairman: François Coallier (Canada) Segreteria: Alain Abran (Canada) Scopo: Normazione di processi, input e output dei processi tecniche per l’ingegneria del software e dei sistemi contenenti software.
3 Tecnopolis Sintesi delle attività in SC7 Gruppi di lavoro dell’SC7 WG2 - System Software Documentation WG4 Tools and Environment WG6 Evaluation and Metrics WG7 Life Cycle Management WG9 System Integrity WG10 Process Assessment WG12 Functional size measurements WG13 Software Measurement Framework WG17 ODP - Enterprise Language WG18 Quality Management WG19 ODP - Modelling Languages WG20 Software Engineering Body of Knowledge
4 Tecnopolis Sintesi delle attività in SC7 Gruppi di lavoro con compiti “speciali” SWG1 Business Planning SWG5 Architecture Management
5 WG2 - System Software Documentation Convener Ken Johnson - UK Scope: Development of standards for the documentation of software systems. Project [ISO 6592] Guidelines for the Documentation of Software Systems (Revision) ISO User Documentation and Cover Information for Consumer Software Package [ISO 9294] Guidelines for the management of software documentation Software Life Cycle Processes - Guidelines for the Content of Software Life Cycle Software User Documentation Process Guidelines For The design and preparation of software user documentation.
6 WG4 Tools and Environment Conveners P. Gonella - USA & D. Lee - Korea Scope: Development of standards and technical reports for tools and Computer Aided Software/System Engineering (CASE) environments. Project Software Engineering Environment Services Configuration Management Tool Requirements
7 WG6 Evaluation and Metrics Convener Motoei Azuma - Japan Scope: Development of standards and technical reports for software products evaluation and metrics for software products & processes Software product quality - General overview and guide : Quality metrics - Metrics reference model and guide : Quality metrics - Base metrics : Quality requirements - Quality requirements and guide ISO/IEC Software Engineering - Software Quality Requirements and Testing Measurement and Rating of Performance of Computer-based Software Systems.
8 WG7 Life Cycle Management Convener Stan Magee - USA Scope: Development of standards and technical reports on Life Cycle Management. Project :1995/AMD 1 - Software Life Cycle Processes Software Maintenance System Life Cycle Processes Guide for ISO/IEC System life cycle processes.
9 WG9 System Integrity..inglobato nel WG7…. Scope: Preparation of standards, technical reports, and guidance documents related to software integrity at the system and system interface level. In this context, software integrity is defined as ensuring the containment of risk or confining the risk exposure
10 WG10 Process Assessment Convener Alec Dorling - UK Scope: Development of standards and guidelines covering methods, practices and application of process assessment in software product procurement, development, delivery, operation, evolution and related service support : Amendment To ISO/IEC TR Reference Model Extensions For Acquirer Processes Software Process Assessment - Part 2: A Reference Model for Processes And Process Capability : Software Engineering - Process Assessment Part 3: Performing An Assessment.
11 WG12 Functional size measurements Convener Pam Morris - Australia Scope: To establish a set of practical standards for functional size measurement. Functional size measurement is a general term for methods of sizing software from an external viewpoint and encompasses methods such as Function Point Analysis Software measurement - Functional size measurement - Part 2: Compliance assessment of software size measurement methods to ISO/IEC : Information technology - Software measurement - Functional size measurement - Part 3: Verification of functional size measurement methods Software measurement - Functional size measurement - Part 4: Reference Model..
12 WG13 Software Measurement Framework Convener Jack McGarry - USA Scope: Development of standards and technical reports to define and implement software measurement processes, frameworks and guidance. Project Software Measurement Processes
13 WG17 ODP - Enterprise Language Convener Joaquin Miller - USA Scope: ODP Enterprise viewpoint Project Information Technology - Open Distributed Processing - Enterprise viewpoint
14 WG18 Quality Management Convener Victoria Hailey - Canada Scope: Quality Management. Project Guidelines to the application of ISO 9001:2000 for software.
15 WG19 ODP - Modelling Languages Convener Bryan Wood - UK Scope: Includes modelling languages, metadata, ODP framework and ODP components related standards and project, as well as provide the focal point to facilitate collaborative work with OMG and ITU-T, and other organizations if required (IEEE) CDIF Transfer Format CDIF Semantic And Presentation Metamodels Information Technology - Open Distributed Processing - Interface Definition Language (IDL) for ODP Systems Information Technology - Open Distributed Processing - Protocol support for computational interactions Information Technology - Open Distributed Processing - Open Distributed Processing Interface References and Binding Information Technology - Open Distributed Processing - Type Repository Function Information Technology - Open Distributed Processing - Naming Framework
16 WG20 Software Engineering Body of Knowledge Convener Scope: Publish the IEEE SWEBOK document as a TR Type 3. Project Software Engineering Body of Knowledge (SWEBOK).
17 Tecnopolis Sintesi delle attività in SC7 SWG1 Business Planning Group Conveners François Coallier - James Moore - USA Scope: 1.Extract the fundamental JTC1/SC7 terms from the following sources: JTC1/SC7 terms of reference, ISO/IEC 9126, ISO/IEC 12207, and words in all titles of JTC1/SC7 in- work and existing standards. 2.Identify contradictions and ambiguities in terms within scope of SWG2. 3.Suggest resolution of these contradictions and ambiguities. 4.Recommend methods of publishing, coordination with JTC1/SC1 and other ISO and IEC technical committees, and controlling JTC1/SC7 fundamental terms. 5.Recommend a plan for next phase of SWG2 including the achievement of the intent of Resolution 218.
18 Liaison con IEEE Tecnopolis Sintesi delle attività in SC7 SWG5 Architecture Management Convener François Coallier - Australia James Moore - USA Terry Rout - Australia Scope: 1.Elaborate and Maintain JTC1/SC7 Architecture and Vocabulary standing documents 2.Provide counsel to JTC1/SC7 Conveners and editors on standards architecture and vocabulary consistency issues 3.Recommend to JTC1/SC7 standard maintenance strategies 4.Report on its activities to the JTC1/SC7 BPG and AG
19 Liaison con IEEE IEEE partecipa alle attività dell’SC7 nella relazione che IEEE presenterà nei lavori della plenaria sono indicati 4 standard che l’IEEE intende pubblicare come sono: IS 12207, Software Life Cycle Processes (IEEE/EIA ) IS 12119, Software Packages--Quality and Testing (IEEE 1465) IS 14102, Guidelines for Evaluation and Selection of CASE Tools (IEEE 1462) IS Functional SizeMeasurementConcepts (IEEE ) A.Jeanrenaud e G.Legalle sono gli editor dello standard
ISO/IEC Software Engineering - Software product evaluation - Requirements for quality of Commercial Off The Shelf software product (COTS) and instructions for testing A.Jeanrenaud, G.Legalle
21 ISO IEC Scope: the standard provides a set of requirements for COTS, requirement for testing and instructions on how to test a COTS against its requirements.
22 ISO IEC It establishes : requirements for COTS; requirements for test (recommendation for the documentation of the test ) ; instructions on how to test a COTS against quality requirements (instructions for testing, in particular for third party testing
23 ISO IEC Main contents: terminology; requirements for COTS ; test dossier ( the collection of documents for test);
24 ISO IEC Requirements for COTS: Every COTS shall contain a product description and a user’s documentation The product description is generally the commercial documentation or the packaging of the product in the case of products sold on shelf The user’s documentation is the complete set of documents, available in printed or non-printed form, that is provided for the application of the product and also is an integral part of the product.
25 ISO IEC Requirements for programs and data : All statements on each quality characteristic expressed in the user's documentation shall be executable according that what was defined in that documentation quality characteristics are defined in: SQUARE Quality Model and architecture
26 ISO IEC Main quality characteristics : Functionality Reliability Usability
27 ISO IEC Requirements for Test Dossier : The test dossier is the collection of the documentation inherent to the testing activities The test dossier shall contain : a test plan, a test description, traceability elements, test results.
28 ISO IEC Requirements for Test plan: The test plan shall contain: Test specification, Test environment, Test activity planning.
29 ISO IEC Test description The description of each test case shall include: its test objective ; a unique identifier ; the reference to the associated test scenarios.
30 ISO IEC Test scenarios The description of each test scenario shall include: environment and others test conditions ; the description of the scenario ; the identifier(s) of the associated elementary test(s).
31 ISO IEC Elementary test The documentation of elementary test shall include: data of test ; the description of the elementary test ; the awaited behavior of the system ; the criterion of the result’s interpretation
32 ISO IEC Test procedures Test procedures shall be sufficiently detailed to make it possible to reproduce the tests.
33 ISO IEC Requirements for Test results Form requirements The test results shall present the way in which the test cases were carried out and the execution reports. They shall include the following information : execution reports ; anomaly reports.
34 ISO IEC Execution report The execution reports shall comprise an overall picture of the results of the test cases. The execution reports shall include : the identifier of the elementary test ; the identifier of the corresponding test case ; the name and the function of the person having carried out the test ; the date and hour (or equivalent information) of the test execution ; the list of the anomalies founded ;with the reference to the corresponding anomaly report.
35 ISO IEC Instructions for testing The instructions specify how a product shall be tested against the quality requirements defined in clause 4. They include : testing for properties required from all conforming products ; testing for properties promised by the product description ; testing by inspection of documents ; black-box testing of programs and data.
36 ISO IEC Test pre-requisites Presence of product items –all items to be delivered as well as the requirements documents identified in the product description shall exist Presence of system elements –it is required that components of all the computer systems as named in the product description shall be available.black-box testing of programs and data.
37 ISO IEC Testing activities The product description, the user’s documentation, programs and data to be delivered as parts of the COTS : shall be verified and tested for compliance with the requirements in clause 4 ; should be verified and tested for compliance with the recommendations in clause 4. If a test dossier is supplied, it: shall be verified and tested for compliance with the prescriptions in clause 5 ; should to be verified and tested for compliance to the recommendations of the article 5.
38 ISO IEC Test report The test report shall have the following structure: Product identification ; Computer systems used for testing (hardware, software and their configuration) ; Documents used (with their identification) ; Results of the tests ; List of the non-conformities to requirements ; A statement that the product was not tested for conformity to recommendations or, either a list of the non- conformities to recommendations or a list of the recommendations that were not followed ; Date of the completion of the test.
39 ISO IEC Follow up Test When a product, which has already been tested, is tested again then : all changed parts in the documents, functions and data shall be tested as if it were a new product ; all unchanged parts that are expected to be influenced by the changed parts or by changes in a required system (according to the specialized knowledge of the tester) shall be tested as if it were a new product ; all other parts shall at least be tested by samples.