Monthly Archive for August, 2007

Page 3 of 5

The 50 50 Marking Scheme

NOTE: The following applies to all currently submitted work and future submissions.

The marking scheme I have decided on for this semester, is one I call “50 50″ (Pronounced: Fifty Fifty).

Basically, it works like this:

All your reports, and documentation that you create and hand in to me, will earn you a score out 50. If you receive a score of 50/50, then that is equivalent to 100%. 49/50 equates to 98%, and so on. I will return your submissions back to you, with the total score out of 50 and the percentage, along with the usual feedback etc.

Overall your documentation and hand-ins will account for 40% of your total score over the entire semester. An online quiz will account for the remaining 10%

The other 50% will be accounted for in practical demonstration. The demonstrations will include your team demonstrating functions of the system you will build, working as required. However, you will all also be tested individually. It is likely I will take some in class demonstrations by yourselves, as evidence that you are capable in the area we are working on. This may be in the form of “Tick Offs” or myself just simply observing your use of skills and knowledge learned.

I like to quiz people on the spot, so be prepared!

Having said all that:

In regards to your documentation, reports, hand-ins, etc, you will need to maintain a minimum average of 60% (30/50) to be credited with a minimum of a “Pass” on your transcript. I will allow resubmissions for scores lower then 30/50, however your resubmission will only earn you a total of 30/50, even if it is worth 50/50.

In regards to your practical demonstration, you will also need to maintain a minimum average of 60% to be credited with a minimum of a “Pass” on your transcript. Often practical demonstration will be a case of “Yes you can do it” or “No, you can not do it”. If time permits, I will give you another chance to demonstrate.

I can not stress this enough. If I teach you something, and you are unsure, or do not understand, please;

ASK ME FOR FURTHER ASSISTANCE! I AM ONLY TOO HAPPY TO HELP YOU!

Create a Security Policy

Hi Everyone,

I have written the following article as a guideline / outline of what your Security Policy report should contain. Again, these articles are derived from the points under “Introduction” on the Power Point Slides. Be sure to always read the Reading Notes, and go back through the Power Point presentation again at least once. If you have any further questions that require answers, please feel free to ask.

  • Assess Security Features of Internet Gateways with Reference to Architecture and the Security Plan
    • What will the users have access to? Hardware? Software?
    • What will the users be denied access to? Hardware? Software?
    • How will the users be protected? – Include Anti-Virus and Firewall Solutions
  • Review Security Measures with the Internet Service Provider with Reference to Firewalls and other Measures
    • Choose an ISP and in regards to ISR:
      • Review their security measures
      • Review their firewalling
      • Review any protective measures they have in place
      • Review any other measures they have in place
  • Brief Users on the Security Plan with Reference to Internet use and Possible Hazards
    • Design a Security Policy, encompassing the information above
    • Include possible issues they may come across, brief solutions to these issues
    • Include a section on “Acceptable Use of the Internet” and “Internal Resources”
    • Include the ramifications for not complying

The Reading Notes contain further information in regards to what is required in each of the four sections of your document above. If you are unsure of where the information in the Reading Notes is, please ask.

Client Requirements Report

Hi Everyone,

I have written the following article as a guideline / outline of what your Client Requirements Report should contain. Again, these articles are derived from the points under “Introduction” on the Power Point Slides. Be sure to always read the Reading Notes, and go back through the Power Point presentation again at least once. If you have any further questions that require answers, please feel free to ask.

  • Confirm and Validate Client Requirements
    • Confirm the client requirements
    • Validate the client requirements
    • Include a validation check list
  • Determine the Scope of Internet Services with Reference to the Client Requirements
    • What are the internet services required?
    • What will be required to make these services available?
  • Identify and Verify the Equipment Specifications and Availability
    • What hardware is already available?
    • What hardware will need to be acquired? Include the costs and evidential reasoning for the acquisition
    • What software is already available?
    • What software will need to be acquired? Include the costs and evidential reasoning for the acquisition

The Reading Notes contain further information in regards to what is required in each of the four sections of your document above. If you are unsure of where the information in the Reading Notes is, please ask.

Design a Server Report

Hi Everyone,

I have written the following article as a guideline / outline of what your Server Design report should contain. Again, these articles are derived from the points under “Introduction” on the Power Point Slides. Be sure to always read the Reading Notes, and go back through the Power Point presentation again at least once. If you have any further questions that require answers, please feel free to ask.

  • Review Vendor Design and Specified Server for Design Applicability
    • Review the Vendor Design, in regards to the selected hardware and software, if you opted to source all your components individually
    • Review the Vendor Design, in regards to the hardware and software selected by the vendor for you, if you have opted to source a complete system
    • Is the design of your server, applicable to the requirements? How? Provide evidence
  • Design a Server
    • Design your server
    • Provide a profile of the server, and the selected hardware and software components. Be detailed
    • Remember: Logical and Physical Design
  • Analyse Server Design against Requirements of the Client
    • Does your server meet the requirements of the client? Detail each requirement that is met by each hardware and/or software component
    • Validate your design against the client requirements
  • Test Server for Benchmarking against Client Specification Requirements
    • Build a server and run the required tests (you can use a machine in the lab, or your own at home) – Provide the results of your tests
    • OR fabricate accurate results for your tests
    • Include any additional hardware and software your used. Including built in hardware and software
  • Make Required Changes to the Design from the Outcomes of the Design Testing
    • Make changes to your server hardware and software or configuration, based on the results of your testing
    • Provide evidence of further testing in the areas that received failures or negative results to show the improvements yielded from the changes

The Reading Notes contain further information in regards to what is required in each of the four sections of your document above. If you are unsure of where the information in the Reading Notes is, please ask.