Local Government Unit Executive Dashboard

3.2 Software Design Specification

Project Study II

Local Government Unit Executive Dashboard 3.2.1 Introduction This chapter describes the design and architectural requirements and specifications in developing the Local Government Unit Executive Dashboard, a web-based dashboard. This section's purpose is to provide a highlevel design framework around which to build the Executive Dashboard. It also provides a list of requirements against which to test the final project and determine whether the researchers of this project were able to successfully implement the system according to design.

3.2.1.1 Goals and Objectives The underlying concepts are the goals and objectives of LGU Executive Dashboard: a. To provide easy-to-understand view of key performance indicators and real time data. Executives can use the system to quickly analyze Local Government Units performance since it is web based dashboard. b. To provide self-sufficiency to those in charged with extracting, reporting and analyzing data. c. To improve data quality, consistency and completeness. d. To enhance business agility and ensure that data is timely, accessible and can be transformed into meaningful information to support effective decision-making. e. To provide an authoritative and secure environment for data management. f. To get insight into Local Government Units behaviour.

Project Study II

Local Government Unit Executive Dashboard 3.2.1.2 Statement of Scope LGU Executive Dashboard is a web-based software that will allow users to generate and to deliver a full range of reporting, analysis and dash boarding on the performance and development activities and projects of the Local Government Unit (LGU), to enable the decision makers (executives) to quickly gain new insights and take actions to drive better outcomes. a. ED will be used by the executive positions of the Local Government Unit (LGU). b. ED will serve as a tool for monitoring the performance and evaluating the results of development activities and projects in the Local Government Unit (LGU). c. ED will enable smart analysis and easy reporting of real time data to support results-oriented decision making. d. ED will allow users to measure output, outcome and impact indicators of Local Government Unit (LGU) projects and activities. e. ED will measure and identify if the Local Government Unit (LGU) projects are achieved according to plan.

Project Study II

Local Government Unit Executive Dashboard 3.2.1.3 Software Context Executive Dashboard also considered as an Executive Dashboard considers the following concepts and interface descriptions; It consolidates relevant data from multiple sources into a single application, it explores the associations among all the data, it enables social decision making through secure and real-time collaboration, it visualizes data with engaging and state-ofthe-art graphics, it searches across all datadirectly and indirectly, it interacts with dynamic applications, dashboards and analytics, and it accesses, analyzes and captures data from other interrelated systems. With Executive Dashboard, users are capable of making

discoveries that drive innovative decisions, asking questions and pursuing insights on their own or collaboratively, searching across all their data to get the big picturejust by typing any word or phrase, in any order, into the Executive Dashboard search box for instant, associative results that let them see new connections and developments across the data and generating real-time or upto-date analytical reports for the Local Government Unit.

Project Study II

Local Government Unit Executive Dashboard 3.2.1.4 Major Constraints The Executive Dashboard (ED) is intended to help Local Government Units (LGU) on identifying progress towards results, precipitating decisions that would increase the likelihood of achieving results and enhancing accountability and learning. The software will only be used by the executive positions of the Local Government Unit. The fundamental principle of a

Executive Dashboard is to allow the users to capture data, process and disseminate information for decision making in a systematic way. As a part of the project, Executive Dashboards capability delivers a full range of reporting, analysis and dash boarding to enable the decision makers to quickly gain new insights and take actions to drive better outcomes. Better outcomes include a full range of decision making capabilities, easily accessible whenever, and whenever needed, tuned for optimal performance with the flexibility to grow with the Local Government Unit. The Executive Dashboard will use Java as the front-end or language, and My SQL Server for the back-end or database. Best performance can be attained by accessing the ED in a high end machine and high speed internet.

Project Study II

