0% found this document useful (0 votes)
86 views

Course Title:-Final Project I

This document provides guidance on writing a project proposal for a course titled "Final Project I". The proposal should include sections introducing the project, stating objectives, and describing significance. Key points covered include writing an informative title, acknowledging contributions, and structuring the introduction to establish context, identify problems, and motivate readers. An abstract should briefly summarize the project purpose, scope, and methodology. The document models examples for components like the problem statement and significance statement.

Uploaded by

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

Course Title:-Final Project I

This document provides guidance on writing a project proposal for a course titled "Final Project I". The proposal should include sections introducing the project, stating objectives, and describing significance. Key points covered include writing an informative title, acknowledging contributions, and structuring the introduction to establish context, identify problems, and motivate readers. An abstract should briefly summarize the project purpose, scope, and methodology. The document models examples for components like the problem statement and significance statement.

Uploaded by

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

Course Title:- Final Project I

 Course No: COSC 491


 Credit Hours: 3
 Contact Hours: 3
 Laboratory: Not Required
 Prerequisite: COSC 352
Course Description
 This is final year course where students apply the
concepts they learn in different courses.
 The first phase of student’s project will be handled.
 This covers project proposal document
preparation, project management concepts,
requirement gathering and analysis and system
design concepts.
 At the end of this course students should submit
their final phase of one document of their project
which will be taken as input for the second phase
that focus on the Implementation and Testing
phase of the project.
PART ONE(CHAPTER ONE)

PROJECT PROPOSAL DOCUMENTS


Title of the Project
 A good title project contains the fewest number of words that
adequately describe the content of the project. The words to
be chosen are those that are both understandable and
retrievable.
 The following basic rules need to be observed when writing
the title of the project:
1. Use specific, familiar and short words.
2. Make your title as understandable and as retrievable as
possible.
3. Use correct syntax (word order) to avoid misunderstanding.
4. Avoid the use of unnecessary words that do not add anything to the
title.
5. Do not include abbreviations, or chemical formulas in your title.
6. Let your title be concise and descriptive.
7. Think of an informative but catchy title.
 Examples of Project Title:
 UNITY UNIVERSITY STUDENT REGISTRATION SYSTEM
 UNITY UNIVERSITY STUDENT FEE PAYMENT SYSTEM
 HOSPITAL PATIENT REGISTRATION SYSTEM
 MATERIALS AND STORE MANAGEMENT SYSTEM
 SUPER MARKET STOCK CONTROL SYSTEM
I. Acknowledgement
II. Table of Contents
III. List of Tables
V. List of Figures
VI. Acronyms
VII. Abstract
I. Acknowledgement
 Acknowledge all peoples, organizations and
others who support, guides and advice you to
guide and complete your project.
 Use one or two paragraphs to write your
acknowledgement
II. Table of Contents
 Used to describe titles and Subtitles of your
project with its corresponding page number
III. List of Tables
 Used to describe lists of all tables used in your
project document with its corresponding page
number
III. List of Figures
 Used to describe lists of all figures used in your
project document with its corresponding page
number
IV. Acronyms
 Used to describe all Abbreviations used in your
project document with its corresponding page
number.
 Example:
 OOSAD-Object Oriented System Analysis and
Design.
 HTTP-Hypertext Transfer Protocol
V. Summary/Abstract
 This Part of the project must be completed with one
paragraph with not more than 200 words and all contents
must be in italic form.
 It is a one page brief summary of the project proposal
 It shows that your work fits with the topic
 It shows what a contribution your work will make.
 It should specify the statement of the problem and how it is
going to be answered.
 Do not put any information not stated in the main text.
 Never contain references, figures and tables.
 It comes first but written last.
 It is the most read part next to the topic
 To write the abstract part of your project include the
following important elements of a project:
 Purpose of the Project
 Statement of the problem and how it is going to
