USA: +1(669)289-8683 
Sign in
Please produce examples of a Sequence Model and a Use Case Modeling for a hiring process.
SYSTEMS ANALYSIS AND DESIGN
WORKING DOCUMENT
Machine Learning Execution
Colton J. T. Farley
CIS 601 – Systems Analysis and Design
Park University
Business Requirements Document
Machine Learning Execution
Revision History:
Date
Version
Name
Description of Changes
Jun. 11 2023
1.0
Insperity
Initial Creation
Jun. 18 2023
2.0
Insperity
System Development Methodology
Jun. 25 2023
3.0
Insperity
Requirements
Insperity
version 1.0
Page 2 of 15
Business Requirements Document
Machine Learning Execution
TABLE OF CONTENTS
BUSINESS REQUIREMENTS DEFINITION ………….. ERROR! BOOKMARK NOT DEFINED.
TABLE OF CONTENTS ………………………………………………………………………………………….. 3
INTRODUCTION …………………………………………………………………………………………………… 4
Executive Summary ……………………………………………………………………………………………………………………….. 4
Purpose of this Document ……………………………………………………………………………………………………………….. 4
Business Objectives ……………………………………………………………………………………………………………………….. 4
Project Objectives ………………………………………………………………………………………………………………………….. 4
Summary of Scope ……………………………………………………………………………… Error! Bookmark not defined.
Issues ……………………………………………………………………………………………….. Error! Bookmark not defined.
Constraints, Assumptions, Risks, Dependencies ……………………………………… Error! Bookmark not defined.
Project Team …………………………………………………………………………………………………………………………………. 4
Context Diagram ……………………………………………………………………………………………………………………………. 5
Use Case Diagram…………………………………………………………………………………………………………………………. 9
Process Swim Lane Diagram ………………………………………………………………… Error! Bookmark not defined.
REQUIREMENTS ………………………………………………………………………………………………….. 5
Functional Requirements List…………………………………………………………………………………………………………… 6
Business Rules List……………………………………………………………………………… Error! Bookmark not defined.
Non-Functional Requirements List ……………………………………………………………………………………………………. 6
Information Requirements List ………………………………………………………………. Error! Bookmark not defined.
PROCESS DEFINITION …………………………………………………………………………………………. 7
1
Use-Case-Name …………………………………………………………………………… Error! Bookmark not defined.
DATA DEFINITION ……………………………………………. ERROR! BOOKMARK NOT DEFINED.
Entity Relationship Diagram ………………………………………………………………….. Error! Bookmark not defined.
Entity / Use Case Table ………………………………………………………………………… Error! Bookmark not defined.
Entity-Name ……………………………………………………………………………………….. Error! Bookmark not defined.
APPENDIX ………………………………………………………. ERROR! BOOKMARK NOT DEFINED.
Appendix 1 – Glossary of Terms and Acronyms……………………………………….. Error! Bookmark not defined.
Insperity
version 1.0
Page 3 of 15
Business Requirements Document
Machine Learning Execution
UNIT 1: INTRODUCTION
Executive Summary
This BRD is intended for Insperity to review the implementation of Machine Learning into the hiring
quoting software. This will be used to identify a trendline on backgrounds, gender, and race from various
departments to enable ethical hiring decisions and allow senior leadership a bi-weekly generated report
that can be used to follow up with applicants who’re less likely to apply right away.
Purpose of this Document
Review the current online hiring systems and take the data from historical advertisements and hires to
implement a machine learning algorithm for identifying applicants less likely to apply to the ad that was
broadcasted. With this data, we enable our hiring team to rapidly pursue these candidates to assist them
with getting a position that will work for them. We will be utilizing the SDLC Waterfall Model to work
through the design of this algorithm to implement.
Business Objectives
▪
▪
▪
Objective #1 – Take the historical online advertisement market data to generate trends analysis
for the last 10 years
Objective #2 – Take the trend analysis and create a machine learning algorithm to implement into
bi-weekly reports to hiring teams.
Objective #3 – Design a SOP for following up on applicants that did not apply for advertised
positions.
Project Objectives
▪
Implement Machine Learning data analytics to review the historical data of ads and hires.
Enabling our hiring team to rapidly pursue these less likely-to-apply candidates to assist them with
getting a position based off of historic data.
Potential Challenges
▪
▪
Lack of historical hiring trends.
advertisements that were started but not finished so we did not capture all the needed data to run
against the machine learning algorithm
Project Team
The following team members were integral in the development and contributions to this
specification:
Name
Role
Colton Farley
Project Team Leader
Caleb Bryan
Systems Design and Testing
Clayton Jones
Execution Support
Insperity
version 1.0
Page 4 of 15
Business Requirements Document
Machine Learning Execution
UNIT 2: SOFTWARE DEVELOPMENT
METHODOLOGY
For implementation of a hiring software project, we selected the waterfall methodology. The waterfall
methodogoloy will break the project into a sequence of tasks to complete. The phases will be completed
in a waterfall approach and will require a stakeholder to sign off on each phase before the next phase will
begin. Please see below for the phases:
Analysis
Requirement
Specification
Design
Development
Testing &
Integration
Implementation/
Deployment
(Farley, C., 2023)
The waterfall method is based on three main principles: low customer involvement, strong documentation,
and sequential structure (Sergeev, A., 2021).
•
Customer involvement is kept low, which is preferred to keep them in the day-to-day tasks. The
team will meet with the developers to review what they want from the software and how they
want it to perform. We would then bring the customer into the testing phase to show what was
developed and how it works. At this time, if no changes are requested, then the final meeting will
be when it is ready to deploy
•
Documentation throughout the project is high. All steps are fully documented, and each
stakeholder with have signed off before moving to the next phase.
•
The sequential stages are the main fundamental principle of the waterfall method. It keeps the
project straightforward.
With the waterfall method, we can complete the project on time and with minimal stakeholder change
requests. Having the sign-offs at the end of each phase as well as the critical panels at the beginning to
gather the information from the client, and right after the testing, we can make sure this is what the client
wants, and we can roll out on time
Insperity
version 1.0
Page 5 of 15
Business Requirements Document
Machine Learning Execution
UNIT 3: BUSINESS REQUIREMENTS
Functional Requirements List
Below are the functions that the developers will implement into the software for the Insperity
hiring software.
Req. Requirement
ID #
1.
Hire & non-hire reports are generated every 72 hours
2.
The hiring system will allow the hiring team to record candidates’ applications upon
follow up.
3
API interface to the hiring system
4
The system will allow candidates to revisit their applications using their phone number
or email address
5
The system will allow the candidates to submit feedback through a contact form in the
app
Non-Functional Requirements List
These functions will not affect the software’s functionality but how it will perform in day-to-day
use.
Usability
With appropriate training, the hiring teams can use the software and easily navigate the tasks
they must complete. The software must be functioning for the customers to navigate the hiring
easily.
Reliability
Every unsuccessful attempt by a user to access an item of data shall be recorded on an audit
trail. We can check the percentage of the probability of failure, or failure rate, to determine the
reliability of a system. If the ratio is higher, the system will likely function normally after important
use.
Performance
The website’s load time should be one second for customers at maximum. The software must
function with a response time of 5 seconds for the customers to navigate through the hiring with
ease.
Security & access controls
Users must change the initially assigned login password immediately after the first successful
login. Moreover, the initial should never be reused. Setting up security questions in the instance
that a user forgets their password is used to identify the user in the system to send a
temporary password.
Insperity
version 1.0
Page 6 of 15
Business Requirements Document
Machine Learning Execution
Supportability
Updates to the system must be processed overnight to eliminate downtime for users. Software
developers must maintain the components after deployment for updates and upgrades.
Maintaining a data backup that is run every night so be able to recover quickly if the site were to
go down to eliminate data loss
Business Process Diagram
Insperity’s hiring application documents the process that follows up on unfilled billets completed
by external applicants in our online hiring system. Below is the process diagram to kick off the
project for Insperity. This process will be followed with the project management team to
determine if the project will be accepted to move forward, and if it does, what will happen to get
it started.
Project Timeline
The project timeline is detailed below; we can complete the development in 3 months using the
waterfall approach. It maps out what must be completed before a new task can commence and
keeps everything moving. Please see the next page for the project timeline.
Insperity
version 1.0
Page 7 of 15
Business Requirements Document
Task
1.) Gather Requirements
Machine Learning Execution
Planned Start Date Planned Finish Date Planned Duration Required Hours
6/30/2023
7/2/2023
5 days
20 hours
Identify Key Hiring Stakeholders
6/30/2023
6/30/2023
1 day
8 hours
Hold Discussions with Stakeholders
6/31/2023
7/1/2023
2 days
4 hours
Define Candidates Applying Criteria
7/1/2023
7/2/2023
1 day
8 hours
2.) Develop the Schedule
7/3/2023
7/19/2023
11 days
57 hours
List Tasks
7/5/2023
7/5/2023
1 day
8 hours
Set Task Priorities
7/6/2023
7/6/2023
1 day
8 hours
Determine Timeline
7/7/2023
7/7/2023
1 day
8 hours
Plan for Communication
7/10/2023
7/10/2023
1 day
8 hours
Identify Applicants Security Requirements
7/11/2023
7/13/2023
2 days
5 hours
Implement Identified Security Measures
7/14/2023
7/19/2023
5 days
20 hours
3.) Design the Software
7/20/2023
7/19/2023
14 days
89 hours
Apply implementation Analytics
7/20/2023
7/22/2023
2 days
14 hours
Create Solution Design Doc
7/23/2023
7/30/2023
7 days
40 hours
Define Product Specifications
7/31/2023
8/3/2023
4 days
27 hours
Update the Schedule
8/4/2023
8/4/2023
1 day
8 hours
8/5/2023
8/25/2023
20 days
112 hours
Configure features
8/5/2023
8/9/2023
4 days
30 hours
Customize the Software
8/10/2023
8/12/2023
2 days
8 hours
Preform System Testing
8/13/2023
8/20/2023
7 days
42 hours
Document Issues Found
8/21/2023
8/21/2023
1 day
8 hours
Correct Issues Found
8/22/2023
8/24/2023
2 days
16 hours
Test Corrections
8/25/2023
8/25/2023
1 day
8 hours
8/26/2023
9/10/2023
13 days
73 hours
Preform On-Site Installation
8/26/2023
8/30/2023
4 days
24 hours
Setup the Applicant Database
8/31/2023
9/2/2023
3 days
12 hours
Migrate Data
9/3/2023
9/7/2023
4 days
21 hours
Integrate the Desktop
9/8/2023
9/10/2023
2 days
16 hours
9/11/2023
9/16/2023
5 days
27 hours
Define Success Metrics
9/11/2023
9/14/2023
3 days
15 hours
Review Business Performance
9/14/2023
9/16/2023
2 days
12 hours
9/17/2023
9/30/2023
12 days
76 hours
Schedule Training
9/17/2023
9/17/2023
1 day
8 hours
Train End Users
9/18/2023
9/22/2023
4 days
28 hours
Create User Documentation
9/23/2023
9/30/2023
7 days
40 hours
10/1/2023
10/1/2023
1 day
8 hours
4.) Build the Solution
5.) Integrate the Solution
6.) Monitor the Solution
7.) Provide Training
8.) Hand Over to Support
Insperity
version 1.0
Page 8 of 15
Business Requirements Document
Machine Learning Execution
UNIT 4: USE CASE DIAGRAM
SUMMARY USE CASE NARRATIVE
Brief description of the Use Case.
SAMPLE USE CASE DIAGRAM
UseCase1
Actor1
UseCase2
UseCase3
UseCase5
UseCase4
Actor3
Actor2
UseCase6
UseCase7
Insperity
version 1.0
Page 9 of 15
Business Requirements Document
Machine Learning Execution
UNIT 4: SEQUENCE DIAGRAM
SUMMARY SEQUENCE DIAGRAM NARRATIVE
Brief description of the diagram. Include legend for notation.
Insperity
version 1.0
Page 10 of 15
Business Requirements Document
Machine Learning Execution
UNIT 5: CLASS DIAGRAM
SUMMARY CLASS DIAGRAM NARRATIVE
Brief description of the diagram. Include legend for notation.
Insperity
version 1.0
Page 11 of 15
Business Requirements Document
Machine Learning Execution
UNIT 6: DATA FLOW DIAGRAM
SUMMARY DATA FLOW DIAGRAM NARRATIVE
Brief description of the diagram. Include legend for notation.
Insperity
version 1.0
Page 12 of 15
Business Requirements Document
Machine Learning Execution
UNIT 6: DATA DICTIONARY
SUMMARY DATA DICTIONARY NARRATIVE
Brief description of the diagram. Include legend for notation.
Insperity
version 1.0
Page 13 of 15
Business Requirements Document
Machine Learning Execution
UNIT 7: SYSTEM EVALUATION
Evaluation Criteria
Define how the system will be evaluated.
Vulnerability
Describe any weaknesses in the information system that can be exploited by malicious actions
against the system and lead to catastrophic consequences.
e.g., System requires firewall blocking for unknown IP addresses
Scalability
Describe any foreseeable issues with the ability to scale the system to meet user demand.
e.g., Response time must be within 2 seconds for 90% of all transactions
Maintainability
Describe any requirements as it relates to system availability and response time.
e.g., Code must be well-documented with README pages and unit tests.
Security & access controls
Describe any requirements as it relates to access, user roles and security.
e.g., User authentication shall be via the corporate Single Sign-on system.
Other
Insperity
version 1.0
Page 14 of 15
Business Requirements Document
Machine Learning Execution
REFERENCES
Sergeev, A. (2021, March 16). Waterfall process model. Hygger. Retrieved June 18, 2023, from
https://hygger.io/blog/waterfall-process-model-principles/
Insperity
version 1.0
Page 15 of 15
