ITECH2002 Assignment 2: Dynamic Modelling, Screen Design, Test Plans

This document presents a comprehensive solution for ITECH2002 Systems Modelling Assignment 2, focusing on dynamic modelling, screen design, and test plans. It includes fully developed use cases for Email Communication and Service Management, detailing scenarios, actors, stakeholders, preconditions, postconditions, and flow of activities. Activity diagrams and system sequence diagrams are provided to visually represent the processes. Additionally, the assignment incorporates a top-level Invision screen design and a detailed test plan, outlining test data, expected outputs, and various testing methodologies such as RIGHT-BICEP and boundary value analysis. The document concludes with a bibliography of cited sources.

Running head: ITECH2002 – SYSTEMS MODELLING
Assignment 2 – Dynamic Modelling, Screen Design and Test Plans
Name of the Student
Name of the University
Author’s Note

1
ITECH2002 – SYSTEMS MODELLING
Table of Contents
Fully Developed Use case: Email Communication.........................................................................2
Fully Developed Use case: Service Management...........................................................................3
Activity Diagram 1: Email Communication....................................................................................6
Activity Diagram 2: Service Management......................................................................................7
System Sequence Diagram 1: Email Communication.....................................................................8
System Sequence Diagram 2: Service Management.......................................................................9
Top Level Invision screen design..................................................................................................10
Test Plan........................................................................................................................................11
Bibliography..................................................................................................................................15

2
ITECH2002 – SYSTEMS MODELLING
Fully Developed Use case: Email Communication
Use Case
Diagram:
Customer Relationship Management System
Scenario: Email Communication
Triggering event: The user should be logged into the system and have access for
communicating with the system.
Brief Description: The input of the user is needed to be validated and email service is
needed to be used for sending and receiving email about the services
needed by the user.
Actor: User, UserController, EmailService and EmailModel
Stakeholders: User, Admin, System
Preconditions: The users should have the login credentials and access to the
information system for sending email to the Admin
Postconditions: The Admin should provide response to the email by checking the
validation and adding the details of the service requested by the client
by generating report from the information system.
Flow of Activities Actor System
The customer should have
logged in into the information
system
The system check for validation
of the input of the user accessing
the system
The availability and details of
the service are displayed to the
customer.
Admin The admin should provide a
response to the email after
checking the details of the
customer query
In invalid query is found an
error message is attached with
email and sent to the customer
Customer The customer can enter valid
details and resent the email after
checking the service

3
ITECH2002 – SYSTEMS MODELLING
Admin New data is added and sent to
the customer
Excepted
Condition
1. Poor internet connectivity
2. Unavailability of customer details
3. Incomplete payment due to gateway error
Fully Developed Use case: Service Management
Use Case
Diagram:
Customer Relationship Management System
Scenario: Service Management
Triggering event: The details of the service are needed to be available to the Sales
manager
Brief Description: The sales manager can login into the system for getting the details of
the ongoing, upcoming and completed service offered by the company
and the details of the clients.
Actor: Sales manager, Company, Service Material and Coordinator
Stakeholders: User, Admin, System
Preconditions: The details of the service and the resources available with the
organization should be inputted in the system for the management of
user request
Postconditions: Training session should be arranged for demonstrating the

4
ITECH2002 – SYSTEMS MODELLING
functionality of the system and increasing the usability.
Flow of Activities Actor System
Sales Manager Sales manager have the access
of the service details from the
database of the information
system
The location details are retrieved
and the service if available is
provided to the customer
Logistics The time and location details of
the service are identified and the
material that would be needed
for providing the service is also
updated in the information
system
The logistics requirement are
checked by conducting meetings
and if no details are found a
notification is sent to the
customer
Customer A response is received from the

5
ITECH2002 – SYSTEMS MODELLING
customer
Coordinator The coordinator is updated with
the notification for the
elimination of error for
providing the service
Excepted
Condition
1. Poor internet connectivity
2. Unavailability of customer details
3. Incomplete payment due to gateway error

6
ITECH2002 – SYSTEMS MODELLING
Activity Diagram 1: Email Communication

7
ITECH2002 – SYSTEMS MODELLING
Activity Diagram 2: Service Management

8
ITECH2002 – SYSTEMS MODELLING
System Sequence Diagram 1: Email Communication

9
ITECH2002 – SYSTEMS MODELLING
System Sequence Diagram 2: Service Management

10
ITECH2002 – SYSTEMS MODELLING
Top Level Invision screen design

11
ITECH2002 – SYSTEMS MODELLING
Test Plan
N
o
Guideline Short Description Test Data Expected
Output
1 RIGHT-
BICEP
Are the results right? Login
credentials of
user are inputted
in the system
The user is
needed to be
redirected to
a portal for
the user
2 RIGHT-
BICEP
Can the inverse relationship be
checked?
The logout
option is clicked
for returning to
the home page
The user
should be
redirected to
the home
page
3 RIGHT-
BICEP
Can the results be cross checked using
other means?
The admin login
credentials are
inputted for
getting access of
the system
modules
functionality
The user
management
and access to
user
information
and service
are needed to
be displayed
4 RIGHT-
BICEP
Can the error conditions be forced for
hapenning?
The database
should be
The response
time of the