Last Reg (na sana ^_^)

D G10 Week 8 Progress Report...

This week we have accomplished:

.:: David Louis Achacon

• Established the connection between the database and the program
• Has retrieved data from the database and displayed it in UI

.:: Helen Grace Borromeo

• Third Normal Form of the Relational Database
• Finalized the Entity Relationship Diagram
• Reviewed Standard Query Language
  
• Further studied and researched about JDBC and how to use it in the project
  

.:: Denise Carlos

• Collated the group's progress reports as part of the User Acceptability Test Case Suite and Data Design
• Reviewed the past lessons discussed in SQL part of CS165
  

.:: Maryann Kaye Puyaoan

• Created and modified User Acceptability Test Case Suite and Data Design
• Studied on how JDBC works

Our next week goals are:

• Submit the final draft of our prototype
• Start making the database of the project usable by connecting more parts of it with the program
  
• Work on with the SMS gateway

Our most important concerns/issues/questions are:

• Integrating the SMS gateway with the system
  

We learned:

.:: David Louis Achacon

• How database is integrated with the program

.:: Helen Grace Borrome

• User Acceptability Test Case Suite and Data Design as discussed in class
• Java Database Connectivity Design Pattern
  

.:: Denise Carlos

• Systematic view of the project through the User Acceptability Test Case Suite and Data Design

.:: Maryann Kaye Puyaoan

• The importance of the User Acceptability Test Case Suite and Data Design for our project
  

WEEK 9 PROGRESS REPORT

Things we have accomplished are:

-=Todz=-

Talk to client to clarify form processing

Did PHP Prototype Draft

Did Normalized Table for the Database

Editted User Manual Draft

Meet with groupmate to plan for the final draft of user manual and prototype

-=Rich=-

Did User Manual Draft

Editted PHP Prototype Draft

Meet with groupmate to plan for the final draft of user manual and prototype

-=Hannah=-

Did initial draft of Normalized Table for database

Editted HTML prototype draft



Our Next Week goals are:

*Submit Final Draft of

prototype

User Manual

Normalized Tables

* Since, there are clarifications and modifications in the prototype

and database design, these will also bemodified:

Analysis Class

Use Case Specifications

*Work on the Database



Our most important concerns/issues/questions are:

*Clarifications on the processing of forms, especially on wasting.

*Studying how to deploy web applications

*Study database



We learned:

-=Todz=-

*PHP

*Normalizing Forms

*The importance of understanding how everything is done in the system

-=Rich=-

*PHP

*The importance of group communication and cooperation

*The importance of understanding how everything is done in the system

-=Hannah=-

*PHP

*The importance of group communication and cooperation

*The importance of understanding how everything is done in the system

JAKA Week 7 Progress Report

This week I have accomplished:

**Andrew Mantes**

• Clarify some issues about the project scope and specifications.
• Researched and read some info about JavaServer Faces.

**Jamilla Tabal**

• Clarified concerns regarding the project by setting an appointment with our instructor.
• Started downloading JSF tutorials.
• Started the migration of the current prototype from static html form to JSF version.

**Karen Pajarito**

• Updated Requirements Traceability Matrix.
• Added additional component in RTM.
• Researched on JSF framework.

**Ada Angeli D. Cariaga**

• Studied the attributes of each entity.
• Started to make the original table for the attributes.

Our next week goals:

• Have a deeper understanding of how JSF works.
• Finish the system prototype.
• Revise use case specifications.
• Create stories and screenshots for use cases.
• Continue update Requirements Traceability Matrix.
• Finish normalization.
• Learn JSF as soon as possible.
• Develop screen prototype using JSF.
• Prepare ourselves for some more things to do.

Our most important concerns/issues/questions are:

• What server to use for our application?
• If the client will agree on the changes we made in the project
• If there will be changes on the requirements

We learned:

**Andrew Mantes**

• Overnight success isn't always possible.
• Proper coordination and cooperation could turn the tide in favor of you.

**Jamilla Tabal**

• Introduction to JSF
• Advantages and Disadvantages of JSF
• Importance of each role each of the team members is expected to play.

**Karen Pajarito**

• Importance of division of labor
• Scoping
• Design engineering phase and deliverables
• Use of design patterns
• Some available frameworks for applications
• Role of analysis classes

