Appendix B. Requirements Questionnaire

This questionnaire should help you identify your requirements as you evaluate products.

Operating Platform Attributes

  1. Which operating system(s) will you use to host the service?

  2. Which programming language(s) will you use to write the service?

  3. Will you need an adapter to connect to a legacy application?

  4. Which Web server(s) will you use?

  5. Which application server(s) will you use?

  6. Which database system(s) will you use?

  7. Which user management system(s) do you use?

  8. Which access control system(s) do you use?

  9. Which management infrastructure(s) do you use?

Client Platform Attributes

  1. Will you support internal or external clients (or both)?

  2. Is there a chance that you will add new clients over time?

  3. Will you have control over the client environment?

  4. Which software distribution tool(s) do you have?

  5. Which operating system(s) will host the clients?

  6. Which programming language(s) will be used to write the clients?

Licensing Requirements

  1. Are you developing an application for commercial use?

  2. How many servers will you use to deploy the application?

  3. Are you developing a commercial product for resale?

  4. Will you need to redistribute Web services platform software?

  5. Does your company have any policies regarding open source software?

  6. What are your support requirements?

Performance and Scalability Requirements

  1. What do you view as the minimum acceptable latency for an online query?

  2. What do you view as the minimum acceptable number of transactions per second that your service must perform?

  3. What is your estimate for the average and peak number of concurrent users that will access the service?

  4. When will you need to support these performance requirements?

Extensibility Features

  1. Do you need to support transactions?

  2. Do you need guaranteed message delivery?

  3. Do you need to support asynchronous communications?

  4. Do you need to support security? (See the next section for details.)

  5. Do you need to support logging or auditing?

  6. Do you need to support alternative transports?

  7. Do you need to support automatic message transformation or version management?

Security Requirements

  1. What type of authentication mechanism(s) do you need to support?

  2. Is transport-level security sufficient to address your needs?

  3. Do you need to restrict access to certain services?

  4. Do you have an existing access authorization system?

  5. Do you need to digitally sign your messages?

  6. Do you need to support single sign-on?

  7. Do you have an existing single sign-on solution?

Developer Preferences

  1. How experienced is your developer staff?

  2. How comfortable are they with command line tools?

  3. Do they prefer to use visual tools?

  4. What integrated development environments do they use?

  5. Will you be using UDDI?

UDDI Requirements

  1. Which operating system(s) will you use to host your registry?

  2. Which database or data storage facility would you prefer to use?

  3. What are your performance requirements?

  4. Will you need to replicate the registry across multiple systems?

  5. Will you need to federate the registry across multiple systems?

  6. Will your users want to subscribe to registry updates?

  7. Will you define custom taxonomies?

  8. Will you need to customize the UDDI browser interface?

  9. Will you need inquiry-based access control?

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
18.117.182.179