SIA-Reviewer (1).pdf

Reviewer: Key Terms in SIA and UML 1. Elicitation Phase: The initial stage in the requirements cycle where user needs and expectations are gathered through various techniques. 2. Organization Phase: The stage where collected requirements are structured and categorized for better und...

Reviewer: Key Terms in SIA and UML 1. Elicitation Phase: The initial stage in the requirements cycle where user needs and expectations are gathered through various techniques. 2. Organization Phase: The stage where collected requirements are structured and categorized for better understanding and analysis. 3. Analysis Phase: The phase in which organized requirements are examined to identify gaps, conflicts, and priorities. 4. Specification Phase: The final stage where analyzed requirements are documented in a clear and detailed manner for implementation. 5. User Requirements: Statements in natural language that describe what the system should do from the user's perspective, including operational constraints. 6. Functional Requirements: Specific behaviors or functions that a system must perform, detailing what the system should accomplish. 7. Non-functional Requirements: Criteria that specify how a system performs a function, including performance, usability, reliability, and security. 8. Sampling: A method of gathering data by selecting a representative subset of users or situations to understand broader requirements. 9. Research and Site Visiting: Techniques used to gather information by studying existing systems and environments where the new system will operate. 10. Observation of Work Environment: A method of collecting requirements by watching users interact with current systems in their natural settings. 11. Questionnaires: Structured forms used to collect information from users about their needs and expectations for the system. 12. Interviews: Direct conversations with users to gather in-depth insights about their requirements and experiences. 13. System Prototyping: The creation of a preliminary version of the system to visualize and refine requirements through user feedback. 14. Joint Requirement Planning: A collaborative approach where stakeholders come together to discuss and agree on requirements. 15. Affinity Diagrams: A tool used to organize ideas and requirements into groups based on their natural relationships. 16. Cause and Effect Analysis: A method for identifying the root causes of problems and their effects on system requirements. 17. Force-Field Analysis: A technique used to identify and analyze the forces that support or hinder a change or requirement. 18. Pareto Diagram: A bar graph that represents the frequency of problems or requirements, helping to prioritize them based on their impact. 19. Quality Function Deployment (QFD): A structured approach to ensuring that customer requirements are met throughout the design and development process. 20. Component: A modular part of a system that encapsulates its contents and can be replaced independently within its environment. 21. Interface: A defined set of operations that a component exposes to other components, allowing them to interact. 22. Provided Interface: An interface that a component offers to other components, indicating the services it provides. 23. Required Interface: An interface that a component needs from other components to function properly. 24. Dependency: A relationship that indicates one component relies on another to perform its functions. 25. Port: A specific point of interaction on a component where interfaces are provided or required. 26. Component Diagram: A UML diagram that illustrates the components of a system and their relationships, focusing on the system's architecture. 27. Node: A physical element that represents a computational resource in a system, such as a server or device. 28. Artifact: A physical piece of information that is used or produced by a component, such as a file or database. 29. Stereotype: A mechanism in UML that allows the extension of the vocabulary of UML by creating new types of modeling elements. 30. Subsystem: A group of related components that work together to perform a specific function within a larger system. 31. Connector: A link that facilitates communication between components, often represented as a line in a diagram. 32. Deployment: The process of distributing and installing components in a specific environment or on specific nodes. 33. Architecture: The overall structure of a system, including its components, their relationships, and the principles guiding its design. 34. Modularity: The degree to which a system's components can be separated and recombined, promoting flexibility and reusability. 35. Encapsulation: The bundling of data and methods that operate on that data within a single unit (component), restricting access to some of the object's components. 36. Service: A function or operation provided by a component that can be accessed through its interfaces. 37. Behavior: The actions or operations that a component can perform, often defined by its interfaces. 38. Collaboration: The interaction between components to achieve a common goal or functionality within the system. 39. UML (Unified Modeling Language): A standardized modeling language used to specify, visualize, and document the artifacts of a software system. 40. Data Flow Diagram (DFD): A visual representation of how data moves through a system, illustrating the processes, data stores, and data flows between them. 41. Level 0 DFD: Also known as a context diagram, it provides a high-level overview of the system, showing a single process and its interactions with external entities. 42. Level 1 DFD: A more detailed diagram that breaks down the main process from the Level 0 DFD into sub-processes, showing how data flows between them and external entities. 43. Level 2 DFD: An even more detailed diagram that further decomposes one of the sub- processes from the Level 1 DFD, illustrating specific tasks and their data flows. 44. Process: A function or activity that transforms input data into output data within the system, represented by a circle or rectangle in a DFD. 45. Data Store: A repository where data is stored for later use, represented by an open-ended rectangle in a DFD. 46. External Entity: An outside actor (such as a user, system, or organization) that interacts with the system, represented by a square in a DFD. 47. Data Flow: The movement of data between processes, data stores, and external entities, represented by arrows in a DFD. 48. Sub-process: A smaller, more detailed process that is part of a larger process, allowing for a breakdown of complex operations into manageable components. 49. Context Diagram: Another term for Level 0 DFD, it provides a simplified view of the system, focusing on the overall process and its interactions with external entities without detailing internal processes.