3.2 Software Design Specification: Project Monitoring System

Project Monitoring System
3.2 Software Design Specification
Software Design Specification
Page 1

3.2.1 Introduction 3.2.1.1 Goals and Objectives It is important not only to meet the requirements of the system but also to surpass it in order to meet the expectations of the users. The proposed Project Monitoring System aims to help the LGU to have a system that will handle their records easily and safely. The proponents considered some related factor about the project monitoring to come up with a good plan and wanted to develop a software application developed using JAVA Eclipse IDE for the development surroundings and uses MySQL Server for the database server. It is computerized for faster project monitoring of the Municipality to be used by them. The Project Monitoring System is designed to establish a well-built recording, planning, determining direct project cost and scheduling of the different projects of Municipality. One of the most general jobs of project monitoring is scheduling and planning. Scheduling is used to sequence project activities and assign dates to them. The detail and sophistication of a schedule produced by a Project Monitoring System can lessen all the works. There are different objectives that the Project Monitoring system involves such as: To give a complete record for the user for the projects that is easily maintained, readily accessible and very comprehensive To prevent the duplication of project record To easily access and record projects To give convenient project monitoring process for the different Municipalities To give consistent record of complete, ongoing and realigned projects To give efficiency and gain access for the progression of a project To plan, organize, and schedule different approved projects in Municipality To influence the factors that cause changes to ensure that changes are beneficial, determine that a change has occurred, and manage actual changes as they occur. To enable a regular tracking of the progress made by the project, highlights areas for improvement in the design or implementation of the project and enables delivery of high quality results.
Software Design Specification Page 2

The Project Monitoring System involves historical information on how projects have progressed, and in particular, how actual and planned performances are related. Users will be able to provide the needs of the Municipality. Innovation of the current system will be provided through the Project Monitoring System. It can produce a high quality and secured program. Security of the documents is highly recommended. The system enables users to robust the productivity work of city hall and lastly, it can give a complete record for the user that is easily maintained, readily accessible and very comprehensive.
3.2.1.2 Statement of Scope Monitoring of project progression is a critical component in the overall monitoring of a project. A projects ability to provide accurate, timely information to a variety of audiences may significantly affect the relationship the project has with its staff, monitoring, and beneficiaries of the project and outside funding agencies. In addition, the quality and accuracy of the project details reported to donors and other governmental entities can affect a projects funding, a projects credibility and the publics perception of a project. A project mon itoring strategy should be developed which will specify how project is created or collected, maintained, reported and stored. All projects should have a monitoring system; it may be informal and undocumented or formal and documented. Monitoring of project should be incorporated into the projects comprehensive monitoring system which includes all of a projects information needs. A projects monitoring system should address the use of both technological and human resources. Project Monitoring System has its scope. As a general the process of monitoring is included planning, implementation and evaluation of the projects that can cater all the projects of Municipality to make sure all development projects can be done consistently at all level and any problem occurs will straight away taken into action. An efficiency of monitoring system always needs to be upgraded from time to time with the introducing of some new method or system from the government due to the current technology changing.
Page 3

Major Inputs Project name, description, start date, end date, duration, and cost Evaluation date, comment, risk Activity name, start date, end date, duration, cost Reminders to remember Risk involved Progression of project Change or modification for project Project Team incharge Personnel
Processing Functionalities Function Project Information Entry Evaluation information entry Reminders to remember Project Team incharge Risk involved Activities done Progression of project Changes in project Priority Essential Essential Desirable Essential Essential Essential Essential Essential
Output Actual vs. Planned Project Report, Actual Cost vs. Planned Cost Report, Semi-Annual Project Progress Reports, Executive Status Report
Page 4

3.2.1.3 Software context A project needs to systematize its information into balanced easily understood categories to increase its access and use. By organizing information a project is able to: implement standards for the depiction of information; relate different pieces of information to one another in meaningful ways; protect information from destruction; and make information available for people to use. The organization, storage, and retrieval of projects information is a critical component of monitoring. The project needs to be able to find the specific information that best answer a query, and to collate information. With issues that arise, certain solution is needed in order to obtain a good and successful project monitoring aid. Information sources are significant to project needs, which at the beginning of the project can be quite large. All projects should have a monitoring system; it may be informal and undocumented or formal and documented. Monitoring of project should be integrated into the projects comprehensive monitoring system which includes all of a projects information needs. A projects monitoring system should deal with the use of both technological and human resources. A well-organized and competent monitoring system to the projects growth is the most vital aspect in order to ensure their performance will be going smooth and not be affected due to the present phenomenon of world economic.
3.2.1.4 Major Constraints The Project Monitoring System will use JAVA Eclipse IDE with the database server MySQL. The system should be excellent enough to perform all the actions fast.
3.2.2 Data Design As the application is being built in java and MySQL, the overall application design can be classified into three parts.
1. Front End Graphical User Interface 2. Back End Data 3. Internal Functional Procedures

