Academic Integrity: tutoring, explanations, and feedback — we don’t complete graded work or submit on a student’s behalf.

Use the Requirements Analysis Matrix to create a draft list of functional and no

ID: 673453 • Letter: U

Question

Use the Requirements Analysis Matrix to create a draft list of functional and nonfunctional system requirements for a system inventory: (functional) outputs, inputs, processes, and (nonfunctional) performance and controls.

Consider the relationship between inputs, processes, and outputs. There must be at least an equal number of each. For example, let's say that we have a Student Information System and we want to print out a Student Transcript. The requirements might be as follows: Input: Transcript Request; Process: Create Transcript; Output: Student Transcript. Notice that both inputs and outputs are pieces of data and are named as nouns. Each begins with a singular noun. Also, notice that the process indicates some action that the system is taking. Processes are named beginning with a singular verb.

Explanation / Answer

Functional requirements

Functional requirements define what the system or application will do - specifically in the context of an external interaction (with a user, or with another system).When placing a new order, the system shall display the total cost and require confirmation from the user. That is a functional requirement; it describes a function of the system.

Non-functional requirements

Non-functional requirements are any requirements that don't describe the system's input/output behaviour. Note that we are still talking about requirements, not implementation details, so just because we're using the phrase "non-functional" doesn't mean that anything is fair game to put in that section.

The most common types of non-functional requirements relate to system operation (availability, continuity, DR), performance (throughput, latency, storage capacity), and security (authentication, authorization, auditing, privacy).

These are all cross-cutting concerns that impact every "feature" yet aren't really features themselves. they're more like feature metadata, helping describe not just whether the system does what it's supposed to but also how well it does it. Don't take that analogy too far, though - it's just an analogy.

Non-functional requirements are not subjective or hand-wavey, contrary to what some people here seem to be suggesting. In fact, they should actually have a hard metric attached to them NF requirements are also not implementation details or tasks like "upgrade the ORM framework".

Functionality -> Feature set capabilities, security, generality
Usability -> Human factors aesthetics, consistency, documentation
Reliability-> Frequency/severity of failure, recoverability, predictability, accuracy, MTBF
Performance-> Speed efficiency, resource usage,throughput, response time
Supportability-> Testability        Extensibility Adaptability      Maintainability Compatibility
Configurability-> Serviceability    Installability Localizability     Robustnes

Input-> Users will be required to input their username and password in order to access the system.The university central student record system will update student records regularly.There fore the student records in school student information system are monitored and refreshed which any change has been made.

system consists of several independent sub-systems.Till now,there is rarely a link between those data bases or
systems.They all operate separately with in the department.Each system possessesone or more functionalities for a particular school activity.Joining those sub-systems,they formal arge StudentInformationSystem,which covers most Requirements Analysis for a Student Information Systems activities.However,student is not a part of the local system user,which brings a lot inconvenience to them.

Input

Login Module
-Username
-Password

Student Information Module
-Student Name

Student Billing Module
-Amount
-Payment Type

Records Module
-Student Name
-Section

Reports Module
-Name
-Payment Mode

Audit Trail Module
-Name
-Action

Process
-Verify if Username and Password is valid
-Verify if the student name is registered in the system
-Verify if a user enters amount on payment
-Verify if the student name is in the system
-Verify if a student’s transaction is recorded in the system Search for the given value

Output
-Show the home page Show the student information
-Show billing confirmation
-Show transactions made by the student Show the transaction report
-Show the result .