week 10 - Methodology

1. Conceptual system modeling   
• Receive the document of current model of SPASA from requirement team
• Identification of current system process/flow
• Problem definition and need identification.
• Identification of current system components.
• Identification of the components of the water resource reference models.
  •  Activity diagram
  •  System sequence diagram
  •  Use case descriptions
  •  Use case diagram 
  • Reference model component description.
  •  Current system component description.
2. Preliminary system design  
• Mapping of reference model components and current system components.
• Analyzing system component specification.
• Design activities
• Integrating elements and activities  
  • Architectural description
  •   System specification
3. Design and development  
   
• Development of models
• Application of reference model components in the design of system.
• System prototype development
• Deployment diagram
• Domain class diagram
• Detail class diagram
• Data design
• Component design

week 9 - LR

These are the key-words for the literature review that I have done.

1. Reference model
2. System Design
3. Water resources
4. Water resource reference model
5. Reference model of open distributed processing (RM-ODP)
6. Design science methodology

Week 8 - Objectives

1. To identify what is the reference model component to be applied in the SPASA. 
2. To harmonize the SPASA component and reference model component. 
3. To apply the water resource component of reference model to SPASA.

Week 7 - Updated Problem Statement

Problem Statement

LUAS is a government agency. It is an Enterprise which manages the water resources in Selangor. Currently, the design of SPASA is meant for a single application. Since LUAS is an Enterprise, SPASA do not refer to the enterprise architecture system perspective.

According to Professor Peter Weill (2007), enterprise architecture is the capabilities in organizing logic for key business process and IT that reflecting the integration and standardization requirements of the firm’s operating model.

Several interviews have been conducted with the team member from LUAS whom stated that they are lack of information integration between the departments of LUAS and several external consultants which involve in the process of licensing.

Currently, SPASA is a stand-alone client server which is not integrated with other systems in LUAS that involve in the water licensing process such as Sistem Notis and Compound System. Moreover, an external consultants such as Minerals and Geosciences Department (JMG) that has their own system cannot share the information smoothly since the applications that been passed to them are in a printed form. These problems occur within the enterprise system environment.

This project is meant to applying related and significant reference model that help in information sharing between departments of LUAS and organizations that involve in SPASA.

Week 6 - Chapter 1

Overview of Chapter 1

Research Background

Sistem Perlesenan Abstraksi Sumber Air (SPASA) is a current system of Lembaga Urus Air Selangor (LUAS) which managing the water resources licensing in Selangor, Malaysia. Companies or individuals need to have license which can only be granted by LUAS before they can use any water resources of Selangor.   

The current SPASA was developed by using oracle application which is stand-alone client-server architecture.

The purpose of this research is to apply a reference model to design a web-based system of SPASA.

By using reference model, each entity of related agency (water resource) has an indication to share the logical model. They provide ideas and understanding on how such procedures, a set of system use cases and the standards that have been adopted can be looked at as a reference and also organizing relationship between entities.

“A reference model is an abstract framework for understanding significant relationships among the entities of some environment. It enables the development of specific reference or concrete architectures using consistent standards or specifications supporting that environment.”(“ Reference Model for Service Oriented Architecture 1.0”,2006)

“The fundamental idea of reference modeling to save process knowledge in models, in order to use it at a later point in time, has currently been recognized by the event management literature. Thus for example, Schwandner states that “it is almost always better to adopt good ideas from others, follow their tips and then optimize them for your individual needs” (Schwandner, 2004, p. 27).”(“Reference Model-Based Event”,2008)

 
 Problem Statement

The process of licensing resides in LUAS involve several departments; Lembangan, Kewangan, Perundangan and Consultants. While the application of license filled in manually by the client. Client need to come to LUAS to get the form, make payment and get the license by themselves. This is where the idea in making web-based application triggered.

The current SPASA was developed by using oracle application which is stand-alone client-server architecture and does not use any water resources based reference model. Therefore, current physical model of SPASA system has no proper modeling representation.

The database of current SPASA holds 6 tables of data which are not normalized and the attributes only separated by the different forms that exist in the system. Since the tables are not normalized, it is seen clearly that there are redundancies of data which violated the definition of data model in software engineering on data storage and accessibility.

But in order to have a proper design of water resources web-based system which of course include the database engineering, SPASA need to use reference model as guidance.

week 5 - Rapid Application Development

RAD

week 5 - Literature on Reference Model

WACOM
WATERWARE
WRON
Water Well Licensing(Division of Water Supply)
 

week 5 - Introduction to SPASA

25th May 2011

• First meeting with the team

June-August 2011

• Requirement Gathering 
• Requirement Analysis
• Meetings with IT Department of LUAS
• Meeting with the Chairman of LUAS
• 1st draft design of SPASA prototype
• Presentation of the 1st draft design of SPASA prototype to team
• 2nd draft design of SPASA prototype

Week 1 & Week 2

• Meetings with supervisor regarding working title
• Presentation of  2nd draft design of SPASA prototype to the head of IT Department of LUAS

Week 3 & Week 4

• Journals & Papers reading on Reference Model
• Meeting with the head of IT Department of LUAS

Week 5

• Discussion with Supervisor on the Reference Model