MINUTES OF THE

BCS SIGiST STANDARDS WORKING PARTY MEETING

HELD ON  8^th APRIL 2003

1. Attendance.

2. Agree Agenda

03/4.1                      The agenda was amended to review the Integration, Interoperability and Compatibility discussion document before the Database/Compatibility example.

3. Technique reviews

                                The following administrative actions were recorded during the domain technique review section of the meeting:

03/4.2                      SWP Administrative Actions

3.1. Compatibility - Database technique example review

The attendees did not know who was the author of the example.

The example did not fit the agreed definition of Compatibility but does not swap to another heading.  Stuart questioned if this example was actually Interoperability.

The meeting wanted to keep the example as it was clearly from a real project. There was a suggestion that it should be made a Case Study. This would open a new section. If the author is willing to adapt the example as a Case Study, all information should be kept. It was felt the example covered many different techniques.

Richard raised the issue of where backwards and forwards compatibility fit into the matrix. The question will be raised for discussion on the website.

                                The following actions were agreed:

03/4.3                      Compatibility/Database

3.2          Definition of Procedure Testing

Nobody at the meeting knew who the author was. 

Various comments suggested the proposed definition did not match previous definitions. Dictionary definition of Procedure – a way of acting or progressing in a course of action. This didn’t answer the question about the correct definition.

The meeting felt that procedure testing is testing the procedure, rather than the documentation of the procedure.

The example given could be worked into the guidelines e.g. a list of documents and analysis and a list of information. The definition should describe what goes on.

Each test case should specify:

1.        Set-up of the test environment

2.        The part of the procedure being exercised.

3.        The input triggering the event in the procedure.

4.        The expected outcome of the procedure.

It was agreed that Figure 1 was not correct.

03/4.4                      Procedure Testing Definition

3.3          Definition for Sign-off – Conversion – MIS and Conversion – Database

The author, Isabel Evans, walked the meeting through the example and comments. There were some typing errors that needed correcting. Invalid output partitions should be justified. There was a question whether this was an MIS conversion example or just a database example. Isabel agreed that the example really only covered database conversion. Another example will be required for MIS conversion.

03/4.5                      Conversion-Database

4. Extended Definitions of Interoperability, Integration and Compatibility

Stuart, as the author, led the meeting through the example, giving regard to the comments received through the website.

4.1.    Interoperability

Isabel suggested a Venn Diagram. Stuart will incorporate one.

A table, possibly in the Guidelines section, should show what phase of testing these apply to. These are part of integration testing in the large.

4.2.    Integration

Accepted.

4.3.    Compatibility

There was a discussion on whether Compatibility testing is part of Integration testing. The meeting decided it was not. Questions were also raised on Portability vs. Compatibility.

Isabel suggested incorporating the comments into the Guidelines as they indicated questions people would have when using the definitions.

Comments will be incorporated as appropriate.

03/ 4.6 Actions from Definition Discussion

5. Living Glossary – Terms for Review

                                The following terms were put forward for discussion. Comments had been received.

·         Fit for Purpose Testing

Isabel had proposed a different definition. This will be posted for discussion. We need a term to describe the type of testing Lawrance had defined, possibly “Specification Testing”- Testing confined to demonstrating that the system meets the specification. Stuart has a definition and will post to the web site.

·         Rigorous Testing

This definition was rejected.

·         Requirement

Definition to be amended to cover functional and non-functional requirements.

·         Specification

Use the short definition as given. The old definition will be used to cover component specification.

·         Reliability

Comments had been received from Neil Hudson:

2.2 will be incorporated

2.1 and 2.3 were rejected

Comments had been received from Marco Giromini. It was felt his definition was too performance based.

·         Reliability Requirements - Accepted

·         Reliability Testing - Accepted

·         Usability

Stuart to update with definition from ISO 9126-1, 2001

·         Usability Requirements - Accepted

·         Usability Testing - Accepted

·         Maintainability

Stuart to update as appropriate.

·         Maintainability Requirements - Accepted

·         Maintainability Testing - Accepted

·         Portability

Stuart to update as appropriate.

·         Portability Requirements - Accepted

·         Portability Testing - Accepted

·         Availability, Integrity, Confidentiality

These will be included as sub items within the Security definition as they are specifically related to security testing.

·         Security

Stuart to update to include availability, integrity and confidentiality

·         Security Requirements - Accepted

·         Security Testing - Accepted

The following items will be carried over to the next meeting:

·         Performance

·         Performance Requirements

·         Performance Testing

·         Storage

·         Storage Requirements

·         Storage Testing

03/4.7                      Living Glossary

6. Minutes from the Previous Meeting

03/4.8                      The minutes of the previous meeting were agreed but all action items were carried over to the meeting on 21st May.

7. Actions from the Previous Meetings

All actions outstanding from the previous meetings will be carried forward to the next meeting.

02/2.7                      New Joiners Guide

03/2.2                      Interoperability/e-business

03/2.3                      Conversion/DB&MIS

03/3.2                      SWP Administrative Actions

03/2.4                      Marketing

8. Any other business

None.

9. Date of Next Meeting

                                The dates for future SWP meetings are listed below. In the absence of Graham, the group did not know what had been received for review over the next month.

                                The above meetings will take place at PA (Consulting), 4^th Floor, 123 Buckingham Palace Road, London.

                                NB. All are welcome to attend, but please confirm attendance in advance with the secretary so that security passes can be arranged.