Best IT Documents.com Blog


The Project Summary

Posted in Projects (400) by Guest on the November 27th, 2009

It’s not enough to say what you’re
going to do…

 

…You must explain, in detail, how  you’re going to do it!

The project summary may be the only part of your proposal that some reviewers read.

Funding agencies typically assemble panels of experts to review dozens of proposals at the same time. A “primary” and a “secondary” reviewer are assigned to each proposal; they read it in detail and report back to the panel Although all members of the panel vote on every proposal, because of time constraints, many will read only the abstracts of those proposals that are not specifically assigned to them.

·      Remember, reviewers are busy
·      The summary may be the only part of the proposal reviewers read
·      If the summary is so poorly written,
·      Some reviewers may not continue into the technical narrative

Even though it comes first in the proposal document, don’t write the project summary until last. The project summary should present the entire scope and contents of the project.

Organize your project summary to reflect the organization of the technical description; present the same concepts, in the same order, using the same words, so that the reviewers remember them

·      Project summary should written last
·      Should present the entire scope and content of the project
·      Organize summary to
·      Reflect organization of technical description
·      Briefly present concepts and main points

The project summary should “stand alone”. It should serve as a well-written, accurate summary of the entire proposal. It should explicitly state the goals and objectives of the project. It should include an overview of the methodology. It should address the aims of the funder that will be served by the project. It should state the project’s significance.

·      Summary should stand alone!
·      Be enough of an introduction to:
·      Accurate summary of entire proposal
·      Explicitly state the goals and objectives of the project
·      Include an overview of the methodology
·      Address the aims of the funder
·      State the project’s significance

Answer these questions, in this order, for a perfect project summary:
·      What do you intend to do?
·      Why is it important?
·      What has already been done?
·      What methods will you use?
·      What results do you expect?
·      How will you analyze your data?
·      What contribution will your project make to the mission of the funder?
·      Make your answers as specific, detailed, and quantitative as possible
·      For a perfect project summary
·      Answer these questions in order:
·      What do you intend to do? What hypothesis will you test?
·      Why is it important?
·      What has already been done?
·      What methods will you use?
·      What results do you expect?
·      How will you analyze your data?
·      What contribution will your project make to the mission of the funder?
·      Make your answers concise as well as:

o       Specific
o       Detailed
o       Quantitative

Use the checklist here to critique your summary

·      The summary states the subject of the investigation immediately and its significance discussed?
·      The summary presents the preliminary work and any unanswered questions posed
·      The summary explains the goals and objectives of the work
·      The summary states the methods and data analysis
·      The summary states the expected findings
·      The summary states the benefits to the funder

Follow style conventions

·      Defined all
·      Abbreviations
·      Acronyms
  

Special symbols

·      No figures are included
·      Summary stands alone
·      No references cited
·      No mention is made figures, tables equations from main text

Ask for input and review course corrections to improve now and in the future.

·      How would your reviewer find your summary?
·      Ask yourself whether:
·      Ideas are expressed clearly and concisely?
·      Language is familiar and precise?
·      Standard western nomenclature and notation used?
·      Stylistic conventions are observed?
·      Text is free from typographical errors?
·      Did you international collaborators review the summary to standardize the language?

Write your summary separate from the technical narrative

·      Do not cut and past the first few paragraphs from your technical narrative
·      Project summary must describe entire project.
·      Omissions in the summary raise questions in the reviewers’ minds about the whole project

Be cautious about stating hypotheses in your summary

·      Don’t assume your hypothesis is true!
·      Identify hypotheses for what they are:
·      Something to be tested
·      Not the truth

Respect the limits of a summary

·      Reserve the most pertinent information for the summary
·      Remove irrelevant information
·      Your summary may become public information

Comments Off on The Project Summary

Setting up your PC

Posted in O S (375) by Guest on the November 11th, 2009

The Configuration
When you first set up a new PC, you should refer to the owner’s manual for all technical specifications. To start your PC Notebook, document the following basic configuration information: 

Make, model, and speed of CPU
Amount of RAM and what type the system uses
The make, model, and speed of any internal/external drives (Hard Drive, CD-ROM, CD-R, CD-RW, DVD-ROM or DVD-RAM drive)
Make, model, and memory of your video card
Type of monitor and the resolutions it supports
Operating System (OS) and its version number
A list of preinstalled software applications
Make, model, and speed of any internal/external modem or fax modem
A list of other peripherals (sound card, speakers, network card, etc.)
 

PC Problems
With the information you’ve gathered in the PC Notebook you created on the previous page, you’re ready to start using some basic troubleshooting skills to take on any computer problem that occurs. As problems arise, start a new page in the notebook for each issue.  You’ll want to document the problem, the date/time it occurs and make detailed notes using the following questions:

What is the exact error message or nature of the problem?
When did the problem first occur?
What applications were open when the problem occurred?
Has the problem occurred more than once?
What tasks were you performing when the problem occurred?
What changes have recently been made to your system?

By asking these questions, you’re trying to isolate and determine exactly what was going on with your PC when the problem occurred and ultimately, why it happened

Comments Off on Setting up your PC

Application Security Related Activities

Posted in Application,Security (1500),Web Services (250) by Guest on the November 9th, 2009

Security Objectives. Define security objectives and requirements early in the process. Security objectives are goals and constraints that affect the confidentiality, integrity, and availability of your data and application. 

Design Guidelines for Security. To avoid many of the vulnerabilities introduced by poor design choices, your design activity should use proven design practices, patterns, and principles. By organizing these design patterns and practices into common vulnerability categories, you can focus on those areas where security mistakes are most often made. 

Threat Modeling. Threat modeling helps you to understand and identify the threats and vulnerabilities relevant to your specific application scenario. 

