Components and Format of IT Project Proposal
Components and Format of IT Project Proposal
Preliminary pages.
i. Cover page.
ii. Table of content.
iii. Lists of figures.
1. Project title.
Title of the project proposal should have the following features or requirements.
Identify the problem, prevailing, explain its trend if possible from the first time it was
reported or occurred. Then explain the effects who were affected most and why, and
weather there were any efforts to address it. If there was a solution project team has to
indicate the result of the solution. The team also must state clearly if the problem is still
prevailing or not. Whatever the result, whether the problem was solved or not, project team
has to indicate that there is a need for the proposed system/ solution.
1.3.Problem statement
Project team is supposed to provide a short introduction in terms of problem trend, efforts,
and its current status. Then, the problem should be defined after a short introduction. A
problem should be clear and understandable. Problem can be stated as a question or
statement.
They should address what will you do in your study, where and for what
purpose.
In this section the team must state the reason(s) for undertaking the study, weather its
worth undertaking and if it feasible. The guiding question are.
Team should explain in detail what does they’re system does and who will be benefited
from the solution. (It should be listed)
3. Literature review
3.1.Literature review.
3.2.Similarity of the project.
3.2.1. Similarity 1
3.2.2. Similarity 2
3.2.3. Similarity 3
3.2.4. Similarity 4
3.2.5. Similarity 5
3.3.Project gap (What to archive or what gaps to fill).
4. System analysis and design
4.1.Analysis.
4.1.1. Feasibility study.
4.1.1.1. Economic feasibility.
4.1.1.2. Technical feasibility.
4.1.1.3. Organizational feasibility.
4.1.2. Data collection tools.
4.1.2.1. Interviews.
4.1.2.2. Observation.
4.1.2.3. Questionnaire.
4.1.2.4. Documentary review.
4.1.2.5. Tool continue.
4.1.3. Data collection process.
4.1.4. Data analysis plan.
4.2.System requirements
4.2.1. Functional requirements
4.2.2. Non - functional requirements
4.2.3. System requirements
4.2.4. Hardware requirements
4.2.5. Software requirements
4.2.6. Environmental requirements
4.3.System design
4.3.1. Input design.
4.3.1.1. Input devices.
4.3.1.2. Input format.
4.3.1.3. Other device participating in feeding data in the system.
4.3.2. Output design.
4.3.2.1. Output design
4.3.2.2. Output formats
4.3.2.3. Output devices
4.3.2.4. All actors which perform in output process.
4.3.3. System design.
4.3.3.1. Deliverables and outcomes
4.3.3.2. Database design
4.3.3.2.1. Entity relationship diagram (ERD).
4.3.3.2.2. Data Flow Diagram.
4.3.3.3. Database table description.
4.3.3.4. Data dictionary.
5. Implementation
5.1.Programming
5.2.Test plan
5.2.1. System testing
5.2.2. Testing strategies
5.3.Maintenance
5.3.1. System evaluation
5.3.1.1. Formative evaluation
5.3.1.2. Summative evaluation
6. Time schedule/ Action plan/ Work plan
This indicate the sequence of activities by stipulating what will be done when and if necessary why that
particular time. It can also include an indication of who will be responsible for what. Time schedule can
be written in outline or in a matrix format.
7. Proposed budget.
This entails indication of cost that will be involved in undertaking certain project as well as the resources
that will be required. Good budget preparation helps help project management team to get funds easily
since the project sponsor (funders) would like to see how rational the project team will be in terms of
spending the project funds. Budget also help project sponsors to determine weather they have enough
fund or not and if not, then how much is required and where to get the remaining. Budget can also be
used to advise the project management team and make some modification in the project.
8. References.
Write using the recommended style selected by the institution or organization. Use the referencing style
according to the demand or instructions.