System Analysis and Design of Vermont Social Service Information System

1
Name
University
Course
Instructor

2
Abstract
Vermont is a social service department that is responsible for providing services for children,
young people, and their families, and for adults who may need assistance in their daily routine
because of their age or disability. This report is an analysis of the requirements of Vermont
social service information system. It identifies the entities, their attributes, and the requirements
from the case study presented. The requirements are then transformed in to processes by
designing diagrams depicting the actors in the system, the processes they undertake in the
system, and the process controls in place to ensure task goals are efficiently achieved.

3
Table of Contents
Abstract....................................................................................................................... 3
Introduction.................................................................................................................. 5
Requirements................................................................................................................ 5
Design.......................................................................................................................... 7
Conclusion.................................................................................................................. 20
References.................................................................................................................. 21

4
Introduction
This report entails the system analysis, design, and architecture of Vermont council social
services information system. It analyses the functional and the non-functional requirements of
the system by elaborating and giving instances. The functional requirements are client record
keeping, employee record keeping, client registration form, client service requisition platform,
client record access requisition, residential and nursing home inspection, and comments or
complaints’ placement platform. The non-functional requirements are functionality, usability,
reliability, performance, and security. The requirements specified and the flow of processes
involved is depicted using the design diagrams; use case diagrams, use case scenarios, sequence
diagrams, activity diagrams, state diagrams, and the class diagrams. Use case diagrams, use case
scenarios, sequence diagrams, and activity diagram depict the flow of events in the information
system. The state diagram depicts the changing states in the system whereas the class diagram
shows the entities and their attributes in the system. The report also shows how the design
patterns could be applied and ends with a conclusion.
Requirements
Functional requirements
These are the actual tasks that a system performs or the tasks that a user can complete when
using a system (Mahmoud, & Williams, 2016). The following are the functional requirements of
Vermont council social services information system:
To record the names, addresses, contact details, status of a client and the social worker assigned
to this client.
To record the names, address, and contact details of all the social workers in Vermont council
social services department
To capture all the payments made by clients for services offered by Vermont council social
services department
To record and monitor staff workloads for every social worker and generating workload reports
for the manager.
To capture client’s assessment results

5
To enable all clients to register complaints and comments on the comments page.
Registration and inspection of residential homes or nursing homes by the chief executive of
Vermont Council
Non-functional requirements
These are requirement that are based on the design and architecture of systems. These
requirements often act as a measure of system quality. The following are the non-functional
requirements;
Functionality. This is the ability of a software to be able to perform all the functions it was meant
for (Filieri, Ghezzi, & Tamburrelli, 2012). In this case scenario, the system should be able to
capture all the client and employee records, payment details, residential homes and nursing home
registration details, and capture inspection information on clients, residential homes, and nursing
homes.
Usability. Refers to the ability of a system to be used easily by users. It should also be easy to
learn how to use the system to perform several tasks to completion. The system should be highly
interactive, containing all the contents of an interactive design; well labelled, appealing colors,
and error handling (Ameller et.al; 2012). For instance, on the comments and complains page, the
section where to enter either comments or complains should be distinct and well labelled to
enhance the process of capturing comments.
Reliability. This is the trust the system earns from its users after a long period of usage. For a
system to be trusted, it should have enabled users to perform their tasks with great accuracy,
efficiency, and effectiveness. The system should also have exhibited little or no faults and
failures during its runtime (Slankas, & Williams, 2013).
Performance. Refers to the efficiency of a system to perform certain activities. Is the system
stable when performing tasks? What is the response time when performing a task in the system?
What is the system’s throughput? What resources does the system consume when performing

6
certain tasks for a user? These resources can be the memory space, central processing unit’s time
schedule and the power consumption of the system (Khan et.al; 2016).
Security. Refers to the design measures in place to ensure the safety of the system, files, data,
and information from internal and external attacks (Behutiye et.al; 2017). For Vermont council
social service department, confidential information about clients is concealed from unauthorized
users through the use of a password system. The update of client data can only be authorized by
the social worker assigned to the client or the supervisor who assigned the social worker to the
client. There is the presence of user access levels where users are allocated privileges in the
system.
Design
Use cases
Service requisition use case