Seminar assignments - metro ticket vending machine PDF

Preview

Summary

Metro Ticket Vending Machine
...

Description

SOEN6481 Software Systems Requirements Specification Summer 2015

Deliverable3 Metro Ticket Vending Machine (Team E)

These are base marks. The marks of individual members can vary.

P1 (60/70) + P2 (7/10) + Organization and Presentation (13/15) + Miscellaneous Support for D2 (Wiki, Glossary, Other) (5/5) = 85.

Submitted By: You should not include names and ID #s simultaneously. Jatinderpal Singh (7727267) Robert Saliba (6412033) Mayur Ravindra Patil (6896871) Babak Boroujerdi Far (6273955)

1

Table of Contents

1

2

Problem 1: User Stories...........................................................................................................................................3 1.1

Language Selection Mode................................................................................................................................3

1.2

Ticket Selection Mode......................................................................................................................................3

1.3

Recharge Card...................................................................................................................................................4

1.4

Payment Selection Mode..................................................................................................................................4

1.5

Make Payment by card.....................................................................................................................................5

1.6

Make Payment by cash.....................................................................................................................................5

1.7

Print Ticket........................................................................................................................................................6

1.8

Payment Receipt...............................................................................................................................................6

1.9

Return Change..................................................................................................................................................7

1.10

Misuse User Information................................................................................................................................7

1.11

Terminate Session..........................................................................................................................................8

1.12

Hack System...................................................................................................................................................8

Problem 2:................................................................................................................................................................9 2.1

Software Requirements....................................................................................................................................9

2.2

User Stories and their required sources.........................................................................................................10

2.3

Backward Traceability Matrix (TMTVM)............................................................................................................11

3

Table of Contribution on Deliverable #3................................................................................................................12

4

Glossary..................................................................................................................................................................12

5

Resource Link.........................................................................................................................................................12

6

References..............................................................................................................................................................13

2

1 Problem 1: User Stories 1.1 Language Selection Mode As TVM user can select one of available language by TVM so that user can perform further operation in his/her preferable language provided by TVM. Identifier: US1 Name: Language Selection Mode Priority: High Constraint: Language will be selected if user selects it else if user press continue, operation will be continue in default language of TVM. Note: Need to discuss Can user change language in middle of operation? Acceptance Criteria:  

User selects one of the available language Or user press continue This is design-specific. without selecting language for default language.

1.2 Ticket Selection Mode TVM user can see the different ticket types along with the fares so that TVM user can choose tickets as per my requirement. Identifier: US2 Name: Ticket Selection Mode Priority: High Constraint: Ticket type should be displayed along with their fares. Note: Need to discuss the possibility to add more types of ticket in future. Acceptance Criteria:  User selects the ticket type and number of tickets.

3

1.3 Recharge Card TVM user can recharge metro card so that user can use it for travelling. Identifier: US3 Name: Recharge Card Priority: High Constraint: Metro card can be recharged if it’s valid metro card and can only be recharged if the user has the sufficient cash or balance in his/her credit/debit card. Acceptance Criteria:  

User inserts the metro card in TVM. User enters the valid PIN number of credit/debit card.

This is not the proper way of expressing a test. You should state a fact.

1.4 Payment Selection Mode TVM user can select payment method so that user makes a payment.

Identifier: US4 Name: Payment Selection Mode Priority: High Constraint: The user will enter incorrect mode of payment inadvertently. Acceptance criteria: 

User has to log in the system and select ticket type This is not atomic.



User has to enter cash or his/her credit card information to proceed.



After submitting the credit card information ticket will be printed.

4

1.5 Make Payment by card TVM user can make payment by card to purchase ticket or recharge card.

Identifier: US5 Name: Make Payment. Priority: High Constraint: Card information entered by user must be correct as all information will be validated via bank’s network. Note: Need to ask which payment method customer wants to adopt, either by credit/debit card or cash. Acceptance Criteria: 

