USA: +1(669)289-8683 
Sign in
A System Requirements Specification (SRS) (also known as a Software Requirements Specification) is a document or set of documentation that describes the features and behavior of a system or software application. It includes a variety of elements (see below) that attempts to define the intended functionality required by the customer to satisfy their different users.
Submit your system requirements in regards to Security System Monitoring. The system requirements model is to be submitted as a Word document that is a combination of sections: a requirements model, a data process model, a data flow diagram, a data dictionary, an object model, and a use case diagram. Copy the image of your diagram into your Word document and include text to ensure that the diagram has proper context within the overall system requirements model through written explanations. Your audience is IT management and the IT project team. IT 510 Final Project Guidelines and Rubric
Overview
The final project for this course is the creation of a System Proposal Document.
In any modern enterprise, it is crucial that all of the different stakeholders, users, inputs, and outputs that relate to the business’s IT systems coalesce in a logical
and cohesive way for the systems to be effective. As a member of an IT team, your overarching goal is to ensure that the IT systems ultimately do what the
business needs them to do. In this course, you have learned about the key principles and practices underlying the analysis, design, implementation, and
management of IT systems. In this final project, you will apply this knowledge by creating a systems proposal document.
The project is divided into four milestones, which will be submitted at various points throughout the course to scaffold learning and ensure quality final
submissions. These milestones will be submitted in Module Two, Module Four, Module Six, and Module Eight. The final submission will occur in Module Nine.
In this assignment, you will demonstrate your mastery of the following course outcomes:
Assess the relationship of systems analysis, design, implementation, and development processes as they relate to the management of information
technology systems
Communicate the paradigms, processes, and activities of systems development to diverse audiences
Apply structure and object oriented analysis modeling techniques to analyze, design, and manage information technology systems
Construct written and visual representations of the analysis, design, implementation, and management of information technology systems based on the
systems development life cycle
Prompt
You will select your own case study and will apply the content provided, describing the business process to complete the final project. Alternate sources for case
studies include the case studies found in the textbook with the exception of the Personal Trainer Case. You can additionally search the internet for business case
ideas.
You will complete an analysis of an existing information technology system and make recommendations for updates to meet business goals based on your chosen
case study. Your final submission will include an introduction, systems requirements, systems design specifications, and an implementation plan. All of the
components listed below should be submitted as a single, organized systems proposal document and include screenshots of all relevant diagrams, charts, and
tables.
I.
Introduction: Provide an overview of your selected case. Be sure to provide appropriate citations and reference to the case study you have selected.
a) Background: Establish a context for understanding your systems proposal. Specifically, explain any essential paradigms, processes, and activities
of the existing information technology systems.
b) Problem Statement: What is the problem that needs to be solved? Why is it a problem? What are the impacts to the enterprise?
c) Audience: Who are your audiences for this systems proposal? How will you effectively communicate the information of your proposal to these
diverse groups?
II.
Systems Requirements: Detail the specific requirements of your case. Be sure to include screenshots of all relevant diagrams, charts, and tables.
a) Requirements Modeling: Assess the current system to identify the requirements for the new system. Be sure to address each of the following
aspects: outputs, inputs, processes, performance, and controls (i.e., security).
b) Data Process Model: Create a visual representation of all relevant data processes that represents a logical model of the requirements of the
system based on the systems development life cycle.
c) Data Flow Diagrams: Create a visual representation of the data flow based on the systems development life cycle.
d) Data Dictionary: Create a data dictionary that annotates your system requirements to build clarity in communicating with the relevant
audiences.
e) Object Modeling: Use appropriate object modeling techniques and tools to describe the system requirements.
f) Use Case Diagrams: Create (a) use case diagram(s) that outline the system requirements based on the systems development life cycle.
III. Systems Design: Propose a solution that addresses the identified problem in your case. Be sure to include screenshots of all relevant diagrams, charts,
and tables.
a) Specifications: Provide a physical design that will meet the specifications outlined in the systems requirement document.
b) Data Design: Create entity relationship diagrams that accurately describe the proposed solution, including 3NF table designs.
c) User Interface Design: Illustrate the user interface design. Specifically, be sure to address your proposed human computer interactions (HCIs)
and graphical user interfaces (GUIs). Your proposals should follow user-centered design principles and address all design requirements.
d) System Architecture: Describe the system architecture. Specifically, be sure to address the corporate organization and culture, enterprise
resource planning, total cost of ownership, scalability, integration and interface requirements, and security.
e) Feasibility Analysis: Provide supporting details that justify why your proposed solution is appropriate for solving the problem. In your defense,
be sure to address operational, technical, economic, and scheduling feasibility. Be sure that you frame your response for communicating
effectively to your target audiences.
IV.
Project Plan: Illustrate your recommended implementation and management strategies. Be sure to include screenshots of all relevant diagrams,
charts, and tables.
a) Work Breakdown Structure: Describe all of the essential roles and functions required for implementing the solution. Who will be doing the work
and what, specifically, will they need to do?
b) Project Monitoring and Control Plan: How are you going to ensure that the project is going smoothly? What is your plan of attack to ensure that
all controls are adhered to? What is the defined critical path? Be sure that you frame your response for communicating effectively to your target
audiences.
c) Timeline: What is the estimated amount of time for implementation? Create a visual representation that captures your timeline (e.g., Gantt
chart) based on the systems development life cycle.
Milestones
Milestone One: Business Case Proposal and Introduction
In Module Two, you will submit a business case proposal, which is a summary of your selected business case for the course project. The business case proposal
will be submitted as a Word document and in paragraph form. This business case proposal provides your instructor insight into the project you are selecting and
allows for instructor feedback and guidance in terms of the scope of the business case for the purpose of this course. The first milestone of the course project is
an introduction. This milestone is graded with the Milestone One Rubric.
Milestone Two: Project Plan
In Module Four, you will submit your project plan. The project plan is a Word document that is a combination of a written explanation of the project plan and
the explanation of the control plan. The WBS and timeline are represented with screenshots of the Gantt chart, resource chart, and cost table. Ensure each chart
and graph is properly noted and has text explanation. This milestone is graded with the Milestone Two Rubric.
Milestone Three: System Requirements
In Module Six, you will submit your system requirements. The system requirements model is to be submitted as a Word document that is a combination of
sections: a requirements model, a data process model, a data flow diagram, a data dictionary, an object model, and a use case diagram. Copy the image of your
diagram into your Word document and include text to ensure that the diagram has proper context within the overall system requirements model through written
explanations. Your audience is IT management and the IT project team. This milestone is graded with the Milestone Three Rubric.
Milestone Four: System Design
In Module Eight, you will submit your system design via a Word document. The system design will include visual presentations of each of the following: modeling
for specifications, data design, and user interface design. Each of the diagrams will visually represent your design. The system design additionally will include each
explanation and supporting detail of the system design execution, in a complete and comprehensive write-up. These are the sections Systems Architecture and
Feasibility Analysis. Your audience is IT management and the IT project team. This milestone is graded with the Milestone Four Rubric.
Final Submission: System Proposal Document
In Module Nine, you will submit a systems proposal document. It should be a complete, polished artifact containing all of the critical elements of the final
product. It should reflect the incorporation of feedback gained throughout the course. This milestone will be graded using the Final Project Rubric.
Deliverable Milestones
Milestone
1
Deliverables
Module Due
Grading
Two
Graded separately; Milestone One Rubric
Four
Graded separately; Milestone Two Rubric
Six
Graded separately; Milestone Three Rubric
2
Business Case Proposal and
Introduction
Project Plan
3
System Requirements
4
System Design
Eight
Graded separately; Milestone Four Rubric
Final Product: System Proposal
Document
Nine
Graded separately; Final Project Rubric
Final Project Rubric
Guidelines for Submission: Written components of projects must follow these formatting guidelines when applicable: double spacing, 12-point Times New
Roman font, one-inch margins, and APA citations. The paper should be 15 to 25 pages, not including cover page and resources.
Critical Elements
Background
Exemplary (100%)
Meets “Proficient” criteria and
uses industry-specific
terminology to effectively
communicate and establish
expertise
Problem Statement
Meets “Proficient” criteria and
selects particularly insightful
examples and supporting
evidence that demonstrate a
nuanced understanding of the
problem
Meets “Proficient” criteria and
selects strategies that
demonstrate particular insight
into the needs of the diverse
audiences
Audience
Requirements
Modeling
Meets “Proficient” criteria and
selects particularly insightful
examples and supporting
evidence that demonstrate a
nuanced understanding of the
problem
Proficient (90%)
Includes a context that
addresses all essential
paradigms, processes, and
activities of the existing
information technology systems
with sufficient detail for
understanding the systems
proposal
Clearly defines and defends the
problem in need of resolution
by illustrating the impacts to
the enterprise
Needs Improvement (70%)
Includes a context, but it does
not address all essential
paradigms, processes, or
activities of the existing IT
systems or it is not sufficiently
detailed for understanding the
systems proposal
Not Evident (0%)
Does not include a context for
understanding the systems
proposal
Value
6
Defines a problem in need of
resolution, but there are clarity
issues, gaps in the defense, or
inaccuracies in the illustration
Does not include a valid
problem in need of resolution
6
Identifies plausible, distinct
audiences for the proposal
based on the case, and selects
appropriate strategies for
effectively communicating with
each identified audience
Identifies distinct audiences for
the proposal, but lacks
plausibility for the case or does
not select appropriate
strategies for effectively
communicating with each
identified audience
Assesses the current system,
but either does not accurately
identify the requirements for
the new system; does not
address the outputs, inputs,
processes, performance, or
controls; or does not use
specific examples
Does not identify distinct
audiences for the proposal
6
Does not assess the current
system to identify the
requirements for the new
system
6
Assesses the current system to
accurately identify the
requirements for the new
system (including the outputs,
inputs, processes, performance,
and controls) using specific
examples
Data Process Model
Meets “Proficient” criteria and
visual representation reflects an
in-depth understanding of the
systems development life cycle
Creates a visual representation
of all relevant data processes,
representing an accurate logical
model of the requirements of
the system based on the
systems development life cycle
Data Flow Diagrams
Meets “Proficient” criteria and
visual representation reflects an
in-depth understanding of the
systems development life cycle
Creates an accurate visual
representation of the data flow
based on the systems
development life cycle
Data Dictionary
Meets “Proficient” criteria and
definitions reflect an in-depth
understanding of the
paradigms, processes, and
activities of IT systems
Meets “Proficient” criteria and
techniques and/or results
demonstrate in-depth
understanding of structure and
object oriented analysis
modeling
Meets “Proficient” criteria and
diagram(s) reflect(s) an in-depth
understanding of the systems
development life cycle
Creates a data dictionary that
annotates the system
requirements and would
effectively build clarity with
relevant audiences
Uses appropriate object
modeling techniques and tools
to effectively describe the
system requirements
Object Modeling
Use Case Diagrams
Specifications
Meets “Proficient” criteria and
physical design reflects an indepth understanding of the
systems development life cycle
Data Design
Meets “Proficient” criteria and
diagrams reflect in-depth
understanding of structure and
object oriented analysis
modeling
Creates (a) use case diagram(s)
that accurately outline the
system requirements based on
the systems development life
cycle
Provides a physical design that
comprehensively meets the
specifications outlined in the
systems requirement document
Creates entity relationship
diagrams that accurately
describe the proposed solution,
including 3NF table designs
Creates a visual representation
of data processes, but there are
significant gaps or the logical
model of the requirements of
the system is not appropriately
based in the systems
development life cycle
Creates a visual representation
of the data flow, but there are
significant gaps or inaccuracies
based on the systems
development life cycle
Creates a data dictionary that
annotates the system
requirements, but there are
gaps or clarity issues given the
needs of relevant audiences
Uses object modeling
techniques and tools, but either
the tools or the description of
the system requirements are
ineffective
Does not create a visual
representation of data
processes
6
Does not create a visual
representation of data flow
6
Does not create a data
dictionary that annotates the
system requirements
6
Does not use object modeling
techniques and tools
6
Creates (a) use case diagram(s),
but there are gaps or
inaccuracies in the system
requirements based on the
systems development life cycle
Provides a physical design, but
does not comprehensively meet
the specifications outlined in
the systems requirement
document
Creates entity relationship
diagrams, but there are gaps or
inaccuracies in describing the
solution or does not include
3NF table designs
Does not create (a) use case
diagram(s)
6
Does not provide a physical
design
6
Does not create entity
relationship diagrams
5
User Interface
Design
Meets “Proficient” criteria and
user interface design reflects an
in-depth understanding of
structure and object oriented
analysis modeling
Illustrates the user interface
design (including HCIs and GUIs)
that follow user-centered
design principles and address all
design requirements
System Architecture
Meets “Proficient” criteria and
system architecture reflects an
in-depth understanding of the
systems development life cycle
Feasibility Analysis
Meets “Proficient” criteria and
evidence and examples reflect
an in-depth understanding of
the paradigms, processes, and
activities of IT systems
Work Breakdown
Structure
Meets “Proficient” criteria and
selects insightful examples that
demonstrate a nuanced
understanding of the
relationship of IT systems
implementation processes
Meets “Proficient” criteria and
plan reflects an in-depth
understanding of the
paradigms, processes, and
activities of IT systems
Describes the system
architecture by addressing the
corporate organization and
culture, enterprise resource
planning, total cost of
ownership, scalability,
integration, and interface
requirements, and security in
specific detail
Justifies the proposed solution
by addressing operational,
technical, economic, and
scheduling feasibility in a
manner suitable for the target
audiences
Describes all of the essential
roles and functions required for
implementing the solution with
specific examples
Project Monitoring
and Control Plan
Timeline
Meets “Proficient” criteria and
visual representation reflects an
in-depth understanding of the
systems development life cycle
Includes a project monitoring
and control plan that addresses
all necessary controls and
defines the critical path in a
manner suitable for the target
audiences
Creates a visual representation
of an appropriate timeline for
implementing the solution
based on the systems
development life cycle
Illustrates the user interface
design, but does not include
HCIs and GUIs, does not follow
user-centered design principles,
or does not address all design
requirements
Describes the system
architecture, but does not
address the corporate
organization and culture,
enterprise resource planning,
total cost of ownership,
scalability, integration and
interface requirements, or
security in specific detail
Justifies the proposed solution,
but does not fully address
operational, technical,
economic, or scheduling
feasibility in a manner suitable
for their target audiences
Describes the implementation
of the solution, but does not
include all essential roles and
functions or does not include
specific examples
Does not illustrate the user
interface design
5
Does not describe the system
architecture
5
Does not justify the proposed
solution in terms of its
feasibility
5
Does not describe the
implementation of the solution
5
Includes a project monitoring
and control plan, but does not
address all necessary controls
or define the critical path in a
manner suitable for the target
audiences
Creates a visual representation
of the timeline for
implementing the solution, but
it is not fully appropriate based
on the systems development
life cycle
Does not include a project
monitoring and control plan
5
Does not create a visual
representation of the timeline
for implementing the solution
5
Articulation of
Response
Submission is free of errors
related to citations, grammar,
spelling, syntax, and
organization and is presented in
a professional and easy-to-read
format
Submission has no major errors
related to citations, grammar,
spelling, syntax, or organization
Submission has major errors
related to citations, grammar,
spelling, syntax, or organization
that negatively impact
readability and articulation of
main ideas
Submission has critical errors
related to citations, grammar,
spelling, syntax, or organization
that prevent understanding of
ideas
Earned Total
5
100%
Running head: SECURITY SYSTEM UPGRADE PROJECT PLAN
Security System Upgrade Project Plan
by
Anjyla Morrison
Master of Science in Informational Technology
With a concentration in Web Design
Southern New Hampshire University
1
SECURITY SYSTEM UPGRADE PROJECT PLAN
2
Security System Upgrade Project Plan
The project involves an upgrade of Security System for a company dealing with online
platforms. There is a lot of clients information that is captured online and hence the need to
improve system security. This raises the reputation of the company and hence trusts from the
clients. The project will involve development of security enhanced mobile application that will
help in improving customer service as well as management serving as an extension of the already
running web based customers management system. The design and development of the mobile
application requires a project plan which is developed by the project manager. The project
manager has a key role to ensure that the project is completed on time, within the set budget, and
meets the users’ requirements of enhancing security. The manager has an overall role of
planning, monitoring, scheduling and reporting about the project. The project plan involves
Work Breakdown Structure (WBS), Project Monitoring and Control Plan, and Timeline for the
project.
Work Breakdown Structure
The development of the mobile application will involve a series of individual tasks that
may be interrelated. The initial step will be inception of the project in which the project manager
SECURITY SYSTEM UPGRADE PROJECT PLAN
3
will initially audit the project requirements, at that point he will make the business case
document to prepare the project (Tilley & Rosenblatt, 2016).
From that point forward, he will make the schedule, lastly in the wake of making
business case archive and calendar, he will get the client signoff to continue further. In the
following stage, alongside the framework the project manager will deal with finding the
framework necessities, for which they will work upon reality finding and looking into existing
framework. In the wake of social affair prerequisites, the framework investigator will chip away
at the framework plan, in which he will initially structure the information stream charts and the
client forms (Burke, 2013). In the wake of structuring stage, the web developer will be in charge
of making page model and portable designer will be in charge of making iOS model. The
subsequent stage will be the check by the framework expert where the arrangement design will
be audited and the model will be approved. Toward the end, the project manager will finish the
project by deciding proposal and making official introduction. The more detail data about the
project plan including the days and hours expected for each undertaking to finish is appeared in
the Gantt Chart.
Task
Task Name
Mode
Auto
initiation
Scheduled
Auto
Review project Notes
Scheduled
Auto
Create business case
Scheduled document
Auto
create Schedule
Scheduled
Auto
Obtain user signoff to
Scheduled proceed
Auto
requirements
Duration
Start
Finish
6.25 days
Mon 4/8/19
Tue 4/16/19
16 hrs
Mon 4/8/19
Tue 4/9/19
24 hrs
Wed 4/10/19 Fri 4/12/19
8 hrs
Mon 4/15/19 Mon 4/15/19 3
2 hrs
Tue 4/16/19
40 days
Tue 4/16/19 Tue 6/11/19 5
Tue 4/16/19
Predecessors
2
4
SECURITY SYSTEM UPGRADE PROJECT PLAN
Scheduled
Auto
Fact Find
Scheduled
Auto
Review Existing design
Scheduled
Auto
Design
Scheduled
Auto
Design user interface
Scheduled
Auto
Design Data Flow
Scheduled
Auto
Design User process
Scheduled
Manually
Prototype
Scheduled
Manually Create web Page
Scheduled prototype
Manually
Create iOS Prototype
Scheduled
Manually
Verification
Scheduled
Manually Review Solution
Scheduled architecture
Manually
Validate prototype
Scheduled
Manually
Finalize
Scheduled
Manually Determine
Scheduled recommendation
Manually Create Executive
Scheduled presentation
4
160 hrs
Tue 4/16/19
Tue 5/14/19
5
160 hrs
Tue 5/14/19
Tue 6/11/19
7
10 days
Tue 6/11/19 Tue 6/25/19 8
40 hrs
Tue 6/11/19
Tue 6/18/19
8
40 hrs
Tue 6/11/19
Tue 6/18/19
8
40 hrs
Tue 6/18/19
Tue 6/25/19
11
10 days
Mon 4/8/19
Fri 4/19/19
12
80 hrs
Fri 5/17/19
Fri 5/31/19
12
80 hrs
Fri 5/31/19
Fri 6/14/19
14
5 days
Mon 4/8/19
Fri 4/12/19
40 hrs
Fri 6/14/19
Fri 6/21/19
15
40 hrs
Fri 6/21/19
Fri 6/28/19
17
3 days
Mon 4/8/19
Wed 4/10/19 18
24 hrs
Fri 6/28/19
Wed 7/3/19
18
16 hrs
Wed 7/3/19
Fri 7/5/19
20
Figure 1: WBS showing the project plan of URCovered Mobile Application.
Project Monitoring and Control Plan
It is exceptionally fundamental for the project manager to follow the advancement of a
project. To guarantee that the project will be finished on schedule, inside the assessed spending
plan and will meet all the client necessities, the project manager will contrast the project plan and
SECURITY SYSTEM UPGRADE PROJECT PLAN
5
the current advancement. They will also set principles and will guarantee that they are pursued.
He will likewise guarantee that the undertakings on the basic way will be in any case finished on
schedule. The manager will confirm the consummation of the project achievements. They will
guarantee that the project plan is leveled out (Kerzner & Kerzner, 2017). The project manager
will lead a gathering meeting daily to track and plan about the project advance. In the
commencement venture of the project plan, for instance, making the business case archive is an
undertaking on the basic way. The deferral in this progression will postpone the commencement
stage.
Time line
The evaluated measure of time for execution of the project is 75 days. The begin date of
the project is Monday 8th April 2019 and it is relied upon to complete on Friday july 5th 2019.
The work breakdown structure with the measure of time for each undertaking is appeared in the
above Gantt Chart. The Gantt Chart appearing for the general project is appeared in the screen
capture underneath.
SECURITY SYSTEM UPGRADE PROJECT PLAN
Figure 2: Gantt Chart showing timeline for the overall mobile security application project.
6
SECURITY SYSTEM UPGRADE PROJECT PLAN
References
Burke, R. (2013). Project management: planning and control techniques. New Jersey, USA.
Kerzner, H., & Kerzner, H. R. (2017). Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
Tilley, S., & Rosenblatt, H. (2016). Systems analysis and design (11th ed.). Boston, MA:
Cengage Learning.
7
Running head: SECURITY SYSTEM UPGRADE PROPOSAL
Security System Upgrade Proposal
By
Anjyla Morrison
Master of Science in Informational Technology
With a concentration in Web Design
Southern New Hampshire University
1
SECURITY SYSTEM UPGRADE PROPOSAL
2
Security System Upgrade Proposal
Introduction
With the increased development in technology, there has been numerous issues with regards to
the security of the firm. The issue of cybercrime has affected the security of the firm. There is the
need therefore to come up with a better security system that will protect the company from
unauthorized access and invasion.
Background
Since the operation of the organization, there have been numerous activities, which has seen the
company grow. There is a lot of progress and company expansion, which means success in the
operations. The company has been into various business deals with other companies making it
one of the greatest performing in the region. The growth however has seen increased target to the
company’s data. In the recent past, there have been issues of attempted hacking to access the
company’s data. The hacking was attributed to a business deal that the company was about to
seal and therefore there were enemies who wanted to access that information. The issue of
security therefore has been a challenge as the current security system has failed (Brownlie, et al.
2017). The levels of security are weak and the hackers can easily access the company`s data.
There was also another instance where an employee shared company information with a
competitor giving them a chance to implement the projects before we did. The existing
information system gives rights to almost every employee to access company`s data and that is a
threat to the company. The proposal therefore is to have a security system upgrade that will see
the company operate under better standards. The security of the network will be affected by
implementing a domain to be controlled by an administrator.
SECURITY SYSTEM UPGRADE PROPOSAL
3
Problem Statement
The problem that needs to be solves is the weak security system. The network in the organization
gives access to crucial information to people who should not have access to it. There is also the
tendency of hacking attacks and some of which have been successful accessing the company`s
system. Access to information possesses a challenge since that means the competitors will know
the secrets of the company (Brownlie, et al. 2017). It’s a problem since the company`s security is
at risk and that means a downfall. The impact to the enterprise is that the competitors will know
everything that will be implemented in the company. Company`s confidentiality is also at risk
and that will challenge its success. If the hackers are able to access Company’s information, they
can use it against us and destroy our image to the outside world. The insiders may also have bad
intentions to the company and can use this information to execute revenge. It’s wise therefore to
implement a better security system to ensure the business success.
Audience
The audience for the system proposal becomes the management of the company and more so the
Information Technology team. The other members of the staff will also be notified about the
system. The different groups however will be approached differently since different attributes
will need to be discussed. To communicate with the management, there will be a meeting so to
explain every step of the proposal. The meeting will also allow me to explain the possible threat
the company is facing with the current security system. The management needs to know every
detail of the proposal and will therefore need more time for the meeting (Hill, et al. 2018). The
Information Technology team will also be included in the meeting since these are the people who
will do the implementation if the proposal goes through. The other team members or the
employees will be notified through emails and allowed to provide feedback about the proposal.
SECURITY SYSTEM UPGRADE PROPOSAL
The feedback will therefore be given to the management to look whether there is any resistance
to the proposal. If the proposal goes through however, there will be a common meeting for all
members of the enterprise to brief them on the need for the project and how well it should be
implemented. Everyone is part of it and therefore briefing each of them will be important.
4
SECURITY SYSTEM UPGRADE PROPOSAL
5
References
Brownlie, M., Hillier, S., & Van Oorschot, P. C. (2017). U.S. Patent No. 6,202,157. Washington,
DC: U.S. Patent and Trademark Office.
Hill, D. W., & Lynn, J. T. (2018). U.S. Patent No. 6,088,804. Washington, DC: U.S. Patent and
Trademark Office.
