एजाइल में प्लानिंग पोकर क्या है? एजाइल आकलन के लिए एक पूर्ण गाइड

Whatever the size of the team, they need to define, estimate and assign work across the team. Planning poker (also known as Scrum poker) is a consensus-based game technique for estimation, which is mainly used to estimate the workload or relative size of development objectives in software development. (无论团队规模如何,他们都需要在整个团队中定义,估算和分配工作。规划扑克(也称为Scrum扑克)是一种基于共识的游戏化技术,用于估算,主要用于估计软件开发中的开发目标的工作量或相对大小。)

Continue reading

UML क्या है?

UML क्या है? यूनिफाइड मॉडलिंग लैंग्वेज एक खुला मानक ग्राफिकल नोटेशन है जो सिस्टम विकास के लिए प्रस्तावित ऑब्जेक्ट मैनेजमेंट

Continue reading
अनुक्रम आरेख क्या है

अनुक्रम आरेख क्या है

A sequence diagram is an interaction diagram that emphasizes the time-ordering of messages. It depicts the objects and classes involved in the scenario and the sequence of messages exchanged between the objects needed to carry out the functionality of the scenario. Typically, you’ll use one sequence diagram to specify a use case’s main flow, and variations of that diagram to specify a use case’s exceptional flows.

Continue reading
https://circle.visual-paradigm.com/wp-content/uploads/2017/08/Activity-Diagram-Swinlane-Proposal-Process.png

एक एक्टिविटी डायग्राम क्या है

Activity Diagrams describe how activities are coordinated to provide a service which can be at different levels of abstraction. Typically, an event needs to be achieved by some operation, particularly where the operation is intended to achieve a number of different things that require coordination, or how the events in a single use case relate to one another, in particular, use cases where activities may overlap and require coordination. It is also suitable for modeling how a collection of use cases coordinate to create a workflow for an organization.

Continue reading
उपयोग केस इवेंट्स के फ्लो में परीक्षण प्रक्रिया लिखना

उपयोग केस इवेंट्स के फ्लो में परीक्षण प्रक्रिया लिखना

In the area of software testing, “use case” and “test case” are the most critical and closely interrelated terms, but they are quite different. A use case tells us how a system will behave or perform a given task under given conditions. A test case contains the actual test data, the instruction set of the system, and the expected results of the interaction with the system.

Continue reading

प्रभावी उपयोग केस लिखने का तरीका

One of the most difficult problems in software development is capturing exactly what you want to build. Inaccurate requirements can eventually lead to significant project delays, rework, or even abandonment. Effective application of use case techniques can help your team capture requirements from the user’s perspective, which can be easily understood by both the end user and your team. Use case-driven development supports subsequent development activities such as analysis, design, and testing.

Continue reading