Across
- 1. A type of UML diagram that illustrates how objects interact with each other in a particular sequence, typically showing the flow of messages between objects over time.
- 4. A method for finding a specific item in a collection of data.
- 8. The process of ensuring that software products and processes meet established quality standards.
- 11. Unified Modeling Language, a standardized visual modeling language used in software engineering to design and document software systems.
- 12. The process of evaluating a software system to ensure that it behaves as expected and meets its requirements.
- 17. A hierarchical data structure consisting of nodes connected by edges, with a single root node at the top and zero or more child nodes.
- 19. A linear data structure consisting of a sequence of elements, where each element points to the next one in the sequence.
- 20. The structure of a software system, including its components, relationships, and principles guiding its design and evolution.
- 21. A type of UML diagram that illustrates the structure of a system by showing the classes, attributes, methods, and relationships between them.
- 22. A traditional sequential approach to software development, where each phase of the project (e.g., requirements, design, implementation, testing) is completed before moving on to the next.
- 24. A non-linear data structure consisting of vertices (nodes) connected by edges, representing relationships between objects.
- 26. The overall experience of a user interacting with a software system, including usability, accessibility, and satisfaction.
- 27. A document that describes the functional and non-functional requirements of a software system, often including user stories, use cases, and acceptance criteria.
- 29. The process of developing software, typically consisting of phases such as planning, analysis, design, implementation, testing, deployment, and maintenance.
- 30. The phase of the software development life cycle where the architecture and design of the software system are planned and documented.
Down
- 2. The creation and maintenance of documents that describe the design, implementation, and usage of software systems.
- 3. The process of managing changes to documents, programs, and other information over time, typically using a version control system.
- 5. A type of UML diagram that shows the relationships and interactions between objects in a system, focusing on the messages exchanged between objects to accomplish a specific task.
- 6. The process of gathering, documenting, and analyzing user requirements for a software system.
- 7. A description of a specific interaction between a user (or actor) and a software system, typically detailing the steps and expected behavior of the system.
- 9. The part of a software system that users interact with, including graphical elements, menus, and input controls.
- 10. The phase of the software development life cycle where the actual code for the software system is written and tested.
- 13. A flexible approach to software development that emphasizes iterative development, collaboration, and customer feedback.
- 14. The phase of the software development life cycle where the software system is updated, modified, and improved to address issues and meet changing requirements.
- 15. A linear data structure that follows the LIFO (Last-In-First-Out) principle, where elements are inserted and removed from the same end.
- 16. A central location where data, files, and software artifacts are stored and managed, often using version control systems.
- 18. A specific Agile framework for managing software development projects, characterized by short iterations called sprints and regular meetings called scrum ceremonies.
- 23. The phase of the software development life cycle where the software system is tested to ensure that it meets its requirements and functions correctly.
- 25. The process of identifying and fixing errors, bugs, and other issues in software code.
- 28. A linear data structure that follows the FIFO (First-In-First-Out) principle, where elements are inserted at the end and removed from the front.