ITC 508 - Object Modelling Report: Fynapa System Elaboration

This report provides an in-depth analysis of the object modelling for a new information system designed for the Fynapa Company, an international digital data collection firm specializing in market research. The report begins by outlining both functional and non-functional requirements for the new system, emphasizing aspects like usability, security, reliability, performance, availability, and scalability. Following the requirements section, the report presents a use case diagram illustrating the interactions between various actors (clients, business researchers, system admins, and panellists) and the system's main functionalities, such as registering, logging in, creating surveys, and viewing results. A detailed use case description is provided for the "Create new survey" scenario. Furthermore, a domain model class diagram is included, depicting the classes and attributes involved in the system, such as Clients, Business researchers, Survey, Permission, Panelists, User, and Registration, along with their relationships. The report concludes by summarizing the benefits of the new system and its ability to streamline business functions, improve data collection, and enhance the client experience. The report adheres to the specified guidelines, includes relevant diagrams, and is properly cited using APA 6th edition style.

Running head: ITC 508-OBJECT MODELLING
OBJECT MODELLING
Name of student
Name of university
Author’s note:

1
ITC 508-OBJECT MODELLING
Table of Contents
Introduction....................................................................................................................2
Requirements..................................................................................................................2
Functional requirements.............................................................................................2
Non-functional requirements.....................................................................................3
Use case diagram............................................................................................................5
Use case description.......................................................................................................6
Domain model class diagram.........................................................................................8
Conclusion......................................................................................................................9
References....................................................................................................................10

2
ITC 508-OBJECT MODELLING
Introduction
Fynapa is an international company that specialises in digital data collection. They
provide the data of market research to the clients. The present information system in the
company is inefficient in providing the adequate services to the company and it does not
allow the business to provide the most optimised services to the clients. This report provides
a detailed description for the new system that is being implemented in the Fynapa Company.
The requirements from the system has been clearly mentioned in this report. Fully developed
use case description has been created from the use case diagram has been provided in this
report. A class diagram has been provided in the report that illustrates how the system would
be used by various people.
Requirements
Functional requirements
 Clients and business researchers are required to be signed up in the company for
availing the facilities
 System must have a registration form that could get all the essential information from
the customers
 Customers should be able to create their surveys
 Clients should be able to get a preview of the survey that has been formed
 Client should be able to view the survey before publishing the survey
 The results of the survey should be provided to the clients
 Response analyser should be chosen by the clients
 Clients could view the survey reports
 List of the live surveys should be present for the clients as well as the invoice of
surveys must be available for the clients

3
ITC 508-OBJECT MODELLING
Non-functional requirements
Non-functional requirements mainly describes the methods by which any system is
required to behave and establish the constraints of the functionality. The major non-
functional requirements of this system of Fynapa are:
Usability: The aspect of usability mainly describes how problematic it could be for
any user to efficiently learn as well as operate the system of Fynapa. The usability
requirements of the Fynapa system are efficiency to use, low understood workload and
intuitiveness. The efficiency of using mainly describes the average time that is taken for
accomplishing any goal of the users, how many tasks could be completed by the users
without any guidance and amount of transactions that could be done without errors
(Alkhateeb et al., 2017).
Security: The security requirements of the Fynapa system mainly ensures that
software has been protected from any kind of unauthorised access to system as well as the
stored data. The various levels of authorisation as well as authentication is considered across
the various roles of users (Azar & Vaidyanathan, 2015).
Reliability: The system of the Fynapa organisation should be significantly reliable in
using. Reliability mainly defines the probability of working of the system without any kind of
failure for any provided time period. The reliability mainly decreases due to the presence of
bugs in code of the system, any hardware failures or even the problems with any other
components of the system (Bullo and Lewis, 2019). For measuring the reliability of the
software of the company, the proportion of the operations, which have been accomplished
correctly could be calculated or even the average time period this system runs without
worsening could be tracked for determining the reliability of the system in Fynapa.

4
ITC 508-OBJECT MODELLING
Performance: The performance of the system in Fynapa could be described as the
attribute of quality that helps in describing effective responsiveness of system to the various
kinds of user interactions. The system should provide the accurate result for the queries that
are made by the users on the system.
Availability: The aspect of availability has been gauged by period of the time that the
functionality of the system as well as the services have been made available for using with all
the operations (Dennis, Wixom & Roth, 2018). The system should be available for the users
even during the period of the maintenance. The clients could create their surveys anytime of
the day and get the appropriate results (Dennis, Wixom and Tegarden, 2015). In any situation
when the system would not be available for the users, the proper notification should be
provided to the users that notifies the unavailability of services from the system of Fynapa.
Scalability: The scalability requirements mainly describes how this system should
grow deprived of any negative influence on the performance (Pedrycz, 2016). The system of
Fynapa should serve more and more users, processing increased data and executing increased
transactions. There are several implications of scalability on the software and hardware. The
system should be able to perform the transactions and allow increased users to avail all the
services that are provided at any point of time.

