CIS5302: System Analysis and Design Report for Cosies Insulation

This report presents a comprehensive system analysis and design for Cosies Insulation, addressing key aspects such as "to-be" design, organizational change, and screen design. It includes detailed activity diagrams illustrating the proposed system's workflow, comparing "as-is" and "to-be" models to assess the impact of the new system. The report also covers screen designs for essential functionalities, acceptance criteria, and the application architecture. Furthermore, it features an entity-relationship diagram, a client report summarizing the analysis, and an overview of the scrum organization used for project development. The analysis focuses on improving Cosies Insulation's operational efficiency, particularly in call center and sales team interactions, with a focus on data-driven decision making and streamlined processes.

Running head: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design
Name of the Student:
Name of the University:
Author Note

1
SYSTEM ANALYSIS AND DESIGN
Table of Contents
Task 2.01 “To-be” design – activity diagram............................................................................2
Task 2.02 Organisational change...............................................................................................3
Task 2.03 Screen design.............................................................................................................4
Reports...................................................................................................................................4
Customer Calling...................................................................................................................5
Task 2.04 Acceptance Criteria...................................................................................................5
Task 2.05 Applications Architecture..........................................................................................9
Task 2.06 Entity Relationship Diagram (ERD).......................................................................10
Task 2.07 Report to Client.......................................................................................................11
Task 2.08 Scrum Organisation.................................................................................................12
Bibliography.............................................................................................................................14
Appendix..................................................................................................................................15
Task A: Project Journal........................................................................................................15

2
SYSTEM ANALYSIS AND DESIGN
Task 2.01 “To-be” design – activity diagram
The to-be design is used for the description of the developments taking place in the
organization. The to-be model used for the description of the Cosies Insulation information
system of the organization is provided below:

3
SYSTEM ANALYSIS AND DESIGN
From the above To-be design it has been assessed that the call centre staffs are mainly
responsible for the making the calls. In this process if the call goes into the waiting stage then
a reminder is provided again for connecting the call. The call gets connected to the staffs at
the call centre the whole call is recorded by the system of the organization. From the process
it has been assessed that the sales representative are responsible for receiving notification,
making quote and attending meetings. In the ending stage the manager receives all the reports
regarding the system.
Task 2.02 Organisational change
The organizational changes can be described easily with the help of the evaluation of
the as-Is and the To-Be model. The model has been developed for the betterment of the
organization and the increase in the business efficiency for themselves. The As-Is process has
been used for the developed of the current system model and identification of the problems
that are being faced in the current model. However, the To-Be model is developed later on for
the identification of the remedies to the problems arising in the system.
The To-Be model describes an information system, which is to be used in the
organization for mitigating the problems faced with the current business model of the system.
There a large number of issues in the current process of the organization such as the no
proper reporting system. In addition to this, issues were created reading the follow ups to be
taken for the client who are not picking up the phone calls and employee dissatisfaction level
was also very high for the system. Hence, these issues were required to be resolved by the
development of the to-be model. The information system developed would be able to send
repetitive reminders to the staffs who are calling the customers. Additionally the developed
system would also be able to provide the administrator and staffs with the report options that
would be helpful in gaining insights on the business of the organization.

4
SYSTEM ANALYSIS AND DESIGN
Task 2.03 Screen design
The MUST Cases identified for the designing of the screens in the system are the
reports viewing option and calling customer options.
Reports
In the above diagram report section screen of the Cosies Insulation has been provided.
From the screen it has been assessed that the report section is having total six functionality.
From this section reports can be generated regarding sales data, production related data,
employee data, staff ranking data, customers without mail, ranking of the staffs and staff
attrition related data. From this functionality area various of important data can be extracted
which are important for the Cosies Insulation organization.

5
SYSTEM ANALYSIS AND DESIGN
Customer Calling
In the above picture customer calling interface has been shown of the Cosies
Insulation. The staffs at the call centre can open this menu for complete information about the
customers which are stored in the database of the organization. In this information the name
of the customer is displayed. With that, the address of the customer is also displayed through
this menu. Gender of the customer can is also provided in this page. If the customer has
provided any type of email address then it will also be displayed in this menu. Also, any type
of provided additional contact will be displayed in this menu.
Task 2.04 Acceptance Criteria
For making a project successful, it is very important that the project is able to meet all
the major functions as wanted by the users of the system. The system should also satisfy the
criteria mentioned by the client for whom the project is being developed. There might be
issues within the project if the customers or the client is not satisfied with the product.

6
SYSTEM ANALYSIS AND DESIGN
Acceptance criteria are the conditions where the software products are required to meet
certain number conditions to be accepted by the users, customers and the other systems. The
criteria developed for the system are different for each of the users’ stories for the developed
system. The acceptance criteria when developed effectively helps in the avoiding any errors
and bugs from developing in the designed system. The acceptance criteria for the information
system development of the Cosies Insulation organization are described in the table provided
below:
User
ID
Requirement Input Acceptance Criteria
1 As manager I would like
it to generate all reports
including Sales, Geo
location, Call centre
activity & Commission
reports
Generate sales report Display Sales Report
2 As a member of Sales
team I would like to view
the ranking of the sales
leads.
Select ranking Display ranking
3 As a member of the sales
team I would like access
to the residential data on
my mobile along with any
additional info that was
recorded by the call centre
Enter the address of the
location
Obtain geographic
coordinates of the location

7
SYSTEM ANALYSIS AND DESIGN
staff during the call.
4 As a call centre staff I
would like the ability to
track my calls and also get
a reminder for call backs
to certain customers who
asked for a callback or
were not available during
initial call.
Store the call record Get reminders
5 As a call centre staff I
would like to have the
ability to call the
customer number using
the software rather then to
manually dial it to avoid
misdialled numbers.
Store customer number in
the system. Press call
button.
Redirect to calling the
customer option.
6 As manager I would like
to be able to view the
generated reports and be
able to add filters to
narrow down on certain
criteria leads.
Generate leads report Display leads Report
7 As an admin I would like
to have the ability to login
and access all of the
Login Authentication

8
SYSTEM ANALYSIS AND DESIGN
above information and
functions
8 As a member of the sales
team I would like the
software to detect my
location and show me the
route to the nearest
customers location so I
can identify and meet
customers according to
the area.
Enter the address of the
location
Obtain geographic
coordinates of the location
9 As a member of the sales
team I would like an
inbuilt calculator in the
software which will
enable me to give the
customers a quote
instantly and help me
close the deal.
Enter values Receive quote
10 As an admin I would like
the ability to manage
permissions for the users
and decide who gets
access to certain types of
classified information.
Change permission Change access control

9
SYSTEM ANALYSIS AND DESIGN
Task 2.05 Applications Architecture
The application architecture defines that is the form of pillars of a specific type of
enterprise architecture system. The application architecture describes application related
behaviour which are used in a business. This is also focused how the interactions will be done
among each other and with the users.

10
SYSTEM ANALYSIS AND DESIGN
In the above diagram architecture of the application has been displayed. There are
three types of layers in the architecture which are the data layer, presentation layer and the
business layer. In this system the users will be directly interacting with the components of the
UI. The UI process component interacts with the business components. This is connected
with the business layer of the application this directly fetches data from the data resources.

11
SYSTEM ANALYSIS AND DESIGN
Task 2.06 Entity Relationship Diagram (ERD)
Here the ER diagram is used for the analysis of the existing database within a system.
Through the analysis, problems in the logic can be identified. In the business information
system this type of diagrams are used analysis of the relational database for the business
processes.
Here the main entities in the system are the staffs, reports, calls, quote and the
customers. The main primary keys in this context are the ID’s of all the entities. For the