Chapter 10 Posting/Developing an effective style

Part 1:
            Chapter 10 demonstrates ways of how to sound confident in our communication, how to communicate effectively, how to convey the meaning of the communication clearly to the reader, and how to create a professional voice. One of the guidelines that I often use is "Find out what is expected." It demands us to predict how formal the subjects expect our communication should be, the style of the communication, personal style or impersonal style to distance ourselves. The subject's expectation of the style depends of several factors such the subject's personality, our personality, traditional customs in our field, employer's organization, our purpose, professional relationship with the subject, etc. I have found myself using this guideline the most when I am attending interviews. Before the interview, I do enough research to find the background information about the interviewers and the company. This information will usually give enough clues on what to expect. The tone is almost always very professional and the distance in communication will change accordingly. It is also important to avoid stereotypes. In most cases, we might not know the background of the person, let it be cultural, institutional, or any other categories of background. It is always better to convey a professional tone from the beginning. It can only help us and the subjects


Part 2:
             In my opinion, Sample 3 does a better job linking the objectives and Solution. It has taken into consideration each functional and non functional requirement objectives and linked the solution to it. Sample 3 even considers the subsections. Though Sample 2 provides a summary at first and then link objectives to solution, it is not as explicit as Sample 3. Sample 3 demonstrates the calculations of how they will approach the grading by linking the formulas correctly with their objectives. A fault that I found for Sample 2 was their lack of alternate solutions. Whereas, Sample 3 gives two separate formulas for performing their task. The Solution for Sample 3 addresses the scope very clearly and precisely. The details were highlighted in a very comprehensive manner. The sub sections and other steps further solidifies the issue that the team is trying to solve. Though both samples provide a system architecture diagram, Sample 3's diagram displays a flow of information visually which can help readers analyze the critical components of the system. In my opinion, Sample 2 has failed in handling its scenarios since it doesn't translate well. Even though Sample 2 addresses the issue redundantly, it still does a good job on addressing the details of the project.


Part 3: 
          I believe that Sample 2 has the most effective Resources section compared to the other two samples. One thing that struck the most is how it is organized into two separate tables. One for resources provided by the team and one for resources provided by the client. Breaking down the resources into two separate tables is useful for the reader as well as for the team. As opposed to that, samples 1 and 3 just include that in a text format, not necessarily grabbing a reader's attention.  Another component that I liked is inclusion of reason, source and cost. It makes it visually easier for a reader to analyze the section. The titles were emphasized for both resources(provided by clients and team). From what we have learned in Chapter 10, this displays professionalism and it is very effective in grabbing a reader's attention. My second choice would be Sample 1 but it is not as succinct as Sample 2. This sample has made my list because it includes two separate sections for the resources as well. One for hardware and software resources and one that's supplied with the help of GTPD. I also like the way they have formatted the section with the inclusion of appropriate spacing, and appropriate font sizes.