Download this complete,fully solved and updated actual exam for CCEA Digital Technology AS 1

Systems Analyst -Identifies the user requirements -Undertakes fact finding -Defines the system specification Project Manager -To oversee the project -To allocate the budget -Allocates resources- personnel, hardware, software, budget -Identifies risks -Reports back to the client Programmer -Writes the code from the module specification -Tests the code using a test plan -Debugs the code -Documents the code Purpose of analysis -Identify the requirements of the system -Identify inputs and outputs of the system -Describe the system using a DFD and a commentary -Identify hardware and software constraints -Develop a data model Observation -Users are shadowed as they perform a particular task -Identifies what their role entails/data required/abilities and constraints Interviews -Users are asked questions on a one-to-one basis or in groups -It may be structured or unstructured -Follow up questions can be asked Document sampling -Identifies the data an organisation needs, how this data flows through the organisation -Existing documents such as forms, invoices, receipts, orders and reports are sampled to see how data is input, processed and output Questionnaires -A set of open or closed questions developed as king's key points about the current system -A wide selection of users are asked Functional User Requirements -Specifies what the system must do for the specific application -It is a function or a process Non functional user requirements -Specifies an additional condition the system must meet -It is not specific to the system itself What is the purpose of a data flow diagram (DFD)? -Shows how data flows through a system -Presents what happens at different levels -Identifies processes and data stores -Shows how the system interacts with external entities (data sources and destination) Level 0 (context) DFDs -No data stores are identified -One process Level 1 DFDs -Main process will be broken down into sub processes -Data stores will be identified -Data flows will be identified Storyboarding The purpose of storyboards in designing a system is: -Used in the design of the user interface -Each screen is represented as a diagram showing the content of screens and the planned sequence of screen displays. -Shows input and output and navigation paths Prototype -The construction of a simple version of the program which is used as part of the design process to demonstrate how the system will work -The prototype is reviewed by the user and changes are made through user feedback. Prototyping in interface design -An initial non-functioning model of the user interface is made. -It has no database access -Additional interaction is added from feedback from the user Prototyping in data model dosign -A 'first-cut' non-functioning model is created. -The prototype will focus on the input/output required -It will allow data structures and relationships to be identified. -It will not focus on user interface design Suitability and usability of software SUITABILITY -Does it meet the user requirements? -Is it compatible with the existing hardware/software? -Is it error free/robust? USABILITY -Is the user interface intuitive? -Can existing skills be transferred? -Does it require training? -Does the user interface match with the ICT expertise of the user? System testing -Performed in house -Comprises of system, module and integration testing -Tests that the system meets the systems specification