What it Means to be Career Ready: Data Analyst Position

Career Ready Project All Parts including your presentation must be completed by your presentation date Upload Completed RDS - Requirement Definition Statement l
This project carries the weight of a test. Your score will be averaged into your test grade
You will create a Requirements Definition Statement (RDS) - This is worth 40% of the project grade
Your final project will be to create a Requirements Definition Statement together with all supporting documentation. Your topic is about being career ready. Remember the RDS is the final document in Analysis. Remember analysis asks the question what must the system do. Another way to say the same thing what must be achieved by the system. The RDS does not tell us how we are going to do something. That is the province of Design which answers those questions. Make certain every part of your document achieves this goal.
You Need to Research What it Means to Be Career Ready
For this project you are expected to do your own research on what it means to be career ready. I will be grading you in part for how you define the concept and assess the factors necessary to be career ready. To help you I am providing the following resources to get you started.
To learn more about being career ready look here Link (Links to an external site.)
What Employers Think of Student's Career Readiness Link (Links to an external site.)
Are Grads Prepared for Work? Link (Links to an external site.)
You should have at least 5 other sources in your resource list in your final deliverable
Template to use for Your RDS
A template of a RDS is contained here : Semester Requirments Definition Template-2.doc Download Semester Requirments Definition Template-2.doc
This is a rough guide to use. I give you leeway to change elements with my consent
Deliverables
The task is to get a job upon graduation. You will determine all of the requirements that must be met in order to successfully get that elusive job. This will not only include the job you want but what you must do to get that job. Today that is called being Career Ready. I will be looking for the following things in your project
You will create a Requirements Definition Statement together with the supporting documentation. This is uploaded here.
In a separate document you will assess your Career Readiness and create a plan of action. This is uploaded later in this module.
You will meet with me at your scheduled times during the project
You will prepare an Assessment of Your Career Readiness as well as a Plan of Action. This is uploaded later in this module
You will schedule a presentation and make an oral presentation before the due date
Your submission should look professionally done.
This document will contain a title page and an index. If you do not know how to do this, consult either myself or Maurice on how to do this
In the RDS you will have a properly defined scope statement
The statement should in detail spell out the job you want, the expected pay, the location in the US you want to work and other pertinent facts about the job you seek
You will research what it means to be career ready. You should have at a minimum 5 new articles on this topic different from the articles I am providing you in this and the linked units to this assignment.
You will research what knowledge , skills and abilities you need for the job you have chosen.
You will list as a section in your RDS how you obtained your information and what information you obtained.
You will list all of the Functional and Information Requirements you must achieve in order to get that job
While this should include your graduation with a degree, it should include the type of courses you need, certificates you should get, the grades you must achieve as well as the skills you need to develop outside the classroom.
You will demonstrate your ability to use the following requirements gathering techniques
Interviews (4 required) I suggest one is with Career Services
You should submit a copy of the questions asked and a summary or transcript of your interviews
Only one interview can be with a student. Your interviews should be with people who can help you with the deliverable of this project. They should be able to help you answer the questions like what is Career ready or what should I do to become career ready or what do you look for in hires
Questionnaire completed (This does not have to be submitted to anyone but it should relate to what you would ask to someone about the things a student would have to do to get a job upon graduation)
You will benchmark yourself to what other students similar to you are doing and use that to set your goals
You should have at least 3 benchmarks subjects
You should include the documentation that shows the subject and your analysis of the information including your conclusion
Flow Chart of the process you must follow to get a job
Gannt Chart of the process you will take to get a job
Interaction Diagram of how you prepare your self to be career ready
Use Case on the functionality Handshake (The tool in Career Services)
You should consider doing a series of these use cases on this topic starting with the overview and drilling down
You will Prepare an Assessment of Your Career Readiness as well as a Plan of Action - This is worth 40% of your project grade
As a separate document you will prepare an assessment of your career readiness. You will also prepare a plan of action which details what activities you must do to develop your self into a career ready individual. This activity is much like what is done in the design phase of a project where you detail how you will be making yourself career ready from where you are at this time.
Project Name: Requirements Document
To use this template:
1. Replace any red italicized text with your own text. You may remove or add sections as needed for your particular projects.
2. Enter the project name in the title and footer (and change the document version number, if necessary).
3. If your document is very long, break each numbered chapter into its own document section, beginning it on a new page. This will make it easier to replace/updagte
4. Delete these instructions and any other italicized instructions.
Project:
Date(s):
Prepaed by:
Document status: __ Draft __ Proposed __ Validated __ Approved
1. Introduction
This document contains the system requirements for project name. These requirements have been derived from several sources, including brief listing of most important sources.
1.1 Executive Summary
Place the executive summary here
1.2 Purpose of the Project
1.3 Scope of the Project
Include a brief narrative here which describes the product as you intend it to be realized. Use this section to define boundaries and set expectations.
1.4 Business Case for the Project
Why is this product required? How will it contribute to the goals of your institution? This section can be used when requirements are being negotiated, to assess whether a particular change is a good idea. This section also helps readers understand why certain requirements have been included.
1.5 Methodology Used
Explain here how you came up with your findings including the methodology you used to find your requirements.
2. Project Overview
This section will give the reader an overview of the project, including why it was conceived, what it will do when complete, and the types of people we expect will use it. We also list constraints that were faced during development and assumptions we made about how we would proceed.
This section contains a nontechnical description of the project, usually in narrative form, which may serve to acquaint new readers with the purpose of the project. It also sets the stage for the specific requirement listing which follows.
Why have you chosen to develop this product? What need does it serve? Who are the primary stakeholders, who is developing the project, and who will benefit from the finished product?
2.3 User Characteristics
Who do you expect to use your finished product, and why? What is their technical background, their training or education, their motivation to use it? What obstacles might they encounter, and what specialized skills will they need?
2.4 General Constraints
Did you work under any constraints such as platform or development environment? Did you have to make your product compatible with any existing software or other products currently in use?
2.5 Assumptions and Dependencies
In this section, list any assumptions you made about your project (for example, did you assume that the finished product would need to be delivered over the internet?). If your project depends on any particular technical infrastructure, or requires administrators or others with specific skills, note that here.
3. Requirements
This section of the document lists specific requirements for name of project. Requirements are divided into the following sections:
1. Functional requirements. These are requirements written from the point of view of end users, usually expressed in narrative form.
2. Nonfunctional requirements. These are detailed specifications describing the functions the system must be capable of doing.
3. Information requirements. These are requirements about the user interface, which may be expressed as a list, as a narrative, or as images of screen mock-ups.
3.1 Functional Requirements
List detailed functional requirements here.
3.2 Nonfunctional Requirements
List detailed nonfunctional requirements here.
3.3 Information Requirements
List information requirements here;
4. Appendices
If you wish to append any documents, do so here. You may wish to include some or all of the following:
• Personas and scenarios developed for this project
• Flow charts, Gannt Chart, Interaction diagrams
• Transcripts of user interviews, observations, or focus groups
• Copies of communications which contain user requirements
• Original project proposals or other historical documents
• Lists of similar projects or products, with notes about how they differ from yours
• A list of requirements which were "wish-listed" or marked unfeasible at present
• Original screen mockups, if they are relevant
5. Glossary
Inclue a glossary of definitions, acronyms, and abbreviations that might be unfamiliar to some readers, especially technical terms that may not be understood by end-users or domain-specific terms that might not be familiar to developers
6. References
List references and source documents, if any, in this section
7. Index
If your document is very large, consider compiling an index to help readers find specific items.
Project Name: Requirements Document (version 1.0)​1
In the modules that follow you will upload the various parts of the project to include
Resources To Help You With Your Writeup of your RDS
Purpose Statements
Purpose statements are very important not just in business but in life. Scary fact: Only 25% of Americans have a clear set of purpose
Purpose is the reason why we are doing something. It is our goal and objective, It answers the question what is it that I am trying to accomplish.
We need to state our purpose for a number of reason
Purpose can and should directs our action. Action without purpose leads to unsuccessful conclusions and results
A purpose connects us with others who have the same purpose
Purpose allows us to build a community with others who share the same passions, interest and values. This makes it easier to accomplish our purposes.
Purposes motivate us to action
Purpose keeps us going when we encounter setbacks
How to Write a Purpose Statement with example >>>>> Writing Effective Purpose Statements.docxDownload Writing Effective Purpose Statements.docx
Please also review the material in Module 3 on the topic of Purpose
Scope Statements
Writing Effective Purpose Statements1
A purpose statement is a declarative sentence which summarizes the specific topic and goals of a document. It is typically included in the introduction to give the reader an accurate, concrete understanding what the document will cover and what he/she can gain from reading it. To be effective, a statement of purpose should be:
 Specific and precise - not general, broad or obscure
