MURDOCH UNIVERSITY

ICT231 Assignment 1
Systems Analysis and Design

2009

ICT231 Assignment 1

2009

Contents
Part 1 Project Management.................................................................................................................................................................. 3
Pert chart................................................................................................................................................................................................... 3
Gantt chart................................................................................................................................................................................................. 4
Part 2 Systems Analysis....................................................................................................................................................................... 5
Background Research................................................................................................................................................................................. 5
Memo...................................................................................................................................................................................................... 5
Problem Analysis........................................................................................................................................................................................ 8
POOC Matrix............................................................................................................................................................................................ 8
Use Case Modelling.................................................................................................................................................................................. 11
Use cases list........................................................................................................................................................................................ 11
Use Case Diagram................................................................................................................................................................................. 13
Data Modelling......................................................................................................................................................................................... 14
Entities List........................................................................................................................................................................................... 14
Entity Relationship Diagram.................................................................................................................................................................. 15
Data Flow Diagrams................................................................................................................................................................................. 16
Context Data Flow Diagram.................................................................................................................................................................. 16
ASSIGNMENT COVER SHEET................................................................................................................................................................. 17
Page | 2

ICT231 Assignment 1

2009

Part 1 Project Management

Pert chart

Legend:
Task name
Start date
Finish date
Resource:

Task ID
Task duration

Assumptions:

Assuming 5 day working week (Saturday and Sunday are days off).
Assuming that task ID starts form 1.

The project should be completed on 19th May 2009.

Note. The critical path is in red colour and the chart can be seen clearly with % 200 zoom views.
Page | 3

ICT231 Assignment 1

2009

Gantt chart

Assumptions:

Assuming 5 day working week (Saturday and Sunday are days off).
Assuming that predecessors start from 1.

The project should be completed on 19th May 2009

Page | 4

2009

ICT231 Assignment 1

Part 2 Systems Analysis

Background Research
Memo

Memo
To: Mr. James Taylor
From: Mohammed Murad
Date: March 24, 2009
Subject: Systems Development Methodologies

In order to determine systems development methodologies for the potential projects this is an internet research describes Unified Process (UP) and Extreme
Programming (XP), what are they targeted towards and how they differ.
Unified Process is an object-oriented system development methodology created by the Rational Software Corporation, a division of IBM (Wikipedia).
Unified Process is not a certain process only, but it can be tailored and customised upon projects needs. It is designed to implement six best practice guidance
suited to particular development or project need:

Develop iteratively.
Define and manage system requirements.

Use component architectures.

Page | 5

ICT231 Assignment 1

Create visual models.

Verify quality.

Control changes.

2009

Unified Process has determined life cycle that consisting of four phases that allow the process to be presented at a high-level.
UP life cycle phases:
1. Inception.
2. Elaboration.
3. Construction.
4. Transition.
The unified process as a system development methodology must be tailored to the development team and specific project. Choices must be made about
which deliverables to produce and the level of formality to be used. Sometimes a project requires formal reporting and controls. Other times, it can be less
formal. The UP should always be tailored to the project.
Extreme Programming is a discipline of software development based on values of simplicity, communication, feedback, and courage. It works by bringing
the whole team together in the presence of simple practices, with enough feedback to enable the team to see where they are and to tune the practices to their
unique situation.( xprogramming.com). It focuses on the proven industry and best practice.
XP core values:
1. Communication.
2. Simplicity.
3. Feedback.
Page | 6

ICT231 Assignment 1

2009

4. Courage.
XB practices:
1. Planning.
2. Testing.
3. Pair programming.
4. Simple design.
5. Refracturing the code.
6. Owning the code collectively.
7. Continuos integration.
8. On-site customer.
9. System metaphor.
10. Small releases.
11. Forty-hour week.
12. Coding standards.

The main aim of XP is reducing costs. It suits the small projects the most.

Page | 7

2009

ICT231 Assignment 1

References:
1. www.wikipedia.com.
2. www.extremeprogramming.org.
3. Systems Analysis & Design in a Changing World, Fifth Edition, Satzinger J., Jackson R., Burd S.

Problem Analysis
POOC Matrix

PROBLEMS, OPPORTUNITIES, OBJECTIVES AND CONSTRAINTS MATRIX

Project:
Tracking

Peak Publishing Sales and Book

Project Manager:

System
Created by:

Mohammed Murad

Last Updated by: Mohammed Murad

Page | 8

2009

ICT231 Assignment 1

Date Created:

25/03/2009

Date Last Updated:

CAUSE AND EFFECT ANALYSIS

Problem or Opportunity
1. Multiple salespeople
working the same lead.

27/03/2009

SYSTEM IMPROVEMENT OBJECTIVES

Causes and Effects

System Objective

Unknown

