Select one of the personality disorders or substance abuse disorders.

 

•             Paranoid

 

•             Histrionic

 

•             Antisocial

 

•             Borderline

 

•             Alcohol dependence

 

•             Drug abuse

 

Prepare a 1,050- to 1,500-word paper that discusses research-based interventions to treat psychopathology.

 

Review and differentiate the characteristics of the selected disorder and discuss the research about intervention strategies for the disorder by completing the following:

 

•Evaluate three peer reviewed research studies using the University of Phoenix Material: Research Analysis.

 

•Conceptualize the disorder using the biopsychosocial or diathesis-stress models.

 

•Discuss the treatments or interventions that have been shown to be the most effective for your selected disorder. Why?

 

Cite at least five peer-reviewed sources.

 

Format your paper consistent with APA guidelines.

 

You are the new HR Director of Ayles Networks, an established IT networking company. The company currently employs over 3,000 people across the Southwestern United States. The HR office is centrally located, but is as much as 500 miles from several of the corporate offices. Some of your primary duties include recruiting, training, and performance management. The CEO has asked you to use HR statistical techniques to assess the staffing, training, and HR assessments that the company currently has in place.

Write a paper of no more than 1,050 words discussing each of the statistical techniques that follow. Determine what type of data you would need; how you would use the techniques to assess the effectiveness of the staffing, training, and HR assessments; and provide a brief example of an application of each technique: t-test, ANOVA, and regression analysis. What other statistical methods might you use to analyze the effectiveness of your training and staffing programs?

 

·      Include at least one peer review reference

Objective

The Milestone Assignments are based on the Projects and Cases for use with the Systems Analysis and Design Methods textbook by Whitten & Bentley.  

There are six (6) parts to the Project, consisting of twelve (12) milestones. During Weeks 2-7, you will be required to complete two (2) milestones. Each milestone is worth 40 points. Milestones 5 and 10 are included as already completed work, so you only need submit them as part of the assignment.

 

Guidelines

Be sure to read the Project area of each Assignment section, as they talk directly to the milestone tasks. Also, for review purposes, note that typical milestone solutions will be posted on Wednesday morning of the following week. This is necessary as it is important for you to observe your errors as you further build on your cases. Note: Once milestone solutions are posted, no late work can be accepted.

Client Technology Tracking System – Case Introduction

The milestones will be graded based on how well they convey the needed information, use of tools and techniques for the section involved, and timeliness of submission.

