Software Engineering Blog

A use-case model is a model of how different types of users interact with the system to solve a problem.  As such, it describes the goals of the users, the interactions between the users and the system, and the required behavior of the system in satisfying these goals. A use-case model consists of a number of model elements.  The most important model elements are: use cases, actors and the relationships between them. A use-case diagram is used to graphically depict a subset of the model to simplify communications.  There will typically be several use-case diagrams associated with a given model, each showing a subset of the model elements relevant for a particular purpose.  The same model element may be shown on several use-case diagrams, but each instance must be consistent.  If tools are used to maintain the use-case model, this consistency constraint is automated so that any changes to the model element (changing the name for example) will be automatically ref...

Context diagrams and   data flow diagrams   are often used interchangeably, but they aren’t the same. There are key differences between using the two. Context diagrams  focus on how external entities interact with your system. It’s the most basic form of a data flow diagram, providing a broad view of the system and external entities in an easily digestible way. Because of its simplicity, it’s sometimes called a level 0 data flow diagram. https://miro.com/blog/context-diagram/#:~:text=Context%20diagrams%20focus%20on%20how,level%200%20data%20flow%20diagram.

  What Is a Stakeholder? A stakeholder is an individual or a group of individuals with an interest, often financial, in the success of a business. The primary stakeholders in a corporation include its  investors , employees, customers, and suppliers. With increasing attention on  corporate social responsibility , the concept has been extended to include communities, governments, and  trade associations. https://www.investopedia.com/terms/s/stakeholder.asp#:~:text=A%20stakeholder%20is%20an%20individual,employees%2C%20customers%2C%20and%20suppliers.

  The software requirements are description of features and functionalities of the target system. Requirements convey the expectations of users from the software product. The requirements can be obvious or hidden, known or unknown, expected or unexpected from client’s point of view. https://www.tutorialspoint.com/software_engineering/software_requirements. htm#:~:text=The%20software%20requirements%20are%20description,from%20client's%20point%20of%20view.

 Software Maintenance   is the process of changing, modifying, and updating software to keep up with customer needs. Software maintenance is done after the product has launched for several reasons including improving the software overall, correcting issues or bugs, to boost performance, and more.   Software maintenance is a natural part of SDLC (software development life cycle). Software developers don’t have the luxury of launching a product and letting it run, they constantly need to be on the lookout to both correct and improve their software to remain competitive and relevant. https://cpl.thalesgroup.com/software-monetization/four-types-of-software-maintenance#:~:text=Software%20maintenance%20is%20the%20process,to%20boost%20performance%2C%20and%20more.

  Agile is an approach to project management that centers around incremental and iterative steps to completing projects. The incremental parts of a project are carried out in short-term development cycles. The approach prioritizes quick delivery, adapting to change, and collaboration rather than top-down management and following a set plan. In the Agile process, there is continuous feedback, allowing team members to adjust to challenges as they arise and stakeholders an opportunity to communicate consistently. Though originally created for software development, the Agile approach is now widely used in executing many different types of projects and in running organizations.