Design Document

Real-Time Financial Data Warehouse

Design DocumentVersion 1.0

Group Id: F1402EC0E8Supervisor Name: Sir Shabib Aftab

17 | Page

Revision History

Date (dd/mm/yyyy)VersionDescriptionAuthor

15/01/20151.0Introduction to Design DocumentMC120400960

22/01/20151.0Sequence Diagrams MC120400960

25/01/20151.0Architecture Design DiagramMC120400960

02/02/20151.0Class DiagramMC120400960

10/02/20151.0Star SchemaMC120400960

01/03/20151.0Interface DesignMC120400960

20/03/20151.0Test CasesMC120400960

Table of Contents

TopicPage1. Introduction of Design Document .. 042. Sequence Diagram. 053. Architecture Design Diagram.. 084. Class Diagram......................................... 095. Star Schema.. 106. Interface Design.. 117. Test Cases 15

1. Introduction of Design Document:

1.1 Purpose:Meaningful engineering representation of the Software that were to build. Software Design Document is the technical kernel of software engineering which is irrespective of software or any other discipline of development. This document play main role in development of any product. Analysis and Design helps for detecting error or function problem before actual development of the project. So the detection and removal of the errors are done at early stages which grow bigger as the days passes with development. In this phase were describing overall functionality of the system, to provide imminent to System Developers, analysts and Stack holder of product.

1.2 Details:In this document we included Sequence Diagrams to show sequences and activity of major processes, Architecture Design Diagram for architectural view of the Data warehouse, Class Diagram to show the system structure by system classes of system were developing, by using Star Schema we represent the under development Data Warehouse in the relational database model for implementation which mainly consist of four components: main fact table, dimensional table, attributes and attributes hierarchy, then Interface Design shows the process of developing method to connect and communicate with different modules of the under developing system and idea of interaction with them and at the last Test Cases is shows the set of conditions to check and test the functionality of software..

1.3 Objective:The core idea is to facilitate the system developers and analysts to analyze and develop the application as to fulfill the actual requirements of end customers. SRS document are the gathering of information which use here in design document with context of language, process and system behavior. After this phase requirement refinement is complete and approved by the stack holders, this also helps to develop a time schedule for development of the system.

2. Sequence Diagrams:

USC-001:Login

Allowaccess ()YesLogin ()

All TypesData warehouse ApplicationUser Account DataValidateUser()NoDisplayError ()

USC-002:Extract Transform and Load Data

loadData()Administratordataset()getDatabase()DisplyInterface()manageEvents()Data WarehouseApplicationUniversity Departments DatabasetransformData()DataWarehouse

USC-003:Add Executive

Notify()AskExecutiveInfo ()AddUserInfo ()YesisAdministrator()AddExecutive ()AdministratorData Warehouse ApplicationUser Account DataupdateUserData()

USC-004:Update or Delete User

isAdministrator()updateExecutiveInfo()YesviewExecutive()AdministratorData WarehouseApplicationUser Account DataselectExecutive()updataExecutive()Notify()

USC-005:Generate Report

YesisValidSendRequest()genrateReport()SendData()ExecutiveYesIsExecutive()getData()DisplyInterface()Data WarehouseApplicationDatabaseprovideParameters()User Account DataReportOptions()DisplayReport()rollupDrilldown()

3. Architecture Design Diagram:

Presentation TierUser interface Top-most level of the application.Which main function is to translate task and resultsthat user can understand.

Real-Time Financial Data warehouse Application..Logic TierThis layer will co-ordinates the application, processes Commands, makes logical decisions and evaluation,And perform data manipulations so the final output will beDisplayed on presentation layer

Data TierHere Information from all departments will be storedand retrieved from Data Warehouse, which is then processback to logic tier for reporting and then eventually back to userQueryData WarehouseReport

4. Class Diagram:

5. Star Schema:

For the Development of Data Warehouse, were dealing with the database which is non-normalized, duplicate, and pre-aggregated. So we to use star schema for multi-dimensional representation to optimize the data query operations. This technique is used for the mapping of multi-dimensional decisions support into relational database.

6. Interface Design:

Login Screen

Admin Interfaces

1. User (Executive) Management

2. ETL Trigger Management

Executive User Interface:

Report Generation

7. Test Cases:

Test Case # 1

Test Case Title: Testing the Login Interface of application

PreconditionsApplication should be connected to the Data Ware Server, Username and Password of Admin and Executive should be created

ActionsOn Entering the Username and Password in given field, and Click on the Login Button

Expected ResultsThe user is logged-in successfully as specified by the Username(Admin or Executive), for Admin the Admin Page should be shown for Administrator Interaction and Executive Page for Executive Interaction

Tested By:MC120400960

