Sunday, December 16, 2007

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

    No comments: