Question
Requirements A. Stakeholder Interests - Identify the interest or objectives for the new hiring system for each stakeholder listed below based on his or her
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 | Specific challenge related to the hiring process | How a technology solution to support the hiring process could address the challenge |
i. CEO |
|
|
ii. CFO |
|
|
iii. CIO |
|
|
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 identified 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, copy the table, and complete the Requirements Statement and Stakeholder columns. Retain the examples but delete the word example and gray shading. No additional information should be entered into the first column, Requirement ID.)
Requirement ID | Requirement Statement | Stakeholder (Name/Position from Case Study that identified this requirement) |
Functional Requirements |
|
|
Example | The system shall store all information from the candidates application/resume in a central applicant database. | Recruiter - Paul OBrien |
1. |
|
|
2. |
|
|
3. |
|
|
4. |
|
|
5. (Reporting) |
|
|
Non-Functional Requirements |
|
|
Example | The system shall be able to run on numerous platforms. | CIO Fadil Abadi |
1. |
|
|
2. |
|
|
3. |
|
|
4. (Security) |
|
|
5. (Security) |
|
|
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 | Specific challenge related to the hiring process | How a technology solution to support the hiring process could address the challenge |
i. CEO |
|
|
ii. CFO |
|
|
iii. CIO |
|
|
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 identified 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, copy the table, and complete the Requirements Statement and Stakeholder columns. Retain the examples but delete the word example and gray shading. No additional information should be entered into the first column, Requirement ID.)
Requirement ID | Requirement Statement | Stakeholder (Name/Position from Case Study that identified this requirement) |
Functional Requirements |
|
|
Example | The system shall store all information from the candidates application/resume in a central applicant database. | Recruiter - Paul OBrien |
1. |
|
|
2. |
|
|
3. |
|
|
4. |
|
|
5. (Reporting) |
|
|
Non-Functional Requirements |
|
|
Example | The system shall be able to run on numerous platforms. | CIO Fadil Abadi |
1. |
|
|
2. |
|
|
3. |
|
|
4. (Security) |
|
|
5. (Security) |
|
|
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 | Specific challenge related to the hiring process | How a technology solution to support the hiring process could address the challenge |
i. CEO |
|
|
ii. CFO |
|
|
iii. CIO |
|
|
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 identified 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, copy the table, and complete the Requirements Statement and Stakeholder columns. Retain the examples but delete the word example and gray shading. No additional information should be entered into the first column, Requirement ID.)
Requirement ID | Requirement Statement | Stakeholder (Name/Position from Case Study that identified this requirement) |
Functional Requirements |
|
|
Example | The system shall store all information from the candidates application/resume in a central applicant database. | Recruiter - Paul OBrien |
1. |
|
|
2. |
|
|
3. |
|
|
4. |
|
|
5. (Reporting) |
|
|
Non-Functional Requirements |
|
|
Example | The system shall be able to run on numerous platforms. | CIO Fadil Abadi |
1. |
|
|
2. |
|
|
3. |
|
|
4. (Security) |
|
|
5. (Security) |
|
|
Step by Step Solution
There are 3 Steps involved in it
Step: 1
Get Instant Access to Expert-Tailored Solutions
See step-by-step solutions with expert insights and AI powered tools for academic success
Step: 2
Step: 3
Ace Your Homework with AI
Get the answers you need in no time with our AI-driven, step-by-step assistance
Get Started