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.