Defining Requirements - The next step is to identify the essential requirements

Question

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.)

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 candidate’s application/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 Service solution.

CIO – Fadil Abadi

1.

2.

3.

4. (Security)

5. (Security)

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 candidate’s application/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 Service solution.

CIO – Fadil Abadi

1.

2.

3.

4. (Security)

5. (Security)

Explanation / Answer

Requirement ID

Requirement Statement

Stakeholder

(Name/Position from Case Study that identified this requirement)

Functional Requirements

1.

Central application database to store the resume of candidate

Head-Recruitment

2.

Through Artificial Intelligence rank the candidate

Chief Developer

3.

Automatically shortlisting candidates according to required qualification and skills

Head- Recruitment

4.

Generating offer letter to selected candidate

CTO

5. (Reporting)

Making report on candidates fit the requirement, attend the interview, selected and accepted offer

Head-Recruitment

Non-Functional Requirements

1.

Software as a service solution

CIO

2.

Software as shortlisting and communicating with candidate

CIO

3.

Use of AI and Machine Language to communicate with the potential candidate

CIO

4. (Security)

ERP should have encryption of data

Chief security Officer

5. (Security)

64 bits encryption and user controlled for authorized assess

Chief security Officer

Requirement ID

Requirement Statement

Stakeholder

(Name/Position from Case Study that identified this requirement)

Functional Requirements

1.

Central application database to store the resume of candidate

Head-Recruitment

2.

Through Artificial Intelligence rank the candidate

Chief Developer

3.

Automatically shortlisting candidates according to required qualification and skills

Head- Recruitment

4.

Generating offer letter to selected candidate

CTO

5. (Reporting)

Making report on candidates fit the requirement, attend the interview, selected and accepted offer

Head-Recruitment

Non-Functional Requirements

1.

Software as a service solution

CIO

2.

Software as shortlisting and communicating with candidate

CIO

3.

Use of AI and Machine Language to communicate with the potential candidate

CIO

4. (Security)

ERP should have encryption of data

Chief security Officer

5. (Security)

64 bits encryption and user controlled for authorized assess

Chief security Officer

Related Questions

Navigate

• Browse (All)
• Browse D
• Subjects

---

---

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.