ResultPass/Fail

Test Case # 2

Test Case Title: Adding Users (Executives) by the Administrator

PreconditionsAdministrator is logged in Application and User Management Interface should be Opened

In User Management Interface, Add User tab is Clicked

ActionsEnter the Executive Data in the Fields given

Click on the Add Executive Button or Refresh Button

Expected ResultsThe system should display a Message of Added Successfully on Add Executive button or Refresh all the fields if clicked on Refresh Button

The data base of the User should be updated and on successful update the message should be displayed under save button.


ResultPass/Fail

Test Case # 3

Test Case Title: Testing the Edit and Delete of Executive.

PreconditionsAdministrator is logged in to the system.

Only administrator can access the User Management Interface of the Application

ActionsClick on the Tab Edit or Delete

System should display the List of all Executives, with option to select all the Executives or single Executive

After selection of the Executive, click on Edit or Delete Button

Expected ResultsIf Edit button is pressed the System should display the Page to Edit the details of Executives

If Delete button is Pressed the Successful deletion and Database or User should be Done after getting Confirmation with warning from the Administrator


ResultPass/Fail

Test Case # 4

Test Case Title: Testing of the ETL Trigger Management Interface.

PreconditionsAdministrator is logged in to the system.

Only administrator can perform ETL Trigger Management.

ActionsClick on the tab of ETL Trigger Management

Application should display the interface to select the options to when ETL process should be automatically performed by the system.Note:- Data Sources are from different Department which is only SQL

After selection of the desired methodology when ETL Process to be done.

Expected ResultsSystem displays the Successful compliance of the desired method.

After applying the settings system should display message or errors in case of any inappropriate occurrence.


ResultPass/Fail

Test Case # 6

Test Case Title: Testing of Report Analysis System. Executive User Interface.

PreconditionsUser should be logged in with executive rights.

Data Warehouse must contained the data from the Department loaded into the Data Warehouse.

ActionsClick on the Report Generation Management Tab.

Executive provide the parameters to generate the reports of desired Department.

Click on the Generate Report button.

Expected ResultsSystem should display the progress bar of report generation.

System should displayed the Reports on the Application. With the Drill Down or Roll up Input bar the show the result of User Requirement

Note:- Result Should be Displayed with in few seconds (3-5 sec)


ResultPass/Fail

Test Case # 7

Test Case Title: Testing of Roll Up and Drill down Functionality in the Reports Generated.

PreconditionsUser must logged in with Executive Rights.

Reports Screen should be displayed with the Generated Reports.

ActionsSelect the required category of the level from the drop down bars in the Roll up & Drill Down Section.

Click on the Apply button to display the change in the Reports.

Expected ResultsReports must be display the Changes provide by the User to Analysis.


ResultPass/Fail

Verifyuser()

-getUsername-getUserPassword-getUserType

Verify user+genrate_report()+viewreport()+drilldown_rollup()

-username-password-name-email-contact no

executive+addExecutive()+deleteExeuctive()+manageExecutive()

-userid-password-name-email

administrator-Creates

1

*

+getData()+TransformData()+LoadData()

-departmentName-serverId-serverPassword-timeStamp-ETLTrigerType

dataAccessObject

uses

uses

+Rollup()+DrillDown()

-expensiveType-revenueType-fromTime-ToTime

rollUpDrillDown

uses

+genrateReport()+viewReport()

-department-feeRevenue-SW_revenue-salaryExpense-utlilityBillExpensives-FurnitureExpense-studentBiodata-studentCourses-faculityBiodata-non-faculityBiodata

Reports-Grenrates

1

*

uses

-Department-ID-Time_ID-Total_Expenses-Total_Revenue-Expense_ID-Revenue_ID

RevenueExpensive (Fact Table)-Time_id-Time_year-Time_month-Time_Day

Time (Dim Table)

-Expense_ID-Employees_Salary-Utility_bills-Furniture_bills-ElectricalDevices_bills

FinanceDep (Dim Table)

-Employ_ID-Employ_Salary-Employ_Name-Employ_Type

HR_Department (Dim Fact)

-Revenue_ID-Student_fee-Software_Income

AccountsDep (Dim Table)

-Student_ID-Student_Name-Student_DOB-Student_Degree-Student_CurrentSem

RegistrationDep (Dim Table)

Form Title

Enter Text

Status bar

?

Enter Text

Text

Text

ABC University- Real Time Financial Data Warehouse

Form Title

Status bar

?

Enter Text

Text

Select and Type


Form Title

Status bar

?

Enter Text

Text

Text

Select and Type

Option 1

Enter Text


Form Title

Status bar

?

Enter Text

Text

Text

Select and Type

Option 1

Enter Text

Text


Documents

Design Document