Embed Size (px)
DESCRIPTION
i need job portal documentation
Citation preview
Chapter one
Introduction and background of the project
Debre Markos trade and transportation office is an office which is responsible for many activities. Among many activities addressing the price and supply information to the society is one of the duties.The current system of market price recording system has many problems including the speed of data processing and allocating the data to the society. Buyers and sellers are unaware about the daily price information due to lack of such system which performs fast recording and addressing to the society. In order to solve those problems I would like to introduce an online mechanism of market price recording and viewing system. In the system someone who wants to know the daily market price in Debre Markos will able to know the daily market price without actually going to the market. It is a new system that prevents going to the market without having any information about the price.
1.2. Statement of the problemIn this office there is a manual system of market price recording and viewing mechanism. In the system employees of the office record the item price twice per week. After dividing this sum by two they take it as a weekly price. After getting a certain result the workers report the weekly price for those who need the information. To distribute this price information worker use the manual process like printing the result and attaching it on board, sending the printed hardcopy as a letter for organizations. This type of doing activities is too tedious and time consuming. Further more customers or users can‘t get the weekly price information as they want since observing boards is tedious especially now at the time of advanced technology.
Generally, in this manual system the following problems are observed:
Manual documented system is time taking than computerized documented system. It isn’t easy to find the daily price data easily in short period of time. The right information can’t accessible at the right time for the right user. Sellers and buyers go to the market without having the information for price and
amount. Customers and sellers can’t guess weather there is sufficient or insufficient supply.
To solve this problem I use an online system daily price recording and viewing mechanism
1.3. Objective of the project
1.3.1 General objectiveThe main objective of this proposed project system will concerned with developing online market price recording and viewing system.
1.3.2 Specific objective To spend less time on searching and retrieving of files.
To easily view the daily prices.
To easily retrieve data.
To record employee information.
To reduce wastage of resource time and effort
.
1.4 significance of the projectThe benefits of this proposed mini_ project will be:-
• Easy access of information (online viewing the daily market prices in Debre Markos) for
customers.
• Less resource wastage (like time, material, money, human power ).
• Easy reporting information for those who needs it.
• Creating well informed market.
• Keeping information safely.
• Recording and knowing the daily supply of the price.
• Showing which serial types have shortage in supply.
• To decide buying or selling is better from merchants or from producers.
• Giving worker as well as customer satisfaction.
• Access information in a fast way.
1.5 Scope of the projectThe project covers online market price recording and distributing the recorded
information for sellers or buyers in Debre Markos market that in detail includes the
following.
• Record the daily market price .
• Viewing the daily Item price.
• Easily searching of data.
1.6. MethodologyA methodology is a set of methods, processes, and practices that are repeatedly carried
out to deliver project.
1.6.1 System Development Methodology System development methodology in system developing refers to the frame work that
is used to structure plan and control the flow of developing an information system.
The project use object oriented software development methodology including class
module.
The reason for selecting object oriented system development is:-
Objects/classes or models are used to represent real world problems in simplified
form.
Object based models appeal to the working of human cognition and hence the human
input in to the development of a system is likely to be more natural and less error
prone.
Allow full exploitation of the power of object based and object oriented programming
languages.
Encourages re-use not only modules but also entire design
1.6.2. Data Collection Methodology For understanding the real facts about the organization the main data collection methods include the following.
1. Observation: -
It is personally observing how to the existing system work, what the employers do and by
obtaining a relatively objective information.
2. Interview: -
This is the way of getting information from workers directly by asking them. Transportation and trade
head and workers under this give information how they work.
3. Documentation: -
This process helps to describe how the existing system operates, get necessary information from the
document like hard copy for further understanding.
1.6.3 Database and Programming toolsTo develop this system the system will use the following programming and database tools:-
HTML and CSS
Because:
It is easy to develop the system interface it does not require writing the
controllers design the system.
Allows data base integration with wide variety of application
It is ease to create forms
SQL SERVER and PHP
Because:
It’s is very fast.
More secure.
It is suitable for php programs.
For writing Documentation.
Microsoft 2007,2010
For drawing UMl Diagram
Edraw
1.7 Feasibility Study Feasibility is the measure of how beneficial the system development or enhancement of an
information system would be to the business. Feasibility analysis is the process by which
feasibility is measured. It is an ongoing process done frequently during systems development
project in order to achieve commitment from the user and to continually assess the current status
of the project.
1.7.1 Technical Feasibility Technically, the system will be feasible to be applied by technical expertise in computer field.
The system will be implementing or will operate the proposed system without the developer of a
proposed system. It will accessible by any person who has a skill of operating computers and
knowledge of English language.
1.7.2 Economic Feasibility This proposed web based system will economically feasible when compared to the existing
manual system. Because of the existing manually system supports all people or person who
wants information must be physically appearing on the market. This also loses users time and
energy. So this proposed system will solve the above problem.
1.7.3 Operational Feasibility The proposed market price record system will intend to provide every user-friendly and easy to
use interface which is beneficial for the market trader, transporter and customer. The system will
also easily acceptable to the user, market trader as well as transporter.
Chapter two
Analysis
2. 1 IntroductionOnline market price recording and viewing system is a mechanism of achieving market price
record and viewing through network accessed areas. In this system anyone who have a network
access is able to view the daily price in Debre Markos town.
The system also provides a comprehensive mechanism of market price awareness for the society.
The system helps sellers and buyers well informed for the daily price and amount of supply in
Debre markos town to prevent the tradition of going to market without information.
2.2. Purpose of the studyThe purpose of the study to this project is:-
Access information’s easily.
Employees able to search available information’s.
Increase customer satisfaction.
Increase speed of activity.
Saving passenger cost, time and energy.
Store any information safely.
To save our time and energy.
To decrease the human labor.
.
2.2.1 The existing system The existing system refers the paper based system that is used currently. The existing
system forces buyers and customers to come over to the market physically.
To buy or sell items users must present physically without any
information about the supply and the corresponding price that is if
there is no enough supply in the market sellers go to the market and
waste energy due to lack of information available.
Workers of the trade and transportation record the daily market
price and attach on board to inform for the surrounding society and
send the recorded data for enterprises as a letter.
2.2.2. Problems of the Existing SystemThe problems of the existing paper based system are described using the PIECES from
work. Where
P is performance
I is information
E is economics
C is control,
E is efficiency and
S is service
Performance
Response Time
The response time to do a given task in the current manual based system is
significantly high because of the time it takes to get the appropriate
recording and distributing manually is time taking and tedious.
Information
Out Put
Time it takes to get the appropriate recording and distributing manually is
time taking and tedious.
Information
Out Put
It is difficult to produce appropriate information using the current manual based system. Because it is time talking and tedious.
Input
Usually the data is not accurately recorded .
Stored Data
The data is not well distributed: everybody who wants to get the information
has no access since the information is store do on paper.
Data is not flexible
It is difficult to generate report from the current system.
Economics
Costs
The current system takes more costs (resources) to perform its tasks
Profit
The current system does not design at producing profit when it compares
with the cost it expense.
Control And availability
The current system does not much accessible due to its manuallness.
Efficiency
The current manual based system is not much efficient because it takes time to
perform tasks and the data may be redundantly recorded.
The system is not well organized to perform each activities and it is not flexible to
change or modify the data whenever needed.
2.2.3 Users of the Existing System
The users of the existing systems are any customer who can read on boards or
heard from others.
Users Is Part Of The New
System
Viewer Yes
Manager Yes
employees Yes
Table 2.1 user of the current paper base system
Administrator
The administrator interacts with the employees. He gives all service for every customer
that wants to support to the station offices
Employees
Employees directly interact with the real buyers and sellers in the market physically.
2.3. The proposed System Web based the existing manual system is the proposed system of this project. The new
system removes the existing manual system of attaching recorded information on board
and sending letters.
The proposed system needs a web based system that users view the daily market price
recording system in their house or any where they want. Through network access users
can view the daily market price and amount of supply in Debre Markos and its
surroundings.
2.3.1. Forms and reports of the proposed systemThe new proposed replaces all the necessary forms that exist in the manual system.
The proposed system has the following forms:-
forms function
log inform To enter in to the system
Viewing form To view the daily price and
amount of supply
Employee form To record employee details
Manager forms To record manager details
Item form To record item and its price
Table 2.2 forms and reports of the proposed system.
2.3.2. Users of the proposed systemThe users of the proposed systems are anyone have knowledge and experience to
use through computer.
Users Is Part Of The New
System
Manager Yes
Employee yes
Viewer yes
Table 2.3 users of the proposed system
2.4 Requirement definition The requirement definition actually is the System Requirements Specification (SRS).In this
section we have kept the basic understanding of the requirements and dependencies of the
current system prior to any actual design or development work.
A well-designed, well-written SRS accomplishes four major goals:
It provides feedback to the customer. An SRS is the customer's assurance that
we have understood the issues or problems to be solved and the software
behavior necessary to address those problems.
It decomposes the problem into component parts. The simple act of writing
down software requirements in a well-designed format organizes
information, places borders around the problem, solidifies ideas, and helps
break down the problem into its component parts in an orderly fashion.
It serves as an input to the design specification. The SRS serves as the parent
document to subsequent documents, such as the software design
specification and statement of work. Therefore, the SRS must contain
sufficient detail in the functional system requirements so that a design
solution can be devised.
It serves as a product validation check. The SRS also serves as the parent
document for testing and validation strategies that will be applied to the
requirements for verification
2.4.1 Functional requirementFunctional requirements are the intended behaviors of the system. This behavior
may be expressed as services, tasks or functions that the system is required to
perform.
Since we are going to develop an online market price recording and viewing system
therefore it should responsible for efficient recording and viewing
Item and price record by Employee
Viewing the item price
Searching of data anywhere and any time
Update unwanted data
Exchanging of ideas through messages
2.4.2. Non Functional Requirements accessibility
The accessibility degree of this system can be viewed in many directions including
employees of the office, sellers, buyers, enterprises and Medias.
Usability
The extent to users of this system includes anyone who wants to get market price
information and mass Medias to distribute the information to the society.
Requirement for reliability
Computer with good processing speed,
Local Area Network (LAN) and internet connection
Security issues
This issue encompasses measures taken throughout the applications life cycle to prevent
exceptions in the security policy of the system through flows in the design, development,
and maintenance of application. In general to make the system asset safe, the system will
follow a role based security which means the access level and privilege for each users of
system is predefined by the system administrator. The end user of the system most of the
time will be asked for authorization login except if the system developer has set its own
criteria to access the collections.
2.5 Business rule identification
View
To view the daily market price having internet access is sufficient. With internet
it is possible to know the daily market price in Debre markos.
Update employee records
To update employee records having appropriate user name and password in the
managerial side is a must.
Record daily market price
To record the daily market price an employee or the manager must have the appropriate
user name and password.
View comment
To view comments somebody must have the appropriate user name and password..
Send comments
To send comment user name and password are necessary requirements.
.
Viewer
Employee
Manager
Login
Record item price
View comments
Update employee
Record new employee
Send comments
View item price
2.5.1 User Diagrams for the proposed system Use case diagram a set of use cases for a system, the actors of these use cases, the relations
between the actors and these use cases, and the relations among the use cases. The UML notation
for a use case diagram is:
An oval represents a use case,
A stick figure represents an actor
A line between an actor and a use case represents that the actor initiates or
participates in the process.
The use case diagram for online market price recording and viewing can
Fig2.5 Use case diagram for Admin.
2.5.2 Use Case Description
Name: Login
ID Use Case 1
Actors Manager and employee
Description
This use case allows the Manager and employees login in to the system
Pre condition Manager and employee must have an account
Post condition Manager and employee login into the system
Table 1 Manager login.
Name: Record item price
ID Use Case 2
Actor Employee
Description This use case allows the employee record the daily item price
Pre condition The employee must have an account
Post condition Employee should record item details
Table 1.1Manager login.
Name: View comments
ID Use Case 3
Actors Admin and employee
Description This use case allows the admin and employees view comment in to the system
Pre condition Admin and employee have an account
Post condition Admin and employee view comments
Table 1.1 Admin login.
Name: Record employee
ID Use Case 4
Actor admin
Description This use case allows the admin record additional employees
Pre condition Admin have an account
Post condition Admin record employees
Table 1.1 Admin login.
Name: Update employee
ID Use Case 5
Actors admin
Description
This use case allows the admin to update employee
Pre condition Admin must have an account
Post condition Admin update users
Table 1.1 Admin login.
Name: Send comments
ID Use Case 6
Actors Viewer
Description This use case allows the viewers and enterprise send comments to the system
Pre condition viewers and enterprises have an account
Post condition viewer and enterprises send comments to the office
Table 1.1 Admin login.
Name: View item price
ID Use Case 7
Actors Viewer
Description This use case allows the viewers and enterprises view the daily item price
Pre condition Viewer and enterprises must have internet access
Post condition Viewer and enterprise can view the daily market price
Table 1.1 Admin login.
2.6 Sequence diagramA sequence diagram is a kind of interaction diagram that shows how processes operate with one
another and in what order. It is a construct of a Message Sequence Chart. A sequence diagram
shows object interactions arranged in time sequence. Sequence diagrams are typically associated
with use case realizations in the Logical View of the system under development.
The figure describe below represents sequence diagram of online market price recording and
viewing.
Manager Homage LOGIN Price information LOGOUT
Open mainHomepage
Click login
Check
Try again
Manager
Figure 2.6.1 login sequence diagram
manager Homage LOGIN MANAGEHOME EMPFORM
Open mainHomepage
Click login
Check
Try again
Manager
SUCCESS
RECORD
LOGOUT
Figure 2.6.2 employee record sequence diagram for online market price record system
Employee Homage LOGIN EMPHOME db
Open mainHomepage
Click login
Check
Try again
I
Employee
SUCCESS
RECORD
LOGOUT
Fig 2.6.3 item record sequence diagram
VIWER Homage VIEW
Open mainhomepage
Click view
Checkif found
Try again
Admin
Success
LOGOUT
Figure 2.6.4 viewer sequence diagram
2.7 Activity Diagram
An activity diagram illustrates the dynamic nature of a system by modeling the flow of control
from activity to activity. An activity represents an operation on some class in the system that
results in a change in the state of the system. Typically, activity diagrams are used to model
workflow or business processes and internal operation
Figure 2.7.1 employee record activity diagram
Figure 2.7.2 item price record activity diagram
Figure 2.7.3 comment view activity diagram
Figure 2.7.4 viewer activity diagram
2.8 Class Diagram
Class diagrams are visual representations of the static structure and composition of a particular
System using the conventions set by the Unified Modeling Language (UML). Out of all the
types it is one of the most used ones. System designers use class diagrams as a way of
simplifying how objects in a system interact with each other. Using class diagrams, it is easier to
describe all the classes, packages, and interfaces that constitute a system and how these
components are interrelated. Classes in class diagrams are represented by boxes that are
partitioned into three:
1. The top partition contains the name of the class.
2. The middle part contains the class’s attributes.
3. The bottom partition shows the possible operations that are associated with the class
purpose of the class diagram can be :
Analysis and design of the static view of an application.
Describe responsibilities of a system.
Base for component and deployment diagrams.
Forward and reverse engineering
The following is the class Diagram.
ADMIN
ID:intname:charsex:charage:int
status:charphone:number email:email
login()addemp()
updateemp()view comment()
EMPLOYEE
id:intname:charsex:charage:int
phone:number email:email
login()record item()
send comment()
VIWER
id:intname:char
age:intphone:number email:email
view()send comment()
1.*
Class Diagram
1.*
1.*
1
Figure 2.8.1 online market price record system class diagram
CHPTER TREE SYSTEM DESIGN
3.1 Design goals
The design goals are derived from the nonfunctional requirements. Design goals guide the decisions to be made by users especially when trade-offs are needed. I divide the system into manageable pieces to deal with complexity Each subsystem is assigned to develop independently.
3.1.1 Performance criteria
Modifiability
The system is easily modifiable when Debre Markos tade and transportation office has willingness
to` change the existing manual system of item price recording system.
Portability
The system is portable from window plat form in to other plat forms easily. I.e. the system
primarily designed to be used in many plat forms. Since the system is designed using php it is
portable in many modern windows.
3.1.2. Maintenance criteriaThe system should be easily extensible to modify the office real working criteria, add new functionality, portable to different platforms. The code for the system should be easily readable, understandable and should be easily mapped to specific requirements.
3.1.3 End user criteriaThe system requires users should have a little knowledge and experience on
internet usage. Since the system is designed with php it is easily adaptable.
3.1.4 Reliability criteria The system is reliable for effectively record and view the daily market price
record in Debre Markos town. Anyone who wants the daily market price is
being able know the daily price. Through this he/she is able to distinguish
cheap and expensive items and total supply in the market
3.1.5 Security criteriaThe system provides privileges to authorized user by giving account (user name and password to
log in to the system). Without the proper user name and password no one cant upload daily
market price to the system.
3.2. System ArchitectureSystem architecture provides an integrated view a design rationale for functionality, usability, and
aesthetics. Understanding the architectural needs of a system requires that designers, developers and
end-users effectively communicate and collaborate with each other about the intended goals of the
system. This is why all such projects must optimally begin with a Requirements document that clearly
defines the intended system processes, functionality, interface, and benefits.
Fig 3.1 system architecture
3.2.2 Communication interfaceCommunication interface describes the attractiveness of the interface that creates
an image for the end user. Since I used html to construct the form it is attractive
for end users.
3.3 Sub system decompositionSub system decomposition describes dividing the whole system in smaller
manageable units according to their manageable criteria. I divide the system in to
different components described below.
Item recording
This component is used to record the daily items and their corresponding price.
Employees of the office are responsible for this activity.
Employee Record System
This component is used to record additional employee in to the organization when
needed. Addminstrator of the office is responsible for this burden.
Item price view
This component is to view the daily market price. Customers can view the daily
market price.
3.4 Component Diagram In this Diagram components of the system will be wired showing that there is relation
among components, management of the system, database and operations performed on
databases such security issue.
This in some extent shows which component or objects will be accessed by whom and
what type of security infrastructures it is using.
The diagram is simulated below
Market price Record System
Manager
Employee
Viewer
Market price Record System
Database
Fig 3.2 component diagram
3.6. Deployment modeling
Fig3.3 deployment modeling
3.5 Database design
The physical database management looks like the following
3. 6 User screen shouts
Employee login form
Price Record form
Chapter four
4.1 Conclusion and RecommendationsSince we are found in the world that everything is within information, the usefulness
of online market price viewing is not questionable.
ConclusionIn the previous our ancestors pass a season which seems like dark. After the
completion of the system it possible to conclude online market price recording and
viewing is possible. If this system is effectively used within the society it speeds up
the activities in the market and effective exchange of goods will save our time and
energy. Since within information everything is possible, if this system is
implemented Debre Markos and its surrounding will become in progress.
If the limitations are reduced it is possible to have effective communication and the
society will satisfy by the system.
RecommendationsI would like to recommend about this system, that the system is usable if it is
distributable to the society. If the system is distributed within our computers as well
as in our mobile we can get the daily market price and their price effectively in
Debre Markos town. Therefore, using the system effectively is the way to progress.
4.2 Future EnhancementsThis system will become better if it is not limited in Debre Markos town. If this
system is includes the whole towns in Ethiopia buyers and sellers can compare
items and their price from one town to the other. Therefore in the future including
the rest tows in Ethiopia is highly recommended.
4.3 References
To implement this system I used different resources described below.
Internet: To drive different php codes and validations
Employees Manual: I used their manual to start the real system
implementation.
My advisor helped me what measures will be taken by advising me including
or excluding things.
Workers of the office: Workers recommend me what is currently running in
the real situating.
My friends: My fiends help by recommending the way what will better for the
system.
Debre Markos website: I used this website to get differ images about the
marketing system in Debre Markos.
