ISO 9000-3 Digest Monday, 24 March 1997 Volume 01 : Number 043
In this issue:
A serial mini-survey (No.8)
A serial mini-survey (No.9)
Re-send survey No.5
----------------------------------------------------------------------
From: Yingxu Wang
Date: Fri, 21 Mar 1997 10:19:42 -0800
Subject: A serial mini-survey (No.8)
Dear colleagues,
- - A Survey of Base Process Activities Towards Software Process Excellency
Thank you very much for your response! Attached please find the mini-survey
No.8.
Best regards,
Yingxu Wang
- ---------------------------------------------------------------------------
Research Centre for Systems Engineering | Email:wang_s@solent.ac.uk or
Southampton Institute | yingxu.wang@comlab.ox.ac.uk
Southampton SO14 0YN, UK | Tel: +44 1703 319773
In collaboration with IVF, IBM, and ESI | Fax: +44 1703 334441
- ---------------------------------------------------------------------------
**************************************************************************
Questionnaire 2: Base process activities on software eng. processes (4/6)
**************************************************************************
2.2.6 Integration and system test
148. (2.2.6.1) Integration test according to defined process
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
149. (2.2.6.2) Acceptance test according to defined process
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
150. (2.2.6.3) System tests generation
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
151. (2.2.6.4) Test integrated system
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
152. (2.2.6.5) Adopt software integration tools
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
153. (2.2.6.6) Adopt module cross-reference tools
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
154. (2.2.6.7) Adopt system acceptance test tools
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
2.2.7 Maintenance
155. (2.2.7.1) Determine maintenance requirements
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
156. (2.2.7.2) Analyse user problem and enhancements
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
157. (2.2.7.3) Determine modifications for next upgrade
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
158. (2.2.7.4) Implement/test modifications
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
159. (2.2.7.5) Update user system
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
160. (2.2.7.6) Maintenance consistency with specifications
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
161. (2.2.7.7) Maintain nonconforming products
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
162. (2.2.7.8) Record nonconformance treatment
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
163. (2.2.7.9) Adopt regression testing tools
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
164. (2.2.7.10) Conduct regression testing
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
------------------------------
From: Yingxu Wang
Date: Mon, 24 Mar 1997 10:36:25 -0800
Subject: A serial mini-survey (No.9)
Dear colleagues,
- - A Survey of Base Process Activities Towards Software Process Excellency
Thank you very much for your response! Attached please find the mini-survey
No.9.
Best regards,
Yingxu Wang
- ---------------------------------------------------------------------------
Research Centre for Systems Engineering | Email:wang_s@solent.ac.uk or
Southampton Institute | yingxu.wang@comlab.ox.ac.uk
Southampton SO14 0YN, UK | Tel: +44 1703 319773
In collaboration with IVF, IBM, and ESI | Fax: +44 1703 334441
- ---------------------------------------------------------------------------
**************************************************************************
Questionnaire 2: Base process activities on software eng. processes (5/6)
**************************************************************************
2.3 Software development environments
2.3.1 Environment
165. (2.3.1.1) Identify environment requirements
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
166. (2.3.1.2) Establish computer-supported cooperative work environment
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
167. (2.3.1.3) Provide software engineering environment
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
168. (2.3.1.4) Provide development supporting tools
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
169. (2.3.1.5) Provide management supporting tools
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
170. (2.3.1.6) Provide interactive communication environment
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
171. (2.3.1.7) Maintain software engineering environment.
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
2.3.2 Facilities
172. (2.3.2.1) Plan required resources
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
173. (2.3.2.2) Identify specialised facilities
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
174. (2.3.2.3) Acquire resources
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
175. (2.3.2.4) Check resources availability
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
176. (2.3.2.5) Provide productive workspace
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
177. (2.3.2.6) Provide data backup
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
178. (2.3.2.7) Provide building facilities
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
179. (2.3.2.8) Provide remote access facility
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
180. (2.3.2.9) Adopt software design tools
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
181. (2.3.2.10) Adopt software testing tools
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
182. (2.3.2.11) Ensure data integrity
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
183. (2.3.2.12) Register/maintain test equipments
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
184. (2.3.2.13) Control customer-supplied equipment
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
185. (2.3.2.14) Record equipment condition
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
186. (2.3.2.15) Ensure equipment availability
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
------------------------------
From: Yingxu Wang
Date: Mon, 24 Mar 1997 12:06:59 -0800
Subject: Re-send survey No.5
This is a multi-part message in MIME format.
- --------------16692514E84
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 7bit
Hello Colleagues,
I have found many of you might not received the No.5 questionnaire.
Therefore I would send it again. My apologies if you get a duplicated
one.
The preliminary analysis of the survey is quite interesting. We look
forward to completing the survey and report you a set of useful
reference data towards software process excellency.
Thank you very much for your help!
Best regards,
Yingxu
- --------------16692514E84
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; filename="SURVEY35.TXT"
Dear colleagues,
- - A Survey of Base Process Activities Towards Software Process Excellency
Thank you very much for your response! Attached please find the mini-survey No.5.
Best regards,
Yingxu Wang
- ---------------------------------------------------------------------------
Research Centre for Systems Engineering | Email:wang_s@solent.ac.uk or
Southampton Institute | yingxu.wang@comlab.ox.ac.uk
Southampton SO14 0YN, UK | Tel: +44 1703 319773
In collaboration with IVF, IBM, and ESI | Fax: +44 1703 334441
- ---------------------------------------------------------------------------
***********************************************************************
Questionnaire 2: Base process activities on engineering processes (1/5)
***********************************************************************
2. Software Engineering Processes
2.1 Software engineering methodologies
2.1.1 Software engineering modelling
82. (2.1.1.1) Aware state-of-the-art in software engineering
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
83. (2.1.1.2) Survey methodologies/technologies adopted external
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
84. (2.1.1.3) Evaluate life cycle model
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
85. (2.1.1.4) Evaluate prototyping model
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
86. (2.1.1.5) Evaluate OOP model
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
87. (2.1.1.6) Evaluate combined model
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
88. (2.1.1.7) Evaluate CASE model
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
89. (2.1.1.8) Integrate methodologies and tools into process
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
90. (2.1.1.9) Distinguish development category: system prototype/
new system/improved version
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
2.1.2 Reuse methodologies
91. (2.1.2.1) Determine organisational reuse strategy
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
92. (2.1.2.2) Identify reusable components
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
93. (2.1.2.3) Develop reusable components
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
94. (2.1.2.4) Establish reuse library
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
95. (2.1.2.5) Certify reusable components
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
96. (2.1.2.6) Integrate reuse into life cycle
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
97. (2.1.2.7) Propagate change carefully
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
2.1.3 Technology innovation
98. (2.1.3.1) Plan technology change
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
99. (2.1.3.2) Identify processes needed tech. change
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
100. (2.1.3.3) Identify/replace obsolete technology/process
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
101. (2.1.3.4) Select new technology
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
102. (2.1.3.5) Introduce new technology/metrics/process
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
103. (2.1.3.6) Pilot trial of new technology
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
104. (2.1.3.7) Incorporate trailed technology into current process
Importance in process: (least) [0] [1] [2] [3] [4] [5] (most)
Experience: Practised [ ] Not practised [ ]
Effectiveness: Yes [ ] No [ ]
Comments (if any): ..............................................
- --------------16692514E84--
------------------------------
End of ISO 9000-3 Digest V1 #43
*******************************
To remove yourself from this list, address a message to: MAJORDOMO@QUALITY.ORG with only the words "unsubscribe iso9000-3-digest" (without the quotes) in the BODY of your message.