07.08.2012
Final Year Project - Part II
This is the second lecture of the discussion about final year project.
- In final year project, not having proper optimization which means minimal wastage of the transportation of optimizing algorithms.
- All should starts with the problem.
ex: You are planning to do a sales forecasting system to the fuel organization. The problem is the waste of fuel rate is very high. To solve this problem we need to get the sales data. It based on the sales that organization get.
- Explain the problem and what you are going to analyze it.
The Project Proposal.
How do you explain the problem.
- Quantify the problem.
ex: According to the above problem,
High fuel cost.
High delay.
- Problem need to be quite clear.
- Need evidence to prove which are like statistics.
- What are the objectives of the project.
- At the end of the nine months what are you going to achieve from your project.
2. Objectives of the problem.
- Objective must be SMART (We discussed it previous lessons).
- Basically what are you going to achieve end of the nine months.
- Increase the efficiency. 54% ----> 84%
- See weather you have achieve the your goals.
3. What systematic approach that you are going to use.
- Identify what software methodology you are going to use. This methodologies are used to over come the problems.
Examples of the methodologies.
- Waterfall methodology.
- Agile methodology.
Evolution Prototyping.
There are five items in evolution prototyping.
- Identify initial requirements.
- Initial prototype which is given to the users.
- Provide new prototypes / Re vied prototype.
- Give it to users.
- Users will feedback. It is a final version of the project. Customers will satisfied with that new project.
- What is going to be my problem, design structured systems analysis design methodology (SSADM) or you can look at the another methodology to use.
- What is the structure going to use in primary methodology. It describes that what are the tangible and intangible benefits.
Project plan will be creates according to the above types of evolution prototypes. It needs to be detailed work break down structure. It is different and it is filled with level of details.
What makes a good proposal?
- The accuracy of the title.
The title should be like this. An Investigation into _______ (research areas) to develop _______ (what type of system) for _______ (what is the company name).
ex: An Investigation into Multiple Criteria Decision Making and Fuzzy Logic to Develop a Loan Approval System for National Development Bank.
2. The clarity of the aims.
It must be need to create with an argument. It may be lots of different different opinions. Need to look at the multiple users views. SSADM is a good evolution prototype.
3. It is a reflection on objective. Need to analyse your data.
4. Probably situations with good English.
5. Need to justify why you use these techniques.
Academic Requirements.
It has to be something new you are using it.
ex: In a decision support systems you need to think about what kind of model and what are the types of the that DSS. If it is a mathematical mode then how does it works for fussy logic.
Content of your project.
- Abstract (This comes to the first in you document but it was the last thing you write).
- Introduction.
- Body.
- Conclusion.
- List the references quoted in the text.
- Bibliography.
- Appendices.
Learning gain of the Lecture.
Identify how to write a good project proposal, evolution prototypes, academic requirements and the contents of the project document.
Personal Opinion.
Get the perfect idea about the final year project.
No comments:
Post a Comment