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.