Stage3
Assignment 3 Study Aid - Stakeholder’s Requirements Table
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 1 and 2 assignments.
Overview
As the business analyst in the CIO's department of Maryland Technology Consulting (MTC), 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 review any feedback from previous stages to help improve the effectiveness of your overall report and then add the new section to your report. Only content for Stage 3 will be graded for this submission. Part of the grading criteria for Stage 4 includes evaluating if the document is a very effective and cohesive assemblage of the four sections, is well formatted and flows smoothly from one section to the next. For this assignment, you will add Section III of the Business Analysis and System Recommendation (BA&SR) Report to your Sections I and II. In this section you will identify 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 MTC's organizational strategy and fulfills its operational needs.
Using the case study, assignment instructions, Content readings, and external research, develop your Section III. Requirements. The case study tells you that the executives and employees at Maryland Technology Consultants (MTC) have identified a need for an effective and efficient applicant tracking or 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
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 or needs the system to do. User 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. System performance 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 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.
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.
Do not add any additional information to this column
Complete the Requirements Statement Column
Follow the Rules for Writing Requirements
Complete the Stakeholder Column With the Position and Name of the Stakeholder
Provide an introductory sentence above the, table Ensure that the introductory sentence explains what is contained in the table, so the reader understands why the table has been included…..
|
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. |
The system must… |
|
|
2. |
The system must… |
|
|
3. |
The system must… |
|
|
4. |
The system must… |
|
|
5. |
The system must …(Reporting-Output of organized information retrieved from the system—replace 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. |
The system must… |
|
|
7. |
The system must… |
|
|
8. |
The system must… |
|
|
9. |
The system must… (Security-replace this with a specific security requirement) |
|
|
10. |
The system must… (Security-replace this with a specific security requirement) |
|
|
B. User Functional Requirements - (What the user needs the system to do) |
|
|
|
Intro Sentence to Part B. |
2 |
2 |
|
Intro Sentence to Requirements Table |
2 |
2 |
|
1 |
|
4 |
|
2 |
|
4 |
|
3 |
|
4 |
|
4 |
|
4 |
|
5. ( Reporting-Output of organized information retrieved from the system) |
|
4 |
|
Total User Functional Requirements |
|
24 |
|
|
|
|
|
System Performance Requirements - (How the system will perform)Non-Functional |
|
|
|
6 |
|
5 |
|
7 |
|
5 |
|
8 |
|
5 |
|
9 |
|
5 |
|
10 |
|
5 |
|
Total System Performance Requirements |
|
25 |
Stage 3: Requirements 03/17/2020 6