Make sure" (Reporting-Output of organized information retrieved from the systemreplace this statement with a specific reporting requirement) " is properly identified for my understanding.

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 or needs the system to do. User requirementsexpress 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. System performance requirementsexpress 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 User Requirements (including one specifically related to reporting) and 5 System Performance Requirements (including 2 security-related requirements). Refer to Week 5 content on requirements; security requirements are covered in Week 6. 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 statements 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 User Requirements, states what tasks the system will support or perform.
• For System Performance 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 "must" (not "shall," "may" or "should"); "the system must xxxx" not "the system must not xxx".
• Avoids the use of terms that cannot be defined and measured, such as "approximately," "robust," "user friendly," etc.
• Is achievable and realistic; avoids terms such as "100% uptime," or "no failures".

For a full requirements document, there will be many requirement 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 MTC to improve its hiring process.

(Provide an introductory sentence, copy the table, and complete the Requirements Statement and Stakeholder columns. No additional information should be entered into the first column, Requirement ID.)

Requirement ID# only	Requirement Statement	Stakeholder (Position and Name from Case Study that identified this requirement)
	User Requirements -(What the user needs the system to do)
EXAMPLE	The system must store all information from the candidate's application/resume in a central applicant database.EXAMPLE PROVIDED - (Retain text but remove this label and gray shading in your report)	Recruiter - Peter O'Neil
1.
2.
3.
4.
5.	(Reporting-Output of organized information retrieved from the systemreplace this statement with a specific reporting requirement)
	System Performance Requirements -(How the system will perform)
EXAMPLE	The system must be implemented as a Software as a Service solution.EXAMPLE PROVIDED - (Retain text but remove this label and gray shading in your report)	CIO - Raj Patel
6.
7.
8.
9.
10.