For week one, I need an 8-10 page software assurance guidelines

For week one, I need an 8-10 page software assurance guidelines document shell or outline. It is not a completed document. It will basically be an outline. I must add more information to this outline each week until eventually I will have a completed software assurance guidelines document. This document can be for a real or hypothetical company. It can be any company that works for the government or it can be a hypothetical company. The selected organization or company must produce software applications for the government, and is therefore subject to software assurance requirements. So, I need an 8-10 page paper:

The first page will be the title page. The second page will be the table of contents that summarizes the entire document. The third page will be the project outlines requirements and page four will discuss Security in the Development life cycle. The following 4 to 6 pages will only be section headings that will be completed in later weeks of the course. For example, week two will discuss Software Assurance Techniques, and Week three will discuss Security in Nontraditional Development Models so on a so forth.

WRITE THIS ESSAY FOR ME

Tell us about your assignment and we will find the best writer for your paper.

Get Help Now!

The selected organization should be large enough to allow reasonable exercise of the software assurance guidelines planning process.

You should be familiar enough with the organization to allow you to focus on the planning tasks without significant time required for domain education.

You should have access to the people and other information related to the organization. This will be an important part of the planning process.

Your first task in this process will be to select an organization (or identify a hypothetical organization) to use as the basis of your projects.

Appropriate research should be conducted to support the development of your guideline document, and assumptions may be made when necessary.

The outline of the document must contain the following information:

• Create a software assurance guidelines document shell in Word. It should include the following:
  • Create a title page (I will create the title page)
  • Table of contents (TOC) (Required week 1)
    • Use autogenerated TOC
    • Separate page
    • Maximum of 3 levels deep
    • Update the TOC before submitting your project
  • Section headings (create each heading on a new page with “TBD” as content, except for sections listed under New Content below)
    • Project Outline (Required week 1)
    • Security in the Development Life Cycle (Required week 1)
    • Software Assurance Techniques (Required week 2) (Section Heading)
    • Security in Nontraditional Development Models (Section Heading)
    • Security Static Analysis (Section Heading)
    • Software Assurance Policies and Processes (Section Heading)
    • Project outline and requirements (Required week 1)
      • Brief description of the organization (can be hypothetical) and where the guidelines will be implemented
      • Company size, location(s), and other pertinent information
      • List of the software applications provided by the company for the government

• The software list must include at least 1 desktop and 1 Web application.
• A database must be used with one of the applications.

• A summary of the software development organization within the company, employees and reporting structure, systems and technologies used for software development, testing, source control, and document storage

• Material can be taken from the approved proposal that was submitted to the instructor (ensure that this project is approved by the instructor).

• Security in the development life cycle (Required week 1)
  • Provide an outline of the SDLC model that is used in your organization, including each of the major phases.
  • This should be a traditional SDLC. Extended models, such extreme programming, will be covered in a later section.
  • Identify specific components of the security development model that can be applied to each of the phases of your SDLC model.
  • For each pairing of security development model component to SDLC model phase, describe how the security model is applied and the major tasks that are involved.