Page 1Design Phase

MRI Processes12/1/2006Page 1

Design Phase – Presentation 3

Project Sponsor: Tim Kropp, Vice President

Project Team:Christie Robbins, Huan Truong, Susan Widmer

March 28, 2007

Page 2Design Phase

Background:

• MRI builds web applications for their customers to streamline processes and improve communications

• There is a need to implement a standard method for communicating issues and suggestions from the end user to the appropriate developer

• We are proposing a Software Change and Problem Reporting (SCPR) web application that documents issues and suggestions directly forwarding them to the appropriate developer

• The SPCR should provide the following functionality:

– Allow the end user to submit an incident

– Auto email the incident to the appropriate developer

– Allow the developer to assess the incident, fix the problem, and submit for closure approval

– Auto email the closure request to the lead developer

– Allow the lead developer to review and close the incident

– Notify the initiator that the incident has been addressed and closed

Page 3Design Phase

Context Diagram

InitiatorSCPR

0

Developer

DeveloperLead

Incident Notification

Incident Assessment

Closure Rationale

Incident Info

Incident Results

Closure Notification

IncidentReport

ClosureNotification

ClosureApproval

Customer

Page 4Design Phase

Level 0 Diagram - Revised

IncidentAssessment

Closure Rationale

IncidentInfo

SCPR Assessment

Incident Notification

Incident Results

Closure Notification

IncidentReport

ClosureNotification

Initiator

Customer

Developer

DeveloperLead

AssessIncident

3

Closure ApprovalAssignDeveloper

IncidentD1

1

Closure Record

2

Open Incident

ReportIncident

5

IncidentRecord

GenerateIncidentReport

IncidentRecord

4

CloseIncident

Assessment Record

DevelopersD2

DeveloperInfo

Updated Incident

Page 5Design Phase

Level 1 Diagrams - Revised

IncidentInfo

IncidentRecord

1.1

Get Initiator

1.2

GetApplicationInfo

1.3

GetCustomer

ApplicationInfo

IncidentD1

InitiatorsD3

ApplicationD4

UpdatedIncident

Initiator

InitiatorInfo

UpdatedIncident

1.4

RecordIncident

D5Customers

CustomerInfo

UpdatedIncident

IncidentNotification

IncidentNotification

2.2

Open Incident

DeveloperInfo

DevelopersD2

GetDeveloper

IncidentNotify

InidentNotification Developer

2.1

IncidentD1

UpdatedIncident

Module 1

Module 2

Page 6Design Phase

System Components Diagram

External Entity

User

Customer

External Entity

Developer

Developer Lead

1

Report Incident

2

Assign Developer

3

Assess Incident

4

Close Incident

5

Generate IncidentReport

Incident Info

IncidentReport

IncidentAssessment

D1 Incident D2 Developers

Processes

Open Incident

ClosureApproval

Data Storage

D3 Developers

Page 7Design Phase

Specific Entity Tables and Attributes

Entity: Software Problem and Change Request

(SPCR)

SPCR_ID

Initiator

Int_phone

Int_email

Date_Opened

SPCR_Title

Activity

Description

Analysis

Entity: Responsible Software Developer

Dev_ID

Dev_UserID

Dev_Name

Dev_email

Dev_Lead

Entity: Application

App_ID

App_Acronym

App_Name

App_Link

Dev_ID

Cust_ID

Entity: Customer

Cust_ID

Cust_userID

Cust_Description

Cust_Name

Cust_email

Entity: Impact

Imp_ID

Imp_Name (i.e. high, medium, low)

Imp_Desc

Entity: Type

Type_ID

Type_Name (i.e. Change Request, Discrepancy, Problem)

Type_Desc

Entity: Disposition

Disp_ID

Disp_Name

Disp_Desc

Page 8Design Phase

Logical Design

Initiator Initiates Incident Assigned Application

Developed

Programmer

Assessed

Impact

1

11

1 M

M

M

MHas

1M Customer

M

Page 9Design Phase

Physical Design

Incident (SPCR_ID, Imp_ID, Int_ID, App_ID, Date_Opened, SPCR_Title, Activity, Description,

Analysis)

Resp_SW_Developer (Dev_ID, Dev_UserID, Dev_Name, Dev_email, Dev_Lead)

Application (App_ID, Cust_ID, Dev_ID, App_Acronym, App_Name, App_Link, Dev_ID,)

Customer (Cust_ID, Cust_userID, Cust_Description, Cust_Name, Cust_email)

Impact (Imp_ID, Imp_Name, Imp_Desc)

Type (Type_ID, Type_Name, Type_Desc)

Disposition (Disp_ID, Disp_Name, Disp_Desc)

New Table to capture Initiator information:

Initiator (Int_ID, Int_Name, Int_Email, Int_Phone)

Page 10Design Phase

ER Diagram

PK

PK

PK

PK

PK

PK

PK

N

1

N

1

1

N

N

1

1

N

N

1

Incident

Page 11Design Phase

Structure Design

SCPRIncident Report System

Report IncidentModule 1

Assign DeveloperModule 2

Assess IncidentModule 3

Close IncidentModule 4

Generate Incident ReportModule 5

Initi

ator

Info

Incident Info

Get InitiatorModule 1.1

Get ApplicationModule 1.2

Initi

ator

ID

App

Info

App

ID

Get CustomerModule 1.3

App Info

Cus

tom

er ID

Record IncidentModule 1.4

Init IDApp ID

Incident Info

Incident ID

Incident ID Validated

A

Assign DeveloperModule 2

A

Get IncidentModule 2.1

Inci

dent

ID

App ID

Inci

dent

ID

Incident NotifyModule 2.2

Dev

elop

er ID

Dev

elop

er In

fo

Incident ID

Email Developer

Page 12Design Phase

SCPR Screen Shots

Initiator FormIncident Confirmation

Developer Form