be solved by this project
 Scope of the project
 Significance of the project
 Methodology (System Development approaches
used to analyze, design and develop the project)
CHAPTER ONE: INTRODUCTION
1.1 Back ground of the Project
1.2 Background of the Organization
1.3 Statement of the Problem
1.4 Objective of the Project
1.4.1 General Objectives
1.4.2 Specific Objectives
1.5 Significance of the Project
1.6 Scope of the Project
1.6.1 Delimitation of the Project
1.6.2 Limitation of the Project
1.7 Methodology
1.7.1 Data Collection Methods
1.7.2 System Development Approaches
1.7.2 System Development Tools
1.8 Project Management
1.9 Definitions of Basic Concepts
1.10 Literature Review
1. Introduction
It establishes a framework for the project you proposed so
that readers can understand how it is related to other project
It shows what the gap in the area is (statement of the
problem).
It shows what a contribution your project will make
(significance of the project).
Should site the most recent and relevant works(literature
review) and
Should explain why work is required (purpose or objectives
of the project you proposed).
It should motivate the reader to read the whole document of the
project.
Should be written from general to specific
1.1 Background of the Project
Overview and Benefits of Information System for the organization,
business or users with relevant site.
Problems of the Existing System (Not Problem of statement)
General Objectives of the project
Scope and Delimitation of the project
Limitation of the Project
Significance of the project and beneficiaries of the System
System Development Approaches or methodologies
1.2 Back ground of the Organization
 Describe about the Organization that you propose
or develop Information System.
 When It is Established?
 Why it is established?
 Where is the location of the Organization?
 How it is Organized and its purpose of the
organization?
 Show the Organizational Structure of the
Organization using Charts
1.3 Statement of the Problem
 Statement of the problem – the issue that leads to the need
for the project.
 It answer the question ‘Why does this project should
be proposed ?’
 The foundation for everything to follow in the proposal.
 Describe the problems that you need to solve by your
proposed project shortly and precisely in one paragraph.
 Let’s watch the following sample problem of statement
and use as a reference what to write in your project as a
statement of problem:
 At present the business has no stock control system in
place. Any items that are sold are not restocked. The
employees normally check the shelves in the store every
week to see what stocks are needed, write up a list of items,
which are purchased from the wholesalers. Telephone
calls are made to the food supplier to re-order food items
when needed; this can take up significant amounts of time,
especially if the sales assistant is managing the shop
counter alone. The stakeholders who are affected by this
problem include; the owner, employees, and the supplier.
 The impact of the problem outlined is that the
current business system does not allow for efficient
business practices, which essentially can be
costly to the business and generating stock
information can be time consuming for the
business. The proposed system will allow the user
to keep track of stocks, user should be able to see
the stock available at any given time, print out
reports of specific queries, and update prices when
they change.
1.4 Objective (aim) of the Project
 Objective/aim of the project– aim which the developer
seeks to bring about as a result of completing the project.
 Objectives should be simple, specific, stated in advance,
stated using action verbs.
1.4.1 General Objectives of the Project
 General objective – showing what exactly to be developed,
and states the desired outcomes from the project.
 Example 1:
 The general objective of this project is to develop Web-
based Student Registration System in order to deliver
reliable, secure, efficient, user friendly and on time
services to the customer and to minimize the cost of the
users and organizations.
1.4.2 Specific Objectives of the Project
 Specific objectives – shows in greater detail the specific aims
of the project you proposed.
 These must be achievable objectives and not statements of
the methods to be carried out.
 The objectives should be written in short concise sentences,
and each not consisting of more than two sentences.
 Example: In line with achieving the general objective the
project, deals with the following specific objectives:
 Design and Implement User Interface Prototype,
 Assess the existing system and database structure,
 Design appropriate system for the key activities of the system,
 Design and implement Database,
 Test and implement key functionalities of the system.
1.5 Significance of the Project
 This section provides answers as to what the project will
contribute.
 It should specifically state the value of the project. Why is
this project important?
 Example: The major significance of the System has the
following benefits:
 The university provides reliable, efficient and on-time
services to the students
 Allows the registrar or the university to complete the
required tasks with limited labor and cost
 The registrar easily manages and controls class schedules,
periods and university calendars.
 Enables the registrar to secure student information and
accessing student information also simple.
 Allows the university or the fiancé manager to manage,
control the financial statements and to generate finance
reports easily.
 Allows the department to assign the required instructors
for the course and easily to manage the schedules of the
instructors weekly or daily.
 Minimize corruptions and increase transparency in
collecting student fees and prepare financial statements
at the end of physical year.
 Enables the registrar to manage and control cheating
made by students during add/drop, prerequisite and
withdrawals.
 Allows the registrar to manage student grade and to
generate accurate and reliable grade reports according to
the schedules of the University.
1.6 Scope of the Project
 The project scope statement is a useful tool for future
