Since our group’s schema is feasibility report, the first step I did was to set a topic which is the Waitless App. I feel like my situation is perfectly for the feasibility report. I had this idea of developing the Waitless App for a while and this feasibility report is the perfect genre to propose my idea in a formal way. Writing this report makes my mind clearer of the functions of the Waitless. The schema helps a lot to organizing my words and report. The schema doesn’t have a page of explaining why do we need this App. I put the explanation in the exclusive summary which I’m not sure if it’s appropriate. The feasibility page has difference types where I can easily express my idea in different field whatever it’s a technical way or a financial way. After the peer reviewing, I found out that how to use the schema to make my sub-contents in the table of contents page which is great that I don’t need to figure it out later. It makes the report looks more organized and clearer. The schema of success criteria needs definition because I was a little confused to use this schema. Also, the timeline page and the estimate cost page is not the same as what I thought. Using the schema is mostly the same as long as I understand the definition and the purpose of each element. The schema for the first project is kind of short and less complicated than this project so it feels like easier for last time. However, the schema we have for this project organize the whole report which is good for me to write it. I would like to discuss about the success criteria and the report pages later.
