Across
- 2. Written information that explains how a software system works, how to use it, and how to maintain it. Documentation can include user manuals, developer guides, technical specifications, and test plans.
- 4. algorithm: is a computer program that organizes data into a specific order, such as alphabetical order or numerical order, usually either ascending or descending.
- 5. methodology: Sequential approach to software development with distinct phases.
- 7. architecture: High-level design of a software system.
- 9. algorithm: is an algorithm designed to solve a searched problem. Search algorithms work to retrieve information stored within particular data structure or calculated in the search space of a problem domain, with either discrete or continuous values.
- 13. specification: A formal document that details the functionalities, features, and behaviors expected from a software system. It serves as a blueprint for developers to understand what needs to be built.
- 15. phase: The stage of the software development life cycle where the software is tested for defects and compliance with requirements.
- 16. Is a centralized digital storage that developers use to make and manage changes to an application's source code.
- 17. phase: The stage of the software development life cycle where the software is updated and improved after deployment.
- 18. diagram: A UML diagram that shows the classes in a system, their attributes (data members), and the methods (functions) they possess. It depicts the relationships and dependencies between these classes.
- 20. case: A scenario that describes how a user interacts with the system to achieve a specific goal. Use cases help define functionalities and user interactions.
- 23. diagram: A UML diagram that illustrates the sequence of messages exchanged between objects in a system to complete a specific operation. It focuses on the chronological flow of interactions.
- 24. methodology: The Agile methodology is a project management approach that involves breaking the project into phases and emphasizes continuous collaboration and improvement.
- 25. analysis: The stage of the software development life cycle where the needs and constraints of the software project are identified and documented.
- 27. Identifying and fixing software errors.
- 28. is a hierarchically organized set of values or 'nodes', where each node is linked to a superior node (parent) and potentially to several inferior nodes (children).
Down
- 1. Is a framework for getting work done within agile. Scrum uses all the core principles of agile to define methods to facilitate a project.
- 3. diagram Another UML diagram that focuses on the message flow between objects during an interaction. It highlights the collaboration between objects to achieve a specific functionality, similar to a sequence diagram, but with a focus on object roles.
- 4. development life cycle: (SDLC) is a process used for designing and building high-quality software. It’s known for being effective in cost and efficient in time.
- 6. experience (UX): Overall satisfaction of users interacting with software.
- 8. An abstract data type that can be used to represent complex, non-linear relationships between objects.
- 9. An abstract data type that serves as a collection of elements with two main operations: Push, which adds an element to the collection, and. Pop, which removes the most recently added element.
- 10. phase: The stage of the software development life cycle where the actual code for the software system is written.
- 11. assurance (QA): Ensuring software meets quality standards.
- 12. phase: The stage of the software development life cycle where the architecture and structure of the software system are planned.
- 14. Evaluating software for defects and quality.
- 19. list: A data structure consisting of a sequence of elements, each element being connected to the next element through pointers or references. Each element, called a node, contains data and a reference to the next node in the sequence.
- 20. interface (UI): Interface allowing user interaction with software.
- 21. control: Is the practice of tracking and managing changes to software code
- 22. A data structure that follows the First-In-First-Out (FIFO) principle, where elements are inserted at the rear and removed from the front. In a linked list implementation, a queue typically utilizes a singly linked list where elements are added to the tail and removed from the head.
- 26. A standardized language for visually representing software systems. UML includes various diagrams to depict different aspects like structure, behavior, and interaction.