Title: Case Study: Agate
1Case Study Agates Information System
2A1AGATE Ltd Case StudyIntroduction
3Requirements
- To record details of Agates 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.
4Requirements (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.
5Requirements (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.
6A2AGATE Ltd Case StudyRequirements Model
7Require-ment list
8Use case for Staff Management
9Use case for Staff Manage-ment (cont)
10Use case for Campaign Management
11Use case for Campaign Manage-ment (cont)
12Use case for Advert Preparation
13Incursion Prototype interface for Find campaign
use case
14Initial Package Architecture
15Initial 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
16Activity diagram for Requirements capture and
modeling
17Activity diagram for Capturing requirements
18Activity diagram for Developing prototype
19Activity diagram for Developingan initial
architecture
20A3AGATE Ltd Case StudyRequirements Analysis
21Use case collaboration Add a new campaign
22Collaboration diagram forAdd a new campaign
23Class diagram forAdd a new campaign
24Use case collaboration Assign staff contact
25Collaboration diagram for Assign staff contact
26Class diagram for Assign staff contact
27Use case collaboration Check campaign budget
28Collaboration diagram for Check campaign budget
29Class diagram for Check campaign budget
30Use case collaborationRecord completion of
campaign
31Collaboration diagram for Record completion of
campaign
32Class diagram for Record completion of campaign
33Class diagram after further requirement analysis
34Activity diagram forRequirement analysis
35Activity diagram forAnalysis use case realization
36A4AGATE Ltd Case StudyRequirements Model
(Cont.)
37Sequence diagram forAdd a new advert to a
campaign
38Sequence diagram forCheck campaign budget
39State-chart for Cam-paign
40State-chart for StaffMember
41Operational specificationfor Campaign
42Operational specificationfor Client Advert
43Revised analysis class diagram with
generalization and aggregation
44Activity diagram for Iteration analysis
45Activity diagram for Iteration analysis (cont)
46A5AGATE Ltd Case StudyDesign
47Package diagram for Software architecture
48Package diagram showing classes
49Prototype UI for Check campaign budget
50Classes in packageAgateBoundary
51Classes in packageAgateControlClientCheckCa
mpaignBudget
52Classes in packageAgateControlServer
53Classes in packageAgateEntityDomain
54Broker classes in packageAgateEntityDataManag
ement
55Factory class in packageAgateControlServer
56Sequence diagram forCheck campaign budget
57Sequence diagram forCheck campaign budget (cont)
58Sequence diagram forCheck campaign budget (cont)
59Sequence diagram forCheck campaign budget (cont)
60Statechart for control of UIin Check campaign
budget
61Event-action for Statechart for control of UIin
Check campaign budget
62Activity diagram for Design workflow
63Activity diagram for Design workflow (cont)