Graphical User Interface (GUI) Java is being used for the development of the front end GUI. The GUI components temporarily stores the keyboard input by the users till its being used by the functional procedures.
Back End Data For the back end, we are using the MySQL for storing all the information in the form of tables. These tables will be globally accessible to all the internal procedures.
Internal Functional Procedures The internal functional procedures are the logical entities that take out dissimilar task of adding, updating, deleting, viewing or printing the database.
3.2.2.1 Internal Software Data Structure There are no data structures available to the internal software architecture. The intermediate information while updating or adding to any table is stored in the java swing component. When the add or edit and update button is pressed the information in those text fields is directly sent to the database for add or update. For the report printing temporary local variables have been defined in the procedures with significant names to store different values and then print the report.
3.2.2.2 Global Data Structure The only kind of data available globally to the whole system is the database itself stored in MySQL.
3.2.2.3 Temporary Data Structure The Project Monitoring application doesnt use any intermediate temporary files of its own. As data being stored by the DBMS until the command commit is executed in the SQL query by the application.
Page 6

3.2.2.4 Database Description
Below are mentioned all tables, their corresponding attributes and a small description of each.
Table Name: Project Attributes: Project Name, Description, Contract Agreement, Start Date, End Date,
Actual Start Date, Actual End date, Project Cost, Evaluator, Activity, Project Team Description: It holds the general information about certain projects. The primary key of this table is Project ID.
Table Name: Activity Attributes: Name, Start Date, End Date, Actual Start Date, Actual End Date, Duration, Risk, Cost, Actual Cost Description: It holds information about the activities done and ongoing. The primary key of this table is Activity ID.
Table Name: Progress Attributes: Progression, Project, Document, Photo Description: It holds the information about the progression of a project. The primary key of this table is Progress ID.
Table Name: Change Attributes: Change, Date, Event Description: Holds information about changes that occur for a project. The primary key of this table is Change ID.
Table Name: Reminder Attributes: Date, Message, Project Description: Reminds the user about a certain project. The primary key of this table is Reminder ID.

Table Name: Risk Attributes: Name, Description Description: Holds information about the risk involved. The primary key of this table is Risk ID.
Table Name: Evaluation Attributes: Evaluator, Date, Project, Comment, Risk Description: Holds information about the evaluated projects thru the work done by the evaluator. The primary key of this table is Evaluation ID.
Table Name: Project Team Attributes: Name, Leader, Member Description: The project team holds information about the team who handles a project. The primary key of this table is Project Team ID.
Table Name: Personnel Attributes: Username, Password, First Name, Last name, Access category Description: It holds the information about the personnel who uses the system. The primary key of this table is Personnel ID.
3.2.3 Architecture and Component Level Design
3.2.3.1 Architectural Diagram
The architectural context diagram for the project monitoring system is shown below. As it is clear from the diagram, various actors are admin, project managers and mobile users which will use the system. The subordinate systems that will be used by the software are the database (MySQL) and Java. Also, NetBean is a tool to connect the java to the database. Maintenance system is super ordinate, which needs the software for testing and maintenance purposes.
Page 8
Figure 1: Architectural Diagram
3.2.3.2 Description of Components
3.2.3.2.1 Component Project 3.2.3.2.1.1 Processing narrative of component Project The component project contains the class Project. It contains the attributes, which are the basic data of the project. It contains the functions, which sets all the related data into and out of the database. The class project contains the data members and functions, which are unique to the project. The responsibilities of this component is to declaring variables of the basic data of the project and implementing functions which set data in the database and retrieve from the database.

3.2.3.2.1.2 Interface description of the component Project The component project has an interface with the class project where it can get the attributes and functions. The attributes and operations which are unique to the project are declared and defined in the component class.
3.2.3.2.1.3 Algorithm description of component Project Component Project; The intent of this component is to set basic project data into the database and get data from the database.
Start Declare variables of the basic data Set basic data of the project in the database Get the data from the database End
3.2.3.2.1.4 Design Class Hierarchy
3.2.3.2.1.5 Restrictions/Limitations This component can only be called when the user requires the data of the project.
Page 10

