Software Engineering Methodology: City Glaziers System Report

Desklib provides solved assignments and past papers to help students succeed.

MITS5501
Software engineering methodology
Assignment 3
Student name:
Student ID:

Table of Contents
Introduction......................................................................................................................................4
Specification document...................................................................................................................5
Executive summary.....................................................................................................................5
System description.......................................................................................................................6
Scope............................................................................................................................................6
Feasibility analysis.......................................................................................................................6
Requirement specification...........................................................................................................6
Assumptions and constraints.......................................................................................................7
Assumptions:...........................................................................................................................7
Constraints...............................................................................................................................7
Use cases......................................................................................................................................8
Context model............................................................................................................................16
Leveled set of functional models...............................................................................................16
Design Document..........................................................................................................................17
Executive summary...................................................................................................................17
Architecture Design...................................................................................................................17
Hardware specifications.............................................................................................................18
Class diagrams...........................................................................................................................18
Interface design..........................................................................................................................19
Business process models............................................................................................................23
Sequence diagrams....................................................................................................................24
Interaction diagrams..................................................................................................................27
State diagrams............................................................................................................................29
Conclusion.....................................................................................................................................31
References......................................................................................................................................32

List of figures
Figure 1 Use case 1..........................................................................................................................8
Figure 2 Use case 2........................................................................................................................10
Figure 3 Use case 3........................................................................................................................12
Figure 4 Use case 4........................................................................................................................14
Figure 5 Context model.................................................................................................................16
Figure 6 Functional model.............................................................................................................16
Figure 7 architecture design of city glaziers..................................................................................17
Figure 8 Class diagram of city glaziers.........................................................................................18
Figure 9 Activity diagram 1...........................................................................................................19
Figure 10 Activity diagram 2.........................................................................................................20
Figure 11 Activity diagram 3........................................................................................................21
Figure 12 Activity diagram 4.........................................................................................................22
Figure 13 Business process model 1..............................................................................................23
Figure 14 Business process model 2..............................................................................................23
Figure 15 business process model 3..............................................................................................24
Figure 16 Business process model 4..............................................................................................24
Figure 17Sequence diagram 1.......................................................................................................25
Figure 18 Sequence diagram 2......................................................................................................25
Figure 19 Sequence diagram 3......................................................................................................26
Figure 20 Sequence diagram 4......................................................................................................26
Figure 21 Interaction diagram 1....................................................................................................27
Figure 22 Interaction diagram 2....................................................................................................27
Figure 23 Interaction diagram 3....................................................................................................28
Figure 24 interaction diagram 4.....................................................................................................28
Figure 25 State diagram 1..............................................................................................................29
Figure 26 State diagram 2..............................................................................................................29
Figure 27 State diagram 3..............................................................................................................30
Figure 28 State diagram 4..............................................................................................................30

Introduction
The report is based on the case study that is of city Glaziers. The work of the company is to
supply glass for doors and windows either in bulk for construction purpose or in small quantity
for repairing purpose. The report is mainly divided into two sections that are specification
document and design document. This section will cover the description of the system, analysis of
feasibility, assumptions and constraints and scope of the system. The content is supported by
various diagrams including use case diagrams, context models, the architectural design of the
system, interaction diagrams, class diagrams, sequence diagrams, interface design, business
process models and state diagrams, etc.

Specification document
Executive summary
The given case study is about the business organization named City Glaziers. The company is
working around the metropolitan area of Melbourne. The main work of the company is to supply
the glass for doors and windows along with other structures. The company supplies glass in bulk
for the construction and even for the repairing purpose (replacement of broken doors or
windows). The existing system of the company has 2 main areas of work that supports large
projects and repairing of the glass. The company is facing various issues that are occurring with
the growth of the company and increased demand for the workload. The main issue with the
company is that the company is working on a manual system which leads to various difficulties.
Thus, the company needs a feasibility study on the operations to computerize them.

System description
The existing system of the business organization depends on the manual system which supported
the organization well. This becomes outdated because of the high demand for workload this can
leads to the situation of bottlenecks. The existing system of the company has mainly two areas
that repair section and large project section. In the section of the large project, quotes are used
for the job by replying to the RFQs of Construction Company. The repair section is headed by
the Ben Hanscom. He also manages the Glazier truck fleet.
Scope
The computerization of all the operations involved in the business organization will remove the
bottlenecks of the system. A computer system will automatically check the schedule as well as
availability of the nearest Glazier truck. Automation will be helpful to check whether the
requirement of the customer can be fulfilled or not. This automation will be helpful to analyze
the job sheets. The completion of job sheets will perform on computer to make the process easy.
The scope of the business is good as the company providing timely and quality delivery of glass
to the customers as well as services for repairing.
Feasibility analysis
The existing system of the company is not feasible technically. As all the operations of the
company are based on the manual system although the existing system is economically feasible.
The computerized system will be more technically feasible. This may not be considered as
economically feasible as a manual system but this system will provide high feasibility in terms of
operations also (Spacey, 2017).
Requirement specification
Functional:
 The system should be able to track the records of job sheets and work orders
 The system should be able to respond to the RFQ of company
 The system must be able to create a work order
 The system should be able to create the timeline document
 The system should support payment and supply orders
Non-functional:
 Security of the system and information
 Portability of the system
 Workload handling power
 Tracking software
 Hardware support
 Skilled workforce (Eriksson, 2015).

Assumptions and constraints
Assumptions:
 The company has enough funds to implement the new computerized based system
 The implementation phase of the system will not affect the operations of the existing system
 There are enough resources to implement the system
Constraints
 Employees who are not sound technically will require training to work on the computerized
based system
 In the absence of backup, the computerized data may get lost, due to any malicious activity.
 Availability of power supply is necessary to use a computerized solution (Usmani, 2019)

Use cases
Figure 1 Use case 1
Description
Actor Customer
Description Customer is responsible to make an order request
or repair request and then do payment if an order is

received successfully.
Pre-condition The client should have a requirement and
knowledge about company services.
Flow  Make order request
 Payment
 Repair request
Actor Melbourne Glass plant
Description Fulfill the request of raw materials generated by the
head of large projects
Pre-condition The large project had should have a requirement of
raw materials
Flow  Receive order
 Fulfill the request
Actor Large project head
Description Head of large project receives request from the
customer, and develop a timeline document, make
request for raw materials from Melbourne glass
plant, prepare the order and book the glazier truck
for delivery.
Pre-condition The project head should receive a request from the
customer or company.
Flow  Receive request
 Develop a timeline document
 Make a request for raw materials
 Prepare order and book truck
Actor Repair section
Description Receive repair request from the client, check and
schedule the truck, then fill the job sheet after the
task completion.
Pre-condition Customer should have a repair requirement and
truck should be available.
Flow  Receive repair request
 Schedule the truck
 Fill the job sheet

Figure 2 Use case 2
Description
Actor Customer
Description The clients make a requirement for the order and
do the payment when order received successfully.
Pre-condition In a computerized system, the internet and
electricity should be available. It also requires a
communication channel.
Flow  Make requirement
 Receive order
 Payment
Actor Supplier
Description The supplier is responsible to prepare an order,
book the glazier truck, generate work requirement,
collate the job sheets and receiving payment and

order.
Pre-condition The supplier should have ordered from the client,
and have enough raw materials to fulfill the order.
Flow  Receive the order
 Prepare installation order
 Book the glazier truck
 Generate work requirement
 Collate job sheets
 Receive payment

Figure 3 Use case 3