Monthly Archives: June 2023

discuss and compare different file systems, in terms of Memory usage, process requirements, computational cost, system overhead, efficiency and reliability? 

I have attached the assignment instruction. Please read throughly. 

Question: Discuss the LEED certification process.

Fully address the question(s) in this discussion; provide a valid rationale or a citation for your choices.

The initial post should be at least 350 words in length.

*** References

***No Plagiarism

*** APA7 Format 

refer to the attached document in the uploads

  Please read chapters  4,  5 and 6 of your textbook and answer the following questions:

1)  What are the seven steps of a computer security defense plan. review chapter 4.

2) What are the Three Categories of Security Policies. List and briefly discuss each category. Review Chapter 5. 

3) What are the Responsibilities of Security Director? Review chapter 6.

Design a treatment plan utilizing the case study of Leigh (page 171) following the format displayed in Figure 6.2 on page 172 of the textbook. Be sure to address the following in your treatment plan:

1. Problem areas identified
2. DSM Diagnosis with specifiers
3. Goals & Objectives to address each problem area identified
4. Describe Treatment Interventions
5. Client’s strengths and weaknesses (liabilities)
6. Theoretical model for treatment strategies

Include at least four scholarly sources in your treatment plan to include the course readings.

Assignment Content

1. We spent a large amount of time in class talking about “good” systems and “not so good” systems…and we saw some of the characteristics of each…and I am sure (at least I hope) that while we discussing it, you were thinking of systems that you think are good, and those that you think are not so good…

   So for this assignment, I want you to tell me one system that you think is good, and one system that you think is not so good…if it is a website, include the link…tell me SPECIFICALLY why you think the system is good or not so good…and tell me how you would improve on what they have…

   And I know your next question…how long does this assignment have to be?…well, I am not really into counting words…but just to give you some perspective, I would say that by the time you are done, you should have a least one full page and maybe two full pages…if you wrote half a page, you probably wrote too little…if you wrote 5 full pages, you wrote too much…as I always tell my classes – just write!…and before you know it, you will have 1 to 2 pages…

CPSC-131 Project 3: 

Document Index 

This project is different from the previous two, where you were given skeleton classes with member functions to complete. Its goal is for you to become familiar with the use of the binary search tree by using the Standard Library (SL) implementation of this container: the STL map. It requires you to use existing SL classes to solve a problem, not to fill in the members of those classes as previous projects have done. The project files provide one class, DocumentIndex, with member functions that you must complete. 

Application

The project requires the design and implementation of an application program that creates a page index for a text document. The index must have one line for each word in the document, with a list of page numbers following the word in that line. Here is a sample: 

Class 12, 34, 56

Warning 

Be very careful about the format of the lines in your output file.

Your index file will be checked by a program that expects the format of the file’s lines to conform to the example shown—a single word, a space, a set of numbers separated by a comma and a space. 

A nonconforming format will cause a test to fail.

Document pages are separated by two successive empty lines, created by pressing Return twice after the Return that ends a paragraph. Here is an illustration:

Last line of a page

First line of next page 

Words are separated by spaces, tabs, and punctuation, which may be: 

period (.) 

comma (,)

colon (:)

semicolon (;)

question mark (?)

exclamation point (!) 

The punctuation should not appear in the index.

Words can end with a possessive—an apostrophe followed by an s. The index must contain the word without the ‘s. 

Word that contain digits or symbols other those mentioned above must not appear in the index. 

Words can begin with opening double or single quotation marks, or parentheses; they can end

with the corresponding closing character. These marks may enclose a string of words, not just a single word. You do not have to check for matching pairs; you only have strip them off like other punctuation. The marks should not appear in the index. Enclosed words, after the marks are stripped, are subject to the other constraints. For example, the word “Room-131” is not a legal word because of the hyphen and the digits. 

If a word appears more than once on a page, the page number must appear only once in the index. 

Words in the exclusion file must not appear in the index.

Words that appear more than ten times in the document must not appear in the index.

The words in the index must appear in sorted order and the page numbers for each word must appear in sorted order.

Classes and Functions 

The document index program must have a DocumentFile class and a documentIndex class with the indicated functions: 

DocumentFile 

• Close: Close the document file after it’s been used. This function’s code will be provided to you. 

• GetWord: Return the next legal word from the document file, stripping out the allowable punctuation and skipping over the illegal words (those with disallowed characters). 

