#4: Derived Requirements and Modeling

Make sure Blog is posted to the correct location on the website. Do not post to more than one area. If we cannot find it we cannot grade it.
Clearly identify project member(s) who and how they contributed to the post. If this information is not included then no grade can be assigned.
Do not plagiarize material. For example if you use a photo, as a minimum provide source. See University “Cheating and Plagiarism” policy for more on this topic.
Failure to follow any of the following directions will result in an automatic grade reduction.
- Once posted only your “Introductory” paragraph should appear on the project page with a “Read more à” link.
- Blog post must include a square teaser photo.
- All blog post must include image(s) for illustrative purposes. See Blog Post 101 and Advanced Editor Basics to learn how to format images for upload. Failure to “optimize” images result in long periods of time from upload to the photo appearing within your blog post. This often leads to multiple uploads, with the instructor spending time deleting photos in the media folder.
- Please use courier font and single spacing on Code examples.
New blog posting Hierarchy
1. All members can create a new post for their project and generate material
2. Project Managers can create and edit all members posts and must approve a post for review
3. Quality Control Engineer reviews posts in “Review” status and publishes or kicks post back to the Project manager