Dynamic Modelling, Screen Design and Test Plans for WMS Subsystem

CRICOS Provider No. 00103D ITECH2002_Assignment2_sem9_2019_201917_T_Keogh.docx Page 1 of 1
4
School of Engineering and Information Technology
Assignment 2, 2019/17
ITECH2002 – Systems Modelling
__________________________________________________________________________________
Assignment 2 – Dynamic Modelling, Screen
Design and Test Plans
Timelines and Expectations
Marks: Assignment will be assessed based on a mark out of 100
The following information is a summary from your Course Description:
Percentage Value of Task: 20% of the course marks
Due: Friday, September 27th, 2019 at 11:55pm
Minimum time expectation: 40 hours (per student)
Individual.
The organization Name:Publicit-e Pty. Ltd.
Student Name student ID sub-system
WMS Subsystem.

CRICOS Provider No. 00103D ITECH2002_Assignment2_sem9_2019_201917_T_Keogh.docx Page 1
3
of 1
3
School of Engineering and Information Technology
ITECH2002 Systems Modelling Assignment 2, 2019/17
Table of Contents
Design and Test Plans..............................................................................................................................................1
Timelines and Expectations..................................................................................................................................1
The fully developed use case descriptions............................................................................................................3
Table 1 below showing the fully developed Register job use case description of wms subsystem..................3
Table 2 below showing the fully developed Register job use case description of wms subsystem..................5
The activity diagrams............................................................................................................................................7
Figure 2 below showing the activity diagram of Register job Use Case of WMS subsystem..........................7
Figure 3 below showing the activity diagram of Make Payment Use Case of WMS subsystem.....................8
Sequence diagrams...............................................................................................................................................9
Figure 5 below showing the Sequence diagram of Make payment Use Case of WMS subsystem................10
Storyboarding......................................................................................................................................................11
The screens of use care register job by client are shown below.....................................................................11
The screens of Make payments by client are shown below............................................................................12
The test plan for register job usecase..................................................................................................................13
Figure 6 below show test plan of register job..................................................................................................13
References...........................................................................................................................................................14

CRICOS Provider No. 00103D ITECH2002_Assignment2_sem9_2019_201917_T_Keogh.docx Page 1
3
of 1
3
School of Engineering and Information Technology
ITECH2002 Systems Modelling Assignment 2, 2019/17
The fully developed use case descriptions.
Table 1 below illustrates the fully developed Prepare quote use case description of QuotenContract
subsystem.
Fully developed use case description
Use Case Name Prepare Quote
Scenario Success Scenario: The quote is
successfully requested, approved,
Prepared and provided.
Failure Scenario: The quote is rejected
because they do not meet the standard.
The system failed to register quote.
Triggering Event The sales person wants to prepare the
quote on the quoten Contract
subsystem.
Actors Client, and sales person .
Purpose To prepare quote for clients.
Overview/Description The use case shows overview and
description of the sales person
preparing quote and receiving quote
request from client on the quoten
Contract subsystem.
Type Business Requirement and Design
Requirement.
Stakeholders Client, system administrator,staffs,
Publicit-e Pty.
Ltd,partners,suppliers , Australia
Government and Sales person.
Pre-Conditions The quoten Contract subsystem is
operating normally. The client is login
on the system and has placed quote
request.
Post-Conditions The sales person has prepared the quote
and client has received quote.

CRICOS Provider No. 00103D ITECH2002_Assignment2_sem9_2019_201917_T_Keogh.docx Page 1
3
of 1
3
School of Engineering and Information Technology
ITECH2002 Systems Modelling Assignment 2, 2019/17
Special Requirements
Flow of Events
Actor Action System Response
The clients login, make quote request. The sales person’s
login on system and checks the status of the quote request.
If the request meets the standard the sales person accepts it
and if the quote does not meet the standard the sale person
rejects it and comment the reason to reject it.When quote is
accepted the client receives the quote.
System Authenticate both salesperson
and Client. The system displays page
which enable client to enter quote
request. The system verify quote
details. The system notify the client
about status of quote.
Alternate Flow of Events/Exceptional Conditions
Authentication client and sale person with correct details,
client make quote request, Prepare quote, complete quote
notification.
Wrong login details.
Quote rejected.
System calculate wrong details.
No internet services.
The system is not working