lOMoARcPSD|3862101

Seminar assignments - ticket vending machine

Software Requirements and Specifications (Concordia University)

StuDocu is not sponsored or endorsed by any college or university

Downloaded by Candy Somar (somarcandy582@gmail.com)
 lOMoARcPSD|3862101

SOEN 6481
Software Systems Requirements Specification
Summer 2015

Deliverable #3
Ticket Vending Machine

(Team-C)
Luis Angel Ipenza Marin
Maneesh Japa
Muhammad Farhan
Navleen Kaur
Sharath Kumar Reddy Jillela
Vijay Shah

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

P1 (58/70) + P2 (9/10) + Organization and Presentation (13/15) + Miscellaneous Support for D2

(Wiki, Glossary, Other) (4/5) = 84.

The style of expressing user story statements and tests can improve.

Instructor: Dr. Pankaj Kamthan

Downloaded by Candy Somar (somarcandy582@gmail.com)

 lOMoARcPSD|3862101

Contents
1. USER STORY.........................................................................................................................................3
1.1 Select Language...........................................................................................................................3
1.2 Select Refill Card..........................................................................................................................3
1.3 Select Type of Ticket....................................................................................................................4
1.4 Payment by Credit/Debit.............................................................................................................4
1.5 Payment by Cash.........................................................................................................................5
1.6 Cancel Transaction.......................................................................................................................5
1.7 Refund.........................................................................................................................................6
1.8 Print Ticket...................................................................................................................................6
1.9 Check History...............................................................................................................................7
1.10 Insert cash into machine.............................................................................................................7
1.11 Hack Financial Information..........................................................................................................8
2. TRACEABILITY MATRIX.........................................................................................................................8
3. Glossary.............................................................................................................................................10
4. REFERENCES......................................................................................................................................10
5. Link to Wiki Hosting service...............................................................................................................10
7. TEAM MEMBER’S CONTRIBUTIONS...................................................................................................11

Downloaded by Candy Somar (somarcandy582@gmail.com)

 lOMoARcPSD|3862101

1. USER STORY

User stories are short, simple description of a feature told from the perspective of the 
person who desires the new capability, usually a user or customer of the system. They 
typically follow a simple template [1]:

As a <type of user>, I want <some goal> so that <some reason>.

 MoSCoW approach [2] is used for prioritizing user stories.

1.1Select Language

Identifier: TVM-US-001

Name: Select Language

Date: June 8, 2015

Author: Team-C

Version: 1.0
Statement: The user selects This is not a proper style. the language preferred or easily to
communicate with machine for his own convenience.
Constraint: User should know either French or English language.
Priority: Should
Acceptance The selected option must be valid.
Criteria:

Downloaded by Candy Somar (somarcandy582@gmail.com)

 lOMoARcPSD|3862101

1.2Select Refill Card

Identifier: TVM-US-002
Name: Select Refill Card
Date: June 8, 2015

Author: Team-C

Version: 1.0
Statement: A User This is overly broad. Use some term such as commuter or traveler. can
recharge the card that they ? already owns, so that user need not purchase the
ticket every time they travel.
Constraint: User must have a valid debit/credit card or cash and a transport refill card. It is
better not to write compound statements.
Priority: Could
Acceptance The card inserted (i.e. Credit Card or Debit Card) must be valid.
Criteria:

1.3Select Type of Ticket

Identifier: TVM-US-003

Name: Select Type of Ticket

Date: June 8, 2015

Author: Team-C

Version: 1.0
Statement: User should ? select a type of ticket that best suits his need How does one
know this?.
Constraint: Not Applicable
There could be usability constraints.
Priority: Should
Acceptance The user selects a type of ticket from the options provided.
Criteria: What if the machine is out of paper or ink to print tickets (or out of tickets,
assuming they are already printed and ready to be dispensed)?

Downloaded by Candy Somar (somarcandy582@gmail.com)

 lOMoARcPSD|3862101

1.4 Payment by Credit/Debit

Identifier: TVM-US-004

Name: Payment by Credit/Debit

Date: June 8, 2015

Author: Team-C

Version: 1.0
Statement: The user can make the payment through debit/credit card so that the
transaction gets completed.
Constraint: There should be connection between TVM and bank in order to process the
transaction.
There could be security constraints.

