System Analysis and Design (BSc CSIT, CSC315): the questions likely to come
33 analyzed questions from 8 past papers (2074-2082), grouped by syllabus unit — each with its probability, how often it's been asked, and where to study the answer.
What is a CASE tool? Explain the different components of CASE tools and their role in system development.
CASE Tools
CASE (Computer-Aided Software Engineering) tools are software applications that automate and support the various activities of the System Development Life Cycle, such as analysis, design, coding, testing and documentation. They improve productivity, reduce errors and enforce standards by providing a common, integrated environment for analysts, designers and developers.
Components of CASE Tools
CASE environments are usually built from the following components:
- Central Repository (Information Repository): A shared database that stores all project data — data dictionary entries, diagrams, design specifications and metadata — ensuring consistency and reuse across the project.
- Diagramming / Graphics Tools: Used to draw DFDs, ER diagrams, structure charts, flowcharts and UML diagrams that model the system pictorially.
- Data Dictionary / Documentation Tools: Record definitions of data elements, data stores and processes, and automatically generate project documentation.
- Analysis and Verification Tools: Check models for completeness, consistency and balancing errors (e.g. ensuring data flows in a DFD are properly defined).
- Code Generators: Automatically produce source code or database schemas from the design specifications.
- Prototyping / Screen-and-Report Generators: Help build sample input screens, forms and reports for user validation.
- Project Management Tools: Support scheduling, estimation and tracking of project tasks.
Classification
- Upper CASE: Supports early SDLC phases — planning, analysis and design (diagramming, repository).
- Lower CASE: Supports later phases — coding, testing and maintenance (code generators, debuggers).
- Integrated CASE (I-CASE): Combines both through a shared repository.
Role in System Development
- Speeds up development and reduces manual effort.
- Enforces standardization and consistency of diagrams and documentation.
- Improves quality through automated error and consistency checking.
- Eases maintenance because changes are reflected automatically across linked components.
- Enhances communication among the development team via a shared repository.
System Analysis: Tools and Techniques
What is a CASE tool? Explain the different components of CASE tools and their role in system development.
What is a Data Flow Diagram (DFD)? Draw a context diagram and a level-0 DFD for a retail clothing store selling system.
Define feasibility study. Explain the different categories of feasibility and describe how economic feasibility is measured using cost-benefit analysis.
What is a data dictionary? Explain its contents and importance in structured analysis.
Explain the relationship between DFD and ERD in system modelling.
What is structured English? Write structured English for a process of computing employee payroll.
Compare and contrast between observation and document analysis while requirement determination. Explain radical methods for determining the requirements.
Draw DFD for the following scenario:
A patient after registration in the online pathology system will get login credentials. After the valid login the patient upon entering the details of test to be conducted will get the test date and time. The patient can also pay online. The patient can download the test report from the system after notification. The patient will also get schedule for doctor visit if required and in that case the report will also be emailed to the doctor.
Explain the different fact-gathering techniques used in system analysis.
Differentiate between technical, operational and economic feasibility.
Explain decision tables and decision trees with an example for representing process logic.
Explain the rules and symbols used for drawing a Data Flow Diagram.
An initial investment of Rs. 5,00,000 is required to start a company. The cash flow-in is Rs. 60,000 per year. Assuming the interest rate as 15%, calculate the discounted payback period. (use Net Present Value)
Sit a probable paper
A full mock exam built from the most likely questions, mirroring the real paper's structure. Every slot is a real past question.
Most Probable Paper
Mirrors the real structure · 60 marks · based on 8 past papers
- 1.[10 marks]
What is a CASE tool? Explain the different components of CASE tools and their role in system development.
This question has recurred in 3 of 8 years; so far only in internal assessments, not the board; and its topic (System Analysis: Tools and Techniques) appears in 100% of years.
- 2.[10 marks]
What is a Data Flow Diagram (DFD)? Draw a context diagram and a level-0 DFD for a retail clothing store selling system.
This question has recurred in 3 of 8 years; so far only in internal assessments, not the board; and its topic (System Analysis: Tools and Techniques) appears in 100% of years.
- 3.[10 marks]
Define feasibility study. Explain the different categories of feasibility and describe how economic feasibility is measured using cost-benefit analysis.
This question has recurred in 3 of 8 years; so far only in internal assessments, not the board; and its topic (System Analysis: Tools and Techniques) appears in 100% of years.
- 1.[5 marks]
What is a data dictionary? Explain its contents and importance in structured analysis.
This question has recurred in 5 of 8 years; so far only in internal assessments, not the board; and its topic (System Analysis: Tools and Techniques) appears in 100% of years.
- 2.[5 marks]
What is structured English? Write structured English for a process of computing employee payroll.
This question has recurred in 5 of 8 years; so far only in internal assessments, not the board; and its topic (System Analysis: Tools and Techniques) appears in 100% of years.
- 3.[5 marks]
Differentiate between technical, operational and economic feasibility.
This question has recurred in 5 of 8 years; so far only in internal assessments, not the board; and its topic (System Analysis: Tools and Techniques) appears in 100% of years.
- 4.[5 marks]
Differentiate between RAD and Agile development approaches.
This question has recurred in 5 of 8 years; so far only in internal assessments, not the board; and its topic (System Concept and the Information System Environment) appears in 100% of years.
- 5.[5 marks]
Define a system. Explain the characteristics and different types of systems with examples.
This question has recurred in 5 of 8 years; so far only in internal assessments, not the board; and its topic (System Concept and the Information System Environment) appears in 100% of years.
- 6.[5 marks]
What is normalization? Explain 1NF, 2NF and 3NF with examples.
This question has recurred in 5 of 8 years; so far only in internal assessments, not the board; and its topic recurs in 6 of 8 years.
- 7.[5 marks]
Explain the different system conversion (changeover) strategies: direct, parallel, phased and pilot.
This question has recurred in 5 of 8 years; so far only in internal assessments, not the board; and its topic recurs in 6 of 8 years.
- 8.[5 marks]
Explain the relationship between DFD and ERD in system modelling.
This question has recurred in 4 of 8 years; so far only in internal assessments, not the board; and its topic (System Analysis: Tools and Techniques) appears in 100% of years.
- 9.[5 marks]
Explain the different fact-gathering techniques used in system analysis.
This question has recurred in 4 of 8 years; so far only in internal assessments, not the board; and its topic (System Analysis: Tools and Techniques) appears in 100% of years.
Behind the numbers
The raw evidence the predictions are computed from: marks per unit per year, syllabus weights, trends, and coverage.
Show the heatmap, topic table and coverage analysis
The receipt: marks per unit, per year
Each row is a syllabus unit, each column an exam year, each cell the marks that unit earned that year. Click any cell to see the actual questions behind it.
| # | Syllabus unit | Probability | Appeared | Avg marks | Syllabus weight | Exam vs syllabus | Trend | Questions |
|---|---|---|---|---|---|---|---|---|
| 1 | U2System Analysis: Tools and Techniques | Very likely100% | 33.8 | 18%8 lecture hrs | Over-examinedexam 45% · syllabus 18% | Fading | 10 recurring13 total | |
| 2 | U1System Concept and the Information System Environment | Very likely100% | 18.8 | 13%6 lecture hrs | Over-examinedexam 25% · syllabus 13% | Steady | 5 recurring8 total | |
| 3 | U4Detailed Design | Likely75% | 14.2 | 20%9 lecture hrs | Under-examinedexam 14% · syllabus 20% | Steady | 3 recurring5 total | |
| 4 | U5Implementation and Software Maintenance Evaluation | Likely75% | 9.2 | 13%6 lecture hrs | Balancedexam 9% · syllabus 13% | Steady | 2 recurring4 total | |
| 5 | U3System Design | Possible50% | 10 | 22%10 lecture hrs | Under-examinedexam 7% · syllabus 22% | Rising | 1 recurring3 total | |
| 6 | U6Security, Disaster, Recovery and Ethics in System Development | Occasional0% | 0 | 13%6 lecture hrs | Under-examinedexam 0% · syllabus 13% | Steady | None |
Study smart, not hard
Drag the slider: studying the top 3 units in priority order covers ~84% of all observed marks.
- ~80% line
Lecture time vs exam marks
Where the exam pays more than the curriculum spends: ● lectures vs ● exam marks, as a share of the whole course. A long teal-leading bar = high-yield unit.