The systems analyst acts as a change agent by identifying organizational improvements through the assessment of current information systems, designing new systems to implement necessary changes, and motivating and training users to adapt to these changes . This role is critical in systems development because it bridges the gap between business needs and IT solutions, ensuring that the developed systems align with the organizational goals and improve efficiency and effectiveness . Systems analysts contribute to the adaptation and innovation within businesses by fostering transformation in line with evolving technological capabilities and business strategies .

Coupling and cohesion significantly affect the maintainability and scalability of software systems. High cohesion within modules ensures that responsibilities are well-defined and consolidated, simplifying understanding and enabling easier updates and maintenance. Low coupling, which denotes loose inter-module dependencies, permits individual modules to be modified independently without affecting others, simplifying upgrades and scalability . A system structured with high cohesion and low coupling tends to have improved readability, greater maintainability, and better capability to accommodate growth, making it possible to evolve the software in response to new requirements or technological changes .

The testing and deployment phases are critical stages in the Systems Development Life Cycle (SDLC) that ensure the system's effectiveness and reliability. During the testing phase, various aspects of the system's functionality, performance, and security are assessed to detect defects or deficiencies. It involves system integration tests and user acceptance testing to ensure the system meets the defined requirements . The deployment phase involves placing the system into a live environment, making it operational for users. Deployment strategies may involve incrementally phasing in the new system or complete replacement of the old system . These phases are interconnected as successful testing identifies issues that must be resolved before deployment, and a well-executed deployment supports system stability and user satisfaction .

The use of questionnaires in system development projects enhances the requirements gathering process by systematically collecting data from various stakeholders. They serve as research instruments comprising a set of questions designed to capture both qualitative and quantitative information about user needs, expectations, and context . Questionnaires allow for the efficient collection of data from a large sample size, ensuring that a wide range of perspectives and insights are gathered, which can be analyzed to inform the system design and development . They provide structured and consistent data inputs that contribute to comprehensive requirements documentation, facilitating the creation of a system that accurately meets user needs .

Iterative processes in the Systems Development Life Cycle (SDLC) enhance outcomes by allowing ongoing refinement and adaptation of the system. By repeatedly revisiting the various phases—such as analysis, design, and testing—the development team can incorporate user feedback, fix issues, and adjust to changes in requirements or technology . This results in a more flexible development approach, which can improve the accuracy of the system’s final design to better meet user needs and reduce the risk of major failures at later stages . Iteration encourages continuous improvement and ensures that the system evolves alongside technological advancements and shifting user expectations .

Data flow diagrams (DFDs) facilitate communication among project stakeholders by providing clear, visual representations of how data flows through a system. This can help align understanding across technical and non-technical audiences, such as developers, managers, and decision-makers, ensuring everyone shares the same view of system processes . The basic rules for creating DFDs include ensuring each process has at least one input and one output, each data store having data flow in and out, and that data must pass through a process for storage or action. This structured visual language helps convey complex system interactions succinctly and accurately .

The 'Design' phase in the Systems Development Life Cycle (SDLC) is crucial as it sets the blueprint for the entire system development. It involves outlining the system's architecture, technical specifications, and interface design, ensuring that the proposed solution aligns with project requirements and addressing deficiencies identified in the planning phase . Inadequacies in this phase can lead to misalignment between the system's functionality and business needs, increased costs, project delays, and potentially a system that is not user-friendly or scalable, thereby failing to solve the intended problems . Moreover, poor design can lead to costly rework and lack of stakeholder satisfaction .

A feasibility study contributes to the success of a project by evaluating the potential for success across various factors, such as economic, technical, legal, and scheduling considerations. It helps in identifying viable options, predicting obstacles, and anticipating resource requirements, thus ensuring informed decision-making . Essential components of a feasibility study include an economic feasibility analysis, technical assessment, legal compliance checks, and a schedule feasibility overview to ensure all aspects are considered for a sustainable project outcome .

Deployment strategies within the SDLC can significantly impact user adoption and satisfaction by determining how smoothly a new system is introduced and integrated into an organization. Phased deployment, where segments of the new system are gradually rolled out, allows users to adjust incrementally and provides opportunities to address issues in stages, which can enhance user satisfaction through reduced disruption . In contrast, a full system deployment, while potentially quicker, can overwhelm users and pose significant operational risks if not properly managed . Choosing the appropriate deployment strategy is crucial, as it affects how users experience the transition, their willingness to adopt the new system, and their overall satisfaction based on the system's stability and utility post-deployment .

Cohesion refers to how closely related and focused the responsibilities of a single module are, indicating the degree of intra-module interdependence. High cohesion within a module is desirable because it means that the module's responsibilities are well-defined and aligned . Coupling, on the other hand, is a measure of the interdependence between different modules, with low coupling being preferred to reduce dependencies and increase the modularity of the system . Balancing cohesion and coupling is significant because high cohesion leads to more understandable and manageable modules, while low coupling minimizes the risk of changes in one module affecting others, thereby facilitating maintainability and scalability in a software project .