1a) Insufficient user participation in IT projects can lead to misaligned systems, delayed timelines and
budget overruns. When users aren't involved, developers may misinterpret business needs, resulting
in poor functionality. This lack of involvement can cause IT teams to take on user tasks, slowing
progress and increasing costs. Poor documentation often follows, with user manuals written by
developers lacking clarity. Insufficient user involvement leads to systems that don't meet actual
business needs. Delays and cost overruns become more likely. Effective system adoption is hindered
by unclear documentation. Finding the right balance of user involvement is crucial to avoid these
issues. To mitigate these risks, project managers should prioritize user engagement strategies. Regular
feedback loops can help ensure developers understand business needs. User training and support are
also essential for successful system adoption. Clear communication channels can prevent
misunderstandings and misinterpretation.
b) Excessive user involvement can lead to unrealistic expectations and demands for impractical
features. This can cause dissatisfaction even if the project ultimately succeeds. Highly engaged users
may disrupt workflows with constant feedback and changes. Developers may feel frustrated, leading
to reduced productivity and morale. Frequent revisions can prolong timelines and complicate project
management. Scope creep becomes a major issue, affecting project delivery. Excessive involvement
can strain the development process. Ultimately, it can impact the project's overall success and team
dynamics. To manage this, clear boundaries and expectations should be set with users from the start.
Prioritizing feedback and focusing on core objectives can help maintain project momentum.
Establishing a structured change management process can also mitigate scope creep. Regular check-
ins with users can help manage expectations and prevent over-involvement. Balancing user input with
project goals is crucial for success.
2) Two adavantages of each of the following data collection methods
a) JAD
Joint Application Development (JAD) enables accelerated delivery through coordinated workshops
that streamline requirement gathering, reducing development time. This approach also promotes cost
efficiency by ensuring early alignment between stakeholders. As a result, rework and resource waste
are minimized. By adopting JAD, projects can achieve faster delivery and better resource utilization.
b) Role Play
Role play identifies usability issues through simulated interactions. This method clarifies user
workflows and pain points. By acting out scenarios, users can highlight potential problems. Role play
helps designers understand user behavior.
c) Focus Group
Focus groups gather diverse user perspectives to uncover unmet needs. This method facilitates
consensus on feature priorities. By bringing users together, designers can identify trends. Focus
groups provide valuable insights into user preferences.
d) Interface Analysis
Interface analysis reveals inconsistencies in user interactions. This method optimizes system usability
through iterative design. By examining user interfaces, designers can identify areas for improvement.
Interface analysis helps create more intuitive systems.
3) System Analysis
System analysis focuses on understanding business requirements and existing processes. It identifies
problems and defines what the system must achieve. Techniques like interviews and data modeling
are used to gather requirements. The goal is to identify needs and constraints. The output is
requirement documents that outline the system's objectives.
System Design
System design translates requirements into technical specifications, outlining how the system will
function. It involves architectural planning, database design, and interface prototyping. The goal is to
create technical solutions that meet the requirements. System design provides a roadmap for
development. The output includes architectural diagrams and prototypes.
Key Differences
System analysis and system design differ in their goals and outputs. System analysis focuses on the
"what", defining what the system should do. System design focuses on the "how", outlining how to
implement the solution. The outputs also vary, with analysis producing requirement documents and
design producing technical specifications. System analysis identifies needs and constraints, while
system design creates technical solutions. These differences highlight the distinct roles of analysis and
design in the development process. By understanding these differences, developers can ensure a
smooth transition from analysis to design.
REFERENCES
i. "Systems Analysis and Design" by Shelly & Rosenblatt.
ii. "Software Engineering: A Practitioner’s Approach" by Roger S. Pressman.
iii. "Why IT Projects Fail: Lack of User Involvement"
iv. "Moving Beyond User Participation to Achieve Successful IS Design"
