Solved by verified expert:Stage 3 Paper about Functional and Non functional requirements in a Case Study. I have attached the functional and non functional requirements that will be needed for this paper.
stage_3___business_analysis_and_systems_recommendation.docx
functional_and_non_functional_requirements.docx
Unformatted Attachment Preview
Stage 3: Requirements
Before you begin work on this assignment, be sure you have read the Case Study and reviewed the
feedback received on your Stage 2 assignment.
Overview
As the business analyst in the CIO’s department of Chesapeake IT Consulting (CIC), your next task in
developing your Business Analysis and System Recommendation (BA&SR) Report is to develop a set of
requirements for the hiring system.
Assignment – BA&SR Section III – Requirements
The first step is to incorporate the feedback you received on your Stage 2 assignment, making any
needed corrections or adjustments. (If you have not incorporated the feedback from your Stage 1
assignment, you should do so prior to submitting Stage 3.) Part of the grading criteria for Stage 4
submission includes addressing previous feedback to improve the final report. For this assignment, you
will add Section III of the Business Analysis and System Recommendation (BA&SR) Report by identifying
requirements for the new hiring system. This analysis leads into Section IV – System Recommendation of
the BA&SR (Stage 4 assignment) that will analyze a proposed IT solution to ensure it meets CIC’s
organizational strategy and fulfill its operational needs.
Using the case study, assignment instructions, Course Content readings, and external resources, develop
your Section III: Requirements. The case study tells you that the executives and employees at
Chesapeake IT Consultants (CIC) have identified a need for an effective and efficient hiring system. As
you review the case study, use the assignment instructions to take notes to assist in your analysis. In
particular, look for information in the interviews to provide stakeholder interests and needs.
Use the outline format, headings and tables provided and follow all formatting instructions below.
III.
Requirements
A.
Stakeholder Interests – Identify the interest or objectives for the new hiring system for
each stakeholder listed below based on his or her organizational role and case study
information. Include how the technology will improve how his/her job is done; that is, identify
what each of the stakeholders needs the system to do. Use information from the stakeholder
interviews and describe what they need, what challenges they have related to the hiring process
and how a system could address their requirements; do not define what that position does.
(Provide an introductory sentence for this section, copy the table below and complete the two
columns with 1-2 complete sentences for each role in each column.)
Role
i.
ii.
iii.
Specific challenge related to
the hiring process
How a technology
solution to support the
hiring process could
address the challenge
CEO
CFO
CIO
Stage 3: Requirements 11/9/2017 v.3
1
iv. Director of Human Resources
v. Manager of Recruiting
vi. Recruiters
vii. Administrative Assistant
viii. Hiring Manager (Functional
supervisor the new employee
would be working for.)
B.
Defining Requirements – The next step is to identify the essential requirements for the
information system. In addition to the stakeholder interests identified above, review the Case
Study, especially the interviews, highlighting any statements that tell what the person expects
the system to do. Functional requirements express specifically what the user needs the system
to do. This can be in terms of tasks the users need to perform, data they need to input, what
the system might do with that data input, and output required. Non-Functional requirements
express how the system will perform in several performance areas and security. As a member
of the CIO’s organization, you will use your professional knowledge to Identify 5 Functional
Requirements (including one specifically related to reporting) and 5 Non-Functional
Requirements (including 2 security-related requirements). Refer to Week 6 content on
requirements; security requirements are covered in Chapter 6 of the textbook. Additional
research can expand your knowledge of these areas.
Once you have written down the 10 requirements, evaluate each one using the criteria below
and create 10 well-written requirements for the new hiring system.
The requirement statement:
• Is a complete sentence, with a subject (system) and predicate (intended result, action or
condition)
• Identifies only one requirement; does not include the words “and,” “also,” “with,” and “or.”
• For Functional Requirements, states what tasks the system will support or perform
• For Non-Functional Requirements, states how the system will perform.
• Includes a measure or metric that can be used to determine whether the requirement is
met (time or quantity), where appropriate
• Is stated in positive terms and uses “shall” (not “may” or “should”); “the system shall xxxx”
not “the system shall not xxx”
• Avoids the use of terms that cannot be defined and measured, such as “approximately,”
“robust,” “user friendly,” etc.
• Is achievable; avoids terms such as “100% uptime,” or “no failures”
For a full requirement specification, there will be many requirements statements; you only need
to provide the number of requirements identified for each category. Do not provide generic
statements but relate to the needs of CIC to improve its hiring process.
(Provide an introductory sentence and copy the table and insert information within.)
Stage 3: Requirements 11/9/2017 v.3
2
Requirement ID
Requirement Statement
Stakeholder
(Name/Position from Case
Study that identified this
requirement)
Functional
Requirements
Example
1.
2.
3.
4.
5. (Reporting)
Non-Functional
Requirements
Example
The system shall store all information from the
candidate’s application/resume. In a central
applicant database.
The system shall be implemented as a
Software as a Service solution.
Recruiter – Paul O’Brien
CIO – Fadil Abadi
1.
2.
3.
4. (Security)
5. (Security)
Formatting Your Assignment
Consider your audience – you are writing in the role of a CIC business analyst and your audience is CIC
and your boss, the CIO. Don’t discuss CIC as if the reader has no knowledge of the organization. Use
third person consistently throughout the report. In third person, the writer avoids the pronouns I, we,
my, and ours. The third person is used to make the writing more objective by taking the individual, the
“self,” out of the writing. This method is very helpful for effective business writing, a form in which facts,
not opinion, drive the tone of the text. Writing in the third person allows the writer to come across as
unbiased and thus more informed.
•
•
•
•
•
•
•
In Stage 3, you are preparing the third part of a 4-stage report. Use the structure, headings, and
outline format provided here for your report.
Begin with Sections I and II, revised according to any feedback received and add to it Section III.
Write a short concise paper: Use the recommendations provided in each area for length of
response. It’s important to value quality over quantity. Section III should not exceed 4 pages.
Content areas should be double spaced; table entries should be single-spaced.
To copy a table: Move your cursor to the table, then click on the small box that appears at the
upper left corner of the table to highlight the table; right click and COPY the table; put the cursor in
your paper where you want the table and right click and PASTE the table.
Ensure that each of the tables is preceded by an introductory sentence that explains what is
contained in the table, so the reader understands why the table has been included.
Continue to use the title page created in Stage 1 that includes: The company name, title of report,
your name, Course and Section # and date of this submission.
Stage 3: Requirements 11/9/2017 v.3
3
•
•
•
•
•
•
Use at least two resources with APA formatted citation and reference for this Stage 3 assignment.
Use at least one external reference and one from the course content. Course content should be
from the class reading content, not the assignment instructions or case study itself.
Add the references required for this assignment to the Reference Page. Additional research in the
next stage will be added to this as you build the report. The final document should contain all
references from all stages appropriately formatted and alphabetized.
Running headers are not required for this report.
Compare your work to the Grading Rubric below to be sure you have met content and quality
criteria.
Submit your paper as a Word document, or a document that can be read in Word. Keep tables in
Word format – do not paste in graphics.
Your submission should include your last name first in the filename: Lastname_firstname_Stage_3
GRADING RUBRIC:
Criteria
Stakeholder
Interests
Identification of
specific
stakeholder
interests and
objectives for
improving the
hiring process and
how a technology
system could
address.
Generally, 0-3
points per role.
Functional
Requirements
5 user
requirements (1
addresses
reporting)
Generally, 0-5
points each
90-100%
80-89%
70-79%
60-69%
< 60%
Far Above
Standards
22-24 Points
Above Standards
Meets Standards
Below Standards
20-21 Points
17-19 Points
15-16 Points
Well Below
Standards
0-14 Points
Challenges and
how a technology
solution will
address are
clearly described
and fully
explained using a
sophisticated
level of writing.
Challenges and how
a technology
solution will
address are clearly
described and
explained using an
effective level of
writing.
Challenges and
how a technology
solution will
address are
described and
explained.
Challenges and
how a technology
solution will
address are not
clearly described
and explained;
and/or lacks
effective
presentation of
information
Few or no
identification of
appropriate
challenges and
explanations of
how a technology
solution could
address are
provided.
23-25 Points
20-22 Points
17-19 Points
15-16 Points
0-14 Points
Correctly
identified and
sourced; clearly
derived from the
Case Study;
demonstrates
sophisticated
analysis.
Identified and
sourced;
requirements are
derived from the
Case Study;
demonstrates
effective analysis.
Stage 3: Requirements 11/9/2017 v.3
Identified and
sourced;
requirements are
related to the Case
Study.
Fewer than 5
requirements are
identified and
sourced; and/or
information
provided is not
correct; and/or
requirements are
not all related to
the Case Study.
Possible
Points
24
25
Few or no
requirements are
listed; sources
are incorrect;
and/or
requirements are
not related to the
Case Study.
4
Non-Functional
Requirements
3 system
performance
requirements and
2 system security
requirements
Generally, 0-5
points each
Research
Two or more
sources--one
source from
within the IFSM
300 course
content and one
external (other
than the course
materials)
Format
Uses outline
format provided;
includes Title
Page and
Reference Page
23-25 Points
Correctly
identified and
sourced; clearly
derived from the
Case Study;
demonstrates
sophisticated
analysis.
20-22 Points
Identified and
sourced;
requirements are
derived from the
Case Study;
demonstrates
effective analysis.
17-19 Points
Identified and
sourced;
requirements are
related to the Case
Study.
15-16 Points
Fewer than 5
requirements are
identified and
sourced; and/or
information
provided is not
correct; and/or
requirements are
not all related to
the Case Study.
0-14 Points
25
Few or no
requirements are
listed; sources
are incorrect;
and/or
requirements are
not related to the
Case Study.
9-10 Points
8.5 Points
7.5 Points
6.5 Points
0-5 Points
10
Required
resources are
incorporated and
used effectively.
Sources used are
relevant and
timely and
contribute
strongly to the
analysis.
References are
appropriately
incorporated and
cited using APA
style.
14-16 Points
At least two sources
are incorporated
and are relevant
and somewhat
support the
analysis. References
are appropriately
incorporated and
cited using APA
style.
Only one resource
is used and
properly
incorporated
and/or
reference(s) lack
correct APA style.
A source may be
used, but is not
properly
incorporated or
used, and/or is not
effective or
appropriate;
and/or does not
follow APA style
for references and
citations.
No course
content or
external research
incorporated; or
reference listed is
not cited within
the text.
12-13 Points
11 Points
10 Points
0-9 Points
Very well
organized and
easy to read.
Very few or no
errors in
sentence
structure,
grammar, and
spelling; doublespaced, written in
third person and
presented in a
professional
format. Any
references used
are appropriately
incorporated and
cited using APA
style.
Effective
organization; has
few errors in
sentence structure,
grammar, and
spelling; doublespaced, written in
third person and
presented in a
professional format.
Any references
used are
appropriately
incorporated and
cited using APA
style.
Some
organization; may
have some errors
in sentence
structure,
grammar and
spelling. Report is
double spaced and
written in third
person.
References may
not be
appropriately
incorporated and
cited using APA
style.
Not well
organized, and/or
contains several
grammar and/or
spelling errors;
and/or is not
double-spaced and
written in third
person.
References may
not be
appropriately
incorporated and
cited using APA
style.
Extremely poorly
written, has
many grammar
and/or spelling
errors, or does
not convey the
information.
16
TOTAL Points
Possible
Stage 3: Requirements 11/9/2017 v.3
100
5
Requirements – Answering the Question "What is the System Supposed to Do?"
The Basics
For purposes of this class, we will focus on what the end user needs or expects the system to do.
These needs and expectations are documented as requirements for the system. They fall into
two general categories:
1. Functional Requirements - that express what the user needs the system to do.
• They describe the tasks the users need to accomplish with the system
o What data the user will input
o What the system is expected to do with the data that is input
o What the system is expected to provide as output (reports, results, etc.)
Example functional requirements:
o
o
o
o
o
The system shall calculate the total of all items in the online or website shopping
cart.
The system shall display to the user similar items that the online shopper may be
interested in.
The system shall require the user to provide a shipping address.
The system shall automatically fill in the State portion of the shipping address based
on the zip code entered by the user.
The system shall provide the user with a report of all purchases made via the
website.
2. Non-Functional Requirements – that express how the system will perform.
• They describe how the system will perform in areas such as:
o Usability – Ability for new users to quickly adapt to the software, including how easy
the system is to use and how help is provided for the users
o Scalability – Ability of the system to accommodate additional users and/or
additional records/transactions
o Availability – Amount or periods of time the system is to be operational and useable
o Reliability – Ability of the system to create and maintain the data correctly
o Maintainability – Ability of the system to be easily maintained, corrected and
updated
o Portability – Ability of the system to run/operate on a variety of end-user devices or
with multiple operating systems
• Or, they describe security requirements for the system and data, such as:
o Protection of data as it is transmitted and when it is stored
o User authentication
o Authorization of user to perform specific functions
o Data backup and recovery
Example non-functional requirements:
o
o
o
o
o
The system shall encrypt the user's payment information when it is transmitted.
The system shall store the user's full name in the database.
The system shall require a retinal scan for login purposes.
The system shall be capable of handling 5,000,000 transactions per hour.
The system shall operate using Motorola hand-held scanners.
Writing the Requirements Statements
The requirement statement:
• Either states what the system will do as a functional requirement, or states how the
system will do it as a non-functional requirement (Never both together)
• Identifies only one requirement; avoid the words "and," "also," "with," and "or"
• Is a complete sentence, with a subject (usually "the system") and predicate
(intended result, action or condition)
• Uses "shall" (vs. "may" or "should")
• Is stated in positive terms; i.e., "the system shall xxxx" vs. "the system shall not xxx"
• Avoids the use of terms that cannot be defined and measured, such as
"approximately," "robust," "user friendly," etc.
• Is achievable; avoids terms such as "100% uptime," or "no failures"
• Is complete; it includes a measure or metric (time or quantity) where appropriate
• Must be testable; that is, there must be some way to test the system to determine
whether a requirement is met
• Generally is written as "The system shall ….."
Below are some examples of poorly written and well-written requirements, with an explanation of what
is wrong with the poorly written one.
Poorly Written Requirement
Users shall have access to their
personal data, which will be
transmitted in a secure manner.
What is Wrong
Two requirements – one
functional and one nonfunctional - are expressed; each
statement should express only 1
requirement.
The system shall calculate the
total of all items in the online or
website shopping cart and
display the total to the user.
Two requirements are
expressed; each statement
should express only 1
requirement.
Report shall be provided within
5 seconds of the user clicking on
"submit."
The system should require the
user to provide a shipping
address.
The system shall be easy to use.
Not a complete sentence; and
should be stated as "The system
shall….."
Avoid the use of "should"; use
"shall."
"Easy to use" is not measurable
or testable.
Well Written Requirement
1. The system shall provide a
user with access to their
personal data.
2. The system shall transmit
personal data in a secure
manner.
1. The system shall calculate the
total of all items in the online or
website shopping cart.
2. The system shall display the
total of all items in the online or
website shopping cart to the
user.
The system shall provide the
report within 5 seconds of the
user clicking on "submit."
The system shall require the
user to provide a shipping
address.
The system shall guide the user
through the steps to place an
order.
...
Purchase answer to see full
attachment
