Identify stakeholders and their interests, and explain four key skills for a systems analyst.

a) Step 1: Identify four stakeholders and their interests. • Customers: Interested in easily placing orders online via the website (Requirement 3). • Office Staff: Interested in easily adding new customers (Requirement 1), recording customer orders (Requirement 2), revising order details (Requirement 5), generating, printing, and emailing invoices (Requirements 4, 7), and varying payment terms (Requirement 9). • Production Manager: Interested in viewing all customer orders to plan production (Requirement 8). • Management (Warren/MD): Interested in driving up sales, receiving weekly reports of unpaid invoices (Requirement 6), and ensuring the system interfaces with the payroll system (Requirement 9). b) Step 1: Explain four key skills for a systems analyst to deploy an information system. • Analytical Skills: To understand complex business problems, gather detailed requirements from various stakeholders, and identify logical solutions for the system. • Communication Skills: To effectively interact with users, management, and developers, translate technical concepts into understandable language, and facilitate discussions to ensure alignment. • Technical Skills: To understand system architecture, database design, software development principles, and potential technologies to ensure the proposed solution is feasible and robust. • Problem-Solving Skills: To identify issues during system development and deployment, troubleshoot errors, and devise effective solutions to ensure the system functions correctly and meets business needs. c) Step 1: Explain the main phases of the Information System Development Life Cycle (SDLC) with examples. • Planning: This initial phase defines the project scope, objectives, and feasibility. Example: For Warren, this involves determining the high-level goals of the new system, such as improving order processing efficiency and increasing online sales. • Analysis: In this phase, detailed requirements are gathered from all stakeholders. Example: Interviewing office staff, customers, and the production manager to understand specific needs like how orders are placed, what data needs to be stored, and what reports are required. • Design: This phase involves creating the blueprint for the system, including its architecture, database structure, user interface, and system processes. Example: Designing the database schema for customer and order information, and sketching the user interface for order entry and invoice generation screens. • Implementation & Testing: This phase involves coding the system based on the design specifications and then rigorously testing it to ensure it meets all requirements and is free of defects. Example: Developing the online order module and the invoice generation feature, then testing if orders are correctly recorded and invoices are automatically created. • Deployment & Maintenance: This final phase involves rolling out the system to users, providing training, and offering ongoing support, updates, and enhancements. Example: Installing the new system, training the office staff on its use, and providing technical support for any issues that arise after the system goes live. d) Step 1: Identify two functional and two non-functional requirements. • Functional Requirements: 1. The system must record customer orders and payments, retaining data for five years (Requirement 2). 2. The system must generate invoices automatically as orders are received (Requirement 4). • Non-functional Requirements: 1. All new customers need to be added to the system easily (Requirement 1 - Usability). 2. It should be possible to vary the payment terms on invoices and interface with the payroll system (Requirement 9 - Flexibility/Interoperability). e) Step 1: Explain two types of feasibility study. • Technical Feasibility: This study assesses whether the proposed system can be built using existing or readily available technology, resources, and expertise within the organization. It considers if the necessary hardware, software, and technical skills are present or can be acquired. • Economic Feasibility: This study evaluates the financial viability of the project by comparing the estimated costs of developing and operating the system against the potential benefits, savings, and return on investment. It helps determine if the project is financially justifiable. f) Step 1: Model the requirements using a Data Flow Diagram (DFD). A Data Flow Diagram (DFD) visually represents the flow of information for the system. Below is a description of the components and flows for a Level 1 DFD based on Warren's requirements: External Entities: • Customer: Places orders online. • Office Staff: Manages customers, orders, invoices, and reports. • Production Manager: Views orders for production planning. • Payroll System: Interfaces for payment terms and invoice data. Processes: • Process 1: Order & Customer Management: Handles adding new customers, recording customer orders (online and via staff), and initial invoice generation. • Process 2: Invoice & Report Generation: Manages invoice revisions, generates weekly unpaid invoice reports, and handles printing/emailing invoices. • Process 3: Production Order View: Provides the Production Manager with access to all customer orders. • Process 4: System Integration & Configuration: Manages payment term variations and interfaces with the payroll system. Data Stores: • D1: Customer Data: Stores information about customers. • D2: Order Data: Stores details of customer orders and payments. • D3: Invoice Data: Stores generated invoice details, including payment terms. Data Flows: 1. Customer (Order Details) Process 1: Order & Customer Management 2. Office Staff (New Customer Info) Process 1: Order & Customer Management 3. Process 1: Order & Customer Management (New Customer Record) D1: Customer Data 4. Process 1: Order & Customer Management (Order Record