Information Technology (IT) is increasing rapidly across the globe. It spreads its business in many sectors such as government, finance, healthcare, telecommunications, and many more (Taylor, Bogdan, & DeVault, 2015). Over the past 10 years, IT enhances their business settings in various areas. The Business Analyst meets business necessities from numerous fields in the company. It interprets them into well-designed system design specifications, which can be fruitfully performed by Information Technology development teams. This is a vital role in the software or system development life cycle.
Data Quality Diagram
As per the given case study is given, Fynapa is a global digital data collection organization. The company provides market research imminent to its customers across the Globe. The customers of Fynapa are either solo researcher carrying out research containing data collection through various inspections. The company provides products, services, marketing, as well as perceptions. Fynapa shows off an internationally distributed as well as extremely diversify panel. The panel contains people from several classes of demographics as well as professions. As a panelist of Fynapa, users have to sign up to their website by giving several required information. Those are an email address, gender, date of birth and residential address. After registration, they can access as per their requirements. But as researchers or businesses must register themselves as well as login to the Fynapa client website. Users enlist their records on their websites to create as well as to conduct surveys just by giving the user’s mail ID. After successful registration clients can access the website and create a new survey. The company has a target in each survey as per the business rules as well as the area of research. The pricing methodology of the business is a little diverse. The cost is based on the base survey listing, survey length, questions type, and the number of replies needed.
1. Functional and Non-Functional Requirements
Function Requirements
The project’s requirements of the company need to be constructed and well organized in nature. It should be presented in a balanced form and also it requires being understandable. The most importantly projects requirements are not compromised in the middle phase of the projects. The Functional Requirement of a company can be described as the formal statement of the applications. It includes some purposes. Those purposed lies in the purpose or requirements of the contract (Ameller et al., 2015). The developer of any company needs to agree to provide the capabilities that ate specified in the fictional requirements. The client will then find it satisfactory ID they satisfy all the capabilities that are specified in the functional requirements. The functional requirements of any company include the intended behavior of the company. This behavior depends on the providing service, functionalities of the company. The functional requirements of the company can be described by some specific points.
The company requires all the detailed data lists and descriptions that are needed to be put into the system requires a detailed description of the operations as well as workflows that need to be performed, & Requires the descriptions of system reports as the outputs. The functional requirements are intended to be interpreted by the general clients of the company. Also, there is some major functional requirement of the company. The company requires their proper business rules, correction of their services as well as the transaction corrections, maintain administrative function, maintain all the track reports the audits, maintain all the external interfaces, requires all the reporting requirements, collect the historical data and do a list of the legal regulatory requirements.
Non-functional Requirements
The definition of a non-functional requirement is the superiority attribute of an application system. They symbolize a set of principles used to judge the precise operation of a system such as a website development and the loading time of that website. It is mandatory to make sure the usability as well as the effectiveness of the complete software scheme. Without fulfilling the needs of the non-functional era, the system can fail to please user requirements. This requirement permits users to inflict constraints or limits on the design. This design of the system based on various agile backlogs. Based on the scenario, there are lots of non-functional requirement examples are available. Those are;
· Users should edit the initially assigned login password on the client’s website. After a successful login, the initial phase ought to never be recycled.
· The staff never permitted updating their data based on wages. This type of attempt ought to be enlisted to the admin of the security section.
· All users’ unsuccessful attempts to access an article of data. This data shall be saved on an assessment track.
· The company’s website must be accomplished enough to regulate nearly 20 million users.
· The things that ought to be audited: Credential data, the export of limited technologies, academic belongings privileges, etc.
· Main requirements are Performance, Scalability, Capacity, Availability, Reliability, Recoverability, Maintainability, Serviceability, Security, Regulatory, Manageability, Environmental, Data Integrity, Usability, and Interoperability.
2. Identify Use case and its Diagram
In the use cases of any company, a business actor plays a specific role. In this company, there are two types of clients. Either they are research or they conduct their research that involves data collections or businesses that need to collect the data as per their products, services, and marketing strategies (Lano, 2017). All the Survey participants are known as the panelists. On the website of the company, anyone can be registered as panelists. For registering as panelists any client needs to sign up at the Fynapa consumer website and they have to provide their basic information. Those basic information requirements are their active email address, their gender, their date of birth as well as their permanent residential address. After completing the registration process the clients are called panelists and they become the registered client of the company. After completing the registration process all the clients have to provide additional information. The company’s pricing methodology that is involved in some prospect but that can be considered as fair. The cost listing of the company contains such steps. Firstly, there is a base survey listing cost. This survey listing cost is applicable throughout the survey. It is not dependent on the process length of the survey. After that, there is always a specific amount or cost that needs to conduct the survey. This kind of cost is dependent on the length of the survey. As usually it can be said that is the length of the cost is too long then the cost amount will increase and if the survey ends within a limited length then the cost is less than previous.
System Development Life-Cycle
For this kind of cost listing, several types of question and responses are a need that includes in the survey. In every survey the company needs the number of clients; they are described as the client business requirements. Business research requirements can be described as the validation of the survey as every survey has its expiry (Chen, Ramamurthy, & Wen, 2015). Every client needs the best result from the company. Some of those only want ID-verified panelists to get the most accurate results. The company provides an email notification policy. The clients are notified while the company has a sufficient number of responses that the client required. That number of responses depends on the budget of the client. The panelists also got a notification for a new survey. Through the notification, they got the link of the survey if the survey is still active. Those links expire after the expiry date of the survey.
The panelists' accounts have been credited if they complete a successful survey. The panelists need to earn a threshold amount of reward first after that the further rewards they can redeem & that threshold value is depending on the place of the company. Those panelists who get rewards have to provide their mobile number to verify their current location. They get redemption methods through bank cheque, direct credit to the bank account, or gift vouchers, etc. hat method is also depended on the country of payout.
Use Case Diagram
Check InSystem Boundary Customer Website Private
Personal Info.
Optional Info.
Survey option
Admin use
Email ID
Check InPanelist Backend
Client Website
Backend
Researchers
Admin Users
Backend
3. Most Important Use Case
As per the scenario, the most important use case is the verification process. Until a user is not successfully registered they do not get permission to move forward for the survey. Verification processes are one of the important things in every scenario of the World. It happens everywhere in our everyday life. The definition of verification is that the action of evaluation, examining, testing, verifying, auditing, or otherwise setting up as well as documenting. All things are based on stuff, processes, services or credentials that conform to particular necessities. Functional verification is one of the steps that ensure the attributes as well as the execution of the design at numerous concept levels. These levels are in concurrence with the design intent.
As per the business case, a panelist of Fynapa, users have to sign up to their website by giving several required information. Those are an email address, gender, date of birth and residential address. After registration, they can access as per their requirements. But as researchers or businesses must register themselves as well as login to the Fynapa client website. Users enlist their records on their websites to create as well as to conduct surveys just by giving the user’s mail id. After successful registration clients can access the website and create a new survey. So both the cases users have to register first then they will process for the next step.
This verification process is based on cybersecurity. The revelation of manufacturing amenities to cybersecurity intimidations has never been advanced. There are lots of essential actions for the investigations of cybersecurity risk are available. Top 3 are High-Level Risk Assessments, Detailed Risk Assessments, as well as Security Level Verification. The Verification of Security Level is the 3rd cybersecurity investigation that reviews the theoretical network design. Its countermeasure is to use to verify that it sufficiently alleviates the cybersecurity risk, which can be arises in the verification phase (Safa, Von Solms, & Furnell, 2016).
Verification Inputs
The verification of the security level is carried out throughout the design phase. Along with the design information, the main inputs are from the top-level as well as the comprehensive risk evaluations. The risk assessments deliver a comprehensive zone. The risk assessments also provide a conduit diagram. It is used for documenting the edge devices to slice higher security zones. This is also useful for decided security level missions for each of these areas of business. These risk targets are used to assess if a current implementation fulfills the security level needed for a region.
Object-Oriented Methodology of the Company
Target
The company utilizes the granular information as their target is to obtain the countermeasure effectiveness also they include the relevance. This design of security has been accepted as that limits the overall risk of the company. That measures the cybersecurity and restricts unauthorized users for data security. They also need to meet all the systematic capabilities of the cybersecurity to achieve the optimal security level. The company’s security level verification represents the security lifecycle of the company (Holzbaur, Ross, & Rothrock, 2016).
4. UML Domain Model Class Diagram
API
Applicat
ion
System
Organization
Users
Server
Checking
Read/Write
Personal Info
Registratio
n
Survey Option
Type of Users
Database
Implementation
Class
Conclusion
In this paper, we have prepared the project requirement reports that included the functional as well as non-functional requirements. All the process of the customer and data handling techniques of the company has been describing. Here Clients are either researchers or business persons who want their responses. A proper and well-structured process of their business strategy is illustrated. Here we create the company’s use case and use case diagram and choose the most important use case. We have described the company’s security. Then we draw the UML Domain Model Diagram of the company. Object-oriented methodology; system development life cycle, as well as a quality diagram of the company, has also been described.
References:
Ameller, D., Franch, X., Gómez, C., Araujo, J., Svensson, R. B., Biffl, S., ... & Moreira, A. (2015, August). Handling non-functional requirements in model-driven development: an ongoing industrial survey. In 2015 IEEE 23rd International Requirements Engineering Conference (RE) (pp. 208-213). IEEE.
Chen, Y. A. N., Ramamurthy, K. R. A. M., & Wen, K. W. (2015). Impacts of comprehensive information security programs on information security culture. Journal of Computer Information Systems, 55(3), 11-19.
Holzbaur, E., Ross, J., & Rothrock, T. (2016). Why Aren’t All Pro/Coa Clinical Trials Using Electronic Data Collection To Optimize Data Integrity And Patient Experience?. Value in Health, 19(3), A105.
Lano, K. (2017). Agile model-based development using UML-RSDS. CRC Press.
Safa, N. S., Von Solms, R., & Furnell, S. (2016). Information security policy compliance model in organizations. computers & security, 56, 70-82.
Taylor, S. J., Bogdan, R., & DeVault, M. (2015). Introduction to qualitative research methods: A guidebook and resource. John Wiley & Sons.
Analysis
Design
Implementation
Maintenance
Planning
Identity
Management
Environment
Governance
Risk Assessment
Risk Management Strategy
Protect
Awareness control
Awareness training
data security
Maintenance
Protective Technology
Detect
Anomolies and events
Security Monitoring
Detection Process
Respond
Recover
response planning
Communication
Analysis
Mitigation
Improvements
Recover Planning
Improvements & communication
Data Quality Diagram
Completeness
Validity
Accuracy
Consistancy
Intigrity
Timelyness