Your SlideShare is downloading. ×
2 Analysis & Deliverables
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

2 Analysis & Deliverables

2,559

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
2,559
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
21
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Coursework Guidance Info 4 Mark allocation in BLUE
  • 2. Analysis & Deliverables (15 marks)
    • Statement of Project Scope (3)
    • Proposed System & Deliverables (3)
    • Processes & Client Agreement (3)
    • Users of the Proposed System (3)
    • Evaluation Criteria (3)
  • 3. Statement of Project Scope
    • This should include any internal or external constraints on the proposed system. These may include hardware, communication technologies, software, format of external information requirements, staffing and environmental factors.
  • 4. Statement of Project Scope
    • There is brief statements of the scope of the project.
    • A substantial problem has been analysed. There is a statement of scope for the project.
    • A substantial problem has been analysed with a clear statement of the scope of the project and any external or internal constraints.
  • 5. Proposed System & Deliverables
    • This may take various formats but should include the benefits for, and likely impacts on, the organisation.
    • What is to be produced and handed over to the client? This may be a prototype system or a partial system.
  • 6. Proposed System & Deliverables
    • A superficial description of the proposed system is included. Some deliverables have been referred to in the report showing some idea of what should be produced.
    • A description of the proposed system with some anticipated benefits is included. The deliverables are listed, demonstrating some understanding of what should be produced.
    • A description of the proposed system, the benefits with an explanation of the likely impact on the organisation. Full understanding of the deliverables that are required is shown.
  • 7. Processes & Client Agreement
    • Again, the formats for the documentation is not fixed but should be appropriate to the system being analysed.
    • Findings must be presented in such a way as to be understandable to the client.
  • 8. Processes& Client Agreement
    • Processes have been identified and some understanding of what is involved in the new system is shown.
    • The processes in the new system are outlined showing some understanding of what is involved in each process. There is some evidence that findings have been checked with the client.
    • Processes are fully documented, showing understanding of what is involved in each process & including the inputs and outputs required. The documentation could be used for design work. Strong skills of analysis and logical thinking and of the need to check and amend in response to client feedback are shown.
  • 9. Users of the Proposed System
    • Details of the skills of the users of the proposed system, appropriate to the system.
  • 10. Users of the Proposed System
    • An attempt to identify the skills of a user of some users.
    • The skills of most types/categories of users have been described showing an understanding of the need to consider user skills when designing a solution.
    • The skills of most types/categorized of users have been described showing an understanding of the need to consider user skills in designing a solution. Including a description of how the users will use the proposed system.
  • 11. Evaluation Criteria
    • Both qualitative and qualitative criteria against which the solution can be tested and evaluated. These should be derived from the requirements of the client.
  • 12. Evaluation Criteria & Client Agreement
    • Evaluation criteria have been provided showing some understanding of the need for the assessment of a solution.
    • Both quantitative and qualitative evaluation criteria have been included showing some understanding of the need for the objective assessment of a solution.
    • Quantitative and qualitative evaluation criteria have been included that match the client requirements and show a good understanding of the need for the objective assessment of a solution.

×