Here you will find all tactics for the quality characteristic Functional Suitability.
Completeness, Correctness, Appropriateness
Requirements Analysis
Collect, analyze, and document functional requirements systematically
Here you will find all tactics for the quality characteristic Functional Suitability.
Completeness, Correctness, Appropriateness
Collect, analyze, and document functional requirements systematically
Appropriateness
Also supports: Operability
Formulate requirements from the user's perspective
Appropriateness
Also supports: Operability
Explore requirements through a fidelity spectrum from paper sketches to clickable models
Correctness
Verify the software's functionality through systematic testing
Completeness, Correctness, Appropriateness
Confirm fulfillment of requirements through formal acceptance tests with users
Completeness, Correctness
Define clear criteria for the completion of functionality
Appropriateness
Assign responsibility for business requirements and acceptance to a dedicated role
Appropriateness
Also supports: Operability, Accessibility
Characterize representative user types through fictional characters
Appropriateness
Also supports: Operability, Learnability
Regularly gather and implement feedback from users and stakeholders
Correctness
Also supports: Operability
Gather feedback from users directly in the software system
Appropriateness
Also supports: Learnability
Directly involve domain experts in development
Appropriateness
Directly involve customers in development
Appropriateness
Also supports: Modifiability
Develop and deliver software incrementally in short cycles
Appropriateness
Also supports: Modularity, Modifiability
Structure and implement software functionality in the form of features
Appropriateness
Also supports: Modifiability, Analyzability
Map domain concepts and relationships in a domain model
Appropriateness
Also supports: Modifiability, Analyzability
Align software architecture with the domain's business structures and terms
Appropriateness
Also supports: Modifiability, Analyzability
Separate business areas with different terms and rules from each other
Appropriateness
Also supports: Modularity, Modifiability
Align the software's structure with domain structures and processes
Appropriateness
Also supports: Interoperability
Elicit business requirements by modeling the underlying business processes
Completeness, Correctness
Use proven standard software instead of developing ordinary functionality yourself
Appropriateness
Also supports: Modifiability
Detail and refine requirements incrementally throughout the project
Correctness, Appropriateness
Have work results reviewed and approved by domain experts
Correctness
Also supports: Analyzability
Conduct regular reviews of the source code by team members
Appropriateness
Also supports: Modifiability
Conduct regular evaluations of the software architecture
Appropriateness
Identify and prioritize problematic implementation of functional requirements
Appropriateness
Also supports: Operability, Learnability
Verify usability and suitability through user tests
Correctness, Appropriateness
Create test cases from a business perspective and have them reviewed by users
Correctness
Also supports: Modifiability
Test domain knowledge through targeted questions
Appropriateness
Also supports: Time-behaviour, Capacity, Availability
Specify and verify quality requirements through business-driven scenarios
Correctness, Appropriateness
Also supports: Testability
Formulate requirements as executable scenarios in natural language
Correctness
Also supports: Modifiability, Testability
Verify fulfillment of business requirements through automated tests
Appropriateness
Also supports: Modifiability, Analyzability
Use programming languages specifically adapted to the domain for business expressions and rules
Appropriateness
Also supports: Analyzability, Availability
Apply proven solutions for recurring business problems
Appropriateness
Also supports: Completeness, Operability
Deliver functionality frequently and incrementally
Appropriateness
Also supports: Operability, Availability
Define business metrics to evaluate the functionality and quality of the software
Appropriateness
Also supports: Completeness, Operability
Build functional business prototypes that execute real end-to-end workflows
Appropriateness
Also supports: Modifiability
Validate end-to-end functionality early through simplified implementations
Appropriateness
Also supports: Modifiability
Investigate business risks through time-limited experiments
Appropriateness
Also supports: Learnability, Operability
Adapt software to the specific requirements and needs of users
Appropriateness
Also supports: Modifiability, Testability
Define and evaluate complex business rules in tabular form
Appropriateness
Also supports: Modifiability
Map business concepts and rules in an executable model
Appropriateness
Define rules that govern the behavior of the software
Appropriateness
Also supports: Interoperability, Time-behaviour
Recognize, process, and respond to business events
Correctness
Also supports: Availability
Ensure data quality through validation, cleansing, and enrichment
Correctness
Also supports: Fault Tolerance
Define acceptable value ranges for inputs and outputs
Appropriateness
Also supports: Integrity, Availability
Control access to sensitive data based on business authorizations
Appropriateness
Also supports: Non-repudiation, Availability, Analyzability
Track and restore changes to domain-specific data
Appropriateness
Also supports: Modularity, Capacity, Modifiability
Enable rapid product experimentation through independent, business-aligned services
Appropriateness, Correctness
Also supports: Confidentiality, Time-behaviour
Collect and store only necessary data
Appropriateness
Also supports: Interoperability
Merge data from various sources and provide it uniformly
Appropriateness
Also supports: Time-behaviour
Supplement data with additional information from external sources
Appropriateness
Also supports: Modifiability, Interoperability
Map business concepts and relationships in a conceptual data model
Correctness, Appropriateness
Align developer and domain expert vocabulary in code and conversation
Appropriateness, Completeness
Map business goals through actors and impacts to concrete deliverables
Completeness, Appropriateness
Visualize complete user journeys as a two-dimensional map of priorities
Completeness, Appropriateness
Also supports: Analyzability
Discover domain events, commands, and aggregates in collaborative workshops
Correctness, Appropriateness
Also supports: Completeness
Define requirements collaboratively through examples that become executable specifications
Completeness, Correctness
Maintain explicit bidirectional mappings from requirements through design, code, and tests
Completeness
Identify missing functionality by comparing capabilities against requirements
Correctness, Appropriateness
Specify preconditions, postconditions, and invariants for verifiable behavior
Correctness
Also supports: Testability
Re-run existing tests after every change against unintended breakage
Appropriateness, Completeness
Also supports: Modifiability
Toggle feature availability at runtime per user segment