یادگیری یک چیز جدید هر روز
Risk management is a system for identifying, addressing and eliminating issues that may be detrimental to the cost, schedule or technical success of a project or to the morale of the project team. “Tomorrow’s problems are today’s risks.” Therefore, “risk” is clearly defined as a problem that could cause some damage or threaten the project schedule, but has not yet occurred.
Continue reading
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
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
The Open / Closed Principle is the most basic design principle in the software development world. It guides us how to build a stable and flexible system. A software entity such as class, module, and function should be open for extension and closed for modification.
Continue reading
Although data flow oriented modeling is considered as an outdated technology by some software engineers, it is still one of the most widely used requirements analysis symbols. Although data flow diagrams (DFDs) are not formal parts of UML, they can be used to supplement UML diagrams and provide additional insight into system requirements and processes.
Continue reading
Causal loops diagrams (also known as system thinking diagrams) are used to display the behavior of cause and effect from a system’s standpoint. A causal loop diagram (CLD) is a causal diagram that aids in visualizing how different variables in a system are interrelated.
Continue reading
Enterprise Integration Patterns (EIP)is a book by Gregor Hohpe and Bobby Woolf and describes 65 patterns for the use of enterprise application integration and message-oriented middle-ware in the form of a pattern language. They help us use standardized ways to integrate applications, no need to reinventing the wheel each time you have a problem.
Continue reading
Structured Systems Analysis and Design Method (SSADM) structural systems analysis and design methods, standards set in the early 1980s development, is widely used in the design and application of the calculation. It uses a combination of text and diagrams for system design throughout the life cycle, from the initial design concept to the application of actual physical design.
Continue reading
A cross-functional flowchart (sometimes referred to as a deployment flowchart) is a business process mapping tool used to articulate the steps and stakeholders of a given process. Typically, we use a cross-functional flowchart to show the relationship between a business process and the functional units (such as departments) responsible for that process.
Continue reading
A flowchart is a diagram of the sequence of steps in a process. It is a general purpose tool that can be used for a variety of purposes, such as manufacturing processes, management or service processes, or project planning. It is often defined as a graphical representation of an algorithm, a step-by-step approach to a task. It displays the steps as various types of boxes and shows their order by connecting the boxes with arrows.
Continue reading