1|Page

Real-Time Financial Data Warehouse

Design Document
Version 1.0

Group Id: F1402EC0E8

Supervisor Name: Sir Shabib Aftab

2|Page

Revision History
Date

Version

Description

Author

(dd/mm/yyyy)

15/01/2015

1.0

Introduction to Design Document

MC120400960

22/01/2015

1.0

Sequence Diagrams

MC120400960

25/01/2015

1.0

Architecture Design Diagram

MC120400960

02/02/2015

1.0

Class Diagram

MC120400960

10/02/2015

1.0

Star Schema

MC120400960

01/03/2015

1.0

Interface Design

MC120400960

20/03/2015

1.0

Test Cases

MC120400960

3|Page

Table of Contents
Topic

Page

1. Introduction of Design Document ..

04

2. Sequence Diagram.

05

3. Architecture Design Diagram..

08

4. Class Diagram.........................................

09

5. Star Schema..

10

6. Interface Design..

11

7. Test Cases

15

4|Page

1. Introduction of Design Document:

1.1

Purpose:

1.2

Details:

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

5|Page

2. Sequence Diagrams:
USC-001:

Login

Data warehouse Application

User Account Data

<<Actor>>
All Types
Login ()

ValidateUser()
Yes

Allowaccess ()

No

DisplayError ()

USC-002:

Extract Transform and Load Data

Data Warehouse
Application

University Departments Database

Administrator
manageEvents()
DisplyInterface()

getDatabase()

dataset()

transformData()
loadData()

Data
Warehouse

6|Page
USC-003:

Add Executive

User Account Data

Data Warehouse Application

Administrator
AddExecutive ()
isAdministrator()
Yes
AskExecutiveInfo ()
AddUserInfo ()
updateUserData()
Notify()

USC-004:

Update or Delete User

Data Warehouse
Application

User Account Data

Administrator
viewExecutive()
isAdministrator()
Yes
selectExecutive()

updateExecutiveInfo()
updataExecutive()
Notify()

7|Page
USC-005:

Generate Report

Database

Data Warehouse
Application

User Account Data

Executive
SendRequest()
IsExecutive()
DisplyInterface()

Yes
isValid

provideParameters()
Yes
getData()
rollupDrilldown()

ReportOptions()
genrateReport()

DisplayReport()

SendData()

8|Page

3. Architecture Design Diagram:

Presentation Tier

Real-Time Financial Data warehouse Application..

User interface Top-most level of the application.
Which main function is to translate task and results
that user can understand.

Logic Tier
This layer will co-ordinates the application, processes
Commands, makes logical decisions and evaluation,
And perform data manipulations so the final output will be
Displayed on presentation layer
Query

Report

Data Tier
Here Information from all departments will be stored
and retrieved from Data Warehouse, which is then process
back to logic tier for reporting and then eventually back to user

Data Warehouse

9|Page

4. Class Diagram:

10 | P a g e

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.

11 | P a g e

6. Interface Design:
Login Screen

12 | P a g e

Admin Interfaces
1. User (Executive) Management

13 | P a g e

2. ETL Trigger Management

14 | P a g e

Executive User Interface:

Report Generation

15 | P a g e

7. Test Cases:
Test Case # 1
Test Case Title: Testing the Login Interface of application
Precondition
s

Application should be connected to the Data Ware Server,

Username and Password of Admin and Executive should be
created

Actions

On Entering the Username and Password in given field, and Click

on the Login Button
The 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
MC120400960
Pass/Fail

Expected
Results
Tested By:
Result
Test Case # 2

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

Precondition
s
Actions
Expected
Results

Tested By:
Result

Administrator is logged in Application and User Management

Interface should be Opened
In User Management Interface, Add User tab is Clicked
Enter the Executive Data in the Fields given
Click on the Add Executive Button or Refresh Button
The 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.
MC120400960
Pass/Fail

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

Preconditions

Administrator is logged in to the system.

Only administrator can access the User Management

Actions

Interface of the Application

Click on the Tab Edit or Delete
System should display the List of all Executives, with
option to select all the Executives or single Executive

16 | P a g e

Expected Results

Tested By:
Result

After selection of the Executive, click on Edit or Delete

Button
If 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
MC120400960
Pass/Fail

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

Administrator is logged in to the system.

Only administrator can perform ETL Trigger Management.

Actions

Expected Results

Tested By:
Result

Click 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.
System displays the Successful compliance of the desired
method.
After applying the settings system should display message
or errors in case of any inappropriate occurrence.
MC120400960
Pass/Fail

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

User should be logged in with executive rights.

Data Warehouse must contained the data from the

Actions

Department loaded into the Data Warehouse.

Click on the Report Generation Management Tab.
Executive provide the parameters to generate the reports
of desired Department.

17 | P a g e
Click on the Generate Report button.
Expected Results

Tested By:
Result

System 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)
MC120400960
Pass/Fail

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

User must logged in with Executive Rights.

Reports Screen should be displayed with the Generated

Actions

Expected Results
Tested By:
Result

Reports.
Select 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.
Reports must be display the Changes provide by the User
to Analysis.
MC120400960
Pass/Fail