1. Each salesperson keeps his or her own

database of leads.

1. The system will include a

central database of author
leads that could be used
for checking duplicates.

1. The system will include a

central database of author
leads that could be used
for monitoring salesperson
performance and providing
for easy direct marketing
to all active leads.
2. It will track call notes for
each salesperson.

Unknown

1. The system will allow an

electronic tracking of
books through the
production process.

Unknown

Cause(s):

System
Constraint

Effect(s):
1. Salespeople fighting over 5 or 10
duplicated leads every week.
2. It costs the company over $20,000 a
year.
3. It wastes labour.
2. Salesperson
Cause(s):
performance and active
leads cant be
1. Each salesperson keeps his or her own
analysed.
database of leads.
Effect(s):
1. The VP of sales cant do analysis of
salesperson performance.
3. It takes long time find a
file in the production
process.

Cause(s):
1. The current production process (file
folders move through plastic bins).

Page | 9

2009

ICT231 Assignment 1

CAUSE AND EFFECT ANALYSIS

Problem or Opportunity

Causes and Effects

Effect(s):
1. It takes workers long time to go
through the bins to find a file.

4. It takes time and costs

Cause(s):
money to find a book
status in the production 1. The current production process (file
process.
folders move through plastic bins).
Effect(s):
1. Each call takes 5 minutes.
2. It costs the company among $15,000
a year.

5. Inability to generate
automated royalty
checks and quarterly
sales report.

Cause(s):
1.

The current system does not support

automated reports.

Effect(s):
1.

SYSTEM IMPROVEMENT OBJECTIVES

System Objective

System
Constraint

2. The bins will be replaced

by a system where book
shepherd will take care of
entering all data.
1. The system will allow an
electronic tracking of
books through the
production process.
2. It will set up a self-service
web site that allows the
authors to check on the
status of their books.
3. The bins will be replaced
by a system where book
shepherd will take care of
entering all data.

Unknown

1. The system will automate

this process ( generating
royalty checks, quarterly
sales report)

Unknown

It costs the company among $2,000 a year.

Page | 10

2009

ICT231 Assignment 1

Use Case Modelling

Use cases list
Use case name
Track leads

Description
This use case describes the event
of the VP of sales tracking sales
leads that each salesperson has
and that will be saved on one
integrated database.

Actors
VP of sales

Assumptions
Assuming that the
VP initiates the use
case.

Page | 11

2009

ICT231 Assignment 1

Track call notes

This use case describes the event

of the VP of sales tracking calls per
lead and leads per sale so if the
sales person promises something,
the VP of sales has a record.

VP of sales

Assuming that the

VP initiates the use
case.

Track tasks

This use case describes the event

Shepherd
of each book that comes in will be
assigned to a shepherd the
shepherd will oversee the
production process for that book.
The shepherd will get a list of the
status of each of his or her books
each day. When the shepherd sees
that a book has finished one task,
he will assign it to another task and
the person who supposed to
accomplish that task will receive an
email generated by the system
with the assignment.

Assuming that
shepherd initiate
the use case.

Record books
information

This use case describes the event

of recording each books
information in a centralized
database.

Shepherd

Assuming that
shepherd initiates
the use case.

Check the status

of books

This use case describes the event

of an author checking on the status
of his or her books by accessing a
self-service web site.

Author

Assuming that
author initiates the
use case.

Generate royalty
checks

This use case describes the event

of generating royalty checks in

Time

Assuming that the

use case initiated
Page | 12

2009

ICT231 Assignment 1

quarterly basis, the sales summary

pulled out form the e-commerce
site and then pulled back to the
system and matched by book and
author and used to generate
royalty checks
Generate sales
summaries

This use case describes the event

of generating sales summaries in
quarterly basis,

in quarter basis.

Time

Assuming that the

use case initiated
in quarter basis.

Use Case Diagram

Page | 13

ICT231 Assignment 1

2009

Data Modelling
Entities List
Page | 14

2009

ICT231 Assignment 1

Entity

Description

Book

This entity contains a book attributes.

Lead

This entity contains a lead attributes.

Author

This entity contains an author attributes.

Royalty
Compensation

This entity contains a royalty compensation attributes.

Call log

This entity contains a call log attributes.

Task

This entity contains a task attributes.

Technician

This entity contains a technician attributes.

Source

This entity contains a source attributes.

Salesperson

This entity contains a salesperson attributes.

Entity Relationship Diagram

Page | 15

ICT231 Assignment 1

2009

Page | 16

ICT231 Assignment 1

2009

Data Flow Diagrams

Context Data Flow Diagram

Note: the diagram can be seen clearly with %200 zoom view.
I assumed that salesperson is represented by sales department.
Page | 17

ICT231 Assignment 1

2009

Page | 18