ROBLOX SEX 27
Studied by 3 people
Learn
Practice Test
Spaced Repetition
Match
Flashcards1/21
There's no tags or description
Looks like no tags are added yet.
Name | Mastery | Learn | Test | Matching | Spaced |
|---|
No study sessions yet.
22 Terms
Requirement
A statement of some behavior or property that the software must exhibit in order to fulfill the product vision
Functional requirement
A statement about what the software must do.
Non-functional requirement
A statement about how the software must behave
Product vision
A high-level description of the problem to be solved and the solution to be developed
Efficiency
How much memory or CPU the software must use software must be.
Reliability
How rarely the software must crash or produce incorrect results
Compatibility
What other software or hardware the software must work with
Availability
What percentage of the time the software must be available
Security
The level of protection the software must provide against unauthorized access and other security threats
Usability
The ease of use, pleasurability, and learnability of the software.
Scalability
How well the software must perform as the number of users or the amount of data increases
Maintainability
How easy it must be to fix bugs, add features, or otherwise modify the software
Portability
How easy it must be to move the software from one platform to another
Stakeholder
Anyone who has an interest in the software
Requirements document
A formal document that describes the requirements of the software
User story
A lightweight way of documenting requirements, typically consisting of a short, informal description of a feature of the software, written from the perspective of the end user
Use case
A lightweight way of documenting requirements, typically consisting of a short, informal description of a feature of the software, but detailed enough to be used as a basis for testing
User interface mockup
A simpler and less expensive version of a prototype, used to help stakeholders understand what the software will look like and how it will behave
Storyboard
A series of pictures or drawings that show how the software will be used
Diagram
A visual representation of how the software will work behind the scenes
Requirements review
The process of ensuring that the requirements are correct, complete, consistent, and unambiguous
Performance
How fast the software must be