WACHEMO UNIVERSITY

ENGINEERING AND TECHNOLOGY FACULTY

INFORMATION SYSTEM DEPARTMENT

PROJECT ON

[TITLE]

SUBMITTED IN FULLFILMENT OF THE …….

BY

[NAME]

[MONTH YEAR]

HOSSANA, ETHIOPIA
TITLE Page 2
ACKNOWLEGMENT

TITLE Page 3
Table of Contents
ACKNOWLEGMENT .................................................................................................................................. 4
LIST OF FIGURES ....................................................................................................................................... 7
LIST OF TABLES ........................................................................................................................................ 8
LIST OF SYMBOLS AND NOTATIONS ................................................................................................... 9
ABSTRACT ................................................................................................................................................ 10
Chapter one: ................................................................................................................................................ 11
1. INTRODUCTION ............................................................................................................................... 11
1.1. Background ................................................................................................................................. 11
1.2. Existing System Study................................................................................................................. 11
1.3. Proposed System ......................................................................................................................... 11
1.4. Objectives of the Project ............................................................................................................. 11
1.5. Scope and limitation .................................................................................................................... 11
1.6. Feasibility study .......................................................................................................................... 11
1.6.1. Economic feasibility ............................................................................................................ 11
1.6.2. Operational feasibility ......................................................................................................... 11
1.6.3. Technical feasibility ............................................................................................................ 11
1.6.4. Time feasibility.................................................................................................................... 11
1.7. Methodology ............................................................................................................................... 11
1.7.1. Methodology of data collection .......................................................................................... 12
1.7.2. System development methodology .................................................................................... 12
1.7.3. System development tools .................................................................................................. 12
1.8. Significance of the Project........................................................................................................... 12
1.9. Project organization .................................................................................................................... 12
Chapter Two: ............................................................................................................................................... 13
2. SYSTEM FEATURES ........................................................................................................................ 13
2.1. Existing System Description ....................................................................................................... 13
2.1.1. Business rule ........................................................................................................................ 13
2.1.2. Actor in the existing system ................................................................................................ 13
2.2. Description of the proposed system............................................................................................. 13
2.3. Functional Requirements ............................................................................................................. 13

TITLE Page 4
 2.3.1. User Requirements .............................................................................................................. 13
2.3.2. System Requirements.......................................................................................................... 13
2.4. Non-Functional Requirements..................................................................................................... 14
Chapter Three .............................................................................................................................................. 15
3. SYSTEM MODEL .............................................................................................................................. 15
3.1. Introduction................................................................................................................................. 15
3.2. Use case diagram ........................................................................................................................ 15
3.2.1. Actor specification ............................................................................................................... 15
3.2.2. Use case description ............................................................................................................ 15
3.3. Dynamic Model ........................................................................................................................... 15
3.3.1. Sequence Diagram............................................................................................................... 15
3.3.2. Activity Diagram .................................................................................................................. 15
Chapter Four................................................................................................................................................ 16
4. SYSTEM DESIGN ............................................................................................................................. 16
4.1. Introduction................................................................................................................................. 16
4.2. Architectural Design.................................................................................................................... 16
4.3. Component Diagram ................................................................................................................... 16
4.4. State chart modeling ................................................................................................................... 16
4.5. User Interface Design .................................................................................................................. 16
4.6. Data Structure Design (database design) .................................................................................... 16
4.7. Algorithm Design ........................................................................................................................ 16
4.8. Deployment Diagram .................................................................................................................. 17
Chapter Five: ............................................................................................................................................... 18
5. IMPLEMENTATION AND TESTING .............................................................................................. 18
CHAPTER Six ........................................................................................................................................... 18
6. CONCLUSION AND RECOMMENDATION ................................................................................... 18
6.1. Conclusion ................................................................................................................................... 18
6.2. Recommendation ........................................................................................................................ 18
REFERENCE .............................................................................................................................................. 18

TITLE Page 5
LIST OF FIGURES

TITLE Page 6
LIST OF TABLES

TITLE Page 7
LIST OF SYMBOLS AND NOTATIONS

TITLE Page 8
ABSTRACT

