System Analysis and Design Project: Biometric Information System

This project report presents a system analysis and design for a biometric information system aimed at enhancing security for an Australia-based financial services organization, XYZ. It outlines the problem of increasing security risks and the proposed iris and fingerprint-based biometric solution to authorize user access and track activities. The report details the system's capabilities, business benefits, and advantages, including improved customer engagement and a competitive edge. It quantifies project approval factors, estimating a 112-day timeline with detailed task breakdowns across four phases, along with development and operational costs. The report includes a comprehensive risk and feasibility analysis considering organizational, technological, resource, and schedule aspects. The project environment is established with information classification, user privileges, and the selection of tools like Microsoft Visual Studio, MySQL, and Agile methodology for development. The report includes system requirements, stakeholder analysis, use case descriptions, diagrams, and system components, concluding with user interface design concepts and deployment strategies. References are provided for further context.

System Analysis and Design
Identification of the Problem.......................................................................................................................4
System Vision Document........................................................................................................................4
Description of the Problem..................................................................................................................4
System Capabilities.............................................................................................................................4
Business Benefits & Advantages.........................................................................................................4
Quantify Project Approval factors...............................................................................................................5
Estimated Time for the Project................................................................................................................5
Development Costs for the Project..........................................................................................................7
Operational Costs for the Project.............................................................................................................7
Project Benefits.......................................................................................................................................8
Project Cost Benefit Analysis..................................................................................................................8
Risk and Feasibility Analysis......................................................................................................................9
Risks and Feasibility - Organizational.....................................................................................................9
Risk Analysis.......................................................................................................................................9
Feasibility Analysis.............................................................................................................................9
Risks and Feasibility - Technological......................................................................................................9
Risk Analysis.......................................................................................................................................9
Feasibility Analysis...........................................................................................................................10
Risks and Feasibility - Resource............................................................................................................10
Risk Analysis.....................................................................................................................................10
Feasibility Analysis...........................................................................................................................11
Risks and Feasibility - Schedule............................................................................................................11
Risk Analysis.....................................................................................................................................11
Feasibility Analysis...........................................................................................................................12
Establishment of the Project Environment.................................................................................................12
Information Classification and User Privileges.....................................................................................12
Tools and Software for Developmental Activities.................................................................................13
Work Environment................................................................................................................................13
Processes and Procedures......................................................................................................................13
Work/Project Schedule..............................................................................................................................15
Work Breakdown Structure (WBS).......................................................................................................15
Gantt chart.............................................................................................................................................16
System Requirements................................................................................................................................17
2

System Analysis and Design
Functional Requirements.......................................................................................................................17
Non-Functional Requirements...............................................................................................................18
Stakeholder Analysis.................................................................................................................................18
Questionnaire for the Operational Stakeholders – Business Analyst.........................................................19
Domain class diagram...............................................................................................................................20
Use case Descriptions................................................................................................................................21
Fully Developed Use Case Description.............................................................................................22
Use case diagram...............................................................................................................................23
Activity diagram................................................................................................................................24
System sequence diagram..................................................................................................................25
System Components..................................................................................................................................27
User Interface Design Concepts – Best Practices..................................................................................28
Deploy the Solution...................................................................................................................................31
References.................................................................................................................................................32
3

System Analysis and Design
Identification of the Problem
System Vision Document
Description of the Problem
XYZ is an Australia based organization that provides financial services to its customer. The data
and information that the organization works into belongs to the category of sensitive and critical
information. There are numerous security risks and attacks that have taken place in the past due
to the violation of the access controls and the insider threats and attacks. Due to the increased
frequency of such attacks, the customer engagement and the level of customer satisfaction has
begun to drop.
System Capabilities
It has been proposed that a biometric information system is designed for the organization which
would capture the users and their identities using the iris and fingerprint based recognition. The
users that would succeed in the attempt will only be provided the access to the organizational
applications. The system will overcome the security attacks as only the authorized users will be
allowed the access. Also, a real-time log of the users accessing each of the application and
associated activities will be maintained by the system for tracking purposes. The user activities
will also be mapped with the set of best practices and standards to ensure that quality of
operations is maintained.
Business Benefits & Advantages
 The security risks and attacks that are currently taking place in the organization causing
