Show:
Requirements
Design
Coding/Building
Testing
Maintenance
100
Name a way of finding the requirements of a client in analysis.
Acceptable answers: Interview, observation, surveys/questionnaires, meetings, review of existing documents
100
Name a way of showing the design of the solution process/system.
- Flow Charts - DFD Diagrams
100
What considerations need to be made when coding the design?
- What language should be used? - What parts should be built first? - What standards should be followed? - Who should code what? - How should the code be translated?
100
Which type of testing is performed in-house by developers?
Alpha
100
Give examples of what would be packaged with "corrective" patches.
- Bug fixes - Security patches
200
Why may a company require a new system?
Old system is: too slow, out-of-date and therefore not compatible, not performing the task reliably, not user friendly; Legal changes, business is expanding/new facilities
200
Name a method of data validation.
- Format check - Check digit - Length check
200
Give an example of a coding standard.
E.g: - No global scope - Brackets on lines of code - Values declared at start of a subroutine - Correct indentation - Repeated code to be in separate functions/procedures - In-line commenting - Different identifier case for constants, variables, classes
200
Name the three types of test data.
- Extreme/limits - Normal - Exceptional/invalid
200
Give examples of what would be included with "perfective" patches.
- Refinement of UI - Refinement of outputs/reports - Speed improvements
300
Name 3 feasibility considerations:
- Is there actually a problem - technically feasible - economically feasible - socially feasible - legal - ethical - meets environmental standards
300
Name a method of data verification.
- Reading back through audio - Double entry
300
Why would it be more suitable for DanPak Shoes® to use a RISC processor, as opposed to CISC, in the solution to a mobile tablet computer to measure shoe sizes of customers?
- Low power usage, customers are less likely to be interupted by periods of charging - Less cooling requirements, less bulky device to carry - Simple function, no need for complex instructions - high level code is unlikely to be frequently compiled to be compatible with these devices, so translation times are not essential - Lighter due to less components, easier to carry
300
Why do the end users test before release?
- To see if those not involved in development can understand how to use the system - Is the UI clear? - Do users fill in the boxes clearly? - Can the outputs be understood? - Does it meet their requirements? - Is it fast enough? - Is it secure? - To squash bugs - To test with real data
300
Why would "adaptive" changes need to be made?
- Changes in law/legislation - Changes in user requirements - Changes in business needs - Changes in procedure - Changes in hardware
400
Name 3 considerations which have to be made about the users.
- What are their technical abilities?/training - What access should they have? - How should outputs be formatted? - What UI is appropriate?
400
What is the difference between the testing approaches taken in white-box & black-box programming?
White-box: Each piece of sequence, selection & iteration is tested individually for their functionality Black-box: Testing is systematic, different data values are tried, through a continuous use of the program.
500
Is it b-ay-tar, b-ay-tah, b-ee-tah, or b-ee-tar?
Google translate reads it as b-ay-tah.