Học một điều mới mỗi ngày
MVC (known as Model-View-Controller) is a pattern in software design that is commonly used to implement user interfaces, data, and control logic. It emphasizes the separation between the business logic and presentation of the software. This “separation of concerns” provides better division of labor and better maintenance.
Continue reading
UML activity diagram is another common tool used by UML to model the dynamic behavior of the system. It describes the sequence of activities and shows the flow of control from one activity to another. UML activity diagram is essentially a flow chart.
Continue reading
Test Driven Development (TDD) is a software development process, which relies on transforming software requirements into test cases before software is fully developed, and tracking all software development by repeatedly testing software for all test cases. This is the opposite of developing software first and then creating test cases. Some popular models support TDD very well, such as MVC and MVP.
Continue reading
A use case approach is a kind of technique for identifying the business goals of a system. The identification of use cases helps define system scope, ensuring that the requirements to be found will all be aligned with the business values, needs and strategy.
Continue reading
A use case is a requirements capture and documentation technique that can be written in plain text to describe in a narrative manner the actions and interactions of participants using the system. Finally, the functionality of the system should satisfy the purpose for which stakeholders use the system.
Continue reading
A Five Forces analysis can help companies assess industry attractiveness, how trends will affect industry competition, which industries a company should compete in — and how companies can position themselves for success.
Continue reading
Use cases are often graphical, and use case diagrams are supported by text descriptions, including use case and participant descriptions, as well as scenarios associated with use case templates that make use case methods simple and intuitive and ideal tools for discussing and clarifying developers’ understanding of user needs.
Continue reading
It’s important to prioritize your product backlog to make sure it doesn’t become an open-ended list where everyone has random ideas about your product. Your to-do list needs to be structured, organized, and prioritized to identify the most strategically important things for your team to do. In this article, I introduce the 100 Points method for product backlog refinement activities.
Continue reading
In software engineering, the software development lifecycle is the process of dividing the software development effort into smaller, parallel or continuous steps or sub-processes to improve design, product management. This approach may include predefined specific deliverables and artifacts that the project team creates and completes for the development or maintenance of the software applications.
Continue reading
Use case modeling is a technique for capturing, modeling, and specifying system requirements that correspond to a set of behaviors that the system may perform when interacting with actors. These behaviors produce observable results and help achieve their goals. Use cases are named for the specific user goals of the principal actors, which in turn describe or explain the general order of activities and events, as well as variations in special conditions, exceptions, or error conditions, through textual description.
Continue reading