Most students have no idea how to begin their project. This is a
common problem because it is the first time you will have had to
tackle a large amount of work which is probably poorly defined.
The following list of steps will help you get started
- Identifying a problem & project proposal
This is the first
step towards ideating a project. You will have to look into a
domain and identify a problem that needs to be solved. This will be presented as project proposal or synopsis
- Requirements generation
Write down what
you want the finished solution to do and get everyone involved
to agree to it.
- Problem modelling
Once you have noted
down the requirements, you can create a model for it
computationally. That is, identify the theoretical tools you
will need to solve the problem. For example, If your problem is
to do with building a database, you will probably model the
system with an entity-relationship diagram and validate the
model by normalization.
- System analysis and specification
the requirements document, problem definition, and computational
model identified, you should now be in a position to state
exactly what our system will do and under what circumstances it
will do it.
- System design
There a few steps
involved in designing a system, these are :
- Identify several design options available to you and
- Analyze your design to ensure it is technically
feasible. Remember, you can’t always build everything you
design, either for theoretical reasons or for practical
- Analyze your design to ensure it meets the
- Create a cost estimation for your system. Select the
- Module implementation and system integration
Finally, we are at the point where we can write the software. It
is best to use a modular construction approach. Don’t attempt to
build the entire system in one go in the hope that, when you run
it, it will work. It is preferable to build and test each module
individually and then link them or connect them together.
- System test and evaluation
students misunderstand the meaning of the word testing. They
think it means showing that something works: their project, for
example. But it doesn’t. Testing means much more than this.
Certainly, you need to show that it works (i.e. that it meets
the requirements and operates according to the specification),
but a good testing strategy also attempts to break the system:
to show not where it works but where it fails.
- Conclusions and identifying future work if any
With complete project in front of you, you should evaluate it
and have conclusions. This is the time where you identify what
is the future scope of work or enhancements which can be
- Preparing your final year project report
Documenting your work and experience in form of a standard
template is the last nail and one of the most important too.
Prepare and submit a professional, industry level final year
project report and impress the evaluator