Group07_mna5045_wpe5006_tjm5345_nwp5051_jrw5159

IST 420 Spring 2012 Dr. Glantz

Assignment 07
Meridian Disaster mna5045 / Michelle N. Ahrens wpe5006 / William P. Evers tjm5345 / Tyler J. Meany nwp5051 / Nam X. Pham jrw5159 / Joshua R. Wentz

Group07_mna5045_wpe5006_tjm5345_nwp5051_jrw5159

Part 1 Scope Statement

Project Objectives
This project has been initiated in order to unify all three departments within Access Data into one unified system for billing purposes and to find the most profitable customers. This project will also reduce the amount of incompatible or corrupted data. This project will be completed within six months without exceeding $500,000.

Deliverables
The deliverables below show all of work that needs to be done in order to design and implement the new system in Access Data. The planning and the majority of the initiating phases have been completed. By listing all the deliverables, this gives a better idea of how long it will take to implement the new system. See Figure for the Gantt chart of the deliverables. The major group projects have been condensed as these projects have already been completed, although they do include smaller steps involved in the deliverables.

Milestones
The milestones shown below are the major points of work that need to be done in order to implement the new system in Access Data. These major milestones give a better idea of how long it will take to implement the new system and when the major amounts of work will be completed. Proposal o Fully detailed document of the specifications and goals/objectives of the unification of Access Datas three departments. Approval o The proposal is presented to head management for review. If approved, then the process of unifying all three systems can commence. If denied, then Meridian Disaster must change the proposal to fit the needs of management. Prototype o After approval, Meridian Disaster will create and implement a prototype system that unifies all three departments into one server. The prototype should include the main features needed to process and clean the data from all three departments. User Testing o While the prototype is in use, Meridian Disaster will communicate with the department heads in order to see if the prototype has all the necessary requirements and is user friendly. New Functioning System o This is the final project, which will be implemented using the input from user testing in order to make the final changes to the system.

Technical Requirements

Group07_mna5045_wpe5006_tjm5345_nwp5051_jrw5159

These are the technical requirements that are needed in order to complete the given project successfully. Hardware Requirements o 3 original departmental databases o 3 new databases (temporary, dirty, and finalclean) Software Requirements o Application or batch file to retrieve and aggregate the data and initiate the process. o Application to cleanse/flag the data and store cleansed data in the correct destination o Web-based application to be accessed by employees, allowing them to generate reports from the aggregated data. Special permissions for Project and Data management to also access and generate reports from the dirty database to analyze potential threats. o Users must be able to compile data by Client Investment, and Wholesaler Commission o Corrupt or inconsistent data must be moved to the dirty database to be deleted or fixed by the system administrators. Other Requirements o The retrieval/aggregation application and the temporary database must be compatible with the original databases. o Being that the organization deals with financial transactions, the downtime during system implementation must be minimal, and the speed of the aggregation and cleansing process must be greater than 10 Gb/s.

Limits and exclusions

These are the limits and exclusions in order to outline what is to be done and what is not included within the scope of the project. Meridian Disaster will not complete any work not exclusively stated in this document unless it 1) poses a safety hazard or 2) the entire project cannot be completed without the change. Maintenance & Repair o Maintenance will be done only up to one month after final inspection. o Testing will be performed for one month following installation. If all errors are resolved at that time, testing responsibilities will be passed onto Access Data. Data Collection o Only the databases of the 3 specified departments (Sales & Contracting, Client Service Management, & Project & Data Management) will be collected. o First system run will be conducted by the Meridian Disaster team. o Data sent to the dirty database will be managed and maintained by Access Datas Project & Data Management department, not Meridian Disaster. Software

Group07_mna5045_wpe5006_tjm5345_nwp5051_jrw5159

o o

System data retrieval, aggregation, cleansing, and storing software will be installed with the requirements detailed in Section 4. Two reports were requested to be built, including Client Investment and Wholesaler Commission. The coding of other generated reports could be an opportunity of future engagement but is not within the scope of this project. One training session will be given to Access Datas Project & Data Management Department.

Part 2 Requirements and Survey Questions

