System Analysis and Design
Explores the systems concept and uses systems analysis and design methodology in developing information systems
Exam objectives
- Define a system and list its characteristics
- Classify systems as open/closed, natural/manmade, living/physical — with examples
Important areas to cover
- Classify-with-example short questions are a common warm-up mark
Lesson content not added yet.
Exam objectives
- Compare OAS, TPS, MIS, DSS, ESS, GIS, KMS, CMS and ERPS by objective and functionality
Important areas to cover
- Matching a system type to a described business scenario is a frequent MCQ/short-answer format
Lesson content not added yet.
Exam objectives
- List and describe the waterfall, spiral, agile, prototyping and RAD models
- Compare structured vs object-oriented development methodologies
Important areas to cover
- Comparing waterfall vs spiral vs agile, each with its own diagram, is a frequent essay component
Lesson content not added yet.
Exam objectives
- Define SSADM and list the SDLC stages it covers
Important areas to cover
- Only 2 periods allocated — expect a short definitional question, not an essay
Lesson content not added yet.
Exam objectives
- Describe the tasks of preliminary investigation and how information problems/priorities are identified
- Explain technical, economic, operational and organizational feasibility
Important areas to cover
- "Describe the four types of feasibility" is a reliable short-structured question
Lesson content not added yet.
Exam objectives
- Distinguish functional from non-functional requirements and write requirements in IEEE-style form
- Draw a Business Activity Model, context diagram, document flow diagram and levelled Data Flow Diagrams (DFDs) for a given scenario
- Write Elementary Process Descriptions (EPDs) and draw a Logical Data Structure (LDS)
- Propose and justify a Business System Option (BSO)
Important areas to cover
- DFD drawing (context diagram plus level-1, with correct process/data-store/external-entity/data-flow notation) is the single most heavily weighted diagram-drawing skill in the whole A/L ICT syllabus — the essay question to prioritise
- EPD writing in structured pseudocode and BSO justification are near-certain companion sub-questions
Lesson content not added yet.
Exam objectives
- Produce logical DFDs and elementary process descriptions for the proposed (to-be) system
- Design a user interface and a logical data structure for the proposed system
- Specify table/record specifications and a data dictionary for the physical database design
Important areas to cover
- "Reconstruct the logical design from elementary processes to context diagram" (and vice versa) is a recurring, high-mark essay question — practise both directions
Lesson content not added yet.
Exam objectives
- List the testing methods: white-box, black-box, unit, integration, system, acceptance testing
- Describe what each testing method checks and when it is used
Important areas to cover
- Matching a testing method to its purpose is a common short-structured question
Lesson content not added yet.
Exam objectives
- Compare parallel, direct, pilot and phased deployment/changeover methods
- Describe post-implementation activities: installation, data migration, training, review and maintenance
Important areas to cover
- "Compare deployment methods on risk vs cost" is a frequent short-essay prompt
Lesson content not added yet.
Exam objectives
- Weigh the costs/benefits of off-the-shelf packages against custom development
- Describe business process gap analysis, mapping and reengineering
Important areas to cover
- Usually a shorter structured question comparing bespoke vs packaged solutions
Lesson content not added yet.