Comp 650
2024-05-18 08:19:23 UTC
Home
Lectures
Assignments
Tactics
UML
Queuing
Books
Web sites
 
Turnitin.com
Textbooks
Guidelines
Writing help
Plagiarism
 
Bulletin board
Contact
  Design paper ask-yourself questions
To stimulate your thinking about SCUFS, this page lists some questions that you should be able to answer by the time your architecture is ready to turn in.
  • How will you ensure that SCUFS code is reliable enough to meet the safety requirements?
  • How will SCUFS respond to bad weather?
  • How will SCUFS support troubleshooting?
  • Is it possible to shut SCUFS down? If so, under what circumstances?
  • How will SCUFS be started up?
  • Will SCUFS run on a small number of large servers, a large number of small servers, or somewhere in between?
  • What operating system(s) will be used?
  • What programming language(s) will be used?
  • What large-scale middleware (e.g. Java EE, .Net) will be used, if any?
  • How will communication inside SCUFS work?
  • Will commercial off-the-shelf components (COTS) be used? If so, what requirements will SCUFS place on the software and/or vendor?
  • What major enhancements or extensions do you think SCUFS will have to support?
  • What are the "critical functions" referred to in the availability quality attribute scenario?
  • What constitutes an outage of a critical function?
  • What systems do you know of that have similarities to SCUFS?
  • What approaches or patterns from those systems might be applicable here?
  • How will SCUFS be administered?
  • How will drivers specify their desired exits? (exit numbers? road names? town names? mileposts?)
  • Will all sources of weather, traffic and road condition data have equal credibility?

back to assignment