System Request
Project Sponsor Broadridge Companys Access Data Corp. Business Needs This project has been initiated to consolidate all three departments within Access Data into one unified system for billing purposes and to find the most profitable customers. Business Requirement Access Data provides Software as a Service to mutual fund companies to collect mutual fund transaction data and disaggregate the data to allow the company to know which investment broker sold the fund, how much, and in what territory. To accomplish this, Access Data has three departments that should be able to work with clients. The three departments include:
1. Sales & Contracting 2. Client Service Management 3. Project & Data Management

The functionality that the system should have is listed below: Integrate three computer system used by the three departments above Standardize tracking time for setup and customization among departments Allow for the different data reporting priorities of each department

Business Value
We expect the consolidated system will increase customer satisfaction through seamless interaction with Access Data Employees. The consolidated system will provide a way for employees to realize which customers are the most profitable. We also expect the system to streamline communication among employees. Discrete value added by the system includes:
Increased revenue due to saved billing time Increased accuracy of allocated resources to most profitable clients Improved profitability among employee to client interactions With the implementation of the system, Access Data will be able to significantly reduce internal costs on an annual basis. In a similar case, the client was able to save:

Group07_mna5045_wpe5006_tjm5345_nwp5051_jrw5159

$500,000 in employee communication time expense $300,000 by eliminating the need for client intelligence reporting

Special Issues or Constraints

This system must be in place by May 25, 2012

Work Plan/ Gantt Chart

Figure shows the work plan/ Gantt chart of the tasks done throughout the semester by Meridian Disaster
and the future tasks to be fulfilled in order to successfully complete the project.

Group07_mna5045_wpe5006_tjm5345_nwp5051_jrw5159

Figure

Feasibility Analysis
Technical Feasibility
Implementing an aggregated data system is technically possible; however, it does come with risk. There is a medium risk involved regarding the employee familiarity with the aggregated data system. o Currently all departments are using different systems entirely, meaning a new system will be foreign to all users.

Group07_mna5045_wpe5006_tjm5345_nwp5051_jrw5159

The new system will use a web-based interface which employees should be able to adapt too quickly. Aggregated data systems risk regarding number of people, time, and features o A limited number of human resources will be available for the project. o The contract only allows 40 hours for setup and customization. o The system must be able to identify the most profitable clients.
o

The risk that the system is compatible with existing systems is medium.
o o

The system will be using XML to transfer data, which is currently used by Access Data. However, all current systems reports data and tracks time differently.

Organizational Feasibility
This project from an organizational standpoint is very low risk and very high gain. This system will eliminate unnecessary spending and improve efficiency and customer satisfaction. The goal to have an aggregated data system in this case is not only beneficial, but necessary in the customer oriented mutual fund sector. Inconsistencies in data in a financial business can make an organization very volatile; this system will provide the data integrity required. This system will make departmental data transfers seamless and accurate. Users will be able to finally rank customers based on their investments and delegate their customer service accordingly. Clients will see enhanced and more accurate feedback on their accounts.

Requirements Definition & Sample Questions

Nonfunctional Requirements

The system must have a web-based interface. The data must be secure and have access control. Must include all three departments Time tracking must be standardized between the three departments. Data must be stored in the same format throughout the system. Each department should be allowed different data reporting priorities.

Functional Requirements

The system must be able to aggregate the data between the three departments. Current data must be cleansed before entering the new system and new data should be cleansed periodically after it is entered. The system should be able to list clients by investment amount. The system must record transactions in real time. Each transaction must have the client listed with it.

Group07_mna5045_wpe5006_tjm5345_nwp5051_jrw5159

Sample Survey Questions What do you think is the most necessary change for your company to be more profitable? __________________________________________________________________________ __________________________ __________________________________________________________________________ ___________________________. What do you think the biggest problem with the billing system is? __________________________________________________________________________ _______________________ __________________________________________________________________________ _______________________. What do you suggest to improve this problem? __________________________________________________________________________ ______________________ __________________________________________________________________________ ______________________. On a scale of 1-10, how necessary to you believe a new system is for billing? (1 means very unnecessary and 10 means highly necessary) 1 2 3 4 5 6 7 8 9 10 On a scale of 1-10, how willing are you to try a new system that connects the three departments? (1 means very unwilling and 10 means very willing) 1 2 3 4 5 6 7 8 9 10 On a scale of 1-10, how willing do you think others are to try a new system that connects the three departments? (1 means very unwilling and 10 means very willing) 1 2 3 4 5 6 7 8 9 10 How often do you talk with employees in the other departments? Multiple times a day Once a day Other ___________ Multiple times a week Once a week