TITLE Page 9
Chapter one:

INTRODUCTION
1.1. Background

 Background of the organization

 Mission, vision and objective of the organization for which you are going to develop
the new system, etc…

1.2. Existing System Study

a. Describe how the existing system functions (manual, semi –automated, automated)

b. List and describe the problems in the existing system

1.3. Proposed System

Brief description of the proposed solutions for the problems mentioned in 3.b

1.4. Objectives of the Project

Describe general and specific objectives of the project.

1.5. Scope and limitation

Clearly show the functions (boundary) of your system that is expected to cover

1.6. Feasibility study

1.6.1. Economic feasibility

1.6.2. Operational feasibility

1.6.3. Technical feasibility

1.6.4. Time feasibility

1.7. Methodology
State how the requirements are gathered, the tools used for analysis and design,
implementation, etc. ….

TITLE Page 10
 1.7.1. Methodology of data collection

1.7.2. System development methodology

1.7.3. System development tools

1.8. Significance of the Project

What is the contribution of the project? Organization ofthe Project Include the chapters
and what it talks about..

1.9. Project organization

TITLE Page 11
Chapter Two:

SYSTEM FEATURES
2.1. Existing System Description

Describe the excising system how it works in detail step by step Proposed System
Description

2.1.1. Business rule

2.1.2. Actor in the existing system

2.2. Description of the proposed system

2.3. Functional Requirements

2.3.1. User Requirements

 List out all user requirements of the system. Each requirement should
be uniquely identified with a sequence number or a meaningful tag of
some kind. You may provide a short description of the
feature/requirement and indicate whether it is of High, Medium, or
Low priority.
 Group the requirements into coherent set of categories like
Grouping 1
REQ-1:
REQ-2:
Grouping 2. ……
 Include all requirements: In addition to the functional requirements
interface requirements, logical requirements and data requirements
should also be included here

2.3.2. System Requirements

 Detail the requirements in section A using fully dressed use cases. This
section should include a use case diagram and detailed use case
descriptions.

TITLE Page 12
 2.4. Non-Functional Requirements
List all the non-functional requirements which are relevant to your system

TITLE Page 13
Chapter Three:

SYSTEM MODEL

3.1. Introduction

3.2. Use case diagram

3.2.1. Actor specification

3.2.2. Use case description

3.3. Dynamic Model

3.3.1. Sequence Diagram

3.3.2. Activity Diagram

TITLE Page 14
Chapter Four:

SYSTEM DESIGN

4.1. Introduction
4.2. Architectural Design

A software system is a set of communicating entities that collaborate to perform a task.

The Architectural Design is a top level design which shows these entities, their
relationships and the relationships. Each entity of the architectural design needs an
abstract specification. The specification is a description of its purpose, its functionality,
its attributes (including dependency on other entities) and the constraints under which it
must operate. Class diagrams or structure charts may be used to represent architecture of
a system.

4.3. Component Diagram

4.4. State chart modeling

4.5. User Interface Design

Describe the logical characteristics of each interface between the software product and
the users. This may include sample screen images, any GUI standards or product family
style guides that are to be followed, screen layout constraints, standard buttons and
functions (e.g., help) that will appear on every screen, keyboard shortcuts, error message
display standards, and so on. Define the software components for which a user interface
is needed.

4.6. Data Structure Design (database design)

Design in detail and specify the data structures to be used in the implementation. If these
include databases, define the table structure of all databases including full field
descriptions and all relations. Graphical languages like ER diagram are appropriate.

4.7. Algorithm Design

TITLE Page 15
 For the elements found in architectural design define the algorithm required for each
element to accomplish its tasks(Pseudo code for each functionality implementation )

4.8. Deployment Diagram

The deployment diagram should show

1. The physical communication links between hardware items (machines and other
sources, such as printers)

2. The relationship between physical machine and processes – what runs where?

TITLE Page 16
Chapter Five:

IMPLEMENTATION AND TESTING

CHAPTER Six:

CONCLUSION AND RECOMMENDATION

6.1. Conclusion

6.2. Recommendation

REFERENCE

TITLE Page 17