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