On average, how long does it take for you to get the information you need from other departments? _______________________________________________________________________ _________________________ _______________________________________________________________________ ________________________.

Group07_mna5045_wpe5006_tjm5345_nwp5051_jrw5159

How long do you think it should take to get the information you need from other departments? _______________________________________________________________________ _________________________ _______________________________________________________________________ ________________________.

How do you best communicate with employees of other departments? E-mail Phone Face-to-face Instant messaging Other_________________

Part 3 Functional Modeling

Activity Diagram
Figure below shows the activity diagram.

Group07_mna5045_wpe5006_tjm5345_nwp5051_jrw5159

Figure

Use Case Description

This use case encompasses two systems. The first one retrieves the data from the three original databases when a batch file, executed by the system, initiates it. The data is then aggregated and

Group07_mna5045_wpe5006_tjm5345_nwp5051_jrw5159

stored in a temporary database. The second system takes the data from the temporary database and cleans it. If data is un-cleanable or corrupt it is then flagged. Finally the clean data is stored in the clean database and the flagged data is sent to the dirty database for review. Table below shows the use case description of the Retrieve Use Case. Table below shows the use case description of the Aggregate. Table below shows the use case description of the Clean Use Case. Table below shows the use case description of the Store Case.

Use Case Name: Retrieve Primary Actor: Original Databases

ID:

Importance Level: High Detail, essential

Use Case Type:

Brief Description: This use case gathers the information from the three original databases. Trigger:Receiving the data from the original database. Type: Internal Relationships: Association: System Include: Extend: Generalization: Normal Flow of Events: 1. Data is entered into the system by the three departments. 2. Data is retrieved from those databases into the central system.
Table

Use Case Name: Aggregate

ID: 2

Important Level: High

Primary Actor: Original Databases

Use Case Type: Essential, Detail

Group07_mna5045_wpe5006_tjm5345_nwp5051_jrw5159

Brief Description: This process aggregates the data from the three original databases, and stores it in a temporary database, where it awaits cleaning. Trigger: Receiving the data from original databases. Type: Internal Relationships: Association: DB_Temporary Include: Extend: Generalization: Normal Flow of Event: 1. Data is received from the three original systems. 2. Data is combined and stored in a temporary database.
Table

Table 3 Clean Use Case Description

Use Case Name: Clean Primary Actor: DB_Temporary

ID:

Importance Level: High Detail, essential

Use Case Type:

Brief Description: This use case gathers information from the temporary database, cleans & flags dirty data, and then stores the data. Trigger:Receiving the data from the aggregate use case. Type: Internal Relationships: Association: DB_Temporary Include: Extend: Generalization: Normal Flow of Events: 1. Data is gathered from the temporary database. 2. Aggregated data is cleaned and dirty data is flagged. 3. Data is stored.
Table Error: Reference source not found

Table 4 Store Use Case Description

Group07_mna5045_wpe5006_tjm5345_nwp5051_jrw5159

Use Case Name: Store Primary Actor: DB_Temporary

ID: 4

Important Level: High

Use Case Type: Detail, Essential

Brief Description: This Use Case takes the cleaned data from the temporary database and stores the clean data in the final clean database. The dirty data that was flagged during cleaning is stored in the dirty database. Trigger: Receiving data after cleaning Type: Internal Relationships: Association: DB_FinalClean, DB_Dirty Include: Extend: Generalization: Normal Flow of Event: 1. Cleaned/Flagged data is received. 2. Data is stored in the final clean database Alternate/Exceptional Flows: 2a. Flagged data is sent to the dirty database
Table

Use Case Diagram

Figure below shows a view of how the different databases are managed by the system.

Group07_mna5045_wpe5006_tjm5345_nwp5051_jrw5159

Figure

Part 4 Structural Modeling

CRC Cards

Group07_mna5045_wpe5006_tjm5345_nwp5051_jrw5159

