Information System: User Requirements and Database System Design

This report delves into the critical aspects of information system design, emphasizing the significance of user requirement investigation in achieving interactive system success. It outlines a four-stage process for user requirement investigation, highlighting its role in understanding existing systems, identifying stakeholders, analyzing context and tasks, and uncovering problems and opportunities within multi-user databases. The report discusses different approaches like centralized and view-integrated methods, emphasizing stakeholder involvement through techniques like affinity diagramming to structure new systems. Furthermore, it distinguishes between functional and non-functional requirements, detailing interface, business, compliance, and security requirements, alongside qualities such as reliability, portability, efficiency, and security, crucial for system satisfaction and constraint management. This document is available on Desklib, a platform offering various study tools and solved assignments for students.

Running head: INFORMATION SYSTEM
Information System
Name of Student
Author’s Note

2INFORMATION SYSTEM
1. Evidence of the Uses of User Requirement Investigation to arrive final
requirements
The proper understanding of user requirements is a central part of any information system design
and also vital stage to achieve any interactive system success (Robertson and Robertson 2012).
In the process of user requirement investigation, 4 stages need to be maintained for any systems
are shown below.
Figure: Stages of User Requirement Investigation Process
(Source: Hind, Dunk and BlackBerry Ltd 2013)

3INFORMATION SYSTEM
With the help of the above mentioned user requirement investigation process in multiple user
view database system the below-mentioned points get cleared:
It helps to understand the existing system that is already implemented and about the problems
that are faced with this system. It also gets cleared about the stakeholders who use the particular
system.
With the user investigation process, it also helps to have the clear idea about both the context of
use analysis and task criteria analysis. After the task analysis of the implemented system, both
the encountered problems and opportunities are identified which helps to understand the needs of
multi-user databases (Ameller et al. 2013). Therefore, to implement the multi-user database
system, different database operators are interviewed to understand the existing system and the
needs of a new system which is going to be implemented.
In the multi-view databases system, different approaches like centralized approach and view
integrated approach are implemented which helps all the stakeholder to collect all information
regarding the users like needs, capabilities etc from one database and also numbers of database
operators can operate these information at a time (Hind, Dunk and BlackBerry Ltd 2013).
To evaluate and envision the implemented system, it is needed to brainstorm the associated
stakeholder by having proper idea generation phase of all problems. To do this, a technique
called affinity diagramming is implemented that helps to organize the proper structure of the new
system and allowing all participants to have the better understanding of the system from group
discussion (Robertson and Robertson 2012).

4INFORMATION SYSTEM
For the requirement specification, function/task mapping and requirements categorisation are
taking place which specifies system functionalities for a user of different performed tasks. It
becomes essential for the multi-view database system to ensure all functions of different
supported user types. However, in requirement categorisation, user requirements, usability
requirements and organisational requirements are considered to set objectives and prioritisation
of usability work. It also depicts the clear idea of understandability and functionalities of the
users. To achieve the organizational requirement, the criteria setting and proper prioritisation are
needed which helps to understand the acceptance criteria by performing pre-tests of the system
before final implementation.
2. The system’s Functional and Non-functional requirements of a database
system (multiple views)
There are various functional and non-functional requirements of the multiple user database
systems. Functional requirements explain the behaviour of a system that supports to achieve
activities, tasks and different user goals. Some of the functional requirements discussed the
interface requirements, business requirements, compliance requirements and security
requirements. It also discussed about the description of entered data in the system, various
performed operations, different workflows of any system and the illustration of all outputs and
various system reports (Chen et al. 2013). The functional requirements of multiple database
systems mention about different business rules, reporting requirements, transactional
cancellations and adjustments, reporting requirements etc.
On the other side, non-functional requirement includes various qualities and constraints. The
system qualities are the characteristics of a system which the stakeholder cares about and also

5INFORMATION SYSTEM
affect the satisfaction of the system degree level (Khan et al. 2016). However, the constraint is
one of the restrictions of degree of freedom maintained to offer a solution. Some of the non-
functional requirements are:
Reliability: it discusses about the system ability for consistent behaviour in an user-acceptable
way to operate within the system environment.
Portability: It discussed about the degree which explains about software running in one
environment can be converted to run on another platform (Khan et al. 2016).
Efficiency: It refers to the system of a software system that mainly uses limited computational
resources like disk space, memory, communicational channels, and CPU cycles. It also gets
characterised based on the dimension numbers (Robertson and Robertson 2012).
Security: it mainly defined about the security attributes of different systems that mostly restrict to
access various features to protect the privacy features of entered data (Khan et al. 2016).
It also described about different properties of both the domain and system. However, it even
phrased as both negative assertion and constraints.

6INFORMATION SYSTEM
References
Ameller, D., Ayala, C., Cabot, J. and Franch, X., 2013. Non-functional requirements in
architectural decision making. IEEE software, 30(2), pp.61-67.
Chen, M., Tan, T.H., Sun, J., Liu, Y., Pang, J. and Li, X., 2013, October. Verification of
functional and non-functional requirements of web service composition. In International
Conference on Formal Engineering Methods (pp. 313-328). Springer, Berlin, Heidelberg.
Hind, H. and Dunk, C.A., BlackBerry Ltd, 2013. System and method for synchronizing data
records between multiple databases. U.S. Patent 8,468,127.
Khan, F., Jan, S.R., Tahir, M., Khan, S. and Ullah, F., 2016. Survey: Dealing Non-Functional
Requirements at Architecture Level. VFAST Transactions on Software Engineering, 9(2), pp.7-
13.
Khan, S., Babar, M., Khan, F., Arif, F. and Tahir, M., 2016. Collaboration Methodology for
Integrating Non-Functional Requirements in Architecture. the Journal of Applied Environmental
and Biological Sciences (JAEBS), 6, pp.63-67.
Robertson, S. and Robertson, J., 2012. Mastering the requirements process: Getting
requirements right. Addison-wesley.