Concise - one or two sentences
 Clear - not vague, ambiguous or confusing
 Goal-oriented - stated in terms of desired outcomes
Some common introductory phrases for purpose statements include:
 "The purpose of this paper/letter/document is to..."
 "Inthis paper, I will describe/explain/review/etc. the..."
 "My reason for writing is to..."
 "This paper will discuss the..."
 "The purpose of this paper is twofold: to ___ and ___"
Examples of Ineffective Purpose Statements:
(1) "The purpose of this paper is to describe the changes that are occurring in corporate America."
Critique: too vague and broad. No clear expectation of what the reader will learn. Questions: What specific changes in corporate America will be described? What types of changes? What aspects of corporate America will be discussed? Will this paper also discuss the effects of these changes?
(2) "The purpose of this report is to discuss the eating disorders Anorexia and Bulimia."
Critique: too vague and broad. It is not clear what aspect of these disorders will be discussed, or what the reader will learn. Questions: What specific aspects of these eating disorders will be discussed? The causes of these disorders? The signs or symptoms of these disorders? The effects of these disorders? If so, what types of effects - physical, emotional, psychological?
Writing Effective Purpose Statements
A purpose statement is a declarative sentence which summarizes the specific topic and goals of a document. It is typically included in the introduction to give the reader an accurate, concrete understanding what the document will cover and what he/she can gain from reading it. To be effective, a statement of purpose should be:
Specific and precise - not general, broad or obscure
Concise - one or two sentences
Clear - not vague, ambiguous or confusing
Goal-oriented - stated in terms of desired outcomes
Some common introductory phrases for purpose statements include:
"The purpose of this paper/letter/document is to..."
"In this paper, I will describe/explain/review/etc. the..."
"My reason for writing is to..."
"This paper will discuss the..."
"The purpose of this paper is twofold: to ___ and ___"