Architecture and Design for Security. The architecture and design review process analyzes the architecture and design from a security perspective. It examines a number of aspects including deployment and infrastructure, overall application architecture and design, and each tier in the application. 

Code Review for Security. All code should be subject to code inspections where the emphasis is on identifying security vulnerabilities. This should be a continuous activity during the development and test phases of the application life cycle. 

Security Testing. Use a risk-based approach and use the output from the threat modeling activity to help establish the scope of your testing activities and define your test plans. 

Deployment Review for Security. When your application is deployed, you need to be sure that weak or inappropriate configuration settings do not introduce security vulnerabilities.

http://www.bestitdocuments.com/Services.html

 

Comments Off on Application Security Related Activities

Sample – Internet Footprint Intelligence Review

Posted in Security (1500) by Guest on the November 7th, 2009

Purpose

Scouting and scavenged information from a Network and Internet presence that can be analyzed as business intelligence. 

Objective
Size and scope of the Internet presence 

Task

  1. A measurement of the security policy to future network plans
  2. Tasks to perform for a thorough Competitive Intelligence Scouting
  3. Map and measure the directory structure of the web servers
  4. Map the measure the directory structure of the FTP servers
  5. Examine the WHOIS database for business services relating to registered host names
  6. Determine the IT cost of the Internet infrastructure based on OS, Applications, and Hardware.
  7. Determine the cost of support infrastructure based on regional salary requirements for.
  8. IT professionals, job postings, number of personnel, published resumes, and responsibilities
  9. Measure the buzz (feedback) of the organization based on newsgroups, web boards, and industry feedback sites
  10. Record the number of products being sold electronically (for download)
  11. Record the number of products found in P2P sources, wares sites, available cracks 

Purpose

Privacy Review 

Objective 

The privacy review is the focal point of the legal and ethical storage, transmission, and control of data based on employee and customer privacy. 

The use of this data is a concern to many private persons and legislation is unveiling specific rules regarding privacy. 

Although some of these laws are local, all of them apply to the Internet and therefore affect security testers internationally. 

Expected Results 

List any disclosures

List compliance failures between public policy and actual practice 

Outcomes

  1. List systems involved in data gathering.
  2. Compare publicly accessible policy to actual practice
  3. List data gathering techniques.
  4. Compare actual practice to regional fraud and privacy laws or compliancy
  5. List data gathered.
  6. Identify database type and size for storing data
  7. Tasks to perform for a thorough Privacy Policy review.
  8. Identify data collected by the organization
  9. Compare publicly accessible policy to actual practice.
  10. Identify storage location of data
  11. Compare actual practice to regional fraud and privacy laws or compliancy.
  12. Identify cookie types
  13. Identify database type and size for storing data.
  14. Identify cookie expiration times
  15. Identify data collected by the organization.
  16. Identify information stored in cookie
  17. Identify storage location of data.
  18. Verify cookie encryption methods
  19. Identify cookie types.
  20. Identify server location of web bug(s)
    Identify cookie expiration times.
  21. Identify web bug data gathered and returned to server
  22. Identify information stored in cookie
  23. Verify cookie encryption methods
  24. Identify server location of web bug(s)
  25. Identify web bug data gathered and returned to server 

http://www.bestitdocuments.com/Services.html

 

Comments Off on Sample – Internet Footprint Intelligence Review

Internet Footprint Intelligence Review

Posted in Security (1500) by Guest on the November 2nd, 2009

Purpose

Scouting and scavenged information from a Network and Internet presence that can be analyzed as business intelligence.

Objective
Size and scope of the Internet presence

Task

  1. A measurement of the security policy to future network plans
  2. Tasks to perform for a thorough Competitive Intelligence Scouting
  3. Map and measure the directory structure of the web servers
  4. Map the measure the directory structure of the FTP servers
  5. Examine the WHOIS database for business services relating to registered host names
  6. Determine the IT cost of the Internet infrastructure based on OS, Applications, and Hardware.
  7. Determine the cost of support infrastructure based on regional salary requirements for.
  8. IT professionals, job postings, number of personnel, published resumes, and responsibilities
  9. Measure the buzz (feedback) of the organization based on newsgroups, web boards, and industry feedback sites
  10. Record the number of products being sold electronically (for download
  11. Record the number of products found in P2P sources, wares sites, available cracks up to

 

Purpose

Privacy Review

Objective 

The privacy review is the focal point of the legal and ethical storage, transmission, and control of data based on employee and customer privacy. The use of this data is a concern to many private persons and legislation is unveiling specific rules regarding privacy. Although some of these laws are local, all of them apply to the Internet and therefore affect security testers internationally.

Expected Results

1.      List any disclosures
a.       List compliance failures between public policy and actual practice
b.       List systems involved in data gathering
c.       List data gathering techniques
d.       List data gathered
2.      Tasks to perform for a thorough Privacy Policy review
3.      Compare publicly accessible policy to actual practice
4.      Compare actual practice to regional fraud and privacy laws or compliancy
5.      Identify database type and size for storing data
6.      Identify data collected by the organization
7.      Identify storage location of data
8.      Identify cookie types
9.      Identify cookie expiration times
10.   Identify information stored in cookie
11.   Verify cookie encryption methods
12.   Identify server location of web bug(s)
13.   Identify web bug data gathered and returned to server


Outcomes

1. Compare publicly accessible policy to actual practice
2. Compare actual practice to regional fraud and privacy laws or compliancy
3. Identify database type and size for storing data
4. Identify data collected by the organization
5. Identify storage location of data
6. Identify cookie types
7. Identify cookie expiration times
8. Identify information stored in cookie
9. Verify cookie encryption methods
10. Identify server location of web bug(s)
11. Identify web bug data gathered and returned to server

Comments Off on Internet Footprint Intelligence Review