Internship Report
Internship Report
An executive summary
now a days developing software system is an emerging
technology in Ethiopia.AMA is one of the organization that
uses different software system and design other required
software by the organization.
According to the program of debre markos university
institute of technology I have been working my internship in
this organization for the last two months from july to
September. During this period I was working in the
sections provided by the company, which are I CT section.
Generally; during the internship period I have improved &
gained different skills, attitude & knowledge of
see external conditions of software development
environment.
Objectives
My objective in my internship program is to improve my
software engineering experience and work on real world
projects at the time of my internship program.
Brief History of AMHARA MASS MEDIA AGENCY
Over all internship experience
How became interned in AMA.
The chance of being interned in AMA is gained by appealing to the company early
in February 2011(E.c). I took an application letter from university industry linkage
office at the institute (DEBRE MARKOS). The application letter was submitted to
AMA ICT section manager Ato mr x and they confirmed my hiring as internship.
Then on the month may 2011 E.c. I took the acceptance letter to the UIL office for
confirmation. The company accepts me for two-month internship from July ,01 up
to august ,30. And then I began my internship program as provided.
Sections of the company I was working
AMA is an organization which works broadcasting of information. Since broad
casting of information requires software system to broadcast and to control over
all distribution of information inside the organization. So in order to proceed this
task the a section of organization called ICT is found. I have got the chance in ICT
section .in this section I was work specially in software design activities.
Work flow in the laboratory section
---------------------------------------------------------
Work piece or work task I have been executing
Amhara mass media agency ICT section have different sections such as network,
software development and technician. in these sections I work a activity of
software design documentation, cable Crimp and file sharing through network.
Procedures used while I was performing my work
Procedures used in the software design documentation for
FM bahir dar running order
CHAPTER ONE
INTRODUCTION
Amhara mass media agency is a media organization found in bahir dar Town. This
organization facilitates the sharing of information through different techniques
such as through tv broadcast, FM radio wave, YouTube applications etc. So, from
these techniques we are going to develop a web-based system for FM bahir dar
running order.
FM Bahir Dar running order has a number of activities in each day. Such activities
are allocation of different programs in each day, checking the continuity of the
running program based on the given time, scheduling the time of prepared news
presented in a day.
The system has employees like news presenter, news producer, studio reporter,
director, technician and editor the news producer prepares news to be presented
by the presenter. The studio reporter records the running program. the editor
checks and edit the running program and the technician fix technical problem in
the distribution of programs. The director provides scheduled program running for
each day. The scheduler prepares using MS-word document and distribute the
schedule manually for each concerned body.
Background
proposed system
The proposed system provides a solution for the manual system by
automating the system using web-based system by providing dynamic web
page and designing interactive interfaces for the user. Unlike the existing
system which consumes resources and time and difficult to access. the
proposed system saves our resource and time and easy to access it.
Objectives of the project
General objectives
The general objective of Amhara mass media agency FM bahir dar
running order make automated web-based system for users of the
organization.
specific objectives
In order to achieve the general objective, the team has considered the
following specific objective have to be take in account during developing this
system. The specific objectives are:
understanding the existing system and trace out the problem
Developing an intuitive user interface for the users
Find out the requirement required to design the prototype
Implementing the desired system
Testing and validating the developed system
scope of the project
The scope of the project to is focused on the following main activities.
Registering (employs, programs, news)
editing running order information.
Deleting running order information if needed
methodology
data collection method
there are different ways of data collection methods to gather
requirments.in this project we use the following data collection
methods.
CHAPTER TWO
System features
Requirement analysis (system feature) consist of requirements such as
functional requirement, nonfunctional requirement, hardware requirement,
software requirement.
Hardware and software requirements
Hardware requirements
memory: - 2Gb
pc: corei3 processor
hard disk: - 500 Gb for storing data
permanently.
USB disk: for data transfer and also for
backup
software requirement
The software requirements are the instructional
components used to develop a system. Software
requirement to develop system are as follows:
Browsers: -such as chrome. Internet explorer,
opera etc. used to access webpages
Operating system: -windows or Linux operating
system
Database management software: -this important
for recording permanent information
Visual studio code: -it is required for editing php
and java script and html, CSS text.
Xampp server: -this is required for accessing
php script through browser.
user requirement
user requirement are services that the system is
expected to provide to the user-based system
constraints and business rule.
functional requirement
functional requirement refers to specific functionality that define what a system is
supposed to accomplish.
Functional requirements that must be included in the system are:
the system should register employee that are participate in the running
order preparation
It should register running programs in the organization
It should map the running program with the employee which provides the
program
It should check weather; the program is performed or not
It should Display running order program
Non-functional requirement
The non-functional requirement is anything and everything that is not covered in
Functional requirement, basically functional requirement can be defined as
requirement that specifies criteria that can be used to judge the operation of a
system, rather than specific behaviors.
Some of non-functional requirement include in this system are:
Performance: -
The performance of the Application can be determined by it responsive time, time
to complete the given task. Also, it is made sure that it will not hindrance to the
user Input.
Scale-ability: -
this system is able to adopt itself to increased usage or able to handle more data as
time progress. when the user data (caches, stored data etc.) increases it is capable
of handling them without delay by optimizing the way storage is done and
accessed.
Availability: - the system is accessed at any time without failure.
Security: -un authorized users cannot modify running order
Analysis Models
Actor Definition
Actors: An actor represents a type of users of that interacts within the system.
The actors involved in this system are:
editor: - someone who checks the continuity and edit of running
program.
postcondition: the editor can check the registered running order information and
edit it.
Activity diagram
Activity diagrams provide a way to model the workflow of a business process.
Different tools such as decisions, start states, end states, are used on the activity
diagram. Activity diagram is basically a flow chart to represent the flow form one
activity to another activity. The activity can be described as an operation of the
system.
figure 10 Activity diagram for login
figure 11 Activity diagram for registering running order information
figure 12 Activity diagram for provide news
figure 13 Activity diagram for edit running order
figure 14 Activity diagram for view technical problem
Figure 15 Activity diagram for create account
Figure 16 Activity diagram for approve running order
Figure 17 Activity diagram for record technical problem
CHAPTER THREE
SYSTEM DESIGN
The purpose of design is to determine how the system is going to build and to
obtain the information needed to drive the actual implementation of the system.
It focuses on understanding the model how the software built. System design is
the detail investigation of system elements from logical view.
Deployment diagram
A UML deployment diagram shows static view of the run time configuration of
processing system user and the components that run on system. In other words,
deployment diagram shows the hardware of our system, the software that to be
installing in that hardware. It also shows how hard ware and software
components work together.
class diagram
A class diagram is diagram that describes the structure of a system by
showing the system's classes, their attributes, operations (or methods)
and the relationships among objects. Class diagrams can also be used
for data modeling. Class diagram has three components. The top
component contains the name of the class. The middle components
contain the attributes of the class. The bottom component contains the
operations the class can execute.
Figure 19 class diagram for FM bahir dar running order
database design
roles table
Role no Role name
Normalization of table
Normalization is a process of achieving better designed relational database
schemas through the user of semantic information given by Functional
dependencies and Primary keys, Normalization process takes a relational schema
through a series of tests to check whether it satisfies conditions. The schemas that
satisfy certain condition are said to be in a given “NORMAL FORM’ and unsatisfied
schema are decomposed by breaking up their attributes into smaller relations
that possess desirable properties.
Since the tables are already normalized there is no any normalization process.
Schema Relationship Diagram
Role table
Practical Skills
During my intern ship period I gained some
practical skills from software design
documentation.
The following are practical skills I have got
Improve skills requirement gathering
Improve skills analysis of the collected
requirement
Improve skills data base design and
prototype software interface design
Theoretical Knowledge
Since the practice depends on theoretical
knowledge. During my internship I read how
to do my internship project and improve my
previous theoretical skills I have learned.
Interpersonal Communication Skills