Systems-Analysis-Uncovering-Requirements.pptx

this is the presentation on one of the topic of system development and analysis.

1. Systems Analysis: Uncovering Requirements Systems analysis is a critical phase in the systems development life cycle, where analysts determine how the current information system functions and assess what users would like to see in a new system. This process involves two key sub-phases: requirements determination and requirements structuring. By thoroughly understanding the existing system, gathering user feedback, and modeling the desired functionality, analysts can lay the foundation for a successful system implementation.

2. Requirements Determination: Gathering Insights 1 Impertinence Analysts must approach requirements determination with an open and impartial mindset, avoiding preconceptions and being willing to challenge existing assumptions. 2 Impartiality Analysts should strive to gather information from a variety of stakeholders, including users, managers, and IT staff, to ensure a balanced and comprehensive understanding of the system requirements. 3 Attention to Details Careful observation and documentation of current processes and pain points are crucial to identifying opportunities for improvement and defining the new system's requirements. 4 Reframing Analysts should be prepared to reframe the problem or challenge, looking at it from different perspectives to uncover hidden needs or innovative solutions.

3. Traditional Requirements Gathering Techniques Interviewing Interviews with key stakeholders, both individually and in groups, are a primary method for gathering information about the current system and desired features. Analysts must carefully craft questions, actively listen, and document the findings. Observation Directly observing users interacting with the current system can provide valuable insights into pain points, workarounds, and unmet needs. However, analysts must be mindful of the potential impact on user behavior. Document Analysis Reviewing existing system and organizational documentation can uncover details about the current system, its design, and the reasons behind its implementation. This can help identify opportunities for improvement.

4. Contemporary Requirements Gathering Techniques 1 Joint Application Design (JAD) JAD brings together key users, managers, and analysts in a series of intensive meetings to collaboratively specify or review system requirements. This structured process can help resolve issues and produce better, error-free software. 2 Prototyping Prototyping is an iterative process where requirements are quickly converted into a working system that is continually revised through close collaboration between analysts and users. This helps ensure the system meets user needs. 3 Agile Methodologies Agile approaches, such as continual user involvement and Agile Usage-Centered Design, emphasize an ongoing, collaborative process for gathering and refining requirements throughout the development lifecycle.

5. Modeling System Processes Data Flow Diagrams Data flow diagrams (DFDs) are a powerful tool for graphically representing the functions, or processes, that capture, manipulate, store, and distribute data within a system. DFDs help analysts coherently structure the information gathered during requirements determination. Decision Tables Decision tables are used to model the logic within system processes, capturing the various conditions and actions that determine how data is processed. This helps ensure the system behaves as intended and meets user requirements. Decision Trees Decision trees provide a graphical representation of decision-making logic, allowing analysts to visually map out the flow of data and decisions within a system. This can be a useful complement to data flow diagrams and decision tables.

6. Conceptual Data Modeling Entities Entities represent the real-world things, such as customers, products, or transactions, that the system needs to track and manage. Identifying the key entities is a crucial step in conceptual data modeling. Attributes Attributes are the characteristics or properties of an entity, such as a customer's name, address, or phone number. Defining the appropriate attributes for each entity is essential for capturing the system's data requirements. Relationships Relationships describe the associations between entities, such as a customer placing an order or a product being sold. Modeling these relationships is key to understanding the system's data structure and dependencies. Entity-Relationship Diagrams Entity-relationship (E-R) diagrams are a common tool for visually representing the conceptual data model, using standardized notation to depict entities, attributes, and the relationships between them.

7. Packaged Data Models Universal Data Models Universal data models provide a generic, reusable foundation for modeling common business entities and relationships, such as customers, products, and transactions. These models can serve as a starting point for developing a tailored data model. Industry-Specific Data Models Industry-specific data models are designed for organizations within particular sectors, such as healthcare, finance, or manufacturing. These models capture the unique entities, attributes, and relationships common to that industry. Validation and Refinement Regardless of the source, conceptual data models should be thoroughly validated and refined through stakeholder feedback and iterative development to ensure they accurately reflect the system's data requirements.

8. Delivering Actionable Requirements Understand the Current System Analysts must first gain a deep understanding of the existing information system, its processes, and its data through techniques like interviews, observation, and document analysis. Gather User Feedback Engaging with key stakeholders, both individually and in collaborative sessions, is crucial for uncovering user needs, pain points, and desired system capabilities. Model the Future System By leveraging tools like data flow diagrams, decision tables, and conceptual data models, analysts can coherently represent the structure and logic of the new system to be developed. Deliver Actionable Requirements The culmination of the analysis phase is a comprehensive set of system requirements that can guide the design, development, and implementation of a successful information system.