Midterm Test - Systems Analysis and Design

The three key principles are: Collaboration, Iterative Development, and Customer Focus.

The three activities are: Defining the project scope, Identifying stakeholders, and Performing feasibility analysis.

<p>The generic competitive strategies are: Cost Leadership, Differentiation, Focus (niche strategy), and Hybrid Strategy. Some examples may include: Cost Leadership strategy: Walmart, Differentiation strategy: Apple, Focus strategy: Red Bull, and Hybrid Strategy: Amazon.</p> Signup and view all the answers

<p>The break-even occurs in the 3rd year.</p> Signup and view all the answers

<p>You should tell the analyst: Plan carefully and clearly define the goals of the interview, Prepare a list of questions beforehand, Establish rapport with the interviewee, Be an active listener, Ask open-ended questions, Use effective questioning techniques, Use a combination of structured and unstructured questions, Note down important information, Be respectful of the interviewee's time, Follow up with interviewee if necessary.</p> Signup and view all the answers

<p>Prototyping is a technique used in system analysis and design for creating a working model or prototype of a system or software to understand user needs and to explore different design ideas and features. The prototype is then used to gather feedback and improve the design. Disadvantages of prototyping include time-consuming, can be expensive, might lead to scope creep, and may not be suitable for all types of projects.</p> Signup and view all the answers

<p>The four levels of Data flow diagram are: Level 0 - Context Diagram, Level 1 - High-Level Diagram, Level 2 - Detailed Diagram, Level 3 - Very Detailed Diagram. These diagrams are used to visualize how information flows within a system. The Context Diagram focuses on the overall system and its external interactions. As we move down the levels, the diagrams become progressively more detailed, focusing on specific processes and data flows. The Level 1 diagram breaks down the overall system into major processes or subsystems. The Level 2 diagram shows more detail about individual processes that were identified in the Level 1 diagram.</p> Signup and view all the answers

<p>The errors in the DFD include 1. Data Store DF2 has no input flow or output flow. 2. Data flow DF5 is not connected to any process or data store. 3. Data flow DF6 is not connected to a process. Data flows must always end or start at a process.</p> Signup and view all the answers

A software development methodology that focuses on iterative development, collaboration, and customer feedback.

Teams work in short iterations (sprints) to deliver working software.

Close collaboration between developers, stakeholders, and users is encouraged.

Regular feedback from users is incorporated to refine the product.

A sequence of activities in a project that determines the overall project duration.

Activities on the critical path have zero slack.

The process of identifying and evaluating potential projects that align with organizational goals.

A structured approach to assessing the feasibility and profitability of potential projects.

A high-level analysis of the business environment to identify threats and opportunities.

Strategies that leverage a company's strengths to gain a competitive advantage in a specific market.

A strategy focused on offering products or services at the lowest cost in the industry.

A strategy that emphasizes differentiation through unique product features or services.

A strategy that targets a specific niche market with specialized products or services.

The point in time when the cumulative benefits of a project equal the total cost of the project.

The cost of capital is the minimum rate of return required for a project to be considered financially viable.

Structured conversations with stakeholders to gather information about their needs and requirements.

A technique for quickly developing a working model of a system to understand user requirements.

Prototypes can change frequently and may not address all system requirements.

Prototyping can be time-consuming and expensive if not managed carefully.

Prototypes can create unrealistic expectations for users, who may believe they are seeing a complete system.

Prototypes can be difficult to discard or modify, even if initial requirements have changed.

A hierarchical representation of data flow within a system, with multiple levels of detail.

The highest level of a DFD, showing the system as a whole.

A level of DFD that decomposes the system into major processes, data stores, and external entities.

A level of DFD that expands upon a specific process from the Level 0 DFD, showing its sub-processes.

A detailed representation of a specific sub-process, showing the finer details of data flow.

A process cannot have a data store as an input.

A data store cannot have a process as an input.

Each process must have at least one input and one output data flow.