Chapter 1 Flashcards
Name Requirement Pain Points
- project’s business objectives, vision, and scope never defined. 2. Customers too busy to spend time working with developers/analysts on requirements. 3. Team couldn’t interact with representative users. Develops had to guess due to missing information and ambiguities.
What are the three levels of Requirements?
1) Business Requirements 2) User Requirements 3) Functional requirements
What are Software Requirements?
Sevices that the customer requires from a system and constraints under which the system operates and is developed. System requirements eescribe the requirements for a product that is composed of multiple componets or sub systems. Can be all software or both software and hardware.
Define Business Requirements
Describe why the organization is implementing the system. Describe the business benefits the organization hopes to achieve. Focus is on the business objectives o of the organization/customer who requested the system.
Where do Business Requirements come from?
funding sponsor, acquiring customer, manager of actual users, marketing department, product visionary
How do you record Business Requirements?
In a vision and scope document/ Business requirement document.
Why does a software engineer care about Business Requirements?
Business Requirements describe the goal the organization wants to achieve. The software engineer can use the goal to tell if the system meets the goal and will satisfy the organization and its objective.
Describe User Requirements
Describes Goals or tasks users must be able to perform with the product that will provide value to someone. Descriptions of product attributes or characteristics that are important to user satisfaction.
Where do I get User Requirements from?
ideally actual users representatives of user class and other stakeholders
What are functional requirements?
Specify the behaviors theproducr will exhibit under specific conditions. Describes what developers must implement eliminating ambiguities.
What are Non-functional Requirements?
Specify not what the system does but how well it does it. Describes important characteristics or properties of the systems such as Quality attributes like availability, portability, security, usability, performance, Also include constraints, compliance, regulatory, certification requirements, localization requirements, design and implementation. Also envioremntal constraints
Name Sample Metrics for specifying nonfunctional requiremwnts
Speed, Size, Was of use, portability,Reliability, Robustness
Define External Requirements
Define Constraints
Define Business Rules?
Corporate policies government regulations, industry standards computational algorithms. Businesses are not themselves Software requirements because they have an existence beyond the boundaries of any specific software application. However, the system must contain functionality to comply with rules. Business rules can be the origin of specific attributes that implement the functionality. like security policies
