System Analysis and Design
Lecture key: L1 = 1st lecture, L2 = 2nd lecture, L3 = 3rd lecture, L4 = 4th lecture, L6 = 6th
lecture.
Part A: Main Questions
Q1. Explain the concept of System Development.
Answer: System development is the step-by-step process of building or improving an
information system. It usually moves through planning, analysis, design, implementation,
testing, and maintenance.
Lecture: L1, L6
Q2. Explain the concept of Software Requirements Specification (SRS).
Answer: SRS is the main document that lists what the system must do. It includes
requirements, models, use cases, limits, and assumptions, and guides design and
development.
Lecture: L6
Q3. What is the key purpose of System Analysis?
Answer: The main purpose of system analysis is to understand the problem, study user
needs, and define what the new system must do. It focuses on the right solution before any
technical design starts.
Lecture: L1, L6
Q4. What is the purpose of System Design?
Answer: System design turns requirements into a technical plan. It shows how the system
will work through database design, interfaces, architecture, and tools.
Lecture: L1, L6
Q5. Illustrate the elements of an information system.
Answer: An information system includes people, hardware, software, data, procedures,
and networks. It also works through input, processing, output, control, and feedback.
Lecture: L2
Q6. Illustrate the life cycle of system analysis and design.
Answer: The main life cycle is planning, feasibility study, systems analysis, system design,
implementation, testing, and maintenance. Each stage supports the next one.
Lecture: L1, L6
Q7. Explain why organizations cannot rely on a single information system.
Answer: Organizations have different users and different decision levels. Daily operations,
management control, and strategic planning each need different kinds of data and reports.
Lecture: L3
Q8. Describe the main functions of a Transaction Processing System (TPS).
Answer: TPS captures, checks, processes, and stores routine daily transactions. In a library,
it handles actions like borrowing, returning, renewing, and paying fines.
Lecture: L3
Q9. What is the difference between MIS and DSS?
Answer: MIS gives regular summary reports for monitoring performance. DSS helps
managers compare options, study scenarios, and make better decisions.
Lecture: L3
Q10. How do Knowledge Work Systems support library professionals?
Answer: KWS support professional knowledge tasks such as metadata creation, indexing,
digital repositories, research support, and preservation work.
Lecture: L3
Q11. A library director wants to decide whether to invest more in digital resources
or physical collections. Which system should be used and why?
Answer: DSS is the best choice because this decision needs comparison of alternatives,
costs, and possible outcomes before choosing one option.
Lecture: L3
Q12. If a circulation system records incorrect due dates, how can this affect higher-
level systems?
Answer: Wrong due dates create wrong fines, wrong records, and wrong reports. This can
mislead managers and affect higher-level decisions.
Lecture: L3
Q13. Why is data validation critical in TPS?
Answer: TPS handles many repeated transactions, so even a small error can spread
quickly. Validation keeps data correct and protects the whole system.
Lecture: L3
Part B: Essay and Application Questions
Q14. Explain why Systems Analysis is a critical phase in the SDLC. What can happen if
it is done poorly?
Answer: Systems analysis is critical because it defines the real problem and the real
requirements. If it is weak, the team may build the wrong system, waste time and money,
and face many changes later.
Lecture: L6
Q15. Why is documentation considered a “contract” during Systems Analysis?
Answer: Documentation is called a contract because it records the agreed requirements
between users and developers. It reduces confusion and gives everyone one clear
reference.
Lecture: L6
Q16. Why is it dangerous to jump directly from Planning to Design without Systems
Analysis?
Answer: Because the team may choose technical solutions before fully understanding the
problem. That often leads to building a system that is organized well but solves the wrong
issue.
Lecture: L6
Q17. Differentiate between Functional and Non-Functional Requirements using
library examples.
Answer: Functional requirements describe what the system does, such as searching books
or calculating fines. Non-functional requirements describe quality, such as fast response
time, security, and 24/7 availability.
Lecture: L6
Q18. How does the Systems Analysis phase affect the System Design phase?
Answer: Analysis gives the requirements that design will use. Good analysis leads to good
database design, good screens, and better technical decisions.
Lecture: L6
Q19. Compare Flowcharts, ER Diagrams, and DFDs in terms of purpose and focus.
Answer: A flowchart shows work steps and decisions. An ER diagram shows data entities,
attributes, and relationships. A DFD shows how data moves through the system.
Lecture: L6
Q20. Explain how DFDs and ER diagrams complement each other during analysis.
Answer: DFDs show the process side of the system, while ER diagrams show the data side.
Together, they give a fuller picture of how the system works.
Lecture: L6
Q21. If users continuously request new features during analysis, how should the
analyst manage scope?
Answer: The analyst should record all requests, discuss them with users, and then
prioritize them based on value, time, and feasibility. This keeps the project controlled.
Lecture: L4, L6
Q22. A university library wants to replace its manual system with an automated
system. Identify three functional requirements, two non-functional requirements,
and two suitable information gathering techniques.
Answer: Functional requirements: track borrowed books, send overdue alerts, and allow
online reservation. Non-functional requirements: quick response and strong security.
Suitable techniques: interviews for detailed needs and observation for real workflow
problems.
Lecture: L6
Q23. A system analyst creates an ER diagram before completing interviews. Critically
evaluate this approach.
Answer: This is risky because the analyst may miss important data or relationships.
Interviews should come first so the ER diagram reflects real user needs.
Lecture: L6
Q24. How does the SRS document reduce future conflicts between users and
developers?
Answer: SRS reduces conflict by writing requirements clearly and officially. It helps both
sides check what was agreed and what should be built.
Lecture: L6
Q25. Explain the difference between Requirements Investigation and Requirements
Specification.
Answer: Requirements investigation means gathering and understanding user needs.
Requirements specification means writing those needs in a clear formal document such as
the SRS.
Lecture: L6
Q26. Why should requirements be prioritized before moving to the design phase?
Answer: Because not all requirements have the same importance. Prioritization helps the
team focus on what matters most and control time, cost, and scope.
Lecture: L4, L6
Q27. A library system has many failures after deployment. Which phase was most
likely weak, and why?
Answer: The analysis phase was likely weak because poor requirements often lead to a
system that does not match real user needs or real work processes.
Lecture: L6
Q28. In what situations would a questionnaire be preferred over interviews?
Answer: A questionnaire is better when there are many users and the analyst wants fast,
standard, and easy-to-compare answers.
Lecture: L6
Q29. Why is observation sometimes more reliable than interviews in systems
analysis?
Answer: Observation shows what people really do, not only what they say they do. It can
reveal hidden problems, shortcuts, and daily work habits.
Lecture: L6
Q30. Explain how conceptual data modelling supports data integrity.
Answer: Conceptual data modelling identifies the right entities, attributes, and
relationships early. This helps prevent missing, repeated, or incorrect data later.
Lecture: L6
Q31. How do non-functional requirements influence system architecture decisions?
Answer: Non-functional requirements affect choices like servers, security controls,
network setup, and system capacity. For example, high performance needs stronger
architecture.
Lecture: L6
Q32. Define a System Analyst in your own words.
Answer: A system analyst is the person who studies business problems, understands user
needs, and turns them into clear system requirements.
Lecture: L4
Q33. Explain the main responsibility of a System Analyst during the SDLC.
Answer: The main responsibility is to gather, understand, analyze, and document
requirements so the team can build the right system.
Lecture: L4
Q34. Why must a System Analyst have both technical and interpersonal skills?
Answer: The analyst needs technical skills to understand systems and models, and
interpersonal skills to talk with users, ask clear questions, and solve conflicts.
Lecture: L4
Q35. Explain how a System Analyst acts as a bridge between users and programmers.
Answer: The analyst understands user language and work needs, then translates them into
technical requirements that programmers can implement.
Lecture: L4
Q36. Why is prioritizing requirements an important role of the System Analyst?
Answer: Because projects have limited time and budget. Prioritizing helps deliver the most
important features first and prevents uncontrolled expansion of work.
Lecture: L4, L6
Q37. Identify the skill or role.
Answer: Resolving requirement conflicts = interpersonal and facilitation skill. Evaluating
cost versus benefits = analytical and feasibility role. Studying workflows = investigation
and analysis role. Explaining specs to programmers = communication and bridge role.
Understanding user language and work = user-focused interpersonal role.
Lecture: L4