**Ada Angeli D. Cariaga**

• Design engineering phase
• Different frameworks that can be used or applied in our project

D G10 Week 6 Progress Report...

This week we have accomplished:

.:: David Louis Achacon

• Designed the Use Case Model
• Made the project's user interface prototype using java and netbeans
• Presented the prototype to our client, Dra. Madera
• Created the Entity Relationship Diagram
• Finalize the Use Case Model and Diagram

.:: Helen Grace Borromeo

• Made the prototype of the project
• Had a meeting with the client to present the prototype and ask her about further questions
• Created the entity relationship diagram of the project

.:: Denise Carlos

• Created the Use Case Specification
• Helped in making the prototype of our project
• Helped in creating the Entity Relationship Diagram of our project
• Presented our deliverables to our adviser
• Had a meeting with our client

.:: Maryann Kaye Puyaoan

• Collaborated with groupmates for the class presentation
  
• Helped in creating draft for ERD
• Had meeting with our client

Our next week goals are:

• Start studying about what technologies will be used in the project
• Normalize the class diagram, entity relationship diagram
  
• Revise user interface for project
• Research on how to send messages from pc to mobile phone
• Have a consultation with our adviser
  
• Study software architecture

Our most important concerns/issues/questions are:

• Hardware to be used, its details and how it works

We learned:

.:: David Louis Achacon

• How to go to the Philippine General Hospital
• The importance of waking up early to avoid being late.
• How to make Entity-Relationship Diagram

.:: Helen Grace Borromeo

• It is easier for the client to have and idea of how the system works through prototypes
• Entity relationship diagrams give a better view of the data to be used in the system

.:: Denise Carlos

• To specify important points in our project to our client with the aid of the prototype and the use case specification
• To apply the Entity Relationship Diagram and Normalization concepts in CS165 in our CS192 deliverables

.:: Maryann Kaye Puyaoan

• The horizontal prototype is a very useful tool in presenting the concepts of the system to the client.

JAKA Week6 Progress Report

This week we have accomplished:

**Andrew Mantes**

• Developed project’s UI prototype using Java Swing
• Helped to accomplish project’s use-case model and diagram
• Visited UPD Health Service to inquire on their own system of accomplishing PHIC claim forms

**Jamilla Tabal**

• Made the draft of the Use Case Model.
• Designed the Use Case Model.
• Created and Designed the System Prototype.
• Took part in redefining the use case model and diagram.
• Went to Infirmary to clarify issues regarding the manual PhilHealth benefits claiming procedure.

**Karen Pajarito**

• Researched on Barcode and PDF generators for Java
• Requirements Traceability Matrix
• Revised Requirements Traceability Matrix
• Use Case Specifications
• Contributed in designing the Use Case Diagram
• contributed in making the Analysis Classes
• Contributed in Designing the revised Use Case Diagram
• Inquired at the Infirmary with the group to clear how PHIC claims are processed
  

**Ada Angeli D. Cariaga**

• Made the draft of the Use Case model.
• Made the Requirements Traceability Matrix
• Made the Use Case Specification.
• Made the Draft of the Class diagram.
  

Our next week goals:

• To talk to our client to clarify concerns regarding the project.
• Perform necessary revisions on the Use Case Model and Class Diagram.
• Finalize the Use Case Model and Diagram.
• Revise the System Prototype.
• Revise the Analysis Classes.
• Fully accomplish correct UML designs for the project
• Start designing the System User Interface.
• Research on possible technologies that will aid in the implementation of the project(Bar Code Generator and PDF Generator).
• Look for a contact person that will clarify our concerns regarding the project.

Our most important concerns/issues/questions are:

• Clarification on the System Requirements set by the client.
• Hardware to use in the project(barcode).
• Efficiency, effects, and probably problems that may arise in migrating the project into a web-based application
• Proper division of labor and effort is important to prevent issues/conflicts

We learned:

**Andrew Mantes**

• How to use netbeans application to create Java Swing UIs and UML
• Importance of self-discipline and priorities
• Importance of constant communication between clients and developers
• Importance of passion and time in developing and producing great outputs
• UML basics

**Jamilla Tabal**

• The importance of clear and efficient communication among the team
• The importance of the components(Use Case Diagram, RTM, Horizontal Prototype, Analysis Classes) and how they affect each other
• The importance of Use Case Diagram and the role it plays in the creation of subsequent deliverables
• UML basics
• The basic guidelines in making a system prototype

