CCEA A-Level Digital Technology 2650
Systems Analysis and Development Approaches
Design, Development and Testing
Implementation and System Security
Programming
Data, Information and Data Representation
Computer Architecture and Processing Systems
System Software, Application Software and the User Interface
Web Technology and Multimedia
Networks
Databases
Artificial Intelligence, Expert Systems and Robotics
Mobile Technology, Data Mining and Cloud Computing
Individual, Social and Legal Considerations
The Development Project: Analysis and Design
The Development Project: Build, Testing and Evaluation
Systems Analysis and Development Approaches
- 12 subtopics
- 36 things to know
- AS Unit 1
What Systems Analysis and Development Approaches covers
Systems Analysis and Development Approaches is examined in Unit AS 1, Approaches to Systems Development. It covers the software crisis and the need for systems development, user needs, time and cost, roles in a systems development team, the purpose of analysis, fact-finding techniques, functional and non-functional requirements, data flow diagrams, the waterfall model, rapid application development and Agile, resources, constraints and risks in a software project, project management, Gantt charts and critical path analysis and version management.
The 12 subtopics
Each one has its own page.
- The software crisis and the need for systems developmentTwo consequences for an organisation whose software project fails and legacy system.Open →
- User needs, time and costThree main factors that shape any systems development project, user needs in a development project and development costs and running costs.Open →
- Roles in a systems development teamMain role of a systems analyst, three tasks a systems analyst carries out during analysis and main role of a project manager.Open →
- The purpose of analysisPurpose of the analysis stage of systems development, three parts that make up any computer system and role of the user interface within a computer system.Open →
- Fact-finding techniquesFact-finding in systems analysis, how an interview is used as a fact-finding technique and how a questionnaire is used as a fact-finding technique.Open →
- Functional and non-functional requirementsWhat a system must do against the qualities it must have, how each is written so it can be tested, and why an untestable requirement can never be signed off.Open →
- Data flow diagramsPurpose of a data flow diagram, four symbols used in a data flow diagram and context diagram.Open →
- The waterfall modelWaterfall model of systems development, stages of the waterfall model in order and produced at the end of each waterfall stage.Open →
- Rapid application development and AgileRapid Application Development with timeboxing and MoSCoW prioritisation, the Agile approach with sprints, user stories and the product backlog, and how each handles a change of requirement compared with the waterfall model.Open →
- Resources, constraints and risks in a software projectThree main elements in the organisation of a software project, resource in a software project and constraint on a project.Open →
- Project management, Gantt charts and critical path analysisProject management, four activities a project manager performs and milestone in a project plan.Open →
- Version managementVersion management, locking a file and merge conflict.Open →
What you need to know
Answer each one before you reveal it.
Why is time the dominant factor for a system tied to an external date?
Explain why involving users throughout development saves money overall.
Why is analysis completed before design begins?
Give two disadvantages of questionnaires.
Why can a system that meets all its functional requirements still be rejected?
What is the purpose of a data flow diagram?
What is the difference between a context diagram and a level 1 DFD?
Produce a context DFD in words for a simple scenario: a dentist's practice recording appointments.
Why does the waterfall model suit a fixed-price contract?
Why does a project manager use a Gantt chart and critical path analysis together?
What is the main role of a systems analyst?
Give two advantages of Rapid Application Development.
Name the three main elements in the organisation of a software project.
Why is version management essential when several programmers work on one system?
Where was the term ‘software crisis’ first used?
Name three tasks a systems analyst carries out during analysis.
What is the purpose of the analysis stage of systems development?
Describe how an interview is used as a fact-finding technique.
What is a functional requirement?
Describe the waterfall model of systems development.
Give two disadvantages of Rapid Application Development.
Give three examples of human resources on a development project.
What is project management?
What is meant by locking a file?
Give three symptoms of the software crisis.
Name the three main factors that shape any systems development project.
What is the main role of a project manager?
Name the three parts that make up any computer system.
Give two advantages of interviews over the other fact-finding techniques.
Give one non-functional requirement for a payroll system, and justify it.
Name the stages of the waterfall model in order.
Describe the Agile approach to systems development.
What is meant by a constraint on a project?
Name four activities a project manager performs.
What is a branch?
Take Systems Analysis and Development Approaches further
The same content, four other ways.
Commonly confused
Pairs that lose marks when they are blurred together.
Constraint vs Risk
Constraint: a limit known at the outset that the plan must fit inside. Risk: a possible future event the plan must be ready for.
Interview vs Questionnaire
Interview: a two-way conversation with a single person, so an answer can be followed up. Questionnaire: a fixed set of written items sent to many people at once.
Observation vs Document sampling
Observation: watching people at work to see what really happens. Document sampling: examining the forms and records to see what data is actually held.
Questions from this topic
Each one with the model answer underneath.
- 1
What does the term ‘software crisis’ describe?
Model answer
The software crisis describes the period in which software projects routinely ran late, cost far more than planned and delivered unreliable systems, because software development could not keep pace with rapidly growing hardware power.
- 2
Where was the term ‘software crisis’ first used?
Model answer
The term ‘software crisis’ was first used at a NATO conference on software engineering held in Germany in 1968.
- 3
Give three symptoms of the software crisis.
Model answer
Projects overran their deadlines, projects exceeded their budgets, and the software delivered was often unreliable or did not do what the user had asked for.
- 4
Why did more powerful hardware make the software crisis worse?
Model answer
Cheaper and faster hardware allowed far more ambitious systems to be attempted, and the informal methods that worked for small programs could not manage the complexity of the much larger systems that became possible.
- 5
How did the software crisis lead to the discipline of software engineering?
Model answer
The scale of the failures showed that building software needed the same disciplined, planned approach as other branches of engineering, so lifecycle models, documented methods and formal project management were introduced.
- 6
State two consequences for an organisation whose software project fails.
Model answer
The organisation loses the money already spent on the project and must carry on running an inadequate existing system, and it may lose customers to competitors whose systems work.
What is inside Levo
Six ways to work the same material.
Systems Analysis and Development Approaches revision questions
- What does Systems Analysis and Development Approaches cover in CCEA A-Level Digital Technology?
- 12 subtopics: the software crisis and the need for systems development, user needs, time and cost, roles in a systems development team, the purpose of analysis, fact-finding techniques, functional and non-functional requirements, data flow diagrams, the waterfall model, rapid application development and agile, resources, constraints and risks in a software project, project management, gantt charts and critical path analysis and version management. Each one has its own page with questions and model answers.
- How is Systems Analysis and Development Approaches organised?
- By the CCEA 2650 specification, subtopic by subtopic, so it matches the order you are taught it in.
Every question in Systems Analysis and Development Approaches, on a schedule.
Attempt a question from memory, write the correct version, then attempt it again. Levo records the jump between your first attempt and your last, and brings each question back on the day you are due to forget it.
Or £46 a year, about £3.83 a month. Cancel anytime.