• GetPageNumber: Return the current page number.

• LoadExclusions: Load the word exclusion list from a file, given the file’s name.

• Open: Open the document file, given its name. This function’s code will be provided to you.

• Read: Read the next line of the document file; update the page number if appropriate. 

DocumentIndex 

• Create: Create the index from the document file. 

• Write: Write the index to a file.

This list is a summary; the documentindex.h file contains a complete declaration of the classes and the documentindex.cpp file contains definitions of the functions—some skeletons for you to complete and some provided for you to use without having to change them. 

Implementation

You are to use the Standard Library (SL) map class to hold index information. You may find it necessary to use other SL containers within the map’s data elements. 

Remember that the nodes of a tree, which is the structure that the SL map implements, are key/data pairs. The map’s insert function takes a key and an associated data element, which can be anything, including a class or structure. The structure can have anything as a member, including other SL containers. 

Resources 

Program Files 

These files will be posted on GitHub for you to download, use or modify, and submit:

• documentindex.h: contains declarations of the DocumentFile and DocumentIndex 

classes. You may add other declarations as needed for your implementation. Do not add definitions (code) to this file; definitions of functions belong in documentindex.cpp. 

• documentindex.cpp: contains skeletons for the required member functions, either

completely empty or partially filled in. You may add other functions, member and

nonmember, as needed for your implementation. 

• getline.cpp: contains the definition of a function that handles text lines with various combinations of line endings—carriage return/line feed. It accommodates the differences between platforms; different editors and word processors use different line endings. 

• getline.h: contains the declaration of the GetLine function.

• main.cpp: contains a set of test functions that will call DocumentIndex’s functions. Do not modify this file. Do not submit this file as part of your project; a controlled version will be used to test your submission. 

Test Files 

These files are used by main.cpp during testing. They will be posted on GitHub for you to download: 

• document.txt: contains a large multipage document to be used as input for the

CreateIndex function. 

• excessiveappearances.txt: contains a number of words, some repeated more than the ten allowed times, to be used as input for testing. 

• exclusions.txt: contains a list of words, one per file line, to be used as input for the

LoadExclusions function. 

• expectedindex.txt: contains a sample index file, created when the document.txt file is

used as input. Main.cpp compares it against the actualindex.txt file created during testing. 

• getword.txt: contains a small document that is simply a collection of legal words,

including some with legal punctuation and some with illegal characters such as numbers and symbols; it is used to test the GetWord function. 

• pagenumber.txt: contains a small document that is primarily a set of pages; it is used to test the “next page” detection function. 

All  of these test files are samples. Do not submit them; your final submission will be tested using different files. 

References 

These files, which describe SL classes of interest, will be posted for your use:

• map.pdf: a brief description of the relevant map functions—insert, find, erase—including how to insert a key/data pair.

• set.pdf: a brief description of the SL set’s relevant functions—insert and size. You may find this container interesting or useful.

A more extension description of the SL classes and their functions can be found at 

www.cplusplus.com.

The Vigenère cipher was thought to be completely unbreakable for hundreds of years, and indeed, if very long keys are used the Vigenère cipher can be unbreakable. But if short keys are used, or if we have a lot of ciphertext compared to the key length, the vigenere cipher is quite solvable. 

In this  you need to study how a cryptanalyst thinks and breaks the code. Applying the Cipher Text Only attack, your job is to break the Vigenère cipher using cryptanalytic techniques and find the key used for the encryption. For this exercise, assume the key length is less than five characters long and only English upper case letters from A-Z are used. You may also assume the plaintext contains only the upper case English letters from A-Z, ignore the space characters. 

• List the security advantages of cloud-based solutions.
• List the security disadvantages of cloud-based solutions.
• Define and discuss the data wiping process.
• Discuss how a cloud-based solution provider may reduce the risk of a DDoS attack.

 Use only 70-words max per topic to discuss and present your answer.   

 References: (Chapter 9)
Erl, T., Mahmood, Z., & Puttini, R. (2014). Cloud computing: concepts, technology, & architecture. Upper Saddle River, NJ: Prentice Hall.
Jamsa, K. A. (2013). Cloud computing: SaaS, PaaS, IaaS, virtualization, business models, mobile, security and more. Burlington, MA: Jones & Bartlett Learning