Needs Assessments Exam 2

what is a functional requirement ?

Describe what the system should do, focusing on specific functions , features, tasks

System requirement

Forms the foundation of the system's design, guiding development and testing to ensure the final product

What is a non-functional requirement ?

behavioral characteristics that define how the system should function

Business requirement

A high level description of a business need or objective that a project or system must fulfill to deliver value to an organization

What is traceability?

Provides a clear path linking requirements to their implementation and testing, ensuring that all project requirements are met

The importance of traceability

Traceability helps manage complexity, reduce errors, and increase project transparency and quality by connecting each requirement

Why is UML used ?

Visual representation of system design
Communication
Detailed system documentation
Supports different development stages
Improves design quality

What are the rules of writing good use case narratives ?

follow a straight path to achieve a use case goal
don't confuse use cases with user stories
treat "if" statements with caution

What are some tips some use case narratives ?

clearly define the user (actor)
establish a clear goal
structure with a narrative arc
include different flows
use descriptive language

waterfall method

a structured approach to gathering and analyzing requirements for a project using the waterfall methodology

test model traceability

The test scenarios will add test data to the use cases to become testable. The test cases will focus on each use case path

Project management traceability

an iterative/incremental project is focused on the production of use cases

application architecture traceability

provides the foundation for how the components and objects are organized on the target technical environment

security traceability

use cases begin by examining the goals of the actors. The actors definitions provide the basis for creating security profiles

product marketing traceability

As new releases of the software go into general availability, the marketing team has a useful list of the new stories that can tell with the product and subsequently new sections for product demonstration scripts

the important goals are the business goals dates and budgets

By defining the set of requirements early and then trying to discourage any changes to them throughout the lifecycle, we may be missing the business point. The requirements should always be flexible

divide and conquer

being able to divide the work amongst a team and put it into three categories, technology, subsystem, and use case

create demonstrable deliverables

when you want to show the business people something show them the working application. The running, tested code. Nothing less

the pieces will be smaller than you think

this fine-grained nature is actually a plus for planning. Project managers must resist the urge to "bundle" use cases together in order to assign them to team

forget about baselines and sign-offs

Take advantage of the fact and remove the sign-off process completely. Sign-offs will only drive stakes into the ground to highlight the differences between the two sides