Writing evaluations

DJMK4 · 7 Apr 2006 at 21:18

This can be done a number of different ways, depending on what the project itself is (this is relating to a university disseration now for a HND course).

Mine was a web-development with several examples of using new found web-technologies to implement and display a number of differnet types of data, mainly using XHTML (with a seperate style sheet), SQL & PHP.

Im writing up the evaluation now but im still not totally 100% sure on what to include in the evaluation.

So far i have:

1)Purpose of the project
2)Was the project completed on time?
3)Was the project carried out to the specification of the customer’s requirements and was the customer satisfied with the final result?

4)Were there any changes made due to customer/developer error?
5)Were there any changes in both design & functionality?
6)Would you make any changes with design & functionality if this project was re-run?

how does this compare to others?

Nix · 7 Apr 2006 at 21:23

What would you do if you had more time...

potential for future projects...

DJMK4 · 7 Apr 2006 at 21:23

Nix said:
What would you do if you had more time...

potential for future projects...

Didnt think of those, thanks

do you think the headings i have included so far are ok or should i scrap any of them?

Nix · 7 Apr 2006 at 21:28

[Sniper][Wolf] said:
So far i have:

1)Purpose of the project
2)Was the project completed on time?
3)Was the project carried out to the specification of the customer’s requirements and was the customer satisfied with the final result?

4)Were there any changes made due to customer/developer error?
5)Were there any changes in both design & functionality?
6)Would you make any changes with design & functionality if this project was re-run?

1) Good.
2) Probably better if related to time management, do you have an action plan?
3) Good.
4) Customer/developer error? - Pehaps change to "Problems encountered and their solutions"
5) 4 & 5 could probably be in the same section.
6) Probably better re-phrased as "What changes could be made if you had more time?" or "What would you have done differently?"

DJMK4 · 7 Apr 2006 at 21:31

Thanks for your feedback

PeterNem · 7 Apr 2006 at 21:33

Is this meant to be purely an evaluation? In which case, I'd say Nix is pretty on the ball.

Or, is it meant to be a complete documentation of the whole software development process including design, specification etc? If it's the latter I can post up the headings I am using for my final year project.

DJMK4 · 7 Apr 2006 at 21:36

PeterNem said:
Is this meant to be purely an evaluation? In which case, I'd say Nix is pretty on the ball.

Or, is it meant to be a complete documentation of the whole software development process including design, specification etc? If it's the latter I can post up the headings I am using for my final year project.

My project is

Final Idea
Requirements
Proposal
Terms of reference
Introduction
Background research report
All the design work
Testing
Evaluation report

so i dont think design comes into it? its just basically how your project went etc..If you could post your headers that would be great

PeterNem · 7 Apr 2006 at 21:53

In which case I'd stick to what you already have/what is posted by Nix.

However, just for your interest, my headings are currently (subject to change, as i'm in the middle of reordering some of it...)

1. Abstract
2. Background
2.1. Aim
2.2. Proposed Solution
2.3. Initial Feasibility Study
3. Methodology
4. Requirements Analysis
4.1. Requirements Definition
4.2. Requirements Specification
4.3. Review of existing solutions
5. Functional Specification
6. Work Plan
7. Design
7.1 Scope
7.2 Screen Flow
8. Implementation
9. Evaluation and Testing
10. Conclusions
11. Future Work
12. References and Bibliography
13. Apendicies
13.1 Error Log
13.2 Database Design

DJMK4 · 7 Apr 2006 at 21:58

PeterNem said:
In which case I'd stick to what you already have/what is posted by Nix.

However, just for your interest, my headings are currently (subject to change, as i'm in the middle of reordering some of it...)

1. Abstract
2. Background
2.1. Aim
2.2. Proposed Solution
2.3. Initial Feasibility Study
3. Methodology
4. Requirements Analysis
4.1. Requirements Definition
4.2. Requirements Specification
4.3. Review of existing solutions
5. Functional Specification
6. Work Plan
7. Design
7.1 Scope
7.2 Screen Flow
8. Implementation
9. Evaluation and Testing
10. Conclusions
11. Future Work
12. References and Bibliography
13. Apendicies
13.1 Error Log
13.2 Database Design

That sure is a lot of work? are you doing a BSc then? im only required to do 6,000 words and my programme,although mine is close to 9,000 words and a programme.

PeterNem · 7 Apr 2006 at 22:09

Yea, BSc. Deadline is the 26th of this month, and the word limit is 10k words. Only the sections labelled Background through to Conclusion are included in the word count.

I'd say I'm about 75% done on my programming. Been tinkering since xmas, but only properly started about 2 weeks ago.

I've written about 6k words so well on the way to that too.

DJMK4 · 7 Apr 2006 at 22:23

hmm, well iv run a few reports past my project sup and he seems to think i am on the right track, and looking at my mates work it seems on par if not better!