3.2.3.2.2 Component Activity
3.2.3.2.1 Processing narrative of component Activity The component activity contains the class activity. It contains the attributes, which are the basic data of the activity. It contains the functions, which sets all the related data into and out of the database. The class activity contains the data members and functions, which are unique to the activity. The responsibilities of this component is to declaring variables of the basic data of the activity and implementing functions which set data in the database and retrieve from the database.
3.2.3.2.2 Interface description of the component Activity The component activity has an interface with the class project which it inherits attributes and functions. The attributes and operations which are unique to the project are declared and defined in the component class.
3.2.3.2.2.3 Algorithm description of component Activity Component Activity; The intent of this component is to set basic activity data into the database and get data from the database.
Start Declare variables of the basic data Set basic data of the activity in the database Get the data from the database End
Page 11

3.2.3.2.2.5 Restrictions/Limitations This component can only be called when the user requires the data of the activity.
3.2.3.2.3 Component Project Team
3.2.3.2.3.1 Processing narrative of component Project Team The component project team contains the class project team. It contains the attributes, which are the basic data of the project team. It contains the functions, which sets all the related data into and out of the database. The class project team contains the data members and functions, which are unique to the activity. The responsibilities of this component is to declaring variables of the basic data of the project team and implementing functions which set data in the database and retrieve from the database.
3.2.3.2.3.2 Interface description of the component Project Team The component project team has an interface with the class user which it inherits attributes and functions. The user class has attributes, which are the basic data that determine what kind of access level the user has. The attributes and operations which are unique to the project team are declared and defined in the component class.
3.2.3.2.3.3 Algorithm description of component Project Team Component Project Team;
Page 12

The intent of this component is to set basic project team data into the database and get data from the database.
Start Declare variables of the basic data Set basic data of the project team in the database Get the data from the database End
3.2.3.2.3.5 Restrictions/Limitations This component can only be called when the user requires the data of the project team.
3.2.3.2.4 Component User
3.2.3.2.4.1 Processing narrative of component User The component user contains the class user. It contains the attributes, which are the basic data of the user. It contains the functions, which sets all the related data into and out of the database. The class user contains the data members and functions, which are unique to the user. The responsibilities of this component is to declaring variables of the basic data of the user and implementing functions which set data in the database and retrieve from the database.
Page 13

3.2.3.2.4.2 Interface description of the component User The component user has an interface where it will get its attributes and functions. The user class has attributes, which are the basic data user. The attributes and operations which are unique to the user are declared and defined in the component class.
3.2.3.2.4.3 Algorithm description of component User Component User; The intent of this component is to set basic user data into the database and get data from the database.
Start Declare variables of the basic data Set basic data of the user in the database Get the data from the database End
3.2.3.2.4.5 Restrictions/Limitations This component can only be called when the user requires the data of the user.
Page 14

3.2.3.2.5 Component Change
3.2.3.2.5.1 Processing narrative of component Change The component change contains the class change. It contains the attributes, which are the basic data of the change. It contains the functions, which sets all the related data into and out of the database. The class change contains the data members and functions, which are unique to the changed made. The responsibilities of this component are to declaring variables of the basic data of the changes and implementing functions which set data in the database and retrieve from the database.
3.2.3.2.5.2 Interface description of the component Change The component change has an interface where it will get its attributes and functions. The change class has attributes, which are the basic data user. The attributes and operations which are unique to the change are declared and defined in the component class.
3.2.3.2.5.3 Algorithm description of component Change Component Change; The intent of this component is to set basic change data into the database and get data from the database.
Start Declare variables of the basic data Set basic data of the change in the database Get the data from the database End
Page 15

3.2.3.2.5.5 Restrictions/Limitations This component can only be called when the user requires the data of the changes.
3.2.3.3 Dynamic behavior for component 3.2.3.3.1 Interaction Diagrams
Page 16

3.2.4 User Interface Design 3.2.4.1 Description of the User interface 3.2.4.1.1 Screen Images
Page 17

3.2.4.2 Interface Design rules 3.2.4.3 Components available 3.2.4.4 UIDs description
3.2.5 Reports Design 3.2.5.1 Inventory of Reports 3.2.5.2 Layout of Reports 3.2.5.3 Data Dictionary of Reports
3.2.5 Restrictions, Limitations, and Constraints 3.2.6 Testing Issues
Page 18

3.2 Software Design Specification: Project Monitoring System

Uploaded by

Copyright:

Available Formats

3.2 Software Design Specification: Project Monitoring System

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3.2 Software Design Specification: Project Monitoring System

Uploaded by

Copyright:

Available Formats

Project Monitoring System