Card must be valid.



Valid PIN must be entered by customer.

1.6 Make Payment by cash TVM user can make payment by cash to purchase ticket or recharge card.

Identifier: US6 Name: Make Payment. Priority: High Constraint: User should provide required cash to make a payment. Acceptance Criteria: 

User should pay using Canadian currency (as TVM is used in Canada )

5

1.7 Print Ticket TVM user can receive a ticket printed by the ticket vending machine so that TVM user can use it for travelling.

Identifier: US7 Name: Print Ticket Priority: High Constraint: The ticket can only be printed after a successful transaction. Note: Need to discuss the possibility of display of the ticket type and ticket validity date on the ticket itself. Acceptance Criteria:    

User selects one of the ticket type Entered Credit/debit card is valid. User enters valid credit/debit PIN number. User inserts sufficient funds (cash) if user opts to pay by cash.

1.8 Payment Receipt TVM user can print payment receipt so that user can keep payment receipt for record. Identifier: US8 Name: Print Receipt Priority: Medium Constraint: The receipt can only be printed after a successful transaction. Acceptance Criteria:   

Entered credit/debit card is valid. Entered credit/debit PIN number is valid. User inserts sufficient funds (cash) if he/she opts to pay by cash.

6



User can choose to either accept or decline with the printing of the receipt by the machine.

1.9 Return Change TVM user can receive change if he pays more than the required amount through cash payment mode.

Identifier: US9 Name: Return change Priority: Medium Constraint: The change will only be returned if the user pays more than required amount by cash payment mode Acceptance Criteria:   

User should enter correct type of ticket on the console. User must select cash mode of payment. User must have inserted more cash than the required amount.

The style of acceptance criteria must improve. Remove “User …” from each, and, for example, say: “The type of ticket entered on the console is correct.”

1.10 Misuse User Information A fraudster wants to steal personal information of credit card so as to make criminal unauthorized (The difference is that a charge will not be criminal unless determined so by the law.) charges.

Identifier: US10 Name: Misuse user information Priority: High Constraint: Need to discuss the ways of misusing the system in different ways.

7

1.11 Terminate Session TVM user can terminate session so TVM user can terminate its current session. The value seems to repeat the goal. Identifier: US11 Name: Terminate Session. Priority: Low. Constraint: 

User must have started one of the processes, like buying ticket or printing payment receipt.



User must get his/her metro card back if it is inserted to TVM machine

Note: Cancellation of process must be reconfirmed from user. Acceptance criteria: 

User must have started one of the process.



Process should be cancelled before start of a transaction.

1.12 Hack System Hacker wants to hack the system so as to get unauthorized access to system.

Identifier: US12 Name: Hack System Priority: High

8

Note: Need to discuss how to close hack able holes and security breaches so that the malicious user cannot hack the system. There could be other negative user stories.

9

2 Problem 2: 2.1 Software Requirements Software requirements for metro ticket vending machine (TVM) are as follows: ID

Software Requirement

Description

SR1

Metro card

Ability to accept and recharge metro card.

SR2

Screen A

Screen that accepts one of the language FR/EN

SR3

Ticket Selection

Ability to select a ticket type among different available types.

SR4

Screen B

Screen that show different type of tickets

SR5

Receive Payment

System has ability to accept payment by different methods.

SR6

Money, Debit/Credit Card

Use one of these things to pay for the purchase

SR7

Ticket Printing

System can print a ticket

SR8

Screen C

SR9

Receipt generation

SR10

Screen D

SR11

Return Change

SR12

Calculating Price

SR13

Ticket Generate

System calculates the price of purchased ticket Ability to generate ticket.

SR14

Protection

System will have ability to secure itself from malicious attacks

SR15

Screen F

Screen F allows users to terminate the process

SR16

Process termination

System can terminate a process.

SR17

Validation

System will validate debit/credit card.