**Karen Pajarito**

• Importance of open communication
  
• Consistency of Information and data
• Effect of abrupt changes in the system design.
• Importance of Personal Collaboration with our group
• How PHIC Claims are processed in some hospitals
• Recent changes in the actual PHIC claims processing
• New Requirements needed for PHIC claims processing
  

**Ada Angeli D. Cariaga**

• The different steps in analysis period from the use case model to the analysis classes.
  
• How important the Use case model in our project and how it may affect the whole project
• It is difficult to do rush analysis, it will just cause more errors.

D G10 Week 5 Progress Report...

This week we have accomplished:

.:: David Louis Achacon

• During the Christmas break, we contacted Doc Vanie and asked her questions concerning the project
• While waiting for Doc Vanie's reply, I researched on the technologies that we might possibly need for the development of our project
• Downloaded e-books and tutorials.
• Doc Vanie finally replied and gave us the project requirements/specifications. As soon as we got these requirements, we immediately started making the Use Case Specifications and Use Case Model for our project and sent it to Doc Vanie

.:: Helen Grace Borromeo

• Contributed to the Use Case Specifications
  
• Corresponded with the client regarding the project
• Started drafting the Class Diagram

.:: Denise Carlos

• Had an initial overview of our project based on the preliminary specifications given by our client
• Reviewed 3.3 - 3.5 of the JEDI material
• Contributed to the Use Case Specifications

.:: Maryann Kaye Puyaoan

• Reading the Requirements Traceability Matrix
• Having a preliminary understanding of our system's requirements
• Collaborated with my groupmates in creating the Use Case Diagram and Use Case Specifications for our system

Our next week goals are:

• Finalize the Use Case Specifications and Use Case Model after consulting the client
• Finalize the technology that will be used for our project
• Clarify some of our questions with our client regarding the system's functionality
• Study concepts of Design Engineering Basics
• Acquire the Project Requirements
• Start the project development
• Continue consulting with our advise and our client
• Share the Requirements Traceability Matrix in Google Docs

Our most important concerns/issues/questions are:

• The response to the e-mail to our client was delayed. However, our client told us to just contact her through text if we have e-mails regarding the project
• Discussing and finalizing the technology that will be used for this project

We learned:

.:: David Louis Achacon

• I learned something on internet applications and how to install and configure these applications
• Importance of communication with clients and groupmates

.:: Helen Grace Borromeo

• The importance of discussing the project with our client
• How to create Use Case Specifications and Class Diagrams

.:: Denise Carlos

• How to make Use Case Specifications and Use Case Diagram
• The importance of collaborating and brainstorming with my groupmates for the deliverables
• The importance of getting in touch with the client and my groupmates to meet with our project's requirements

.:: Maryann Kaye Puyaoan

• Concepts of Requirements Traceability Matrix
• How to make Use Cas Specifications and Use Case Diagram
• Better understanding of Use Case Analysis Technique
• That the Requirements Engineering Phase is really an iterative process. At the time we created the deliverables, we usually go back from the start everytime we make changes on some parts of the Use Case Model.

JAKA Group - Week 5 Progress Report

This week I have accomplished:

**Andrew Mantes**

• Had meeting with our client and was informed about the process and scope of the project
• Read basic information about HTML, XML, and JavaScript

**Jamilla Tabal**

• Had a chance to meet the client in person.
• Joined the project official website.
• Had a clearer understanding of how the system works.
• Acquired the forms needed for the project.
• Researched on the needed technologies for the system(bar coding system).

**Karen Pajarito**

• Met with our client
• Researched the new concepts and tools that will be needed in the system
• Got a copy of the necessary forms needed in developing the system
• Joined our project’s site

**Ada Angeli D. Cariaga**

• Having a meeting with Dr. Alvin Marcelo (our client) and discuss our project

Our next week goals:

• Start finalizing the requirements
• Start doing the analysis model
• Start doing the RTM
• Research circulars on how to fill-up forms.
• Continuously communicate with client.
• Decide on the technology to be used to implement the system.
• Look for the tools that will be used in developing the system
• Continue to communicate with our client
• Start working on the deliverables
• Reflect on the details and functionalities of the project based on the data given by the client
• Formulate a personal draft of the project’s system requirements
• Initially determine the actors, use cases, and other functionalities concerned in the project

