Early modeling and validation of timed system requirements using Timed Use Case Maps

Computer Science

• Use Case 100%
• Modeling 100%
• System Requirement 100%
• Non-Functional Requirement 66%
• Design 66%
• Model 66%
• Real Time Systems 33%
• Process Model 33%
• Time Requirement 33%
• Functional Requirement 33%
• Software Quality 33%
• Software Development Lifecycle 33%
• State Machine 33%
• Nonfunctional Property 33%
• Business Process Model 33%
• System Development Life Cycle 33%
• Fully Automated Approach 33%
• Good Requirement 33%
• Requirement Level 33%
• Multicast Routing 33%
• Requirement Engineering 33%
• Standards 33%
• Roles 33%
• Detection 33%
• Analysis Technique 33%
• Service 33%
• Case Study 33%
• User Requirement 33%
• Motivation 33%
• Selection Criterion 33%

Engineering

• System Requirement 100%
• Maps 100%
• Requirement 100%
• Models 75%
• Lifecycle 50%
• Nonfunctional Requirement 50%
• Applicability 25%
• Selection Criterion 25%
• System Development 25%
• Redesign 25%
• Early Stage 25%
• Model System 25%
• Functional Property 25%
• Review Process 25%
• Supports 25%
• Level Requirement 25%
• Engineering 25%
• Design 25%
• Development 25%
• Tasks 25%
• Illustrates 25%
• Error 25%
• High Quality 25%
• Design Decision 25%
• Detection 25%
• Performance 25%
• Research 25%
• User Requirement 25%
• Consensus 25%
• Functional Requirement 25%
• State Machine 25%