damage to the information and data sets will come to a stop.
 The customer engagement and trust will improve as the customers will be able to be
assured that their information is in the safe hands.
 With the use of the latest security measures and information systems in the organization,
it will be able to gain a competitive advantage.
 The market shares and the revenues earned by the organization will improve as the
customer base will expand.
4

System Analysis and Design
 The employees of the organization will understand that any of the malicious practices
will result in adverse actions and will enable them to follow best practices and standards.
Quantify Project Approval factors
Estimated Time for the Project
The estimated time for the project has been calculated to be 112 days. The starting date of the
project will be 19th September 2017 and it will end on 21st February 2018. There will be a
number of activities that will be carried out in the project. All of these activities have been
described in the table below along with their sub-activities. The time that has been allocated to
each of these activities has been in accordance with the effort that will be required. It has been
made sure that there is no over-lapping of the resources during the project activities. The project
will be carried out in four broad phases and there will be activities carried out in each phase.
Task ID Task Name Duration Start Finish Predecessors
1 Biometric Information
System
112
days
Tue
9/19/17
Wed
2/21/18
1.1 Initiation and Project
Planning 15 days Tue
9/19/17
Mon
10/9/17
1.1.1 Technical,
Operational and
Economical Feasibility
Analysis
3 days Tue
9/19/17
Thu
9/21/17
1.1.2 Project Estimation
- Scope, Cost and
Schedule
6 days Fri
9/22/17
Fri
9/29/17 3
1.1.3 Risk Identification,
Assessment and
Evaluation
2 days Mon
10/2/17
Tue
10/3/17 4
1.1.4 Team selection and
allocation 2 days Wed
10/4/17
Thu
10/5/17 5
1.1.5 Communication 2 days Fri Mon 6
5

System Analysis and Design
Guidelines 10/6/17 10/9/17
1.1.6 Milestone One:
Project Plan 0 days Mon
10/9/17
Mon
10/9/17 7
1.2 Execution of the
Project 56 days Tue
10/10/17
Tue
12/26/17
1.2.1 Interfaces and UI
design for Information
System
12 days Tue
10/10/17
Wed
10/25/17 7
1.2.2 Wireframes and UI
elements 6 days Thu
10/26/17
Thu
11/2/17 10
1.2.3 Creation of Source
Code 30 days Fri
11/3/17
Thu
12/14/17 11
1.2.4 Syncing with
database and analytical
tools
5 days Fri
12/15/17
Thu
12/21/17 12
1.2.5 Unit testing of the
system 2 days Fri
12/22/17
Mon
12/25/17 13
1.2.6 Release of source
code 1 day Tue
12/26/17
Tue
12/26/17 14
1.2.7 Milestone Two:
Source Code 0 days Tue
12/26/17
Tue
12/26/17 15
1.3 Testing and
Implementation 23 days Wed
12/27/17
Fri
1/26/18
1.3.1 Testing Processes 9 days Wed
12/27/17
Mon
1/8/18 16
1.3.2 Reporting of the
defects 1 day Tue
1/9/18
Tue
1/9/18 18
1.3.3 Change
Management 5 days Wed
1/10/18
Tue
1/16/18 19
1.3.4 Reviews and 5 days Wed Tue 20
6

System Analysis and Design
Inspection 1/17/18 1/23/18
1.3.5 Integration of the
sub-systems 3 days Wed
1/24/18
Fri
1/26/18 21
1.3.6 Milestone Three:
Defect Report 0 days Fri
1/26/18
Fri
1/26/18 22
1.4 Project Closure 18 days Mon
1/29/18
Wed
2/21/18
1.4.1 System
Documentation 10 days Mon
1/29/18
Fri
2/9/18 22
1.4.2 Deliverables and
Sign Offs 3 days Mon
2/12/18
Wed
2/14/18 25
1.4.3 Closure Report
Preparation 5 days Thu
2/15/18
Wed
2/21/18 26
1.4.4 Milestone Four:
Closure Report 0 days Wed
2/21/18
Wed
2/21/18 27
Development Costs for the Project
Type of Cost 0 1
Cost of tools - One
time
$12,160
Design Costs $4,200
Development Costs $11,760
Program Total Costs
By Year
$12,160 $15,960
Operational Costs for the Project
7

