If A occurs 60% of the time and B 40%, for example, the operational profile is A = 0.6 and B = 0.4.
It requires some currency such as transactions-per-hour in order that the alternatives can be usefully
expressed. See section D.7 in Appendix D for details of some measures and the organizations defining them.
It requires about one person-month to prepare for an ???average??? project of about 10 developers, 100,000
source lines, and a development interval of 18 months [Musa 4].
The process has 6 steps:
1. Find the customer profile.
2. Establish the user profile.
3. Establish risk levels.
4. Define the system-mode profile.
5. Determine the functional profile.
6. Determine the operational profile.
Not all these steps are essential. Any feature change should be reflected as a change to the operational profile.
7.7.1 Find the Customer Profile
The customer is the type of institution or business using the system. This may be (for example): schools,
hospitals, military, church, retail, manufacturing, and others with proportions of 10%, 21%, 5%, 5%,
25%, 33%, and 1%. This is also known as the customer base.
7.7.2 Establish the User Profile
Each customer contains users who will use the system in some form or some way. Each group of users
has an occurrence probability of ever being involved with the system. This may vary as the system develops
and more customer types are drawn into the system??™s use. Those people who will never use the system
and are unconcerned with it, have an occurrence probability of zero.
Pages:
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279