Defining Requirements - The next step is to identify theessential requirements for the information system. In addition tothe stakeholder interests identified above, review the Case Study,especially the interviews, highlighting any statements that tellwhat the person expects the system to do. Functional requirementsexpress specifically what the user needs the system to do. This canbe in terms of tasks the users need to perform, data they need toinput, what the system might do with that data input, and outputrequired. Non-Functional requirements express how the system willperform in several performance areas and security. As a member ofthe CIO's organization, you will use your professional knowledge toIdentify 5 Functional Requirements (including one specificallyrelated to reporting) and 5 Non-Functional Requirements (including2 security-related requirements). Refer to Week 6 content onrequirements; security requirements are covered in Chapter 6 of thetextbook. Additional research can expand your knowledge of theseareas.

Once you have written down the 10 requirements, evaluate eachone using the criteria below and create 10 well-writtenrequirements 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 willsupport or perform

• For Non-Functional Requirements, states how the system willperform.

• Includes a measure or metric that can be used to determinewhether the requirement is met (time or quantity), whereappropriate

• Is stated in positive terms and uses "shall" (not "may" or"should"); "the system shall xxxx" not "the system shall notxxx"

• 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 "nofailures" For a full requirement specification, there will be manyrequirements statements; you only need to provide the number ofrequirements identified for each category. Do not provide genericstatements but relate to the needs of CIC to improve its hiringprocess.

(Provide an introductory sentence and copy the table and insertinformation within.)

Requirement ID	Requirement Statement	Stakeholder (Name/Position from Case Study that identified thisrequirement)
Functional Requirements
Example	The system shall store all information from the candidate’sapplication/resume. In a central applicant database.	Recruiter - Paul O’Brien
1.
2.
3.
4.
5. (Reporting)
Non-Functional Requirements
Example	The system shall be implemented as a Software as a Servicesolution.	CIO – Fadil Abadi
1.
2.
3.
4. (Security)
5. (Security)