decision making when new change requests are considered
to modify the project scope.
 It also defines the boundaries of a given project and
clarifies what deliverables are in and out of scope.
 Describe shortly what the proposed project to accomplish or to
deliver.
 Example:-
 The Scope of the proposed System is to track or handle the
problems of the current student registration system in Unity
University, Adama Campus.
1.6.1 Delimitation of the Project
 Delimitations are conditions or parameters that the
system developers intentionally imposes in order to
limit the scope of a project or deliberately self
imposed constraints on the project.
 Examples:-
 Using English language only to design user
interface,
 Use Web-based scripting languages to implement
the system or project,
1.6.2 Limitation of the Project
 Limitations are constraints to the project that are beyond
developer control but that may influence the objectives
of the project.
 Limitations are external conditions that restrict or
constraint the project’s scope or may affect its outcome.
 Limitations may emerge at any time during your project
development.
 Limitation of the project is explained shortly those issues
that may not be included while the developer design and
develop a project beyond the capacity of the developers.
 But the project is implemented and perform its operation
by using other alternatives (i.e; tools, methods and
others).
 And the project reliability, performance,
acceptability and etc must be insignificant
difference with the alternatives.
 Example: Student Registration System designed
and implement in Unity University, Adama campus
faced the following limitations:
 The project or the system does not consider disabled
users.
 The project is implemented using trial version
software due to high cost of the software available
for commercialization.
 The developed software is only working in LAN
based technology.
1.7 Methodology
1.7.1 Data Collection Techniques
 List down only those data collection methods
used to determine or gather the requirements
of the user.
 Not necessary to include those data collection
techniques not used in your project.
 Not necessary to describe or explain the
techniques but simply list down.
 Reason out why you select those techniques
for your project if possible.
1.7.2 System Development Process Model
 List down clearly those development
approaches used to analyze and design the
proposed system
 Clearly List down those Object Oriented
System Development models to model the
existing and proposed system.
1.7.2 System Design and Development Tools
 Tools are computer programs, such as Computer Aided
Software Engineering (CASE) tools, that make it easy to
use specific techniques.
 List down those tools used to design, develop and
implement the system you proposed.
 Examples:
 Microsoft Project Management- to schedule the time frame
of the project.
 Enterprise Architecture to design UML diagrams.
 PHP to develop server side application program
 MySQL- to implement the database
 Wamp Server- to integrate both PHP and MySQL
1.8 Project Management
1.8.1 Time Management
 Clearly define the time frame required to design and
develop the project to follow either the project is performed
according to the time frame you define.
 Use Software such as Microsoft Project Management or
others to schedule the project.
1.8.2 Cost Management
 Determine the total cost required to complete the system
you will develop.
 List down all the resources (materials, equipments, human
resources, software costs and others) with its corresponding
quantity and costs required in a tabular form.
1.9 Definitions of Basic Concepts
 Define those basic concepts that we need to address
in the project to provide general knowledge and
understanding for the readers or for end users of the
system.
 Try to specify sources and put evidence for the
definition of those concepts that you need to define.
1.9 Literature Review
 Literature review – a description of the literature very
relevant to your system development.
 Gives an overview of what has been said, who the key
authors in the area are, what are the prevailing theories,
principles, algorithms, development approaches and etc.
 Relevant materials could be from books, journal articles,
other related system development materials and government
or organization reports, and etc.
 Be very careful to check your sources when doing your
literature review.
 Include 15-20 individual literatures or related works done
by others with clear evidence.
 These Literature reviews that you include here is used as a
reference of your project must be used in bibliography.
 References – citation of all the information that you
obtain very related to your system.
 The style of writing list of references varies from
one discipline to another.
 Abebe T. 2005. Frequent use of internet use and distance
learning. Journal of Computer Science. Vol.1, pp. 200-
205.
 Anderson, A.T. and B.D. Sharma. 2001. Frequent
use…..
 Andersont, A.T., B.D. Sharma and R.S. Garg. 2007.
Freuent use ….
 Abebe, T. 2005. Applied Physics. Selam printing press,
4th ed. Addis Ababa.
• Appendices/annexes – additional information
provided for the reader. These include, for
example,

Sample Code
Sample UI
Dummy tables
Biographical data
Questionnaire, forms, etc.

You might also like