Draft Proposed TQM Standard for activities
Posted: Wed Apr 16, 2003 1:54 pm
Gents,
I enclose a proposed draft Total Quality standard for the preparation and distribution of activities, for comments.
Preamble
Activities that have been prepared to meet this standard should display in the Readme file:
This activity has been prepared to meet the Total Quality standard for Activities displayed on the Activity Forum of http://www.uktrainsim.com (and if applicable), and has been tested by at least one other person who believes it meets the standard.
Objectives of the standard
The objectives of the standard are to ensure that the user:
1. Has an idea of the activity before loading it, and the material required
2. Can easily locate the material required
3. Does not overwrite the users existing consists, paths and traffic patterns
4. Can be easily deleted from the users system.
Read Me file.
The read me file should be in .txt or PDF format. Where it is in PDF format all links should be clickable [Word should not be used because of macro viruses. Freeware PDF makers are available eg PDF995].
Name and E-mail address of activity maker.
· Activity name
· Activity file name (See file/path name convention below)
· Version of activity and date
· Route Name and Version
Description:
The description should enable a user to determine if he wants to load it and should consist of at least
· Description of activity
· Time Length of Activity
· Number of AI trains
· Whether loose consists used
Special Instructions to running of activity
For example
· This activity requires a computer with at least a Pentium 1.5Ghz processor or more
· This activity requires a version of MSTS upgraded to at least Version 1.2 for the front couplers to work
· If you change the player consist ensure it is the same length for the reversing points to work.
Material required.
A table indicating the material required, with at least:
Internet site where material located
· Reference number (For UKTrainsim.com), or page number where sites do not have search facilities.
· Zip file name
· File directory used in MSTS
· Where activity used (if it is an pack of activities)
It is recommend that where the writer used the material in a number of this is indicated. Eg the following material was required for my previous activity XXXX.
The Route-Riter listing should also be included as a separate file.
Loading Instructions
The activity should be included in a zip file with the read –me, a packed (.apk) and Zip version (Zipped by Route-Riter), the Route-Riter listing and the .jpg picture.
Installation instructions should be included in the Read me for both for the .apk and zip version.
Uninstall instructions.
Instruction for uninstalling the activity, paths, and traffic patterns and consists used should be included.
Naming convention
In order to ensure the above is achieved the following traffic, pattern and file naming convention should be used.
All consists; paths and traffic patterns should be renamed renamed, even if there are standard.
All consist names; activity names, path names and traffic names should begin with a three-letter/number code for the activity writer eg ABC_
All Paths names should have a numeric ABC_XXXX_ where ABC is the name of the author and XXXX is a specific code denoting the route and the activity.
Timetable
All player timetable should be physically checked, and timed to the nearest minute.
All reversing points should be set using a template.
It is advised that all work orders include only one car per set of cars being picked up, to assist in usability (eg in a set of three cars, the work order activity is for one of the cars).
I enclose a proposed draft Total Quality standard for the preparation and distribution of activities, for comments.
Preamble
Activities that have been prepared to meet this standard should display in the Readme file:
This activity has been prepared to meet the Total Quality standard for Activities displayed on the Activity Forum of http://www.uktrainsim.com (and if applicable), and has been tested by at least one other person who believes it meets the standard.
Objectives of the standard
The objectives of the standard are to ensure that the user:
1. Has an idea of the activity before loading it, and the material required
2. Can easily locate the material required
3. Does not overwrite the users existing consists, paths and traffic patterns
4. Can be easily deleted from the users system.
Read Me file.
The read me file should be in .txt or PDF format. Where it is in PDF format all links should be clickable [Word should not be used because of macro viruses. Freeware PDF makers are available eg PDF995].
Name and E-mail address of activity maker.
· Activity name
· Activity file name (See file/path name convention below)
· Version of activity and date
· Route Name and Version
Description:
The description should enable a user to determine if he wants to load it and should consist of at least
· Description of activity
· Time Length of Activity
· Number of AI trains
· Whether loose consists used
Special Instructions to running of activity
For example
· This activity requires a computer with at least a Pentium 1.5Ghz processor or more
· This activity requires a version of MSTS upgraded to at least Version 1.2 for the front couplers to work
· If you change the player consist ensure it is the same length for the reversing points to work.
Material required.
A table indicating the material required, with at least:
Internet site where material located
· Reference number (For UKTrainsim.com), or page number where sites do not have search facilities.
· Zip file name
· File directory used in MSTS
· Where activity used (if it is an pack of activities)
It is recommend that where the writer used the material in a number of this is indicated. Eg the following material was required for my previous activity XXXX.
The Route-Riter listing should also be included as a separate file.
Loading Instructions
The activity should be included in a zip file with the read –me, a packed (.apk) and Zip version (Zipped by Route-Riter), the Route-Riter listing and the .jpg picture.
Installation instructions should be included in the Read me for both for the .apk and zip version.
Uninstall instructions.
Instruction for uninstalling the activity, paths, and traffic patterns and consists used should be included.
Naming convention
In order to ensure the above is achieved the following traffic, pattern and file naming convention should be used.
All consists; paths and traffic patterns should be renamed renamed, even if there are standard.
All consist names; activity names, path names and traffic names should begin with a three-letter/number code for the activity writer eg ABC_
All Paths names should have a numeric ABC_XXXX_ where ABC is the name of the author and XXXX is a specific code denoting the route and the activity.
Timetable
All player timetable should be physically checked, and timed to the nearest minute.
All reversing points should be set using a template.
It is advised that all work orders include only one car per set of cars being picked up, to assist in usability (eg in a set of three cars, the work order activity is for one of the cars).