ICT231 Assignment 1

Contents

3Part 1 Project Management

3Pert chart

4Gantt chart

5Part 2 Systems Analysis

5Background Research

5Memo

8Problem Analysis

8POOC Matrix

11Use Case Modelling

11Use cases list

13Use Case Diagram

14Data Modelling

14Entities List

15Entity Relationship Diagram

16Data Flow Diagrams

16Context Data Flow Diagram

17ASSIGNMENT COVER SHEET

Part 1 Project Management

Pert chart

Legend:Task name

Start dateTask ID

Finish dateTask duration

Resource:

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.. 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 2009Part 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.

Create visual models.

Verify quality.

Control changes.

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.

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.

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 MATRIXProject:

Peak Publishing Sales and Book Tracking

System Project Manager:

Created by:

Mohammed Murad

Last Updated by:Mohammed Murad

Date Created:25/03/2009Date Last Updated:27/03/2009

CAUSE AND EFFECT ANALYSISSYSTEM IMPROVEMENT OBJECTIVES

Problem or OpportunityCauses and EffectsSystem ObjectiveSystem Constraint

1. Multiple salespeople working the same lead.Cause(s):

1. Each salesperson keeps his or her own database of leads.

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.1. The system will include a central database of author leads that could be used for checking duplicates.Unknown

2. Salesperson performance and active leads cant be analysed.Cause(s):

1. Each salesperson keeps his or her own database of leads.

Effect(s):

1. The VP of sales cant do analysis of salesperson performance.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

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).Effect(s):

1. It takes workers long time to go through the bins to find a file.1. The system will allow an electronic tracking of books through the production process.

2. The bins will be replaced by a system where book shepherd will take care of entering all data.Unknown

4. It takes time and costs money to find a book status in the production process. Cause(s):

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

1. Each call takes 5 minutes.

2. It costs the company among $15,000 a year.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

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. It costs the company among $2,000 a year.1. The system will automate this process ( generating royalty checks, quarterly sales report)Unknown

Use Case Modelling

Use cases list

Use case nameDescriptionActorsAssumptions

Track leadsThis 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.VP of salesAssuming that the VP initiates the use case.

Track call notesThis 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 salesAssuming that the VP initiates the use case.

Track tasksThis use case describes the event 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. ShepherdAssuming that shepherd initiate the use case.

Record books informationThis use case describes the event of recording each books information in a centralized database.ShepherdAssuming that shepherd initiates the use case.

Check the status of booksThis use case describes the event of an author checking on the status of his or her books by accessing a self-service web site.AuthorAssuming that author initiates the use case.

Generate royalty checks This use case describes the event of generating royalty checks in 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 checksTimeAssuming that the use case initiated in quarter basis.

Generate sales summariesThis use case describes the event of generating sales summaries in quarterly basis, TimeAssuming that the use case initiated in quarter basis.

Use Case Diagram

Data Modelling

Entities List

EntityDescription

BookThis entity contains a book attributes.

LeadThis entity contains a lead attributes.

AuthorThis entity contains an author attributes.

Royalty CompensationThis entity contains a royalty compensation attributes.

Call logThis entity contains a call log attributes.

TaskThis entity contains a task attributes.

TechnicianThis entity contains a technician attributes.

SourceThis entity contains a source attributes.

SalespersonThis entity contains a salesperson attributes.

Entity Relationship Diagram

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.Murdoch University

2009

ICT231 Assignment 1

Systems Analysis and Design

Page | 7

_1300830039.vsdTable