Table Contents

1. Table Contents........................................................................................................................I
2. Introduction............................................................................................................................1
1.1. Purpose........................................................................................................................................1
2.1 Objectives....................................................................................................................................2
2.1.1 General objective................................................................................................................2
2.1.2 Specific objective................................................................................................................2
1.2. Scope...........................................................................................................................................2
1.3. Definition.....................................................................................................................................3
1.4. Abbreviations...............................................................................................................................3
1.5. Reference.....................................................................................................................................3
1.6. Overview......................................................................................................................................4
3. Overall Description................................................................................................................4
3.1 Product Perspective.....................................................................................................................4
3.2 Product Functionality...................................................................................................................4
3.3 User Characteristics.....................................................................................................................5
3.4 General Constraints.....................................................................................................................5
4. Specific Requirements............................................................................................................5
3.1 External interface requirement.........................................................................................................5
3.1.1 User Interface.............................................................................................................................5
3.1.2 Hardware Interface.....................................................................................................................6
3.1.3 Software Interfaces.....................................................................................................................6
3.2 Non-Functional Requirements...........................................................................................................7

I
1. Introduction

Now days, in many part of the world and also in our country Mobile devices are dominant and,
beyond the future it is anticipated that mobile internet utilization will exceed desktop utilization
worldwide. In this project, we need to develop an integrated system on Advertising System
(UHU LEMNE).

The Advertising System(UHU LEMNE) will provide an interface on the university official
Integrated system in which customer can access information and interact with other members
of their respective class. It will be implemented with the collaboration of Information and
Communication Technology directorate office (ICT) and Collage of Computing and Informatics
(CCI) Department of Computer Science.

1.1. Purpose

The purpose of this document is to present a detailed integrated system UHU LEMNE. It will
explain the different functional as well as non-functional requirements of the system, the
interfaces of the system, what the system will do or how the system will interact with the
external users, the constraints under which it will operate. This Software Requirement
Specification document will provide a clear understanding of what is expected by the client in
the proposed UHU Lemene Integrated system. This will give a clear idea on how the software
should be developed by the development team for the end users. This SRS will provide a solid
base or foundation for the project. From this SRS and the testers can create test plans and various
test case documents.

The main goal of the project is to design an important system for managing the advertisement
activities. The new proposed system will operate efficiently by eliminating all the time
consuming issues and provides a better and much enhanced services to the customers as well as
the management and staff. The proposed software is multi-platform software such that it will
work in all the operating systems and most of the browsers.
1.1 Objectives
1.1.1 General objective
The general objective of this project is to develop Advertisement system for Haramaya
University.

1.1.2 Specific objective

In order to achieve the above general objective we:

 Design the architecture for the proposed system use for next version.
 Develop user friendly and interactive system.
 To provide easy information sharing system.
 To provide better controlling system.
 To minimize time and resources for information processing.
 To solve problems of disable user.
 To increase transparency of information.
 To easy data storage and management.
 To develop a computerized system in Haramaya University

1.2. Scope

The software to be produced is an Integrated System known as UHU Lemne which will help the
customers of all Haramaya university communities such as clubs, unions, forums, student,
teacher, the Haramaya University Security and administrator. The core part of the project is to
give information online. There are three types of the users for this system the first one is the
customer who uses the system to see news. The other user is the manager to address news and
the admin who are given separate authentication to users of the system.

The system is used to give new information. The user can give and receive news or information
through online, through phone or in web. The customer needs to enter their personal details. An
email containing the confirmation details will be sent to the customer’s email address or message
 to mobile. The staff members of the Haramaya University like, clubs, unions, forum, students,
teacher and administrator need to enter the customer details by authorization.

1.3. Definition

In this documentation there is no new word to be defined, but the name of the project that is
UHU LEMNE simply UHU mean a thing that is used for attaching a notice papers in the wall
and the word LEMNE is Amharic mean “I do not want” so UHU LEMNE means I do not UHU
for nothing.

1.4. Abbreviations

Acronyms/Abbreviations Definition
IEEE Institute of Electrical and Electronics Engineering Standards

GUI Graphical User Interface, the part of the application that the
user sees and interacts with.
XML Extensible Markup Language is a simple, very flexible text
format which is designed to carry data, not to display data.
PHP Personal home page
Html Hypertext markup language
Admin System administrator
RAM Random Access Memory
SW Software

