1 / 8

Deliverable No. 3

Deliverable No. 3. Explained. Some Requirements phase Artifacts. System functions and attributes are the absolute minimum

javan
Download Presentation

Deliverable No. 3

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. Deliverable No. 3 Explained

  2. Some Requirements phase Artifacts • System functions and attributes are the absolute minimum • Requirement andliaison teams--list of parties that should be involved in specifying the function and system attributes, and performing reviews, testing,, negotiations, and so on. X Assumptions –Things we assume will be true. X Risks: Things which can lead to failure or delay. X Dependencies: Other parties, systems and products that this system depends upon for completion. * Use Case: * Draft conceptual Model Deliverable # 3. Submit the ed Deadline 17.02.11

  3. System Functions and Categories Function CategoriesMeaning EvidentShould perform, and user should acknowledge that it is performed HiddenShould perform, but not be visible to users. This is true of many underlying technical services, such as save information in a persistent storage mechanism. Hidden functions are often missed during the requirements gathering process FrillOptional; adding it does not significantly affect cost or other functions. To verify that some X is indeed a system function, it should make sense in the following sentence: The system should do <X>

  4. Category Ref# Functions Record the current sale - the items purchased Calculate current sale total, including tax and coupon calculations R1.1 evident R1.2 evident Capture purchase item information from a bar code using a bar code scanner, or manual entry of a product code, such as a universal product code(UPC) evident R1.3 R1.4 Reduce inventory quantities when a sale is committed hidden R1.5 hidden Log completed sales Cashier must log in with an ID and password in order to use the system evident R1.6 hidden R1.7 Provide a persistent storage mechanism Exemplary Basic Functions: Common/General Cont…2

  5. Basic Functions Category Ref# Functions Provide inter-process and inter-system communication mechanisms Display description and price of item recorded R1.8 hidden R1.9 evident

  6. Category Ref# Functions Handle cash payments, capturing amount tendered and calculating balance due R2.1 evident Handle credit payments, capturing credit information from a card reader or by manual entry, and authorizing payment with the store’s (external) credit authorization service via a modem connection. R2.2 evident Handle check payments, capturing drivers license by manual entry, and authorizing payment with the store’s (external) check authorization service via a modem connection evident R2.3 Log credit payments to the accounts receivable system, since the credit authorization service owes the store the payment amount. R2.4 hidden Payment Functions

  7. System (Quality) Attributes characteristics and dimensions (not functions) Attribute Detail and Boundary Constraints (boundary constraint) When recording a sold item, the description and price will appear within 5 seconds Response time (detail) Forms-metaphor windows and dialog boxes (detail) maximize for easy keyboard navigation rather than pointer navigation Interface Metaphor (boundary constraint) must log authorized credit payments to accounts receivable within 24 hours, even if power or device failure Fault tolerance Operating System platforms (details) Microsoft Windows 95 and NT

  8. System Attributes in Function Specifications Details and Constraints Ref# Functions Cat. Attribute Cat. Display description and price of item recorded R1.9 Response time evident 5 second maximum must Must want Forms based output colorful Interface metaphor Log credit payments to the accounts recei- vable system, since the credit authorization service owes the store the payment amount Must log to accounts recei- vable within 24 hours, even if power or device failure hidden Fault tolerance must R2.4 must Response time 10 second maximum

More Related