Beruflich Dokumente
Kultur Dokumente
7.1 User role in Projects Management 7.2 User role in various stages of S/W development 7.3 User role in System Implementation
Provide promised:
Resources Inputs
Return document in specified period. Do not sign anything that you do not understand. Insist on getting project progress reports. Participate in steering committee meetings. Never forger that it is your own project. Strictly adhere to change control procedure. Above all, get involved in all development activities.
developers and the users. Participation of users during all phases of software development is essential. Software development activity is too important to be only to the discretion of developers.
3.
Users willing to cooperate but they do not know how to do Users unclear about: Project goals Own roles Own responsibilities Users do not have time for: Giving requirements Verifying requirements Performing acceptance
Form steering committee Establish responsibilities for own employees Ensure that developer establishes his organization structure
Project goals, scope, and acceptance criteria Development standards Project reporting procedures and frequency Change control procedures Mechanism for acceptance of deliverables
4. Specify constraints
Understand requirement specifications Sign specification document Keep the requirement current
Provide acceptance test data Provide agreed resources for acceptance testing Verify accuracy of acceptance test results Be satisfied about the performance Be satisfied about the manual procedures Try out restart and recovery procedures
5.