Note: Please upload your completed assignments to the Dropbox as directed. Please be sure to submit BOTH milestone assignments to the Dropbox using ONE Word document. (Also, please paste created diagrams and illustrations from other software—like Visio—into this document. 

	Basic Tasks in Visio 2010   Visio 2010 Training

Part 1 of 6: Milestones 1 & 2 (80 pts.) – Due Week 2

 

Be sure to read the Project area of each Assignment section, as they talk directly to the milestone tasks. Also, for review purposes, note that typical milestone solutions will be posted on Wednesday morning of the following week. This is necessary as it is important.

Deliverables:

• Request for System Services form
• Problem Statement Matrix
• Context Diagram
• Problems, Opportunities, Objectives, and Constraints Matrix
• Tentative List of Functional and Non-Functional Requirements

Review all of the Milestone project steps below. Post questions in the CTTS Milestone discussion area.

Milestone 1

The purpose of the preliminary investigation phase is threefold. First, it answers the question, “Is this project worth looking at?” To answer this question, this phase must define the scope of the project and the perceived problems, opportunities, and directives that triggered the project.

In this milestone, you will prepare a Request for System Services, which is the trigger for the preliminary investigation phase. Also, you will use fact-finding techniques to extract and analyze information from an interview to determine project scope, level of management commitment, and project feasibility for the Client Technology Tracking System (CTTS). With these facts and facts obtained from the Case Background, you will have the necessary information to complete the Problem Statement Matrix.

Milestone 1 Instructions

For this milestone, you will be using the following templates/resources:

• Click here for Template A 
• Click here for Template B 

Note: Please be sure to submit BOTH milestone assignments to the Dropbox using ONE Word document. (You may paste created diagrams and illustrations from other software as needed.)

 

Milestone 2

 

There’s an old saying that suggests, “Don’t try to fix it unless you understand it.” With those words of wisdom, the next milestone of our project is to study and analyze the existing system. There is always an existing business system, regardless of whether it currently uses a computer. The problem analysis phase provides the project team with a more thorough understanding of the problems, opportunities, and/or directives that triggered the project. Indeed, the analyst frequently uncovers new problems and opportunities. The problem analysis phase may answer the questions, “Are the problems worth solving?” and â€œIs a new system worth building?”

 

The purpose of the problem analysis phase is threefold. First and foremost, the project team must gain an appropriate understanding of the business problem domain. Second, we need to answer the question, â€œAre these problems (opportunities and directives) worth solving?” Finally, we need to determine if the system is worth developing. The problem analysis phase provides the systems analyst and project team with a more thorough understanding of the problems, opportunities, and/or directives that triggered the project. In the process, they frequently uncover new problems and opportunities.

 

In this milestone you will perform a cause-effect analysis on the Client Technology Tracking System (CTTS) and document your findings using the Problems, Opportunities, Objectives, and Constraints Matrix. The PIECES framework, originally developed by James Wetherbe and then adapted by the authors, can serve as a useful tool to classify the various problems, opportunities, and directives identified in Milestone 1.

Milestone 2 Instructions 

For this milestone, you will be using the following templates/resources:

• Click here for Template C 

Note: Please be sure to submit BOTH milestone assignments to the Dropbox using ONE Word document. (You may paste created diagrams and illustrations from other software as needed.)

Part 2 of 6: Milestones 3 & 4 (80 pts.) – Due Week 3

Be sure to read the Project area of each Assignment section, as they talk directly to the milestone tasks. Also, for review purposes, note that typical milestone solutions will be posted on Wednesday morning of the following week. This is necessary as it is important.

Deliverables:

• Use-Case Glossary
• Use-Case Model Diagram
• Use-Case Narrative
• Entity Definition Matrix
• Context Data Model
• Key-Based Data Model
• Fully Attributed Data Model

Review all of the milestone project steps below. Post questions in the Milestone Virtual Lab Forum discussion area.

Milestone 3

Use-case modeling has gained popularity as a technique for expressing system requirements for two reasons: (1) it facilitates user-centered development, which often leads to building systems that better satisfy user needs, and (2) use cases diagrams and narratives are easy for users to understand.

In this milestone, you will first uncover the actors, use cases, and relationships that define the requirements for the proposed system and document that information in a Use-Case Glossary. You will use that to build a Use-Case Model Diagram for the system and a Use-Case Narrative for one use case.

Milestone 3 Instructions 

For this milestone, you will be using the following templates/resources:

• Use-Case Glossary – create in Word or Excel
• Use-Case Narrative
  
  

 

Milestone 4

 

The requirements analysis phase answers the question, “What does the user need and want from a new system?” The requirements analysis phase is critical to the success of any new information system! In this milestone, we need to identify what information systems requirements need to be defined from the system users’ perspectives and draw graphical, logical models to document the data requirements for a new and improved system.

 

Data modeling is a technique for organizing and documenting a system’s data. Data modeling is sometimes called database modeling because a data model is usually implemented as a database. Data is viewed as a resource to be shared by as many processes as possible. As a result, data must be organized in a way that is flexible and adaptable to unanticipated business requirements—and that is the purpose of data modeling.

 

In this milestone, you will first discover those entities in the system that are or might be described by data. Then we will define each entity we identify in respect to the business. Then we will construct a Context Data Model that graphically depicts each of the entities and their relationships with each other. Next, we will refine the context data model to include primary and foreign keys. The resulting model is called a Key-Based Data Model. Finally, we refine the key-based data model to include any hierarchies and attributes, and this model is referred to as the Fully Attributed Data Model.

Milestone 4 Instructions

For this milestone, you will be using the following templates/resources:

• Entity Definition Matrix – create using Word or Excel (see Table 8-5)
• Context Data Model – create using Visio or other drawing tool
• Key-Based Data Model – create using Visio or other drawing tool
• Fully Attributed Data Model – create using Visio or other drawing tool

Note: Please be sure to submit BOTH milestone assignments to the Dropbox using ONE Word document. (You may paste created diagrams and illustrations from other software as needed.)

 

At this point, you want to put together the work that has been completed to deliver a working program for alpha testing. You will combine the elements you have written to this point and deliver a working solution. You will read the contributor information from a file similar to this table below; it is a comma delimited (CSV) file.

Jeff	Sherman	USA	9035551212	100	50
John	Dallas	USA	9035552121	200	51
Bob	Atlanta	USA	9035551111	300	52
Bill	Chicago	USA	9035553333	400	53
Sam	Phoenix	USA	9035557777	500	54

• First Name in first column
• Last Name in second column
• Country in third column
• Phone # in fourth column
• Donation amount in fifth column
• Contributor ID in sixth column

As each record is read, create a sorted Linked list of the contributors using the Insertion sort method. You also need to maintain your table, with one modification. You need to add an object to the Hash Collision Object that is a pointer to the data in the Linked list. In addition, you need to implement Contributor search functionality based on a Contributor Name. Your design should include the following:

High Level Implementation Instructions:

• Sorted Linked list
• Sorted using Insertion sort
• Hash bucket of size 5 with a collision solution using a linked list (no need to order)
• A Search Algorithm based on ID and Contributor Name.
  • The Contributor Name Algorithm needs to be implemented using the Sequential Search

Each contributor will have the following information:

• Name: String; //the name of the contributor
• City: String; //the city in which the contributor lives
• Country: String; //the country in which the contributor lives
• Phone: String; //the phone number for the contributor
• Contribution: Double; //the amount of the contribution given by the contributor to the zoo
• ID: Integer; //identifier key for future needs

Contributor functions/methods:

• Input constructor: //to accept a string for the name and additional information for each contributor (this should call the Add constructor to implement the sorted list)
• Print constructor: //to print out the contributor data
• Print All constructor: //to print the entire list of contributor names
• Add constructor: //to traverse the Linked list and find the proper location for adding the instance
• Search constructor: //the Search algorithm to implement is Sequential Search

Each hash bucket collision item will have the following information:

• ID: Integer; //identifier key for future needs
• Contributor Address: Pointer; //a pointer to the address of the contributor instance in the sorted linked list

Hash bucket functions/methods:

• Input constructor: //to accept a string for the name and additional information for each contributor (you will only need the ID portion of the input data)
• Hash Function constructor: //Hint: You only have 5 Hash buckets so the function can be very a simple calculation
• Pop constructor
• Push constructor
• Print constructor: //to show the information of the contributor based on a given ID

Deliverables:

• The design saved in a Key Assignment Draft that does not include any actual code and will be submitted as the deliverable in the next discussion board.
• A fully documented program to load the data creating a sorted linked list.
• A test plan to show how the program runs and can be executed.
• A screenshot showing that the program loaded the data, and after all data is loaded perform the following:  
  • Print All showing the sorted list.
  • Contributor information for Georg Pipps
  • Contributor information for ID 25