Priority: Could
Acceptance  There should be enough balance in the account of user.
Criteria:  PIN (Personal Identification Number) should be correct.

1.5 Payment by Cash

Identifier: TVM-US-005

Name: Payment by Cash

Date: June 8, 2015

Author: Team-C

Version: 1.0
Statement: The user can pay by cash in order to complete the transaction.
Constraint: Multiple denominations should be available in the machine.
Priority: Could
Acceptance The user should insert the amount of cash equal to or greater than the
Criteria: amount to be paid. This could be better expressed. Remove “The user
should …”.

Downloaded by Candy Somar (somarcandy582@gmail.com)

 lOMoARcPSD|3862101

1.6Cancel Transaction

Identifier: TVM-US-006

Name: Cancel Transaction

Date: June 8, 2015

Author: Team-C

Version: 1.0
Statement: User can cancel the transaction at any time before the payment has been
made.
Constraint: The cancelation can be possible only before the payment
Priority: Could
Acceptance The cancelation is accepted only before the payment is made.
Criteria:

1.7 Refund

Identifier: TVM-US-007

Name: Refund
Date: June 8, 2015

Author: Team-C

Version: 1.0
Statement: The system will refund the user when there is a problem in transaction or
printing the ticket.

Constraint: When the payment is successful and the transaction is incomplete.

Priority: Would
Acceptance The machine will register a refund complaint only if there is a problem in
Criteria: completing the transaction.

Use tense consistently: “is” in one place “will” in another.

Downloaded by Candy Somar (somarcandy582@gmail.com)

 lOMoARcPSD|3862101

1.8Print Ticket

Identifier: TVM-US-008

Name: Print Ticket

Date: June 8, 2015

Author: Team-C

Version: 1.0
Statement: The machine ? This is a user story! should print the traveling ticket(s). If
required by the user a receipt can also be printed. This is a compound user
story.
Constraint: There should be enough ink and paper in the machine for printing.

Priority: Should
Acceptance The payment transaction should be approved.
Criteria:
1.9 Check History

Identifier: TVM-US-009

Name: Check History

Date: June 8, 2015

Author: Team-C

Version: 1.0
Statement: The maintenance employee should check the history of last’s week demand on
transport tickets to put a suitable amount of cash into the machine.
Constraint:  The history of transactions should be shown by week.
 The maintenance employee should be able to check the transaction’s
history of the last 12 past months.

Priority: Should
Acceptance N/A
Criteria:

1.10 Insert cash into machine

This is too granular (too small for a user story).

Downloaded by Candy Somar (somarcandy582@gmail.com)

 lOMoARcPSD|3862101

Identifier: TVM-US-010

Name: Insert cash into machine

Date: June 8, 2015

Author: Team-C

Version: 1.0
Statement: The maintenance employee will insert the amount of cash required on the
specific denominations into the machine.
Constraint:  The cash inserted on the TVM cannot exceed the cash container’s
capacity.
 The amount of cash inserted cannot exceed the limit established by
the managers.

Priority: Would
Acceptance The bills and coins denominations of the cash inserted on the TVM are also
Criteria: selected following the last week’s demand.
1.11 Hack Financial Information

Identifier: TVM-US-011

Name: Hack Financial Information

Date: June 8, 2015

Author: Team-C

Version: 1.0
Statement: The Hacker can get account details in order to gain authorization to user’s
financial account.
Constraint: N/A
Priority: Could
Acceptance N/A
Criteria:

There could be more negative user stories. For example, use of counterfeit money.

2. TRACEABILITY MATRIX

A traceability matrix is a table that correlates any two baselined documents that require a many
to many relationship to determine the completeness of the relationship. It is often used with high-

Downloaded by Candy Somar (somarcandy582@gmail.com)

 lOMoARcPSD|3862101

level requirements (sometimes known as marketing requirements) and detailed requirements of

the software product to the matching parts of high-level design, detailed design, test plan, and
test cases. [3]

Identifier Name User Stories Elicitation Source

TVM-US-001 Select Language The user selects the language UC6-C-D2
preferred or easily to
communicate with machine
for his own convenience.
It is not necessary to mention
the entire statement. That is
why one has identifiers.
TVM-US-002 Select Refill User can recharge the card http://www.stm.info/en/info/fares/
Card he already owns so that he opus-cards-and-other-fare-media/
need not purchase the ticket opus-card
every time he wants to travel.
TVM-US-003 Select Type of User can select type of ticket http://www.stm.info/en/info/fares/
Ticket that best suits his need. transit-fares

