Looks like no one added any tags here yet for you.
Requirement
Something a computer application must do for its users
ex. function or feature
Business requirements
What the business needs to do or have in order to stay in business
ex. running payroll, generate a paystub
User Requirements
What the user wants the system to do or what the user needs the system to be able to perform
ex. place an order on a website, having radio buttons to make choices
System Requirements
Building blocks developers use to build the system
ex. display a welcome page, allow automatic email messages
Functional Requirement
Needed for the system to help the user complete a task
Non-functional requirements
other, often hidden areas which contribute to system success (or Failure)
ilities, ex. scalability, reliability
Traceability
Concept or principle that the various documents which support and define a project should be related -traceable-to one another
The Writing Process
prewriting, drafting, revising, editing, submitting
why do traditional expressions of functionality lead to less than desirable results?
Traditional expressions of functionality tend to write and duplicate requirements which can lead to less than desirable results since the user does not fully understand the requirements.
Actors
something with a behavior or role(person, system, organization)
Scenario
sequence of actions and interactions between actors and the system
Use Case
collection of related success and failure scenarios, describing actors using the system to support a goal
Primary Actor
User whose goals are fulfilled by the system
Secondary Actor
an actor who provides/receives info or output
Include
Base Use Case explicitly incorporates behavior of another use case
Never stands alone
Extend
Base Use Case implicitly incorporates behavior at certain points, usually in branching under conditions
May stand alone, but only under certain conditions, behavior may behavior may be extended by behavior of another use case
Incremental Approach
breaks down the software development process into small, manageable portions known as increments
Iterative Approach
breaks down the software development cycle into repeated cycles known as iterations
What does Increasing levels of granularity mean?
The greater the level of granularity the deeper the level of detail. meaning that with more granularity the detail is becoming clearer
Why is risk analysis important?
It allows you to examine the risks that you or your organization face, and helps you decide whether or not to move forward with a decision
How do Use Cases help in design?
They help explain how the system should behave and in the process, they also help brainstorm what could go wrong.
What is a business rule?
A rule that defines or constrains some aspect of business and always resolves to either true or false.
What are the types of Iterations?
FaƧade, Filled, Focused
What are the objectives of the FaƧade iteration?
- create placeholders for major interactions between actors and the application
- contains minimal information
- identify actors
What are the sources of the FaƧade Iteration
- Users
- Project team
- Industry experts
- IT management
- User management
- Data Owners
What are the steps of the FaƧade Iteration?
1. Creating a problem statement
2. Identify and review existing documentation
3. Get executive sponsor's viewpoint
4. Review business process definitions
5. Identify Users, user groups
What are the FaƧade iteration outputs?
- Clear Problem statement
- statement of work
- risk analysis
- use case diagram
- use cases
- business rule
What are the objectives of the Filled Iteration?
- More detailed, comprehensive list of requirements
- more complex task
- break down faƧade use cases into several filled use cases
What are the sources of the Filled iteration?
The FaƧade iteration
What are the steps of Filled Iteration?
- break out detailed use cases
- create filled use cases
- add business rules
- document the basic course of events
- test filled use cases
Preconditions
What must be true before the use case begins
Postconditions
what must be true upon the successful completion of a use case
Basic course of events
Simple correct path
Alternative flow of events
Exceptions, errors, conditions
Boundary
A rectangle that you draw in a use case diagram to separate the use cases that are internal to a system from the actors that are external to a system
What are the objectives of Focused Iteration?
- moves from essential to nice to have
- results in clear project requirements
- more challenging
- focus on essential core functionality and eliminates waste
- focuses more on how the user will interact with the system
What are the sources of Focused Iteration?
- Filled and FaƧade Iterations
What are the steps of Focused Iteration?
- merge duplicate processes
- bring focus to each use case
- manage scope changes
- manages risk and assumptions
- review
What are the deliverables for the Filled Iteration?
- candidate use case list
- use cases
- use case diagrams
- business rule catalog
- scenarios
What are the deliverables for the Focused Iteration?
- complete problem statement
- complete statement of work
- use cases
- use case diagrams
- business rule catalog
-risk analysis
What is a needs assessment?
A systematic set of procedures undertaken for the purpose of setting priorities and making decisions about program or organizational improvement and allocation of resources. The priorities are based on identified needs.