This document discusses functional and non-functional requirements for a mobile-ready learning management system (LMS). It provides 20 examples of different types of requirements, including the ability to access course content on mobile devices, student tracking features, security measures, language and accessibility options, and reporting capabilities. Requirements cover areas like functionality, performance, usability, look and feel, security, portability, and more. The document aims to outline key requirements for an LMS to ensure it can meet various technical and user needs.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
101 views4 pages
0 - New FR and NFR
This document discusses functional and non-functional requirements for a mobile-ready learning management system (LMS). It provides 20 examples of different types of requirements, including the ability to access course content on mobile devices, student tracking features, security measures, language and accessibility options, and reporting capabilities. Requirements cover areas like functionality, performance, usability, look and feel, security, portability, and more. The document aims to outline key requirements for an LMS to ensure it can meet various technical and user needs.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4
TM354 – Software Engineering – MTA Revision 1
Software engineering
TM354 MTA SAQ
FR and NFR TM354 – Software Engineering – MTA Revision 2
Non-Functional Requirements 1
6 TM354 – Software Engineering – MTA Revision 3
Examples for FR and NFR
1 Ability to use mobile devices to access course content and all NFR operational or course tools are available in the mobile client portability 2 Available tools in the mobile client have the same functionality as NFR usability or the web version performance 3 The LMS is mobile-ready when using the web version through NFR portability smart phones 4 Detailed student system tracking available (log in, log out, last NFR security accessed, IP address) 5 Detailed student tracking available for each course tool (How many Functional requirement discussion posts were read; how long they spent on each question) 6 Ability to set different assessment time frames for individual functional requirement students (e.g., students with disabilities who need more time) 7 Ability to provide a variety of feedback types (e.g., text, audio, NFR look and feel video) for assignments, discussions, other student activities 8 Ability to add audio/video components to quizzes or exams NFR look and feel 9 Ability to add captions to assessments functional requirement 10 Concurrent user capabilities performance 11 The system protect confidential data and session activity both NFR security within the application and in transit 12 Data and session activity are encrypted NFR security 13 The system supports mass notifications for users during Functional requirement emergencies 14 Learners must be able to access the LMS and its content in their NFR cultural native language and learner interface available in multiple languages 15 The system administrator must be able to configure permissions Functional requirement 16 The LMS must support specific country regulations related to NFR legal security and accessibility 17 The LMS must be easily scalable to handle increasing numbers of NFR performance users and content to keep in step with the growth of the organization. 18 Methods of data exchanges and encryption supported Functional requirement 19 Help Desk options available for students such as email, chat etc NFR usability 20 Login encryption/validation with password and user IDs determine Functional requirement secure authentication 21 Configurable security settings (password characteristics) NFR security 22 Automated system to help students who have forgotten passwords Functional requirement TM354 – Software Engineering – MTA Revision 4
23 Built in wizards to guide administrators on difficult tasks usability
24 Links to other training sites or resources (Online Resources) Functional requirement 25 System is modular, allowing deployment of only required operational functionality (turning on or off features and modules) 26 Integration with virtual meeting/classroom tools such as WebEx Functional requirement 27 Ability for a new learner to request an account Functional requirement 28 Ability for users to select specific language culture 29 Create, change and view user information/profile and user can Functional requirement belong to multiple user groups 30 Enroll users in courses (individual, groups/batch) and mass Functional requirement registration for multiple learners to one course 31 Can disable a course without removing it from the LMS Functional requirement 32 Possible to conduct online tests and ability to set passing scores for Functional requirement tests 33 Real-time reporting available and ability to export report data portability 34 Automated reminder notices via email Functional requirement 35 Ability to send emails to user's email address listed in their profile Functional requirement and ability to send emails to selected users 36 Provides full synchronous and synchronous Interaction. Functional requirement 37 Provides collaboration features common to both synchronous & look and feel asynchronous environments, such as video + visual presentation (example: PowerPoint) 38 Ability to convert training materials to other formatting and culture languages 39 Provides for links to external sources of information and course Functional requirement evaluations 40 Profiles contain basic personal information, training history, job political information, education levels, skills, training preferences, supervisor's name, tutor’s name