1 / 15

Chapter 7

Chapter 7. Other Requirements Good Fast Cheap Pick any two. Other Requirements Artifacts. Supplementary Specification: Such as reports, documentation, packaging, supportability, licensing, etc. Glossary: terms used Vision: Short summary of overall product

velvar
Télécharger la présentation

Chapter 7

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. Chapter 7 Other Requirements Good Fast Cheap Pick any two. CS6359 -- John Cole

  2. Other Requirements Artifacts • Supplementary Specification: Such as reports, documentation, packaging, supportability, licensing, etc. • Glossary: terms used • Vision: Short summary of overall product • Business rules: rules that affect more than one application, such as tax laws, employee discounts, etc. CS6359 -- John Cole

  3. How Thorough? • At inception, not very. • Writing the Vision and the Supplementary Specification clarify a first approximation of the product. • Written requirements will seldom be completely accurate. CS6359 -- John Cole

  4. FURPS+ for NextGen POSFunctionality • Logging and error handling • Pluggable rules • Security CS6359 -- John Cole

  5. Usability • Text visible from 1 meter • Avoid colors associated with color blindness • Speed and ease of use are essential CS6359 -- John Cole

  6. Reliability • Failure of external systems such as payment should be solved with a local solution, such as store and process later • Prove critical parts of your system correct • Good error handling CS6359 -- John Cole

  7. Performance • Quick lookup of items • Quick processing of payment • (Implies good database design, efficient algorithms) CS6359 -- John Cole

  8. Supportability • Adaptability to different kinds of users. Different stores using a POS have different rules. • Configurability: network configurations, credit card processes, etc. CS6359 -- John Cole

  9. Implementation • Java language • Perhaps MySQL CS6359 -- John Cole

  10. Hardware Interfaces • Touch screen monitor • Barcode scanner • Receipt printer • Credit card reader • Signature reader CS6359 -- John Cole

  11. Software Interfaces • Tax calculator • Accounting system • Inventory CS6359 -- John Cole

  12. Vision • Introduction • Positioning • Stakeholder descriptions • High-level goals • User-level goals • Product overview • Summary of features CS6359 -- John Cole

  13. Writing the Feature List • Terse is good • Use cases are not sufficient CS6359 -- John Cole

  14. Glossary • Description • Aliases • Format (for data elements) • Relationship to other elements • Range of values • Validation rules CS6359 -- John Cole

  15. Domain Rules • Could apply to more than one project • Should be in a separate document CS6359 -- John Cole

More Related