1 / 9

Team

Team. Team Leads: Put your list of questions for Galaxy Sleuth on your web page and send me the URL Everyone: get ready to discuss questions on Thursday. Requirements. Required for architecture design Requirements elicitation Requirements modeling Requirements specification Results in a

regina
Download Presentation

Team

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Team • Team Leads: Put your list of questions for Galaxy Sleuth on your web page and send me the URL • Everyone: get ready to discuss questions on Thursday.

  2. Requirements • Required for architecture design • Requirements elicitation • Requirements modeling • Requirements specification • Results in a • Requirements document

  3. Requirements document format • List of possible sections • Not all sections will be in all requirements docs • Think of the sections as a guide for eliciting requirements for any system

  4. Requirements document format • Supported activity list • User activities supported by the system • HCI description • Illustrations/Diagrams of UI • Solved problems list • Problems solved by new system

  5. Requirements document format • Information sources list • Location of information that supports new system. Connectivity between systems, data entry bottlenecks. • Information-requesting organizations • Who depends on this system? What information does this system supply to dependents.

  6. Requirements document format • Checks and Balances • Data integrity tests • Online checking or Batch checking? • Security and fault-tolerance requirements • List of proprietary, classified, or private info • If critical system consequences of failure

  7. Requirements document format • Interoperating systems list • Systems that this one needs to work with • Estimates of information capacity and growth • Volume of data, network traffic, limitations • Project time frame • Time frame for milestones, constraints due to changes in law or life endangerment because of existing system

  8. Requirements document format • Prioritization of requirements • Which requirements need to be met first for smooth transition from old to new system • Non critical features • Ethical concerns • Privacy issues and how these issues are addressed

  9. Library System • College library needs a new Library Management System (LMS).

More Related