<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel rdf:about="http://hdl.handle.net/123456789/79">
    <title>DSpace Collection:</title>
    <link>http://hdl.handle.net/123456789/79</link>
    <description />
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://hdl.handle.net/123456789/473" />
      </rdf:Seq>
    </items>
    <dc:date>2026-04-05T15:13:32Z</dc:date>
  </channel>
  <item rdf:about="http://hdl.handle.net/123456789/473">
    <title>WEB-BASED SEAMAN MANNING ETHIOPIAN SHIPPING LINES</title>
    <link>http://hdl.handle.net/123456789/473</link>
    <description>Title: WEB-BASED SEAMAN MANNING ETHIOPIAN SHIPPING LINES
Authors: W/Amanual, Senait; Hailu, Ghirmai; Abate, Temesgen; Mulugeta, Abiy
Abstract: The purpose of this Project was to solve practical problems of Seaman Manning&#xD;
Department of the Ethiopian Shipping Lines Company by developing user friendly&#xD;
software database which is web-based seaman system. In the Company, there was&#xD;
difficulty in accessing easily pieces of information on its seamen in the vessels. To this&#xD;
end, the Project generally made the ESL services more satisfactory to seaman than the&#xD;
previous times which, in turn to its customers. Specifically, the research-based Project&#xD;
also aimed at (a) assessing and analyzing the existing system to investigate and to&#xD;
identify the problems with the ESL; (b) observing the benefits of implementing webbased&#xD;
seaman manning system in the ESL; (c) developing software to process the&#xD;
activities of recording seaman data; (d) eliminating the burden of paper usage as&#xD;
much as possible in the Company; (e) simplifying searching for documents; and (f)&#xD;
providing reliable, timely and accurate information about the seaman corresponding&#xD;
body (such as Manning Officer for Administration HRM report). Data were collected&#xD;
using interviews using interview guide, survey using standard questionnaire and direct&#xD;
observation using observation checklist methods. The team members used Object&#xD;
Oriented System Analysis and Design (OOSAD) technique and the tools, such as the&#xD;
Argo UML, Microsoft Project, Microsoft Project and Microsoft Office. In the process&#xD;
of finding problems of the existing system, the team used PIECE (Performance,&#xD;
Information, Economics, Control, Services). Practices, like passport book issuance,&#xD;
seaman book issuance, medical certificate validation, vaccination card issuance,&#xD;
coordinating visa issuance activities and seaman reporting should be preserved from&#xD;
the existing system On the other hand, there are alternative options to address&#xD;
problems of the existing system. These are: (a) to examine our options we will perform&#xD;
SWOT (Strength, Weakness, Opportunities, Threat) analysis technique; (b) there are&#xD;
generally two options off-the-shelf and custom soft wares. In addition to examining&#xD;
general software category, the team also identified the following three types of&#xD;
database development approaches: standalone database, distributed database&#xD;
approach, and centralized database approach. The Project team proposed a webbased&#xD;
seaman manning system by developing user friendly software and database to&#xD;
improve the problems mentioned above. There are functional and non-functional&#xD;
requirements of the proposed system. The functional requirements include: (a) validate&#xD;
user which are users should have user name and password; users can be an&#xD;
317&#xD;
administrator; seaman; manning officer; HRMA Manager; evaluator (i.e. HRM&#xD;
Division Head, Technical Manager, Training Officer, and Captain); the system&#xD;
prompts the user to enter password and user name; and (b) If they are correct, the&#xD;
system will display the required page else it prompts the user to reenter his correct&#xD;
identity. The non-functional requirements include: (a) The system should be&#xD;
operational for 24 hours per day; (b) For most queries, the system should generate&#xD;
report in short period of time; (c) virus protection facilities; and (d) efficient backup&#xD;
every week. In addition to these, the proposed system has documentation, user&#xD;
interface and performance. Regarding exception and error handling, the Project&#xD;
devised portability, reusability and maintainability. As to essential modeling,&#xD;
administrator, captain, fleet manger, HRMS, and technician were identified as major&#xD;
actors. The use cases identified are: (a) Login; (b) Register new employee; (c) Search&#xD;
seaman information; (d) Register new staff; (e) Follow up employee; (f)&#xD;
Recommendation; and (g) Technical Issue. The design deliverables include: class type&#xD;
architecture, controller classes of the system and business classes of the system in&#xD;
design. In addition, the five-layer class-type architecture for the design of the objectoriented&#xD;
software which include: user interface layer, controller/process layer,&#xD;
business/domain layer, persistence layer, and system layer was employed. In&#xD;
conclusion, designing seaman manning system helps the ESL Company to ease its&#xD;
burden and lessen the cost by facilitating manning order report generation and by&#xD;
avoiding some of the problems which are related to the above activities. Finally, it is&#xD;
recommended that the HRM Division of the Company should utilize the benefits of&#xD;
web-based information technology system and should implement this Project to solve&#xD;
its problems faced on this particular area. The ESL should also extend the Project by&#xD;
adding its some other uncovered tasks.</description>
    <dc:date>2014-06-01T00:00:00Z</dc:date>
  </item>
</rdf:RDF>

