1. Page 1 Design Phase MRI Processes 12/1/2006 Page 1 Design Phase – Presentation 3 Project Sponsor: Tim Kropp, Vice President Project Team: Christie Robbins, Huan Truong, Susan Widmer March 28, 2007

2. Page 2 Design 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

3. Page 3 Design Phase Context Diagram

4. Page 4 Design Phase Level 0 Diagram - Revised

5. Page 5 Design Phase Level 1 Diagrams - Revised Module 1 Module 2

6. Page 6 Design Phase System Components Diagram External Entity User Customer External Entity Developer Lead 1 Report Incident 2 Assign Developer 3 Assess Incident 4 Close Incident 5 Generate Incident Report Incident Info Incident Report Incident Assessment D1 Incident D2 Developers Processes Open Incident Closure Approval Data Storage D3 Developers

7. Page 7 Design 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

8. Page 8 Design Phase Logical Design Initiator Initiates Incident Assigned Application Developed Programmer Assessed Impact 1 1 1 1 M M M M Has 1 M Customer M

9. Page 9 Design 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)

10. Page 10 Design Phase ER Diagram PK N 1 N 1 1 N N 1 1 N N 1 Incident

11. Page 11 Design Phase Structure Design SCPR Incident Report System Report Incident Module 1 Assign Developer Module 2 Assess Incident Module 3 Close Incident Module 4 Generate Incident Report Module 5 Initiator Info Incident Info Get Initiator Module 1.1 Get Application Module 1.2 Initiator ID App Info App ID Get Customer Module 1.3 App Info Customer ID Record Incident Module 1.4 Init ID App ID Incident Info Incident ID Incident ID Validated A Assign Developer Module 2 A Get Incident Module 2.1 Incident ID App ID Incident ID Incident Notify Module 2.2 Developer ID Developer Info Incident ID Email Developer

12. Page 12 Design Phase SCPR Screen Shots Initiator Form Incident Confirmation Developer Form