Cloud Scheduler Requirements

This document contains all potential and realized requirements for the cloud scheduler that is being designed as of May 2009. Though the categories below are representative of formal requirements engineering, this document is intended to be informal. Requirements should be brief, and categorized correctly as best as possible. Also, please note whether the requirements are absolute (nonnegotiable), flexible, or potential (any ideas are appreciated).

If the categories below do not suffice, or subcategories are required, please add your own.

Functional Requirements

(Describe the function of the intended system. What should the scheduler do?)

Performance Requirements

(Describe the performance constraints on the intended system. How fast / with how many resources should the scheduler function?)

Design Requirements

(Describe what standards the intended system should meet. How, and in accordance with what standards or guidelines, will the scheduler be built?)

Client Requirements

(Any suggested requirements from clients of the intended system. These may fit into other categories as well.)

-- DuncanPenfoldBrown - 01 Jun 2009

Edit | Attach | Watch | Print version | History: r7 | r4 < r3 < r2 < r1 | Backlinks | Raw View | More topic actions...
Topic revision: r1 - 2009-06-01 - dpb
  • Edit
  • Attach
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback