|
| Topic | Details |
|
| Introduction | Project; informant’s role. |
| Requirements and use cases | How were they defined? Who was involved? Check for accuracy. |
| User interface | How were look and feel defined? Who was involved? Positive and negative influences; check for accuracy. |
| Testing | What was tested? Goals of testing; time of testing; usability tests. |
| Personal assessment | Relationship between RUP and UCD; amount of UCD; behaviour under time and budget pressure; relationship between clients and usability; involvement of end users. |
| Project management discipline | Number of iterations; when were end users involved? Measurement of user satisfaction; measurement of client satisfaction. |
| Business modelling discipline | Elaboration of requirements with clients and end users; on-site visits; same workers as in other disciplines? |
| Requirements discipline | Ease of use as explicit requirement; elaborations with end users or clients; what are advantages and disadvantages of such a process? Different levels of requirements; explicit requirements for visual design of the UI. |
| Analysis and2 design discipline | Which artifacts resulted from this discipline? |
| Implementation discipline | The same employees as in other disciplines? Was implementation based on use cases? Prototypes. |
| Test discipline | What was tested? Tests against requirements or against use cases? With end users? When was tested? Consequences of tests. |
| Configuration and change management discipline | How was it handled? Decision processes; consideration of changes for the whole application. |
| Environment discipline | UI guidelines; business modelling guidelines; use case modelling guidelines; reasons for guidelines; did people follow the guidelines? |
| Deployment discipline | Education of the users; technical writer; client support. |
| Influences | Management; technology; customer. |
|
