Introduction and Conclusions/Recommendations’ Posting

                 In order to maintain the aptness of the feasibility report, it is critical to connect the introduction and the conclusion. Some of the main points in an introduction includes stating the issue that the project is addressing, outlines major alternatives, summarizing the research to justify the alternatives, and stating the conclusion. Similarly, there are tactics to create an effective conclusion/recommendation. It would be better if the conclusion and recommendation were broken down into separate paragraphs instead of combining them into one. Conclusion creates a brief summary of the entire feasibility report. It draws details from the research that we have done and information from the evaluations sections. For the recommendation section, we are suggesting what needs to be done next, or the actions that the reader has to do. It is better to make a recommendation for each alternative that we provided. For example, taking my team's feasibility report into consideration, for the introduction we stated the possible alternatives (android application, web application, web app with text alert), in conclusion we stated the results of each evaluation and why it would be better to use an alternative over the other. In the recommendation section we suggested that it would be reasonable to make the android application.