0% found this document useful (0 votes)
22 views5 pages

Cover Letter: Application To Supervisor For Permission To Submit The Proposal

The document outlines a project proposal format, including sections such as an abstract, needs/problems, goals/objectives, existing system analysis, and features of the proposed project. It emphasizes the importance of a structured approach to project development and provides guidelines for team organization, solution recommendations, and documentation formatting. Additionally, it includes a section for references and a detailed activity and time schedule.

Uploaded by

Abir Shah
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
22 views5 pages

Cover Letter: Application To Supervisor For Permission To Submit The Proposal

The document outlines a project proposal format, including sections such as an abstract, needs/problems, goals/objectives, existing system analysis, and features of the proposed project. It emphasizes the importance of a structured approach to project development and provides guidelines for team organization, solution recommendations, and documentation formatting. Additionally, it includes a section for references and a detailed activity and time schedule.

Uploaded by

Abir Shah
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

1.

Cover Letter
Application to supervisor for permission to submit the proposal
[Institute Name]
[Date]

PROJECT PROPOSAL
On

[Project Name: Give an Elegant Project Title]

[Submission Date: 7th, July, 2018]


3. Table of Contents

Sl. No. Title Page No.


1 Abstract 02
2
3

1. Abstract (Executive Summary)


Describes the way the proposed system will be develop and who, what, where, when and why.
The summary should also contain a summary of recommendations as well because most of the
time they only read summaries.
2. Needs/Problems
Write down the main problems or requirements to develop this system?
3. Goals/Objectives
Write Down brief description on your Project. SMART is the recommended method to develop a
project goals and objectives.
4. Existing System Analysis
Write down short descriptions with proper references about at least 2-3 existing software/web
apps for following Problem. Analyze them and find what the shortcomings of these systems are.
Basically, you should write project profile, some features of existing system and your
recommendation about these systems.
5. Features / Scopes of proposed project
What should be done in this project exactly and do not write extra over estimating features that
you cannot provides in here. So List out the possible and most likely features and deliverable
facts that you can finish in time.
6. Development Model
What types of development model do you choose? Why explain (Lists) your answer in here.
7. Solution Overview
Write down your proposed recommended solution (at least two different solutions) in brief also
show the design part here. The objective here is to give the person who is making the decision
enough information so that they understand what the system is so, how it will work, and what the
major building blocks are:
a. DFD
b. Use Case Diagram
c. ERD
8. Requirements
Lists all possible requirements (e.g. hardware configurations, software, personnel, tools &
technology, languages etc.)
Project Breakdown with time estimation
9. Activity And Time Schedule/
For example,

10. Development Team & Stakeholders


Lists your team structures with proper responsibilities. Remember! There should be
maximum 2 person for per task. They will be responsible for that part. Give everyone fair
working distributions. If possible give everyone a designation. Otherwise imbalanced flow of
works will provide you a major penalty. There should be a team leader and a co-leader. You may
hire or take help from other’s source/person then include them into another expert category.
Also list all stakeholders & Key users in your projects. For example,
Id Name Designation Responsibilities
Team managing , Co-coordinating
00005 X Team Leader among members and organize the
project works to achieve the goals
00001 Y Back-end Programmer ASP.NET Programmer
00004 Z DBA Database Design and Administrator

11. System Analysts Recommendation


After the different solutions are recommended then you should prioritize those solutions and
give recommendations as to which one best fits the project’s needs.
12. References
Lists down reference links or book pages, web contents or others in here Please for further
reading See IEEE citation style [ https://libguides.murdoch.edu.au/IEEE/all ]. For Example:
[1]. R. Aedy, Interviewer, D. Hector, Interviewee, and S. Clark, Producer, "The future of
engineering," The Buzz, 25 Sept., 2004 [Radio broadcast]. Sydney: ABC Radio.
[2]. NRK. "Medieval helpdesk with English subtitles," YouTube, Feb. 26, 2007 [Video file]. Available:
http://www.youtube.com/watch?v=pQHX-SjgQvQ. [Accessed: Jan. 28, 2014].
[3]. European Telecommunications Standards Institute, “Digital Video Broadcasting (DVB):
Implementation guidelines for DVB terrestrial services; transmission aspects,” European
Telecommunications Standards Institute, ETSI TR-101-190, 1997. [Online]. Available: http://www.etsi.org.
[Accessed: Aug. 17, 1998].

Documentation Formatting Rules & Regulations


1. A4 Size Paper Portrait, Margin TOP-1”, BOTTOM-0.5”, LEFT- 1”, RIGHT- 0.5”
2. Body contents (Full) text font should be “Trebuchet MS” size-13, normal
3. Line Spacing 1.15, No Space after Paragraph
4. All 1st grade Title should be Bold, size-15
5. 2nd grade Title should be Bold size-14
6. Links and special line should be in UNDERLINED
7. Use footnotes if necessary to explain detailed information contained in the table.
8. EMPHASIZE contents text should be ITALIC
9. HIGHLIGHTED text should be in BOLD
10.TABLE Double bordered, alignments- Left and Middle, Title fonts- BOLD , Body contents-
Normal
11.Try to fit the entire table vertically on a single page.
12.Figures & Images should be center alignments and Figure Title in ITALIC.
13.Choose a style of graph that communicates your intended meaning well.
14.Give the graph a sequential figure number and a meaningful title.
15.Label each axis, and any lines, columns, bars, or pieces of the pie on the graph.

You might also like