Our most important concerns/issues/questions are:

• Start doing the project
• How to manage the project
• What is the most efficient way to implement a bar coding system?
• The tools that will be used in developing the system
  

We learned:

**Andrew Mantes**

• Some basics of internet applications
• Project leader's responsibilities
  

**Jamilla Tabal**

• The importance of clear and efficient communication among the project team in order to finish the desired project.
• The impact of efficient project implementation.
• The importance of meeting the client in person to easily clarify things regarding the project.
• Importance of Project Management

**Karen Pajarito**

• Importance of project management
• How to negotiate with our client
• Importance of personal collaboration with our group and client
• Processing of Philhealth claims
• Present situation of Philhealth claims
• Relevance and impact of the project on the community
• An overview of project management
  

**Ada Angeli D. Cariaga**

• The importance of our project
• The possible effect if we finished our project
• Prioritization

PYRAMID PROGRESS REPORT

This week we have accomplished...

Todz:
Meeting with our client
Learning more about the system to be developed
Meeting with the group to summarize meeting with the client, plans and delegation of tasks
Reviewing the RTM, Use Case Diagram and Use Case Specifications
Creating a site to where files are uploaded and members can communicate

Rich:
Meeting with our client
Learning more about the system to be developed
Meeting with the group to summarize meeting with the client, plans and delegation of tasks
Reviewing the RTM, Use Case Diagram and Use Case Specifications
Posting plans and minutes of meeting to 192 blog

Hannah:
Learning more about the system to be developed
Meeting with the group to summarize meeting with the client, plans and delegation of tasks
Reviewing the RTM, Use Case Diagram and Use Case Specifications
Suggesting timeline for our project

Our next week goals:
Completing timeline for the project
Start with the Use Case Diagram and Use Case Specifications
Follow up some questions with our client
Learn php

Our most important concerns/ issues/ questions are:
Some clarifications about the system
Start with the deliverables

We learned:

Todz:
Requirements Traceability Matrix
The importance of communicating and negotiating properly with the client

Rich:
The importance of communication with clients
The importance of planning our actions and delegation of tasks

Hannah:
Requirements Traceability Matrix
The importance of communication with clients

JAKA Group - Week 4 Progress Report

This week I have accomplished:

**Andrew Mantes**

• Set appointment with our client
• Plan our unofficial time line
• Expose to the concept of requirements traceability matrix (RTM) and its perspectives

**Jamilla Tabal**

• Understanding the purpose of a Requirements Traceability Matrix
• Learning how to create an RTM
• Collaborated with the group in arranging an appointment with the project client

**Karen Pajarito**

• Cooperated with out group in setting out the schedule to accomplish the deliverables
• Provided the absentees a file containing a brief summary of the discussion about RTM
• Researched on PHILHEALTH claims matters

**Ada Angeli D. Cariaga**

• Planning on how to do the project, ask for a meeting to discuss certain issues

Our next week goals:

• Meet with our client for the requirements of the system
• Discuss the project in person with our client
• Discuss the details and functionalities of the project based on the data given by the client
• Initially determine the actors, use cases, and other functionalities concerned in the project
• Get sample forms and data needed in developing the system
• Start working on the deliverables as soon as the client and our group agreed on the system’s requirements
• Formulate a draft of system’s requirements and specifications
• Start listing the requirements for the project
• Plan how the project will be done

Our most important concerns/issues/questions are:

• Concrete details of the system we’ll be going to develop
• What is the step-by-step procedure in managing the forms?
• What data do we have to keep track of?
• What are the major functions the system performs?
• How to do the task during Christmas break

We learned:

**Andrew Mantes**

• Learned the implication and possible effects of having plenty of requirements and/or having your requirements revised from time to time

**Jamilla Tabal**

• Requirements Traceability Matrix
• The importance of having a clear idea on the system requirements and functionalities so as to minimize future RTM revisions

**Karen Pajarito**

• Requirements Traceability Matrix (RTM) and its initial components
• Some possible components that can be added in the RTM
• Importance of RTM in software development

**Ada Angeli D. Cariaga**

• Requirements traceability matrix and how will it be helpful in our project
• That in any project you need to prioritize things

