63

Click here to load reader

Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Embed Size (px)

Citation preview

Page 1: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Case Study: Agate’s Information System

Page 2: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

A1:AGATE Ltd Case Study:

Introduction

Page 3: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Requirements

• To record details of Agate’s clients and advertising campaigns for those clients.– To record names, address, contact details for each client.– To record details of each campaign for each client (title of

campaign, planned start & finish dates, estimated costs, budgets, actual costs & dates, current state of completion).

– To provide information that can be used in separate accounts system for invoicing clients for campaigns.

– To record payments for campaigns that are also recorded in separate accounts system.

– To record which staff are working on which campaigns, including campaign manager for each campaign.

– To record which staff are assigned as staff contacts to clients.– To check on status of campaigns and whether they are within

budget.

Page 4: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Requirements (cont’)

• To provide creative staff with recording details of adverts and products of creative process that leads to development of concepts for campaigns and adverts.– To allow creative staff to record notes of ideas for campaigns

and adverts.– To provide other staff with access to those concept notes.– To record details of adverts, including progress on their

production.– To schedule dates when adverts will be run.

• To record details of all staff in company.– To maintain staff records for creative and administrative staff.– To maintain details of staff grades and the pay for those grades.– To record which staff are on which grade.– To calculate annual bonus for all staff.

Page 5: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Requirements (cont’)

• Non-functional requirements.– To enable data about clients, campaigns, adverts, staff to be

shared between offices.– To allow system to be modified to work in different languages.

Page 6: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

A2:AGATE Ltd Case Study:

Requirements Model

Page 7: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Require-ment list

Page 8: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Use case for Staff Management

Page 9: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Use case for

Staff Manage-ment (cont’)

Page 10: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Use case for Campaign Management

Page 11: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Use case for

Campaign Manage-

ment (cont’)

Page 12: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Use case for Advert Preparation

Page 13: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Incursion & Prototype interface for Find campaign use case

Page 14: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Initial Package Architecture

Page 15: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Initial Package Architecture (cont’)

• Use cases have been grouped into 3 sub-system packages: Campaign Management, Staff Management, and Advert Preparation.

• Distribution Package is necessary to meet Requirement # 16

Page 16: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Activity diagram for Requirements capture and modeling

Page 17: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Activity diagram for Capturing requirements

Page 18: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Activity diagram for Developing prototype

Page 19: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Activity diagram for Developingan initial architecture

Page 20: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

A3:AGATE Ltd Case Study:Requirements Analysis

Page 21: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Use case collaboration: Add a new campaign

Page 22: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Collaboration diagram forAdd a new campaign

Page 23: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Class diagram forAdd a new campaign

Page 24: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Use case collaboration: Assign staff contact

Page 25: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Collaboration diagram for Assign staff contact

Page 26: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Class diagram for Assign staff contact

Page 27: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Use case collaboration: Check campaign budget

Page 28: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Collaboration diagram for Check campaign budget

Page 29: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Class diagram for Check campaign budget

Page 30: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Use case collaboration:Record completion of campaign

Page 31: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Collaboration diagram for Record completion of campaign

Page 32: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Class diagram for Record completion of campaign

Page 33: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Class diagram after further requirement analysis

Page 34: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Activity diagram forRequirement analysis

Page 35: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Activity diagram forAnalysis use case realization

Page 36: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

A4:AGATE Ltd Case Study:

Requirements Model (Cont.)

Page 37: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Sequence diagram forAdd a new advert to a campaign

Page 38: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Sequence diagram forCheck campaign budget

Page 39: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

State-chart for

Cam-paign

Page 40: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

State-chart for

StaffMember

Page 41: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Operational specification

for Campaign

Page 42: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Operational specificationfor Client &

Advert

Page 43: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Revised analysis class diagram with generalization and aggregation

Page 44: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Activity diagram for Iteration analysis

Page 45: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Activity diagram for Iteration analysis (cont’)

Page 46: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

A5:AGATE Ltd Case Study:

Design

Page 47: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Package diagram for Software architecture

Page 48: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Package diagram showing classes

Page 49: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Prototype UI for Check campaign budget

Page 50: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Classes in packageAgate::Boundary

Page 51: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Classes in packageAgate::Control::Client::CheckCampaignBudget

Page 52: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Classes in packageAgate::Control::Server

Page 53: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Classes in packageAgate::Entity::Domain

Page 54: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Broker classes in packageAgate::Entity::DataManagement

Page 55: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Factory class in packageAgate::Control::Server

Page 56: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Sequence diagram forCheck campaign budget

Page 57: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Sequence diagram forCheck campaign budget (cont’)

Page 58: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Sequence diagram forCheck campaign budget (cont’)

Page 59: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Sequence diagram forCheck campaign budget (cont’)

Page 60: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Statechart for control of UIin Check campaign budget

Page 61: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Event-action for Statechart for control of UIin Check campaign budget

Page 62: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Activity diagram for Design workflow

Page 63: Case Study: Agate’s Information System. A1: AGATE Ltd Case Study: Introduction

Activity diagram for Design workflow (cont’)