Table shows the CRC card for the Original Database. Table shows the CRC card for the Temporary Database. Table shows the CRC card for the final clean database. Table shows the CRC card for the final dirty database. Front: Class Name: Original Database ID: 1 Type: Detail, essential

Description: Data is retrieved from all of the three departmental databases.

Associated Use Cases: Retrieve

Responsibilities Retrieve _____________________________ _____________________________ _____________________________

Collaborators Sales & Contracting DB Client Services DB Project & Data Management DB __________________________

Back:

Group07_mna5045_wpe5006_tjm5345_nwp5051_jrw5159

Attributes: Project_ID Employee_ID Employee_Name

Status Start_Time End_Time

Total_Time Total Client_Name

Priority Date_Created Date_Modified

Relationships: Generalization (a-kind-of): Departmental Databases Aggregation (has-parts): _____________________________________________________ Other Associations: ________________________________________________________

Table

Front: Class Name: DB_Temporary

ID: 2

Type: Detail, essential

Description: All of the collected data is aggregated into a temporary database.

Associated Use Cases: Aggregate, Clean

Group07_mna5045_wpe5006_tjm5345_nwp5051_jrw5159

Responsibilities Hold the data to await cleaning / final storage _____________________________ _____________________________ _____________________________

Collaborators Sales & Contracting DB Client Services DB Project & Data Management DB __________________________

Back: Attributes: Project_ID Employee_ID Employee_Name

Status Start_Time End_Time

Total_Time Total Client_Name

Priority Date_Created Date_Modified

Relationships: Generalization (a-kind-of): ___Departmental Databases_________________________ Aggregation (has-parts): ___Clean & dirty data_________________________________ Other Associations: ______________________________________________________

Table

Front:

Group07_mna5045_wpe5006_tjm5345_nwp5051_jrw5159

Class Name: DB_FinalClean

ID: 3

Type: Detail, essential

Description: Clean data is stored in this final clean database in order for the Sales & Contracting / Client Services Department to use.

Associated Use Cases: Store

Responsibilities Store aggregated & cleansed data Generate reports based on attributes _____________________________ _____________________________

Collaborators DB_Temporary __________ _____________________________ _____________________________ _____________________________

Back:

Group07_mna5045_wpe5006_tjm5345_nwp5051_jrw5159

Attributes: Project_ID Employee_ID Employee_Name

Status Start_Time End_Time

Total_Time Total Client_Name

Priority Date_Created Date_Modified

Relationships: Generalization (a-kind-of): _________________________________________________ Aggregation (has-parts): _____________________________________________________ Other Associations: ________________________________________________________
Table

Front: Class Name: DB_Dirty

ID: 4

Type: Detail, essential

Description: Flagged data is stored in this dirty database in order to await further review by Project & Data Management Department.

Associated Use Cases: Store

Group07_mna5045_wpe5006_tjm5345_nwp5051_jrw5159

Responsibilities Store flagged / dirty data _____________________________ _____________________________ _____________________________

Collaborators DB_Temporary _________ _____________________________ _____________________________ _____________________________

Back: Attributes: Project_ID Employee_ID Flagged_Attribute

Relationships: Generalization (a-kind-of): _________________________________________________ Aggregation (has-parts): _____________________________________________________ Other Associations: ________________________________________________________
Table

Class Diagram

Group07_mna5045_wpe5006_tjm5345_nwp5051_jrw5159

Figure shows the Class/Object Diagram for the temporary database.

Figure

Part 5 Behavioral Modeling

Sequence Diagram
Figure below shows our sequence diagram.

Figure

Communication Diagram
Figure below shows our communication diagram.

Group07_mna5045_wpe5006_tjm5345_nwp5051_jrw5159

Figure

Behavioral State Machine

Figure below shows our behavioral state machine.

Figure

CRUD Matrix
Table below shows our CRUD Matrix.

Group07_mna5045_wpe5006_tjm5345_nwp5051_jrw5159

DB_Original

System Clean

DB_Temporary

CleanData

DirtyData

DB_Original

System Clean

CU

CU

CU

DB_Temporary

CleanData

Group07_mna5045_wpe5006_tjm5345_nwp5051_jrw5159

DirtyData

Table