Local Government Unit Executive Dashboard 3.2.2 Data Design 3.2.2.1 Internal Data Structure Graphical User Interface (GUI) Java is being used for the development of the front end Graphical User Interface. Java provides a huge set of reusable GUI components such as button, text field, label, choice, panel and frame for building GUI applications. Java GUI components which are also called controls or widgets, allow users to interact with the software via mouse and keyboard as forms of inputs. Back End Data My SQL is being used for the development of the back end as the database technology and data storage system. My SQL offers great reliability and ease of use. It includes several client and utility programs. These include both command-line programs and graphical programs. It is mainly for administering data contained within tables and databases. Internal Functional Procedures For accessing or viewing any table, the data is fetched directly from the Database Management System to the Java database objects and are displayed directly on the screen. For report printing, temporary local variables have been defined in the procedures with meaningful names to store different values and then print the report.

Project Study II

Local Government Unit Executive Dashboard 3.2.2.2 Global Data Structure The only kind of data available globally to the whole system is the database itself stored in My SQL. After the JDBS connection, any data stored can be fetched and updated. 3.2.2.3 Temporary Data Structure The LGU Executive Dashboard does not use any intermediate temporary files of its own. As data is being stored in a Database Management System, all the intermediate data is being stored by the DBMS until the command commit is being executed in the SQL query by the application. Hence , no temporary intermediate files or data structures are used. 3.2.2.4 Database Description All tables with their corresponding attributes and descriptions are mentioned below: Table Name: Attributes: Description: User user_id, username, password, user_type, user_lname, user_fname, user_mname, email_add, department_id, position_id This table holds all the general information of all the users of LED. The primary key of this table is user_id. Department department_id, department_name, department_desc This table holds the information of different departments of the users of LED. The primary key of this table is department_id. Position position_id, position_name, position_desc This table holds the information about the positions that correspond to specific users of LED. The primary key of this table is position_id. Achievement achievement_id, achievement_type, sponsored_by

Table Name: Attributes: Description:

Table Name: Attributes: Description:

Table Name: Attributes:

achievement_name, achievement_desc, date_start, date_end, Status, Location,

Project Study II

Local Government Unit Executive Dashboard Description: This table contains the details about the Mayors successfully implemented missions and operations for the community. The primary key of this table is achievement_id. Achievement Type achievement_type_id, achievement_type_name, achievement_type_desc This table holds the information about the types of achievement the Mayor of the LGU has accomplished. The primary key of this table is achievement_type_id. Collection collection_id, date_collected, department_id, total_amount This table contains the formal account of the gains, proceedings or transactions of the LGU. The primary key of this table is collection_id. Budget budget_id, for_year, fund_account, function_program_project, expenditures, obligation, department_id, allotment_amount This table contains the details about the accounted and the assessed budget of the LGU spending for effectiveness. The primary key of this table is budget_id. Material Management material_mngt_id, item_name, item_category, supplier_id, quantity, unit_price, total_cost, department_id This table contains the details about the integrated approach to manage the entire need, flow and cost related to materials. The primary key of this table is material_mngt_id. Supplier supplier_id, supplier_name, supplier_desc, supplier_location This table holds all the general information of all the suppliers of materials of the LGU. The primary key of this table is supplier_id. Progress progress_id, date, total_no_permit, no_permit_released, no_permit_pending, no_permit_forfeited, no_permit_denied This table contains a comprehensive report on the LGUs activities throughout the preceding year. The primary key of this table is progress_id.

Table Name: Attributes: Description:

Table Name: Attributes: Description:

Table Name: Attributes: Description:

Table Name: Attributes: Description:

Table Name: Attributes: Description:

Table Name: Attributes: Description:

Project Study II

Local Government Unit Executive Dashboard 3.2.3 Architecture and Component Level Design 3.2.3.1 Architectural Diagram

Project Study II

Local Government Unit Executive Dashboard

Project Study II