System Analysis and Design
Type of Cost 0 1
Cost of Resources $15,470
Maintenance and
Support
$2,870
Testing Processes
Cost
$3,540
Program Total Costs
By Year
0 $21,880
Project Benefits
Benefit Sources 0
Reduction in
operational processes
$15,670
Enhancement of
security
$12,300
Tangible Benefits $9,870
Intangible Benefits $5,780
Total Benefits Per Year $43,620
Project Cost Benefit Analysis
8

System Analysis and Design
Risk and Feasibility Analysis
Risks and Feasibility - Organizational
Risk Analysis
Name of the risk Brief Description Risk Impact Probability of the
Risk
Treatment
Process
Strategic Risks There may be
inadequate
design and
implementation
of the project
strategies and
methodologies
High Low Risk avoidance
shall be done by
assessing the
requirements
carefully along
with enhanced
planning
Management
Risks
The skills of the
Project Manager
may not be
adequate as per
the project
requirements
(Berg, 2016)
High Low Risk avoidance
by selecting the
manager as per
the project
factors and
requirements
Feasibility Analysis
The project will be feasible from the organizational point of view since all of the risks that have
been identified have a low probability. It will be possible to avoid the risks by following
adequate measures (Dey, 2016).
Risks and Feasibility - Technological
Risk Analysis
Name of the risk Brief Description Risk Impact Probability of the
Risk
Treatment
Process
Technical Fault The technical Medium-High Medium Risk mitigation
9

System Analysis and Design
tools being used
in the project
may suffer from
a severe fault
by keeping the
alternative of
every tool ready
to be used
Integration and
Compatibility
Risks
The problems of
incompatibility
of the tools and
technologies
with the final
system (Grimes,
2016)
High Medium Risk avoidance
by carrying out a
compatibility and
integration
analysis in
advance
(Microsoft,
2016)
Feasibility Analysis
The project will be feasible from the technical point of view as it will be possible to apply the
adequate controls on the risks that have been identified (Bateman, 2016).
Risks and Feasibility - Resource
Risk Analysis
Name of the risk Brief Description Risk Impact Probability of the
Risk
Treatment
Process
Efficiency and
Productivity
Risks
The increased
number of
resources may
lead to enhanced
conflicts and
disputes which
may bring down
the levels of
efficiency and
productivity
High Low The project
management
must avoid the
risks by
enhanced
monitoring and
control along
with effective
communication
during the
10

System Analysis and Design
project
Resource
Scarcity
The resources
may quit the
organization in
abundant
numbers
High Low The project
management
must avoid the
risks by
enhanced
monitoring and
control along
with effective
communication
during the
project (Scu,
2016)
Feasibility Analysis
There shall be a daily meeting organization by the Project Manager so that the communication
processes carried out in the project are effective in nature (Sychrava, 2016). As per the resource
feasibility, the project would be feasible since the risks can be avoided and controlled (Bause,
2016).
Risks and Feasibility - Schedule
Risk Analysis
Name of the risk Brief Description Risk Impact Probability of the
Risk
Treatment
Process
Schedule
Overrun
The project team
may not be able
to meet the
deadlines of the
project due to
increased
changes and
High Low Risk avoidance
and mitigation by
following proper
estimation and
revision of the
schedule in case
the same is
11

System Analysis and Design
conflicts
(Trendmicro,
2016)
caused
Feasibility Analysis
The project would be feasible as per the schedule feasibility since the avoidance of the risk will
be possible (Kim, 2015). The management must make sure that the schedule and the other
estimated values are maintained by frequent monitoring and control.
Establishment of the Project Environment
Information Classification and User Privileges
Information Captured by the
System
Brief Description View/Update the Information
– User Privileges
Sensitive Information It will include the financial
details of the clients and
employees, such as, their
account numbers and
passwords
Only the Project Manager will
be allowed to view the
information and its update
rights will not be provided to
any of the project resource
Confidential Information The information on the
organization strategies and
projects will come under this
category (Hoiem, 2013)
View: Project Manager,
Project Developer,
Implementation Head
Update: None
Private Information The demographic details of
the employees and the clients
View: Project Manager,
Project Developer,
Implementation Head, System
Tester
Update: Implementation Head
Public Data The details of the organization
such as its profile, main list of
customers, mission and vision.
View: The entire project team
Update: Project Manager
12