Using the internet for recruiting, training, and target selection

How is the Internet used for recruiting, training, and target selection? In answering the question, provide examples of each.
What, according to the text, is the essence of the drama pattern? List and explain the different type of TV drama patterns.
Explain the tension between the media and the government, police and security forces. Provide an example.

Sample Solution

Software Development Life Cycle (SDLC).

Writing Instructions:

  1. Write an explanation essay from the following text.
  2. Use simple English language.
  3. Use plain English.
  4. Use simple sentence structures.
  5. Use simple grammar.
  6. Use simple vocabulary.
  7. The essay must be cohesive (hint: use conjunctions).
  8. The sequences of sentences should be followed.
  9. The writer should understand the text before re-writing the sentences.

Requirements Engineering (RE):

  1. RE is the first phase in the Software Development Life Cycle (SDLC).
  2. RE is the process of understanding and defining what services are required from the system and identifying the constraints on the system’s operation and development.
  3. There are three main activities in the RE process: (1) Requirements elicitation and analysis, (2) Requirements specification, and (3) Requirements validation.

3.1 Requirements elicitation and analysis:

3.1.1 There are three sub-activities in the requirements elicitation and analysis: (1) Requirements discovery and understanding, (2) Requirements classification and organization, (3) Requirements prioritization and negotiation, and (4) Requirements documentation.
3.1.2 The aims of the requirements elicitation and analysis process are to understand the work that stakeholders do and how they might use a new system to help support that work. During requirements elicitation and analysis, software engineers work with stakeholders to find out about the application domain, work activities, the services and system features that stakeholders want, the required performance of the system, hardware constraints, and so on.
3.1.3 Requirements elicitation and analysis involves meeting and interacting with stakeholders of different kinds to discover information about the proposed system. It can be done using some techniques like interviews, questionnaires, observations, etc.

3.2 Requirements specification:

3.2.1 It is the process of writing down the user and system requirements in a requirements document. Ideally, the user and system requirements should be clear, unambiguous, easy to understand, complete, and consistent.
3.2.2 User requirements are almost always written in natural language supplemented by appropriate diagrams and tables in the requirements document.
3.2.3 System requirements may also be written in natural language, but other notations based on forms, graphical, or mathematical system models can also be used.

3.3 Requirements validation:

3.3.1 It is the process of checking that requirements define the system that the customer really wants. It overlaps with elicitation and analysis, as it is concerned with finding problems with the requirements.

  1. In practice, RE is an iterative process in which the activities are interleaved.
  2. The output of the RE process is a system requirements document.
  3. RE is a particularly critical phase of the SDLC, as mistakes made at this phase inevitably lead to later problems in the system design and implementation. RE is critically important because errors in a requirements document can lead to extensive rework costs when these problems are discovered during development or after the system is in service.
  4. Natural Language (NL):

7.1 Natural language is often used to write system requirements specifications as well as user requirements. However, because system requirements are more detailed than user requirements, natural language specifications can be confusing and hard to understand.

7.2 There are three main problems that often arise when requirements are written in NL sentences:
7.2.1 Lack of clarity:
-It is sometimes difficult to use language in a precise and unambiguous way without making the document wordy and difficult to read.
7.2.2 Requirements confusion:

  • Functional requirements, non-functional requirements, system goals and design information may not be clearly distinguished.
    7.2.3 Requirements amalgamation:
  • Several different requirements may be expressed together as a single requirement.

7.3 Because of these problems, requirements specifications written in natural language are prone to misunderstandings. These are often not discovered until later phases of the software process and may then be very expensive to resolve.

Sample Solution

IT management and systems

Part 2: Identify Vulnerabilities in IT Security

Overall Scenario
Aim Higher College is a fictitious institution located in the United States. The college offers undergraduate and graduate courses in domains, such as business management, information security, and nursing. Imagine that you have a new job at Aim Higher College as an information security analyst. Throughout this course, you will analyze the threats and vulnerabilities of Aim Higher College and recommend controls to secure the college’s information systems.

Aim Higher College has been the target of focused attacks from a variety of attackers. Your manager has assigned you the task to review the port and vulnerability scan data recently gathered from a typical system to determine what ports and services are exposed to attackers, and what vulnerabilities exist on that system.

Required Resources
 Access to the Internet
 Text sheet: Zenmap Intense Scan Results pdf file (hacking_ts_zenmapscan.pdf Download hacking_ts_zenmapscan.pdf)


  1. Analyze the results of the Zenmap scan. Your report must answer the following questions:
     What are the first five open ports as identified by the Zenmap scan?
     Include the port number
     Include the service name
     Include a brief description of how each is used
  2. The Nessus scan identified two critical vulnerabilities, identified as ID 32314 and ID 33850.
     Research the vulnerabilities against the Common Vulnerabilities and Exposure (CVE) database .
     Include the name and a brief description of each vulnerability.
  3. Determine what can be done to protect the system and defend the campus network against attempts to gather data, and to resolve vulnerabilities. Also determine which ports and services likely need to remain open.
  4. Write a report targeted at IT management and systems administration staff explaining the vulnerabilities and protection mechanisms that Aim Higher College should adopt, which will be applied to all similar systems at the college.

Sample Solution