I need a good answer for this Thank you 1 During the analysi

I need a good answer for this. Thank you!

1. During the analysis of requirements, we often have to categorize and then prioritize items. Discuss why we would need to do these activities.

Solution

Requirement anaysis is the fundamaetal and key phase of softare developement life cycle, in this phase itself, system should clearly difined as this will be useful for verificqation and validation reference . if any thing assumed wrong totol work done up to any phase from requirement analysis.

from tracebility matrix constrcted during requirement analysis, we have to categirize and then prooritize items.

reason to do categirization of items in requirement analysis phase:

Software Requirements

in the requirement elicitation phase We should understand what kind of requirements may arise and what kinds of requirements are expected from the software system.

software requirementscan be categorized in two categories:

Functional Requirements

these Requirements are related to functional aspect of software ,

They define functions and functionality within and from the software system.

EXAMPLES -

Non-Functional Requirements

Requirements are not related to functional aspect of software.They are implicit or expected characteristics of software, which users make assumption of.

Non-functional requirements include -

Requirements are categorized logically as

While developing software, ‘Must have’ must be implemented, ‘Should have’ is a matter of debate with coustmers and negation, whereas ‘could have’ and ‘wish list’ can be kept for software updates.

User Interface requirements

UI is an important part of any software or hardware or hybrid system. A software is widely accepted if it is -

User acceptance majorly depends ohow user can use the software. UI is the only way for users to perceive the system. A well performing software system must also be equipped with attractive, clear, consistent and responsive user interface. Otherwise the functionalities of software system can not be used in convenient way. A system is said be good if it provides means to use it efficiently. User interface requirements are briefly mentioned below -

presentation

Navigation

interface

Responsive

Consistent UI elements

Feedback

Default settings
usefullayout
use of color and texture.
help information
User centric approach
Group based view settings.

reason to do prioritize items in requirement analysis phase:

Prioritization means “importance order ”. BABOK 3.0 proposed 8 factors that influence the prioritization of requirements.