1.5. Reference

 Software Architectural and Design Document Template given by the teacher.

1.6. Overview

This software architecture and design documentation is intended for the software development
team, they can use it a base line for developing the system. This document contains different
topics and sub-topics which help for understanding the architecture and the entire design of the
system.
2. Overall Description
2.1 Product Perspective

Even though the product which is going to be implemented is a new product it can be used as
enhancing solution for an existing manual system. This system explained in this document is the
first version. This system will replace the existing manual system of Haramaya University
Advertisement. The systems are interacting with security employers, students, teacher, clubs,
forums and administrator. Customer can view information posted by manager and admin can
control overall system.

2.2 Product Functionality

The key functionality of this system can be abstracted as follows.

 The customer can be register to system.

 Enable customer to have information easily since the system online advertisements
instead of paper.
 To help the manager easily distributes (uploads) any related information and
advertisement.
 The Administer can control overall services proved by the system.

2.3 User Characteristics

UHU LEMINE to the following user classes:-

The end user who plays an important role in the proper function of the application must
be familiar with Android Mobiles. The users, when they use the application they should
know how enable network connection.
Primary User – It defines student and staff.
Developer – The role of a developer is to maintain the application. It is assumed that the
developer is adept in html, PHP, XML, java and Android.
Data Clerk-is an IT literate and a person with detail system component knowledge and
experience. Has access to preparing news, notices and advertisement to the system.
 System Admin –this is a programmer and a person with detail system knowledge and
experience .has access to control database and server.

2.4 General Constraints

 Shortage of time.
 Hardware and software failures.
 Shortage of internet access.
 Shortage of consultancy service.
 Shortage of power access.

3. Specific Requirements
3.1 External interface requirement
3.1.1 User Interface

The user interface should be easy to understand and use by the end user, so that he or she can
choose the operation he wants to do without any confusions. The format on the screen should
describe the operations that can be done using the proposed system.

The proposed system has the integrated system.

 the Integrated system

 the GUI of the Integrated system must be responsive in order to have ease of access
while accessing remotely
 the Integrated system must have attractive loading page which can enhance the work
sprit of the user and also which inform about the system for the visitors
 the Integrated system shall have special login interface for the administrator of the
website
 the Integrated system shall have attractive and easily manageable interface after
login
 the Integrated system shall protect any wrong entry of the user
 the Integrated system shall interact with the server as fast as possible
 The proposed system requires server to store information
3.1.2 Hardware Interface

The hardware interface specifies the logical characteristics of each interface between the SW and
hardware on which the SW run.

Computer (Laptop) with a connection: For developing software

Compact Disk: To back up the software documentation

Flash Disk: For transferring files

800 GB hard disk (HDD) 512 memories (RAM), 3.2 GHz processor, Server, Printer

3.1.3 Software Interfaces

The software interfaces specify the SW and hardware on which the SW can run, so in this system
we have used:-

 Eclipse: -software to design the proposed system. It is a multi-language

integrated development environment (IDE) comprised a base workspace and
an extensible plug-in system for customizing the environment.

 API services

 MySQL

 Notepad

 Microsoft Office 2010: For writing system documentation

 Enterprise Architect: For developing charts and diagrams in documentation.

 Internet: To search additional information about system development

Functional Requirements are those that refer to the functionality of the system, i.e. what services
it will provide to the user. Statements of services the system should provide how the system
should react to particular inputs and how the system should behave in particular situations.

F1: Enable customer to register.

 F2: Enable the customer, manager, administrator to login and logout.
F3: Enable the customer and manager to view and update his/her profile.
F4: Enable the customer to view information.
F5: Enable the manager to post, edit and delete advertisement.
F6: Enable the administrator to manage the account.

3.2 Non-Functional Requirements

Non-functional requirement mean necessities of the new system that not directly related to
the functionality of the new system.so

 The system must keep copy of every day work as back up. This should be done every
day and kept in DVD disks.
 The database server should be updated for latest update of anti-virus every morning.
The system must also employ user authentication features of the system by setting
user name and password.
 Security becomes crucial issue in the proposed system. A user must login to the
system with user name and password. The system should allow login to only
authorized users. Users that have previously created account through user name (E-
Mail) and password.
 The system should give information about services that users have been used every
month, So users can use system.
 Performance also is the core non-functional requirements
 In case of time and
 In case of capacity.