TVM-US-004 Payment by The user can make the http://www.stm.info/en/info/fares/

Credit/Debit payment through debit/credit points-sale
card so that the transaction
gets completed.
TVM-US-005 Payment by The user can pay by cash in http://www.stm.info/en/info/fares/
Cash order to complete the points-sale
transaction.
TVM-US-006 Cancel User can cancel the Figure 2.0 Use Case Diagram – Ticket
Transaction transaction at any time Vending Machine- C-D2
before the payment has been
made.
TVM-US-007 Refund The system will refund the https://efixmetrocard.mtanyct.info/
user when there is a problem MVMPrerequisites.aspx
in transaction or printing the
ticket.

TVM-US-008 Print Ticket The user can print the https://en.wikipedia.org/wiki/

traveling ticket(s). If required Ticket_machine
by the user a receipt can also
be printed
TVM-US-09 Check History The maintenance employee UC2-C-D2
should check the history of
last’s week demand on
transport tickets to put a
suitable amount of cash into

Downloaded by Candy Somar (somarcandy582@gmail.com)

 lOMoARcPSD|3862101

the machine.
TVM-US-010 Insert cash into The maintenance employee UC2-C-D2
machine can insert the amount of cash
required on the specific
denominations into the
machine.
TVM-US-011 Hack Financial The Hacker can get account http://www.technotification.com/
Information details in order to gain 2014/02/top-10-black-hat-hacker-and-
authorization to user’s thier-story.html
financial account.

3. Glossary
 
TVM-US Ticket Vending Machine User Story of a Use Case

MoSCoW The abbreviation MoSCoW stands for Must, Should, Could, and Would.

Acceptance Criteria The criteria under which the system satisfies or performs a certain task.

Identifier An alpha-numeric code is used in order to identify a user story.

Statement Description of a task performed by a system ? or user.

Denominations A proper description of a currency amount, usually for coins or banknotes.

[4]
Constraint A rule that specifies a valid condition of data. [5]

Baselined Modification or rewriting of any officially approved document.[6]

documents

4. REFERENCES

[1] Available Online: http://www.mountaingoatsoftware.com/agile/user-stories

Downloaded by Candy Somar (somarcandy582@gmail.com)

 lOMoARcPSD|3862101

[2] Available Online: Kamthan P, “ Introduction to User Stories”.

http://users.encs.concordia.ca/~kamthan/courses/soen-6481/user_stories_introduction.pdf
[3] Available Online: https://en.wikipedia.org/wiki/Traceability_matrix

[4] Available Online: https://en.wikipedia.org/wiki/Denomination_(currency)

[5] Available Online: (IEEE 1320.2-1998 (R2004) IEEE Standard for Conceptual Modeling
Language Syntax and Semantics for IDEF1X97 (IDEFobject), 3.1.41)
[6] Available Online: http://www.geekinterview.com/talk/1086-base-line-document.html

[7] Available Online: Kamthan P, “ Quality of User Stories”.

http://users.encs.concordia.ca/~kamthan/courses/soen-6481/user_stories_quality.pdf
[8] Kamthan P, “ User Stories in Context”.
http://users.encs.concordia.ca/~kamthan/courses/soen-6481/user_stories_context.pdf
[9] Available Online : Kamthan P,”Negative User Stories”.
http://users.encs.concordia.ca/~kamthan/courses/soen-6481/user_stories_negative.pdf

5. Link to Wiki Hosting service

https://soen6841-teamc.wikispaces.com/D3

6. TEAM MEMBER’S CONTRIBUTIONS

Team Member Contributions

 Brainstorming
1. Navleen Kaur
 User Stories Identification
2.Muhammad Farhan  User Stories Description
 Peer review
1. Sharath Kumar Reddy Jillela  Brainstorming
2. Luis Angel Ipenza Marin  User Stories Identification
 User Stories Description
 Peer review

Downloaded by Candy Somar (somarcandy582@gmail.com)

 lOMoARcPSD|3862101

1. Maneesh Japa  Brainstorming
2. Vijay Shah  Elicitation of User Stories
 Backward Traceability Matrix construction
 Integration of document.
 Peer review

Downloaded by Candy Somar (somarcandy582@gmail.com)