ITC 508-OBJECT MODELLING
Added on 2022-09-08
11 Pages2149 Words17 Views
|
|
|
Running head: ITC 508-OBJECT MODELLING
OBJECT MODELLING
Name of student
Name of university
Author’s note:
OBJECT MODELLING
Name of student
Name of university
Author’s note:
ITC 508-OBJECT MODELLING 1
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
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
ITC 508-OBJECT MODELLING 2
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
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
ITC 508-OBJECT MODELLING 3
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.
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
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.
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
End of preview
Want to access all the pages? Upload your documents or become a member.
Related Documents
They provide the data of marketlg...
|11
|1856
|20
ITC 508 OBJECT MODELLING AND ITS SIGNIFICANCElg...
|17
|2937
|26
ITC508 - Airline Information Systemlg...
|15
|1605
|426
System Development for Human Resource Management | Deskliblg...
|14
|1739
|154
ITC 548 System Analysislg...
|11
|2592
|236
Object Modelling Assignmentlg...
|17
|1662
|22