SYSTEM ANALYSIS AND DESIGN.docx

**SYSTEM ANALYSIS AND DESIGN. (SAD) ANSWERS** 1. **What is a system?** - A system is a group of connected parts working together for a purpose or one common goal. 2. **Characteristics of a system:** - Interconnected: Parts interact with each other. - Boundary: Defines its limits. -...

**SYSTEM ANALYSIS AND DESIGN. (SAD) ANSWERS** 1. **What is a system?** - A system is a group of connected parts working together for a purpose or one common goal. 2. **Characteristics of a system:** - Interconnected: Parts interact with each other. - Boundary: Defines its limits. - Purpose: Has a specific goal. - Inputs and Outputs: Takes inputs, produces outputs. - Environment: Exists within an environment that affects it**.** 3. **Classifications of a system:** - Open vs Closed: Open interacts with the environment, closed does not. - Physical vs Abstract: Physical is tangible, abstract is conceptual. - Deterministic vs Probabilistic: Deterministic is predictable, probabilistic is based on chance**.** 4. **Who is a system analyst?** - A professional who studies systems to improve efficiency and solve problems. 5. **Roles of a system analyst:** - Gather Requirements: Identify needs. - System Design: Create system specifications. - Feasibility Analysis: Assess viability. - Oversee Implementation: Supervise development. - Testing: Ensure the system works correctly. 6. **Qualities of a good system analyst:** - Analytical Skills: Understand complex systems. - Communication Skills: Explain clearly. - Problem-Solving Skills: Find solutions. - Technical Knowledge: Know current technologies. - Attention to Detail: Be accurate. 7. **Qualities of a good system analyst:** - Analytical Skills: Understand complex systems. - Communication Skills: Explain clearly. - Problem-Solving Skills: Find solutions. - Technical Knowledge: Know current technologies. - Attention to Detail: Be accurate. 8. **What is system analysis?** - The study of systems to identify problems and propose improvements. 9. **What is an information system?** - A system combining hardware, software, data, people, and processes to manage information. 10. **Three major types of information systems:** - Transaction Processing Systems (TPS): Handle daily transactions. - Management Information Systems (MIS): Help manage organizations. - Decision Support Systems (DSS): Assist in decision-making. 11. **Explain the following terms in system analysis:** - Feasibility Study: Checks if the project can be done and is worth it. - Requirement Specification: Lists what the system needs to do and how it should perform. - System Design: Creates a detailed plan for building the system. - Implementation: Actually builds and launches the system based on the plan. - Maintenance: Keeps the system running smoothly with updates and fixes. 12. **What is the system development life cycle (SDLC)?** - SDLC is a process used to plan, create, test, and deploy software. 13. **Phases of SDLC:** - Planning: Decide the goals and scope. - Analysis: Gather and understand requirements. - Design: Plan the system's structure. - Implementation: Build and test the system. - Maintenance: Update and fix the system. 14. **What is an information system?** - A system that collects, processes, and manages information using hardware, software, and people. 15. **Why should organizations have information systems?** - Efficiency: Streamlines operations. - Decision Making: Provides useful data. - Communication: Improves communication. - Competitive Edge: Helps stay ahead in the market. 16. **What is a feasibility study**? - It checks if a project is doable and worth it. 17. **Why feasibility study?** - To see if the project is practical and beneficial. 18. **Types of feasibility study:** - Technical: Can we make it with current technology? - Economic: Is it cost-effective? - Legal: Are there any legal issues? - Operational: Will it work in the organization? - Schedule: Can it be done on time? 19. **Difference between technical and economic feasibility:** - Technical: Focuses on technology. - Economic: Focuses on costs and benefits. - Legal and ethical feasibility: - Legal: Ensures the project follows laws. - Ethical: Makes sure the project is morally right. 20. **What is system conversion?** - Changing from an old system to a new one. 21. **Conversion approaches:** - Parallel: Use both systems at the same time. - Direct: Switch to the new system immediately. - Pilot: Test the new system in one area first. - Phased: Implement the new system in stages. 22. **Advantages of feasibility study:** - Risk Mitigation: Find issues early. - Resource Allocation: Plan resources well. - Decision Making: Provide data for decisions. 23. **What is the spiral life cycle?** - A development model that combines planning, risk analysis, engineering, and evaluation in cycles. 24. **Stages in spiral model:** - Planning: Set goals and alternatives. - Risk Analysis: Identify and solve risks. - Engineering: Develop the system. - Evaluation: Review and improve. 25. **Application of spiral model:** - Used in large, complex projects like defense systems. A**. Discuss the system development lifecycle** SDLC is a structured process used to develop information systems. It ensures the system meets business requirements, is completed on time, and is cost-effective. **B. Describe different phases of SDLC** Planning: Identify objectives and resources. Analysis: Gather detailed requirements. Design: Create system architecture and design specifications. Implementation: Develop, test, and integrate system components. Maintenance: Provide ongoing support and improvements. **C. Why organizations develop information systems** Efficiency: Automate and streamline operations. Data Management: Organize and manage data effectively. Decision Making: Provide accurate information for better decisions. Competitive Advantage: Enhance market position and innovation. **D. Describe different stages of a typical system development lifecycle** Initiation: Define goals and feasibility. Requirements Gathering: Collect user and system requirements. System Design: Plan system structure and user interfaces. Development: Write and compile code, create databases. Testing: Verify that the system works as intended. Deployment: Roll out the system to users. Maintenance: Update and fix the system over time. **e. What is system conversion?** System conversion is the process of transitioning from an old system to a new one, ensuring minimal disruption to operations. **F. Describe different system conversion approaches** Parallel Conversion: Run both old and new systems simultaneously until the new system is proven reliable. Direct Cutover: Switch entirely to the new system in one go. Pilot Conversion: Implement the new system in a small part of the organization first. Phased Conversion: Gradually implement the new system in stages. **A. What is a system development lifecycle model?** An SDLC model is a framework that outlines the steps involved in developing an information system. It helps ensure the system is well-planned, designed, and implemented. **B. Discuss different system development lifecycle models** Waterfall Model: A linear and sequential approach where each phase must be completed before the next one begins. V-Model (Validation and Verification): An extension of the Waterfall Model, emphasizing testing at each stage. Iterative Model: Develops the system in repeated cycles (iterations), refining each version. Agile Model: Focuses on flexibility, customer feedback, and iterative development with small, manageable chunks. Spiral Model: Combines iterative development with systematic aspects of the Waterfall Model, focusing on risk assessment. **C. Talk about Spiral Life Cycle Model** Design: The Spiral Model involves multiple iterations (or spirals), each consisting of four phases: planning, risk analysis, engineering, and evaluation. Each spiral builds on the previous one, gradually developing the system. Application: Ideal for large, complex projects where requirements may change, such as defense systems or large-scale infrastructure projects. **Advantages:** Handles changing requirements. Allows for extensive risk analysis. Encourages customer feedback at each stage. **Disadvantages.** Can be expensive and time-consuming. Requires careful management and documentation. **D. Differentiate between JAD and RAD** JAD (Joint Application Development): A collaborative approach involving stakeholders and developers in a series of intensive workshops to gather requirements and design the system. RAD (Rapid Application Development): Focuses on quick development and iteration of prototypes, with user feedback integrated at each stage. **E. Describe the JAD process is based on four simple ideas** **Involvement:** Bring together key stakeholders and users. **Focus:** Concentrate on specific parts of the system in each workshop. **Integration**: Combine different viewpoints to create a comprehensive design. **Iteration:** Repeat the process as needed to refine requirements and solutions. 26. **What is Software Prototyping?** Software prototyping is the process of creating an early, simplified version of a software application to visualize and test its features and functions. It helps stakeholders understand how the final product will work. B. **System Development Lifecycle (SDLC) and Software Prototyping** In the SDLC, prototyping can be used during the design phase to create mock-ups of the system. It allows for early user feedback and can lead to better requirement gathering and system design before full-scale development begins. C. **Different Types of Software Prototypes** - **Throwaway/Rapid Prototyping**: Create quick models that are discarded after use. They help refine user requirements. - **Evolutionary Prototyping:** Build prototypes that evolve into the final system through continuous refinement. - **Incremental Prototyping:** Develop parts of the system in increments, and eventually combine them into the final product. - **Extreme Prototyping**: Mostly used for web development. Involves three phases: create a static mock-up, code the dynamic aspects, and refine through user feedback. - D. Software Prototyping Pros and Cons **Pros**: - **Early Feedback:** Helps gather user feedback early in the development process. - **Better Understanding:** Allows stakeholders to visualize the system. - **Reduced Risks**: Identifies potential issues early. **Cons:** **Scope Creep**: Users may continuously request changes. **Resource Intensive**: Can be time-consuming and expensive. **Miscommunication**: Prototypes may create false expectations if not managed well. E**. Stepwise Approach to Design a Software Prototype** - **Identify Requirements**: Gather and understand user needs and requirements. - **Develop Initial Prototype:** Create a basic version focusing on core features. - **User Evaluation**: Have users test and provide feedback on the prototype. - **Refinement**: Make necessary changes based on user feedback. - **Iterate**: Repeat the process until the prototype meets user expectations. - **Finalize:** Use the refined prototype as a basis for developing the final system. 1. **A. Discuss System Development Project Fundamentals** System development projects involve creating and implementing information systems to meet organizational needs. Key fundamentals include project planning, requirements gathering, system design, development, testing, deployment, and maintenance. Effective communication, stakeholder involvement, and resource management are crucial for project success. 1. **B. What is Project Initiation?** Project initiation is the first phase of a project where the idea is explored and defined. It involves identifying the project\'s purpose, scope, objectives, stakeholders, and feasibility. - **C. Why is Project Initiation Important?** Project initiation is crucial because it sets the foundation for the entire project. It helps ensure that the project is viable, aligns with business goals, and has clear objectives. Proper initiation helps avoid costly mistakes and misunderstandings later. **D. Describe the Process of Project Initiation** **Conceptualize**: Develop the initial project idea. **Feasibility Study:** Assess if the project is practical and viable. **Define Objectives**: Clarify what the project aims to achieve. **Identify Stakeholders**: Determine who will be involved and affected. **Develop a Project Charter**: Create a formal document outlining the project's purpose, scope, and key details. Approval: Get approval from stakeholders to move forward. **E. What is Project Feasibility?** Project feasibility assesses whether a project is possible and worthwhile. It includes examining technical, economic, legal, operational, and scheduling aspects to ensure the project can be successfully completed. **Cost-Benefit Analysis (CBA) for Projects** **A. Discuss Cost-Benefit Analysis for Project** Cost-benefit analysis (CBA) is a process used to evaluate the financial feasibility of a project by comparing the costs involved against the benefits it will deliver. It\'s a crucial step to ensure that the project is financially viable and worth pursuing. **B. What Is a Cost-Benefit Analysis?** CBA is a systematic approach to estimating the strengths and weaknesses of alternatives. It helps to determine options that provide the best approach to achieving benefits while preserving savings. Essentially, it involves calculating the net benefits by subtracting the costs from the benefits. **C. Talk about Costs and Benefits** Costs: Include all expenses involved in the project, such as labor, materials, equipment, and any indirect costs like overheads. Benefits: Encompass all gains from the project, such as increased revenue, cost savings, improved efficiency, and any intangible benefits like customer satisfaction or brand enhancement. **D. The Purpose of Cost-Benefit Analysis** The main purpose of CBA is to determine the best course of action by quantifying the financial impact. It helps stakeholders make informed decisions, allocate resources efficiently, and justify investments by demonstrating the value derived from the project. **E. How to Do CBA** **Identify Costs and Benefits:** List all potential costs and benefits associated with the project. **Assign Monetary Value**: Quantify costs and benefits in monetary terms. **Calculate Net Benefits:** Subtract total costs from total benefits to find the net benefit. **Analyze Results**: Evaluate whether the net benefits justify the project. Compare with alternative options if necessary. **F. Limitations of CBA** **Intangible Benefits**: Hard to quantify benefits like customer satisfaction. **Future Uncertainties:** Inaccuracies in predicting future costs and benefits. **Subjectivity**: Bias in assigning monetary values to costs and benefits. **Complexity:** Can be complex and time-consuming for large projects.