5
ITC 508-OBJECT MODELLING
Use case diagram
Figure 1: Use case diagram
Source: (Created by author)
In this diagram, the use cases and the actors of new system in this company has been
illustrated. The main use cases of the system are Register, Login, Input information, View
survey availability, Notification of new survey, View payment invoice, View survey result,
Prepare report, Preview report, and Create survey. With the proper utilisation of the new
system in the company, the clients could register, login, information their personal
information, view the availability of survey, view the survey result, preview the report, and
create survey. The system admin mainly uses the system for login, notification of new
survey, prepare report and create survey for the clients. The business researcher mainly uses

6
ITC 508-OBJECT MODELLING
the system for registering, login, input information, view the availability of survey, view the
survey result, preview the report and create survey. The main uses cases of the panellists are
registering, login, input information, notification of new survey, view the payment invoice,
and prepare report.
Use case description
Use Case Name: Create new survey
Scenario:
Clients or business researchers creates a new survey that is required by
them
Triggering Event:
Client logs in into the system and then provides all information about
survey in the system
Brief Description:
The clients of the company registers in the system using their personal
information and creates an account. Then they provide the specifications of
the survey that is required by them and selects the option “create survey”.
Clients gain the notification of successful creation of survey in the provided
email.
Actors: Clients
Stakeholders: Members, business researchers, system admin, clients
Preconditions:
Clients and business researchers should be registered in the system and
successful login should be done in the system of Fynapa for creating the
survey
Post conditions:
Survey has been successfully created and the successful creation of survey
has been provided in the provided email.

7
ITC 508-OBJECT MODELLING
Flow of Activities: Actor System
1. Clients provide their
personal details in the
system for registering.
2. Clients provide their
login credentials in the
system
3. Clients provide the
survey specifications in the
form provided by the
system
4. Client logout from the
system.
1. System verifies the information and then
notifies the client of successful registration.
2. System verifies the login credentials and
then returns the homepage of the company for
creating the survey
3. System verifies the information of the
survey and returns the confirmation of survey
creation.
4. System returns the confirmation of
successful logout of the clients.
Exception Conditions:
The login credentials are invalid.
Survey is not created.

8
ITC 508-OBJECT MODELLING
Domain model class diagram
Figure 2: Domain class diagram
Source: (Created by author)
In this diagram, the domain class diagram of the new information system of the
company has been provided.
Class Attributes
Clients clientName, clientID, clientAddress, clientGender, clientPhone,
clientDOB, clientEmail
Business
researcher
researcherName, researcherID, researcherAddress,
researcherGender, researcherPhone, researcherDOB,
researcherEmail

9
ITC 508-OBJECT MODELLING
Survey surveyName, surveyLocation, surveyDate, surveyDesc, surveyTime
Permission permissionTitle, permissionID, permissionModule, permissionDesc
Panelists panelistName, panelistID, panelistAddress, panelistGender,
panelistPhone, panelistDOB, panelistEmail
User userName, userID, userAddress, userPhone, userEmail
Registration registrationName, registrationID, registrationType, registrationDesc,
registrationNumber
In this class diagram, the working of the various classes of the system has been
illustrated. The main classes are the clients, business researchers, panellists, permission, user
and the registration. Any client could request several surveys from the system. One panellist
can participate in several surveys. One user can have only one registration. Any particular
client can be panellist but not all clients are not panelists.
Conclusion
Therefore, it could be concluded from the above discussion that the new information
system in the company could provide several benefits to the clients and provide simplified
methods of gaining the results of the surveys. There are several functional requirements from
the system of the company and the main non-functional requirements from the system are the
availability, reliability, scalability, security, performance and usability. The main functions of
the business could be significantly improved with the introduction of the new system.

10
ITC 508-OBJECT MODELLING
References
Alkhateeb, A., Nam, Y.H., Rahman, M.S., Zhang, J. and Heath, R.W., 2017. Initial beam
association in millimeter wave cellular systems: Analysis and design insights. IEEE
Transactions on Wireless Communications, 16(5), pp.2807-2821.
Azar, A. T., & Vaidyanathan, S. (Eds.). (2015). Chaos modeling and control systems
design (Vol. 581). Germany: Springer.
Bullo, F. and Lewis, A.D., 2019. Geometric control of mechanical systems: modeling,
analysis, and design for simple mechanical control systems (Vol. 49). Springer.
Dennis, A., Wixom, B. H., & Roth, R. M. (2018). Systems analysis and design. John wiley &
sons.
Dennis, A., Wixom, B.H. and Tegarden, D., 2015. Systems analysis and design: An object-
oriented approach with UML. John wiley & sons.
Pedrycz, W., 2016. Granular computing: analysis and design of intelligent systems. CRC
press.