Screen C can print the ticket. System can generate a receipt of payment. Screen D can print on-screen data to the printer. Ability to give out change in form of coins

2.2 User Stories and their required sources For some of the user stories, there should be other source besides SRs. For example, use cases, people, literature, … 10

Identifier

User Story

Source(s) SR2

As TVM user can select one of available language by TVM so that user can perform further operation in his/her preferable language provided by TVM. TVM user can see the different ticket types along with the fares so that TVM user can choose tickets as per my requirement. TVM user can recharge metro card so that user can use it for travelling. TVM user can select payment method so that users make a payment. TVM user can make payment by card to purchase ticket or recharge card. TVM user can make payment by cash to purchase ticket or recharge card. TVM user can receive a ticket printed by the ticket vending machine so that TVM user can use it for travelling. TVM user can print payment receipt so that user can keep payment receipt for record. TVM user can receive change if he pays more than the required amount through cash payment mode. A fraudster wants to steal personal information of credit card so as to make criminal charges. TVM user can terminate session so TVM user can terminate its current session. Hacker wants to hack the system so as to get unauthorized access to system.

US1

US2 US3 US4 US5 US6 US7 US8 US9 US10 US11 US12

US1,SR3,SR4

US2,SR1 US2,US3,SR5,SR4 US4,SR5,SR6,SR17 US4,SR5,SR6 US5,US6,SR7,SR8,SR12

US5,US6,SR9,SR10,SR12,SR13 US7,US6,SR6,SR11,SR12 SR14 US7,US8,SR15,SR16,US7,US8 SR1

2.3 Backward Traceability Matrix (TMTVM)

SR1

US1 US2 US3 US4 US5 US6 US7 US8

SR2

SR3

SR4

X

X

SR5

SR6

X X X

X X

SR7

SR8

SR9

S10

S11

S12

SR13

SR14

SR15

SR16

SR17

X X X

X X

X X

X

X X

X 11

US9 US10 US11 US12

X

X

X X X

X

X

2.4

12

3 Table of Contribution on Deliverable #3

Team Member Name Jatinderpal Singh Robert Saliba Mayur Ravindra Patil Babak Boroujerdi Far

Details of contributions 1. 2. 1. 2. 1. 2. 1. 2.

User Stories Editing and Final Documentation User Stories User Stories sources User Stories User Stories Requirements User Stories Traceability Matrix

4 Glossary Sr. No 1 2 3

Abbreviation TVM TM PIN

4 5 6

Unauthorized user Traceability Hackable Holes

Description Ticket Vending Machine use to buy ticket or recharge card Traceability Matrix Personal Identification Number: it is provided by the bank and is unique. Unofficial, Unapproved Ability to trace software requirements or history so on. Possibilities for unauthorized access

5 Resource Link https://softwarerequirementspecification.wikispaces.com/file/detail/E-D3.docx

13

6 References [1] P. Kamthan, "SOFTWARE SYSTEMS REQUIREMENTS SPECIFICATION, SOEN 6481", summer 2015. [Online]. Available: http://users.encs.concordia.ca/~kamthan/courses/soen-6481/user_stories_introduction.pdf.

[2] P. Kamthan, "SOFTWARE SYSTEMS REQUIREMENTS SPECIFICATION, SOEN 6481", summer 2015. [Online]. Available: http://users.encs.concordia.ca/~kamthan/courses/soen-6481/user_stories_quality.pdf.

[3] P. Kamthan, "SOFTWARE SYSTEMS REQUIREMENTS SPECIFICATION, SOEN 6481", summer 2015. [Online]. Available: http://users.encs.concordia.ca/~kamthan/courses/soen-6481/user_stories_negative.pdf.

[4] Wikipedia.com, “Traceability Matrix”, http://en.wikipedia.org/wiki/Traceability_matrix [5] Ofnisystems.com, “Traceability Matrix”, http://www.ofnisystems.com/services/validation/traceabilitymatrix/.

14...