Local Government Unit Executive Dashboard 3.2.3.2 Description of Components 3.2.3.2.1 Component User 3.2.3.2.1.1 Processing Narrative of Component User The component User contains the class User. It contains the basic attributes of the Administrator and the Executives. It also contains the functions and processes that enters and get the data from the database. The class User holds the data members and functions that are unique. The primary role of this class is to declare the variables of basic data of the user and to get relative data in and out of the database. 3.2.3.2.1.2 Interface Description of the Component User The component user has an interface with the class Administrator and Executive which attributes and functions are inherited. The User class holds the attributes that can separate the administrator to the executives. The users are identified thru the accounts that are set by the administration. This is to limit and set restrictions to users of the system. The attributes common to both administrator and the executives are shown in this interface and also the functions that are related to these attributes to set and get from the database are defined in this class. 3.2.3.2.1.3 Algorithmic Description of Component User Component User; The primary duty of this component is to set basic user data and set restrictions into the database and get data from the database Start Declare variables of the basic data Set the basic data of the user in the database Get the data from the database End

Project Study II

Local Government Unit Executive Dashboard 3.2.3.2.1.4 Design Class Hierarchy

3.2.3.2.2 Component Administrator 3.2.3.2.2.1 Processing Narrative of Component Administrator The component Administrator contains the class Administrator. It contains the basic attributes an Administrator. It also contains the functions and processes that enters and get the data from the database. The primary role of this class is to declare the variables of basic data of the administrator for the user and to get relative data in and out of the database. 3.2.3.2.2.2 Interface Description of the Component Administrator The component administrator has an interface with the different class which attributes and functions are inherited. The Administrator class is the one that is in charge of the control of data and information displayed for the user. The administrator attributes are share with the class User and other attributes related to the administrator class.

Project Study II

Local Government Unit Executive Dashboard 3.2.3.2.2.3 Algorithmic Description of Component Administrator Component Administrator; The primary duty of this component is to get data from the database to be displayed into the dashboard. Start Login Set the data of the Admin to the database Set the data of the Executive to the database Get the data from database Display the data to the dashboard End

Project Study II

Local Government Unit Executive Dashboard 3.2.3.2.2.4 Design Class Hierarchy

Project Study II

Local Government Unit Executive Dashboard 3.2.3.2.3 Component Executive 3.2.3.2.3.1 Processing Narrative of Component Executive The component Executive consists of the class Executive. The responsibility of this component is only to view the data from the dashboard and to print selected reports from the dashboard. This component only gets related data from the database to print the reports. 3.2.3.2.3.2 Interface Description of the Component Executive The component executive has an interface of only for viewing purposes of the data that are needed by them. The executive attributes are shared with the class User and other attributes related to the executive class. 3.2.3.2.3.3 Algorithmic Description of Component Executive Component Executive; The primary duty of this component is to view data from the dashboard Start Login Choose report to view Display the data to the dashboard End

Project Study II

Local Government Unit Executive Dashboard 3.2.3.2.3.4 Design Class Hierarchy

3.2.3.2.3.5 Restrictions /limitations The component executive is only allowed to view and print reports. Any action to modify the data from the database is not allowed.

3.2.3.2.4 Component Report 3.2.3.2.4.1 Processing Narrative of Component Report The component Report consists of the class Report. The responsibility of this component is only to print the data from the dashboard chosen by the users either the Administrator or the Executives. This component only prints the data of the selected report at the dashboard from the database.

Project Study II

Local Government Unit Executive Dashboard 3.2.3.2.4.2 Interface Description of the Component Report The component Reports has the interface with the classes Budget, Collection, Material Management, Achievement and Progress. It inherits the data members and functions from all the class to print the data report. 3.2.3.2.4.3 Algorithmic Description of Component Report Component Report; The primary duty of this component is to print the reports Start Get the Budget data Print the Budget data report Get the Collection data Print the Collection data report Get the Material Management data Print the Material Management data report Get the Achievement data Print the Achievement data report Get the Progress data Print the Progress data report End

Project Study II

Local Government Unit Executive Dashboard 3.2.3.2.3.4 Design Class Hierarchy

Project Study II

