A small agency specialising in providing translation services to the
legal system namely courts, judges, probation services and social
services. they have a number of interpreters/tranlators on their book,
speaking a variety of languages.the agency tries to match the
interpreting demand with the supply. the agency would like to
computerise the process of matching the demands to the supply, and
also keep records of their customers, their charges and the payments
made to the interpreters.
Task 1: Project Proposal
a.)A comparison of different methodologies/approaches including RAD
(Rapid Application Development), top down, bottom up, data driven,
event driven. A brief justification of why top down is the most
appropriate should be included.
b.)The different data structures that could be used to store and
manipulate the data in your proposed system, showing examples for each
appropriate type of structure, with identification of the structures
you propose to use in your system.
Task 2: Project Plan
You should now finalise your project proposal with the use of a
project plan. The plan should use recognized planning techniques and
software.
The plan should show clearly all tasks to be performed, all relevant
deliverables and associated milestones.
The plan should also show resource allocation, and budgeting requirements.
The costings of hardware, software and your time as developer will be
involved here.
This plan should be reviewed and updated whenever required as the
differences will need to be discussed in the evaluation.
alteration are required because you keep to time throughout, then
this to can be mentioned in the evaluation.
Task 3: Analysis
Develop a report, showing the user and technical specifications for
your project, covering:
* The client?s requirement included
o Users
o Objectives
* The system requirements including:
o Users interface
o Inputs
o Outputs
o Processing
o Data storage
o Design constrains
You should use a recognized methodology to present this analysis. It
will form part of the technical documentation.
Task 4: Design
Produce the design documentation, with enough detail to allow another
programmer to implement your proposed system, based closely on your
specified system requirements, for the creation and maintenance of the
application. Note any design problems as you may wish to discuss these
in the final task, Evaluation.
The test plan, to be developed as part of the design, must include
normal dada, erroneous and extreme data will also slow algorithms and
interface tests.
Your design documentation should include, as part of the use of your
chosen methodology/approach discussed in task 1:
ˇ Structure diagrams, or recognised alternative, showing sequence,
selection and iteration.
ˇ Data structures (choosing appropriate ones identified in Task 1)
ˇ Data storage
ˇ Inputs
ˇ Outputs
ˇ Processes
ˇ User interface
ˇ User initiated events using an action chart (if appropriate)
ˇ Data dictionary including:
o Procedures
o Functions
o Variables (Names, Data types, Data scope)
ˇ Modularisation (keeping module re-use in mind)
ˇTest plan, to meet system and user showing:
Priority of test
Test dada to be used
Reason for use
Expected result
Priority of test:This column should demonstrate the order in which tests will be
performed.
Test dada to be used:This column highlights the actual data to be used.
Reason for use: This column shows the reason (justification) for the
use of the data.
Expected result:This column shows what you expect to happen when the test is run.
You should use a recognized design methodology. It will form part of
the technical documentation.
Task 5: Implementation
Implement the prototype following your design proposal carefully, any
deviation from the design must de noted, as it will form part of the
evaluation in the final task. You should ensure that you make good use
of the available user interface design features to allow for the
varying users specified to your system. You should also ensure that
you make the most efficient use of selected components and their
properties.
Your developed prototype system must make correct use of the chosen
language including reserved words, control structures, functions,
procedures, subroutines, data types and data structures where
appropriate. The documentation should allow another programmer to
maintain the program developed with ease.
The completed documentation should include a program listing showing:
ˇThorough code annotation ? this annotation should also include
relevant and appropriate variable names, explanations, not repetition,
of the developed code and indentation of the code
ˇProgram code that matches the design structure (or equivalent)
diagrams where possible.
ˇ Appropriate use of methods or equivalent
ˇ Appropriate use of event handlers or equivalent
ˇ Correct use of reserved words
ˇ Appropriate use of selection and iteration statements
ˇ Use of built in functions/procedures
ˇ Correct use of data types/structures and constants.
Task 6: Testing
Use the test data you have formulated in task 4 and test your program
thoroughly, making good use of any debugging tools available with your
programming language software. You must ensure that you note all
aspects of the testing as any functionality issues can be discussed in
the final task, Evaluation.
The evidence of testing may be in the form of screen shots and/or,
Witness Statements but you should maintain a test log showing:
ˇEvidence of a range of appropriate tests being carried out
ˇTest plan from task 4 being implemented
ˇResults of any tests that failed, action taken to fix the problem.
Evidence of re-running test.
You must also include evidence of using a range of different testing
techniques, where appropriate to the chosen language, such as:
Test number:This column should demonstrate the order in which tests will be
preformed.
Test data used:This column highlights the actual data to be used.
Actual outcome:This column allows space to discuss outcomes.
Proof:Cross reference to screen shot or print out.
Comments:This column is where you should discuss any problems and their resolution.
ˇUse of debugging tools
ˇUse of breakpoints, step over, trace into
ˇVariable inspections whilst code is running
ˇUse of debugging code with pop up messages.
It is suggested that a tabular format be used to demonstrate testing such as:
Task 7: Presentation
Prepare a user guide for the system covering:
ˇ Normal use
ˇ Troubleshooting
The user guide should be written for all possible users of the system.
Task 8: Evaluation
Now is the time to review every aspect of your application. You must
evaluate your program critically and justify any conclusions made. The
evaluation must cover:
ˇ Strengths and effectiveness
ˇ Weaknesses
ˇ Scope for improvement
In each of the following areas:
ˇ Design
ˇ Implementation
ˇ Testing
ˇ Meeting user requirements and user feedback
ˇ Programming environment
You should also provide an evaluation of your time management and your
ability to follow the project plan. Decide whether your initial
costings were accurate, and discuss any discrepancies.
The application developed may yet be incomplete or have outstanding
problems. Discuss any improvements you need to make. Identify any
enhancements you would like to make to the system or any further user
requirements.
Throughout the evaluative aspects you should refer to the notes made at each stage. |
