2016
DOI: 10.7763/lnse.2016.v4.242
|View full text |Cite
|
Sign up to set email alerts
|

The Most Important Functional and Non-Functional Requirements of Knowledge Sharing System at Public Academic Institutions: A Case Study

Abstract: Abstract-This qualitative study aims to explore and describe the most important functional requirements (FR) and non-functional requirements (NFR) of knowledge sharing system (KSS) used at a Malaysian public academic institution. The strategy used is a single case study which aims to gather deeper insights on the requirements of the KSS. Data were collected through semi-structured interviews. A total of fifteen renowned academicians were interviewed. Content analysis method was used to extract the requirements… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
4
0

Year Published

2017
2017
2024
2024

Publication Types

Select...
4
2
1

Relationship

0
7

Authors

Journals

citations
Cited by 8 publications
(4 citation statements)
references
References 24 publications
(30 reference statements)
0
4
0
Order By: Relevance
“…The study includes both functional and non-functional requirements. The functional requirements indicate what a user needs from the system, while the non-functional requirements refer to the system architecture (Alsaleh and Haron, 2016). The functional requirements for developing this prototype cover:…”
Section: Methodsmentioning
confidence: 99%
“…The study includes both functional and non-functional requirements. The functional requirements indicate what a user needs from the system, while the non-functional requirements refer to the system architecture (Alsaleh and Haron, 2016). The functional requirements for developing this prototype cover:…”
Section: Methodsmentioning
confidence: 99%
“…Following discussions with CH designers during a focus group, the outcomes of the literature review have been evaluated and a number of prototype screens (mockups) have been generated, as shown in Figure 1. The objective was to define how information is organized, structured, and presented in order to achieve the most suitable GUI, generating another set of functional and non-functional user requirements [17][18][19]. The proposed system's final functional (FR) and non-functional (NFR) requirements are presented in Tables 1 and 2, respectively.…”
Section: Requirement Analysismentioning
confidence: 99%
“…Functional requirements define the result the system is expected to achieve and deliver to the users (Alsaleh & Haron, 2016). Automated information capture, federated search and retrieval, collaborative tools, hierarchical file indexing and classification, storage and archival method, automated workflow, security, audit trail, and support and administer compliance are all functional requirements of an EDMS (Laserfiche, 2020).…”
Section: Introductionmentioning
confidence: 99%