Quelpr

Systems Analysis and Design · CAPE Computer Science Unit 2

73 past-paper questions on Systems Analysis and Design, part of Software Engineering, from every CAPE Computer Science Unit 2 paper on Quelpr.

Practise Systems Analysis and Design
  1. 3(a)6 marks· CAPE Computer Science Unit 2 · 2005 · Paper 1Briefly describe THREE techniques that can be used to gather the requirements for a new system.
  2. 3(b)(i)2 marks· CAPE Computer Science Unit 2 · 2005 · Paper 1State what a feasibility report produced early in the analysis phase contains.
  3. 3(b)(ii)2 marks· CAPE Computer Science Unit 2 · 2005 · Paper 1State why a feasibility report is produced early in the analysis phase.
  4. 4(a)6 marks· CAPE Computer Science Unit 2 · 2005 · Paper 1Draw THREE of the symbols used in a data flow diagram and say why EACH is used.
  5. 4(b)4 marks· CAPE Computer Science Unit 2 · 2005 · Paper 1Differentiate between functional requirements and non-functional requirements.
  6. 5(b)6 marks· CAPE Computer Science Unit 2 · 2005 · Paper 1In a hospital GUI used to view a patient's current condition (shown in Figure 1), suppose a nurse enters an incorrect patient name. Discuss THREE features that should be considered when displaying the error message, to…
  7. 11(a)5 marks· CAPE Computer Science Unit 2 · 2005 · Paper 1Describe the purpose of EACH type of user interface object shown in the diagram (Window, Textfields, Button, Labels, Fonts).
  8. 11(b)(i)1 mark· CAPE Computer Science Unit 2 · 2005 · Paper 1Identify the most important event that the program should anticipate.
  9. 11(b)(ii)4 marks· CAPE Computer Science Unit 2 · 2005 · Paper 1Write an algorithm to define the processing steps that should take place when the event identified in (b)(i) occurs.
  10. 2(a)4 marks· CAPE Computer Science Unit 2 · 2006 · Paper 1Explain what is involved in conducting interviews and administering questionnaires to collect information during the analysis phase.
  11. 2(b)2 marks· CAPE Computer Science Unit 2 · 2006 · Paper 1Sunil prefers interviews to obtain the required information. Provide ONE reason supporting his argument.
  12. 2(c)4 marks· CAPE Computer Science Unit 2 · 2006 · Paper 1Camille considers questionnaires more suitable. Provide TWO reasons supporting her argument.
  13. 4(a)2 marks· CAPE Computer Science Unit 2 · 2006 · Paper 1Explain what occurs during system structuring.
  14. 4(b)1 mark· CAPE Computer Science Unit 2 · 2006 · Paper 1State what occurs during modular decomposition.
  15. 4(c)4 marks· CAPE Computer Science Unit 2 · 2006 · Paper 1Distinguish between a sub-system and a module.
  16. 4(d)3 marks· CAPE Computer Science Unit 2 · 2006 · Paper 1Describe the output generated from architectural design.
  17. 5(a)6 marks· CAPE Computer Science Unit 2 · 2006 · Paper 1Outline THREE guidelines for designing an effective user interface.
  18. 5(b)4 marks· CAPE Computer Science Unit 2 · 2006 · Paper 1Briefly describe TWO guidelines for designing a report.
  19. 1110 marks· CAPE Computer Science Unit 2 · 2006 · Paper 1Draw a clearly labelled dialog box for this task containing at least one textfield, window, font, label, and button.
  20. 1(a)16 marks· CAPE Computer Science Unit 2 · 2006 · Paper 2Draw a level-0 data flow diagram representing the given costume rental scenario.
  21. 2(a)(i)6 marks· CAPE Computer Science Unit 2 · 2006 · Paper 2Describe THREE main components of an entity-relationship model.
  22. 2(a)(ii)2 marks· CAPE Computer Science Unit 2 · 2006 · Paper 2State TWO sources from which a systems analyst can gather information to create an entity-relationship model.
  23. 2(a)(iii)16 marks· CAPE Computer Science Unit 2 · 2006 · Paper 2Draw an entity-relationship model based on the bank narrative provided.
  24. 2(b)(i)3 marks· CAPE Computer Science Unit 2 · 2006 · Paper 2Explain what is meant by a data dictionary.
  25. 2(b)(ii)3 marks· CAPE Computer Science Unit 2 · 2006 · Paper 2Describe the contents of an entry made in a data dictionary.
  26. 5(a)6 marks· CAPE Computer Science Unit 2 · 2006 · Paper 2Identify the GUI objects to use in this application and state the purpose of each.
  27. 5(b)4 marks· CAPE Computer Science Unit 2 · 2006 · Paper 2Draw the GUI layout and label the GUI components identified in 5(a).
  28. 5(c)4 marks· CAPE Computer Science Unit 2 · 2006 · Paper 2Explain TWO events that the program should anticipate.
  29. 5(d)6 marks· CAPE Computer Science Unit 2 · 2006 · Paper 2Write the code to instantiate GUI object L, populate it with the numbers 1 to 30, and add it to the GUI.
  30. 5(e)6 marks· CAPE Computer Science Unit 2 · 2006 · Paper 2Write code to retrieve user inputs, calculate the Simple Interest, and display the result in the corresponding GUI component.
  31. 5(f)4 marks· CAPE Computer Science Unit 2 · 2006 · Paper 2Using the calculated Simple Interest from 5(e), write code to compute the monthly instalment and display it in the appropriate GUI component.
  32. 3(b)14 marks· CAPE Computer Science Unit 2 · 2009 · Paper 2Draw a Level-0 data flow diagram (DFD) for the described doctor visit scenario.
  33. 3(c)(i)4 marks· CAPE Computer Science Unit 2 · 2009 · Paper 2Describe TWO ways in which a CASE tool can be used during the software development process.
  34. 3(c)(ii)2 marks· CAPE Computer Science Unit 2 · 2009 · Paper 2State ONE advantage and ONE disadvantage of using a CASE tool.
  35. 4(a)(i)2 marks· CAPE Computer Science Unit 2 · 2009 · Paper 2Define functional requirements.
  36. 4(a)(ii)3 marks· CAPE Computer Science Unit 2 · 2009 · Paper 2Discuss how functional requirements are obtained during the analysis phase of a software system.
  37. 4(b)14 marks· CAPE Computer Science Unit 2 · 2009 · Paper 2Draw an entity-relationship (ER) model representing the described hospital scenario.
  38. 3(b)4 marks· CAPE Computer Science Unit 2 · 2010 · Paper 2Explain, giving TWO reasons, why it is important to involve end users and management in the development of a software product.
  39. 3(d)14 marks· CAPE Computer Science Unit 2 · 2010 · Paper 2Draw a Level-0 data flow diagram representing the described hiring process of an organisation.
  40. 4(a)(i)2 marks· CAPE Computer Science Unit 2 · 2010 · Paper 2State TWO reasons why a feasibility study is undertaken.
  41. 4(a)(ii)3 marks· CAPE Computer Science Unit 2 · 2010 · Paper 2Describe the contents of the requirements specification document.
  42. 4(b)14 marks· CAPE Computer Science Unit 2 · 2010 · Paper 2Draw an entity-relationship model for the described organisation scenario involving departments, employees, skills, projects, and tasks.
  43. 3(b)8 marks· CAPE Computer Science Unit 2 · 2011 · Paper 2Describe FOUR tasks that must be performed during the design phase of systems development.
  44. 3(c)14 marks· CAPE Computer Science Unit 2 · 2011 · Paper 2Draw a Level-0 data flow diagram showing the flow of information between the customer, the company, and the various departments (sales, warehouse, dispatch, accounts) based on the described mail order scenario.
  45. 4(a)(i)3 marks· CAPE Computer Science Unit 2 · 2011 · Paper 2Identify THREE fact-finding methods available to a systems analyst undertaking software development.
  46. 4(a)(ii)4 marks· CAPE Computer Science Unit 2 · 2011 · Paper 2Outline TWO deliverables from the analysis phase of the systems development life cycle.
  47. 4(b)(i)4 marks· CAPE Computer Science Unit 2 · 2011 · Paper 2Describe TWO ways in which a CASE tool can be used in a software development process.
  48. 4(b)(ii)2 marks· CAPE Computer Science Unit 2 · 2011 · Paper 2State ONE advantage and ONE disadvantage of using CASE tools in a project.
  49. 4(c)12 marks· CAPE Computer Science Unit 2 · 2011 · Paper 2Draw an entity-relationship model for the described university scenario involving colleges, departments, lecturers, and courses (with attributes code [primary key], name, and credit hours).
  50. 3(a)14 marks· CAPE Computer Science Unit 2 · 2012 · Paper 2Draw a level-0 data flow diagram depicting the university registration scenario.
  51. 4(a)(i)6 marks· CAPE Computer Science Unit 2 · 2012 · Paper 2Describe the main components of an entity-relationship model.
  52. 4(a)(ii)13 marks· CAPE Computer Science Unit 2 · 2012 · Paper 2Draw an entity-relationship model for the described software project and employee scenario.
  53. 3(b)9 marks· CAPE Computer Science Unit 2 · 2013 · Paper 2Draw an entity-relationship model for the described hospital scenario, clearly naming relationships and specifying cardinality.
  54. 4(a)9 marks· CAPE Computer Science Unit 2 · 2013 · Paper 2State THREE traditional methods of determining requirements of a new software system, identifying ONE advantage and ONE disadvantage of each method.
  55. 4(b)(i)3 marks· CAPE Computer Science Unit 2 · 2013 · Paper 2State the purpose of external entities, data stores, and processes when used in a Data Flow Diagram (DFD).
  56. 4(b)(ii)3 marks· CAPE Computer Science Unit 2 · 2013 · Paper 2For external entities, data stores, and processes, give a diagram showing how each symbol is used in a DFD.
  57. 4(b)(iii)6 marks· CAPE Computer Science Unit 2 · 2013 · Paper 2Draw a level-0 data flow diagram for the scenario where a customer sends an order, the system checks inventory, sends shipping notices to warehouse for dispatch and updates stock if available, or returns rejected orders…
  58. 4(c)4 marks· CAPE Computer Science Unit 2 · 2013 · Paper 2Distinguish between 'functional requirements' and 'non-functional requirements', providing ONE example of each type.
  59. 3(c)6 marks· CAPE Computer Science Unit 2 · 2014 · Paper 2Describe THREE main factors that must be evaluated during a feasibility study in the systems development life cycle.
  60. 3(d)12 marks· CAPE Computer Science Unit 2 · 2014 · Paper 2Draw an entity-relationship (ER) diagram representing the described scenario.
  61. 4(a)(i)6 marks· CAPE Computer Science Unit 2 · 2014 · Paper 2Provide TWO examples of data that may be entered for EACH of the three options (Student ID, Date of Birth, Course Code and Name).
  62. 4(a)(ii)3 marks· CAPE Computer Science Unit 2 · 2014 · Paper 2For EACH option, explain whether a textbox, menu, command line, checkbox, or other interface element would be suitable.
  63. 4(a)(iii)3 marks· CAPE Computer Science Unit 2 · 2014 · Paper 2Describe a validation test that could be applied to EACH option to verify that valid data is entered.
  64. 4(b)13 marks· CAPE Computer Science Unit 2 · 2014 · Paper 2Draw a Level-0 data flow diagram (DFD) showing the flow of information between the pharmacy, the pharmaceutical company, and various departments within the company.
  65. 3(d)13 marks· CAPE Computer Science Unit 2 · 2015 · Paper 2Draw a Level-0 data flow diagram (DFD) to represent the flow of data described in the clinic scenario.
  66. 4(a)3 marks· CAPE Computer Science Unit 2 · 2015 · Paper 2Explain why data flow diagrams are developed during both the analysis phase and the design phase of the system development life cycle.
  67. 4(b)3 marks· CAPE Computer Science Unit 2 · 2015 · Paper 2State three benefits of the object-oriented approach to software design.
  68. 4(c)4 marks· CAPE Computer Science Unit 2 · 2015 · Paper 2Describe two major deliverables resulting from the design phase of the system development life cycle.
  69. 4(d)15 marks· CAPE Computer Science Unit 2 · 2015 · Paper 2Draw an entity-relationship (ER) model for the company scenario, naming relationships and clearly indicating cardinality and all given attributes.
  70. 3(e)12 marks· CAPE Computer Science Unit 2 · 2016 · Paper 2Draw a Level-0 dataflow diagram (DFD) to model the data flows described in the university registration system scenario.
  71. 4(a)2 marks· CAPE Computer Science Unit 2 · 2016 · Paper 2Define cardinality in the context of database design and state one example.
  72. 4(c)4 marks· CAPE Computer Science Unit 2 · 2016 · Paper 2Differentiate between functional and nonfunctional requirements, giving one example of each.
  73. 4(e)12 marks· CAPE Computer Science Unit 2 · 2016 · Paper 2Draw an entity-relationship (ER) diagram representing the described scenario, defining all relationships and cardinalities in both directions using standard ER conventions.

Related topics in Software Engineering