Dear Sir/Mdm
This survey is part of a research to determine the feasibility of extracting & distributing only relevant sections of a Systems Requirements Specification (SRS) to different project stakeholders instead of the entire set of specifications in full. The purpose is to reduce the document reading costs and promote the efficiency and effectiveness of communications between different stakeholders to ultimately help promote the success of projects. The final research results will be posted in the PMI survey website for your reference.
Please share with us your views. This survey comprises only 21 questions and should take less than 20 minutes of your valuable time to complete.
Your participation in this study is completely voluntary. There are no foreseeable risks associated with this project. However, if you feel uncomfortable answering any questions, you can withdraw from the survey at any point. It is very important for us to learn your opinions.
Your survey responses will be stricly confidential and data from this research will be reported only in the aggregate. Your information will be coded and will remain confidential. If you have questions at any time about this survey or the procedures, please email me at [email protected]
If you have any concerns with regard to the possibility of your identity being made known in the course of this project, please do not hesitate to contact Ms Kimberley Larsen, The Executive Officer, IGSM Human Research Ethics Committee, University of South Australia, GPO BOX 2471, Adelaide SA 5000, Australia. Email: [email protected]; telephone number + 61 8 8302 0475; and Fax : + 61 8 8302 0709 to discuss any ethical concerns about the project or answer questions about the rights of participants.
Thank you very much for your time and support. Please start with the survey now by clicking on the Continue button below.
Yours sincerely,
Wan Mei Mok
Please check ALL that apply.
Please check ALL that apply.
Please check ALL that apply.
Please check ALL that apply.
Please check ALL that apply.
13. Typically, who are the critical, essential and non-essential stakeholders (SH) in your projects ?
CRITICAL SH can prevent your project from achieving success.
ESSENTIAL SH can delay your project from achieving success but you have alternative stakeholders.
NON-ESSENTIAL SH are interested in your project but have no direct impact on its success.
Please check ALL that apply. | | | | | | | | | Negative Stakeholder eg Opponent of a project/product | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Technical Designer, Systems Architect or Organizational Architect | | | | | | | | | | | | | | | | | | | Consultant in Sales, Marketing, Aesthetics, Graphics, Usability, Safety, Security, Cultural, Legal, Environmental, Standards, Financial or Negotiation | | | | | | | | | | | | | | | Maintenance Operator eg product installer | | | | | Operational Support eg Trainer | | | | |
16. Please check those Project Drivers sections in a typical Systems Requirements Specifications that you would consider compulsory to distribute to your different categories of stakeholders :
17. Please check those PROJECT CONSTRAINTS sections in a typical Systems Requirements Specifications that you would consider compulsory to distribute to your different categories of stakeholders :
18. Please check those FUNCTIONAL REQUIREMENTS sections in a typical Systems Requirements Specifications that you would consider compulsory to distribute to your different categories of stakeholders :
19. Please check those NON-FUNCTIONAL REQUIREMENTS sections in a typical Systems Requirements Specifications that you would consider compulsory to distribute to your different categories of stakeholders : | | | | a) Look & Feel Requirements | | | | | b) Usability & Humanity (language, currency, understandability, learnability, etc) Requirements | | | | | c) Performance (speed, safety, accuracy, reliability, availability, accessibility, etc) Requirements | | | | | d) Operational (eg physical & technological environment, interoperability, productization, etc) Requirements | | | | | e) Maintainability & Support Requirements | | | | | | | | | | g) Cultural & Political Requirements | | | | | h) Legal Requirements (standards & compliance) | | | | |
20. Please check those PROJECT ISSUES sections in a typical Systems Requirements Specifications that you would consider compulsory to distribute to your different categories of stakeholders :
|