JAKA Group - Progress Report

This week I have accomplished:

**Andrew Mantes**

• Collaborated with our group to create use case diagram for The Bulilit Liga case study.
• Created the revised use case diagram for the above study.
• Researched on some possible technologies to be used in the project.
• Gathered information and details regarding the PHILHEALTH claims management system and other related matters.

**Jamilla Tabal**

• Creating and Developing a use case model for the sample case, “Bulilit Liga”.
• Performing a walkthrough on the mentioned case study, assuming the role of a reviewer.

**Karen Pajarito**

• Played the role of a reviewer of the other group’s use case model
• Preferred format for the action list document

**Ada Angeli D. Cariaga**

• Designed and created the use case model of “Ang Bulilit Liga” as a sample case study.
• Act as the scribe in the walkthrough done for the case study

Our next week goals:

• Get in touch with our client and tried to acquire necessary information regarding the project personally.
• Decide on the project’s requirements and features
• Learn design engineering

Our most important concerns/issues/questions are:

• What are the specifications of the project?
• What is the step-by-step procedure in managing the forms?
• What data do we have to keep track of?
• What are the major functions the system performs?
• Requirements of the project assigned to the group

We learned:

**Andrew Mantes**

• I've learned some concepts regarding requirements engineering especially requirements specs and requirements analysis.

**Jamilla Tabal**

• I’ve learned the step-by-step process of developing a use case model and how a walkthrough is done as well as the things that need to be included in an action list. Also, I learned the differences among the three classes, namely : Boundary Class, Control class and Entity class.

**Karen Pajarito**

• Software engineering and what it is all about
• Importance of quality to the software development
  Role played of each person involved in the software development process and its mportance
• Object-oriented concepts and process model
• UML and how to do some modeling activities
• Concepts of requirements engineering
• How to perform a walkthrough to a group’s use case model

**Ada Angeli D. Cariaga**

• The importance of the walkthrough in software development
• The importance and uses of action list
• Requirements engineering

Week 3 Progress Report...

This week we have accomplished:

.::David Achacon

1. We had a chance to experience a walk through. We didn't have the pre- and post-walk through activities, only the walk through proper. The chairman presented the Use Case Model to the reviewer while the scribe listed all the errors and the comments of the reviewer. This is also called action list.
   

.::Helen Borromeo

1. Researching about the project assigned to us namely "Surgery Follow-up Through Text Messaging"
   

.::Denise Carlos

1. Reading chapter 3 – Requirements Engineering
2. Reading “Ang Bulilit Liga” case study
3. Creating a Use Case Model for the said case study
4. Reviewing the Use Case Model of the said case study by a walkthrough

.::Maryann Kaye Puyaoan

1. Creating and Developing Use Case Model using Use Case Diagram for “Bulilit Liga” case study
2. Discussing Use Case Model, and Use Analysis Technique

Next week our goals are:

1. To understand the requirements traceability matrix
2. Start creating the basic deliverables of our project

Our most important concerns/issues/questions are:

1. The format that we'll have to follow when creating an action list during a walk through
2. Arguments raised between the project developer and the reviewer of the work product
3. Details of the Special Project we are going to make
4. Do we need to make our project web-based to support its text messaging capability?

We learned:

.::David

1. I have learned to criticize the product and not the person who made it. I also learned to always document the action list.

.::Helen

1. Use Case Analysis and the correspondence of the deliverables to the components of the project

.::Denise

1. Making Use Case Model for a system. By just looking at this model, it would be easier for the developers, users and costumers to understand the specifications of the system
2. From our walk through activity, I realized that the people in a review team must cooperate and do their job well because it will be the basis of how effective the walk through will be. That is, the developer must present the work product clearly to avoid ambiguities and misunderstandings. In doing so, it will be easier for the reviewer to find bugs. Also, the scribe must document the walk through with a clear and precise action list during the walk through.

.::Maryann

1. How to make Use Case Model using Use Case Diagram
2. UML
3. What is Analysis Modeling technique
4. Differences between Boundary, Control and Entity

Links To Our Web 2.0 Classroom

Hello, everyone. I am hoping this post can help you have a one-stop accessing to our learning Web 2.0 tools.

CS 192 HMRU Blogspot for Progress Report
CS 192 HMRU Google Groups for Collaboration