Local Government Unit Executive Dashboard 3.2.4 User Interface Design The systems Graphical User Interface (GUI) has been build using java. The design is created according to the required standards. In this section, the screen of the system has been showed below 3.2.4.1 Description of the User Interface 3.2.4.1.1 Screens The first page will appear in the beginning of the system is the login screen. The user will enter the username and password to direct on the system. The users are either administrator or the executive.

The information entered will verify by the system. When login is not verified, a message will prompt on the screen, otherwise, it will direct to the system page. Upon logging in, the next page will be the dashboard of either administrator or the executive users. Here below is the interface of administrators dashboard.

Project Study II

Local Government Unit Executive Dashboard

Above interface is the same as the dashboard of the executive that shows the summary of reports of other integrated systems. But only administrator can manage the setup of users and executive. The screen shows 4 rectangles that shows the main important report of other system. The charts below in the screen is another reports, a comparative report After clicking the system setup, it shows user and executive. The next screen shows the form of adding user. There are table beside the form to show the other data, confidential data doesnt show in the table like password.

Project Study II

Local Government Unit Executive Dashboard 3.2.4.1.2 Object and Actions The GUI shown above consists of java components. The screen consists of label for displaying text. Text fields for input of text. Command button are for the use of the execution and procedures. The charts display the reports of the systems. 3.2.4.2 Interface Design Rules Consistency and Standards Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions. Consistency of same procedure for same command buttons Flexibility and Efficiency of Use Accelerators -- unseen by the novice user -- may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions. Error Prevention Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action. Aesthetic and Minimalist Design Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.

Project Study II

Local Government Unit Executive Dashboard 3.2.4.3 Components Available Since the system will develop in java, java includes libraries to provide multi-platform support for Graphic User Interface objects. Java's GUI components include labels, text fields, text areas, buttons, etc. These GUI components are automatically drawn whenever the window they are in is drawn. When the components clicked, an event will generate according to the use of the component 3.2.4.4 User Interface Development System Description In the development of executive dashboard, there are user interface development system has been used. Advanced HTML has been used together with CSS. Javascript and jQuery used for the enhancement of different functions in the user interface design. 3.2.4.5 Reports The reports of the system are shown in graphical representation. The summary report of other integrated system will be show to the report of Executive Dashboard. Moreover, the system will produce reports for the executive weekly, daily, monthly, annually or as if needed the report. The data of the report came from other integrated to other system, to ensure the consistency of all systems.

Project Study II

Local Government Unit Executive Dashboard 3.2.5 Restrictions, Limitations and Constraints a. The system should integrate with the other systems and will show different important reports. b. The system is written in Java and the database is My SQL. c. The system will be only used by Executives and Administrator. 3.2.6 Testing Issues The various tests to be conducted to validate the software developed are login test, get/collect data test, display standing test and view report test.

Classes of Testing

Description

Expected Software Response

Performance Bounds

Components to be Identified

Log In

This test class is defined to validate whether the user is able to log in with his username and password. This test class is defined to validate whether all the information from the other interrelated systems are being processed and collected. Gathering all the data is being called in this test.

The user will be able to log in when he enters his username and password.

The user should not log in if enters a wrong username or password.

Test Data

Test Standing

This test class is defined to validate whether the status of the Local Government Unit is being displayed

The administrator will be able to collect data from the other interrelated systems when he clicks the appropriate button for getting data with the help of Application Programming Software (API). The user will be able to quickly gain insight of the Local Government Units standing

Reports

Project Study II

Local Government Unit Executive Dashboard for quick insight of by accessing information. and viewing the dashboards graphical and analytical charts. This test class is The user will be defined to validate able to view all whether all the the reports and reports of LED on perform the development analytical activities, projects approaches and and progress of decision making LGUs by accessing the performance on dashboard which different aspects automatically are being displays generated. information of different systems and search for the desired report to be printed.

Test Report

Reports

Project Study II