Debre Markos University Burie Campus Department of Computer Science Group-5
Debre Markos University Burie Campus Department of Computer Science Group-5
Debre Markos University Burie Campus Department of Computer Science Group-5
BURIE CAMPUS
GROUP-5
PROJECT ON
1.6.2.Technical feasibility…………………………………………………………………………………………………………………………5
1.6.3.Economic feasibility………………………………………………………………………………………………………………….……6
1.6.4.Political feasibility…………………………………………………………………………………………………………………….……6
1.6.5.Sechedule feasibility…………………………………………………………………………………………………………………….…7
1.11. Reference…………………………………………………………………………………………………………………………………….12
2.2.
_
Paper 1 packet
Total ----- 0
Pen 6
Mobile card 20
Flash 2
Computer 1
1.7. Scope of the project
Software Tools
MS word Free
The proposed system includes the following
E-draw max, Visual Free
features for the cost sharing management
Paradigm and
system.
Microsoft Visio.
Apache Free
MYSQL server 2012 Free Manage cost share status
Total cost
students and employees. This means, increase number of customer and lose of paper
because they use manual system.
anywhere and anytime students are
authorized to use this system effectively
1.10. Methodology
through internet accesses. This system is
The methods that facilitate us to capture
expected to bring remarkable change on cost
information about requested system is called
sharing management system. Thus, it will
Methodology. Starting from proposed
document the student information in an
system we gathered information and data
organized manner. Among this main
through different mechanisms.
significance some of them are listed below:-
Minimize errors 1.10.1. Fact-finding techniques
To develop online cost sharing management
Eliminate paper based recording
system the primary task is collecting
Reduce resource wastage
required data from different sources to
Easy to use the system
perform further tasks. The data will be
Minimize work load
gathered by using the following techniques:-
The system can be accessed by multiple
users concurrently Primary data sources:-
Students:-gets fast access to see what Interview: -The other method we have used
types of goods they want.
to get information about the general view of
the system is by interviewing employee of
Manager: - System reduces time
wastage and work load. cost share office and some students. It is fact
finding technique where by the system
Campus: - Provide more effective analyst collects information from individual
system and reduce need of man power,
face to face interaction. It gives us an
Increased reusability
How to process the current system?
Users usually understand the objects
Document analysis:-we also collected
easily
certain relevant information from written
It highly reduces the interaction gap
documents in the cost share office. Not only
between the reality and models
that but also we tried to review other
Object oriented system analysis and
relevant documents to develop our project
design methodology is more user
proposal.
friendly
Secondary data source:- Tackle more challenging problems
Software tools:-
Edraw max:- for UML modeling and Fig 1.1.Required Resources and Cost
diagram
Notepad++:- to write implementation or
code
Microsoft word 2007 for documentation
Microsoft power point 2007 for
presentation
Apache: web server
MYSQL-database:-for storing data in the
database.
PHP engine :-for running PHP scripts
Web browser :-to run our program or
code from the server side
Hard ware tools:-
Personal computer
Flash disk(8GB)
Hard disk(500GB)
Paper and pen
Printer
Scanner
resources amount
pen 1
Single paper 50
Caling 10 times
Total cost
1.11.Reference
As the system is manual there are different
1. The Elements of UML Style, Scott drawbacks among those:-
W. Ambler Ronin International,
Cambridg university.2003 Poor way of data handling
2. FDRE (Federal Democratic Republic Resource wastages like time, paper, pen,
of Ethiopia). (2003b). Council of and labor
Ministers Higher Education Cost Data Redundancy and Inconsistence
sharing Regulations No. 91/2003, Problem.
Negarit Gazette, Addis Ababa.
3. Use case: -Users of Existing System
https://en.wikipedia.org/wiki/Use_ca
To provide job opportunity for
se last retrieved on Dec, 23, 2016.
many employees
Non-functional requirements describe how the system works, while functional requirements
describe what the system should do. They specify criteria that judge the operation of system
qualities to capture the required properties of the system. Then the team is going to develop its
own non-functional requirements, such as:-
Security: Security is major problem now a day. People’s knowledge and ability to bypass
security measures is also one constraint to build more secured systems. Besides the usual
authorization and authentication (deals with identifying a user and what a user is allowed to do
respectively) such as username and passwords. The new cost sharing management system
considers these security risks.
Performance: The response time that the system uses to process, query and retrieve cost sharing
data and information from database is very short. That means it takes short response time for a
given piece of work. The designed system will use low utilization of system resource in terms of
space and time. Many tasks can be performed on the same time that in turns provide time and
cost effective services.
Usability: The online cost sharing management system is simple to understand, easy to use and
user friendly because it making questioners in native language.
Modification/ maintainability
Through time there should be changes in when the user needs another additional functionalities
and new features, when the cost share administrator identifies the system need to be modified,
while the cost share system work style is changed and depending on different reasons. This can
be easily done because the whole system development tasks divided into several smaller work
parts. Since the system was modularized not the whole system should be maintained rather only
the specific modules that need modification will be modified and maintained. Some of the user
interface and basic modification can be performed by the collection of developers but the system
developers are the right persons to update the system.
Graphical user interface: The system we are going to develop will have a user friendly
graphical user interface (GUI) which allows users to interact with the system easily. The user is
expected to have knowledge of using device and also navigating through this device interfaces.
Error handling: - When a user interacts with the system errors may occur. To control this kind
of inaccuracies system will generate different user friendly messages. To do this, most of the
system execution buttons will be controlled according to the sequence which the user is expected
to follow, or this can be done by generating different system responses to the input of the user.
BR2: Every student should fill cost sharing for his/her partial cost of education, dormitory, and
meal services once per year.
BR3: When students transfer from one university to other university, they expected to fill cost
sharing for total year stayed even one semester fill half annual cost sharing.
BR4: When students dismissed from the university by academic, discipline, other cases; he/she
doesn’t expected to fill cost sharing at that year.
BR5: Any beneficiary student who completes his education shall be given a document stating the
amount owed in cost sharing.
BR6: Every graduate student should fill cost sharing for all years unless he/she can’t get
Temporary degree.
BR7: Every alumnus person to finish the payment he/she get the official transcript otherwise
he/she can’t get.
It describes the interaction between the user and system in a more detailed way than an essential
use case. There are four actors in the current proposed system those are:-
Student
Cost sharing officer
Registrar officer
Inland Revenue officer
Create <<use>>
Upload Student
Account
List
Regist
Enable/Disable rar
Account Update Office
Manage Cost
Account r
Register
Cost
Login View Cost
Cost <<use>> Sahre
Sharin Update Cost
g Offi View
cer
FeedBack Fill Cost
Share
<<use>>
Stude
nt
Student List Send
Feedback
<<use>>
Cost Share
Manage Inland
Print Payment Reven
ue
Office
<<use>>
Post Notice r
View Update
Payment Payment Register
Payer
Print
Name Login
Use case id UC01
Brief description When the user enter user name, password and select user type, it
checks the input from database, if it is valid the user can access, if not
it displays error message.
Actors Cost sharing officer, student, Inland revenue officer, and registrar
officer
Pre condition User must be authorized user who has username and password
Post condition The user is authenticated and the system displays all features available
for the role for the user is associated.
Basic flow of events User action System response
1. The student, cost sharing officer, 2. The system display login
Inland revenue officer, and registrar form
officers are want to login to the system. 4. The system verifies that
3. The cost sharing officer, student, all the filled have been
inland revenue officer and registrar filled out and valid.
officer Enter user name ,password and 5. The system successfully
select user type then request to login logged in.
6. Use case ends.
Alternate Flow of events
Title Description
A. the user fill invalid 1. The system display message “invalid username or password or
data user type”
2. The system prompts the user to reenter the valid information
3. Use case continues with step 2
Actor(s) Student
Pre condition student wants to fill cost share agreement form
Post condition Store the agreement into database
Basic flow of events User actions System response
1.Students want to fill agreement of cost 2. the system displays the
sharing form
3. Student fills all necessary information to 6. The system make sure
the form such as all inputs are filled (check
3.1 date of withdrawal(date, month, year, the input is valid or not)
semester) 7. The system saves the
3. 2.transfered from other university(name, input data and the
college, department) following information
3.2.1 date of transfer(date, semester) 7.1 year, price for(food,
3.2.2 total cost before coming dormitory, education,
3.3.type of service you choice total) Into DB
3.3.1.In kind(food only, boarding only, 8. The system display”
food and boarding) fill successfully” message
3.3.2.In cash(food only, boarding only, 9. Use case ends
food and boarding)
3.5 If the student is graduate class he/she
fill in addition to the above
3.6. duration of year
4. choose photo if any
5. student press submit button after filling
the form
Include:- 1. the registrar officer want to upload 2. the system display the form
New student list student information 5. The system automatically
Graduate student list 3. A. the registrar officer upload the creates account for each
new student file from excel that include student’s that have not an
3.1. Full name, id, sex account before. using(id as a
3.2. Region, woreda, phone number user name& mother first name
3.3. University name, faculty, year of as a password)
entrance, department, academic year 5.1 the system also updates
3.4 Mother adopters (full name, phone his previous information if it
number) is different
3. B. the registrar officer upload the 6.the system save information
Graduate student file from excel that into database
include( id, full name , faculty,
7. the system display
department, graduation year , total cost
“Successfully upload”
expense)
message.
4.the registrar request to upload
8.use case ends
Title Description
A. The user 1 the system display invalid entry message
select invalid 2 The system prompts to re-enter the valid data
login login
home page DB
<<UI>> <<controller>>
user
open
click login()
chick validity
invalid
valid
display message
SD for update
cost share cost
sharing
officer open
fill information
update()
check validity
invalid
record data
updated
open
access form
fill information
click fill()
check validity
invalid
confirm and record
data
successfully filled
write comment
click send()
check validity
if it is empty
sent successfully
fill information
update()
check validity
invalid
updated
login
<<UI>>
yes login
initiate login is valid
successfully
fill information
yes
initiate send is valid store to DB
send
feedback
<<UI>>
fill information
yes
initiate send is valid store to DB
update payment
expense
<<UI>>
fill information
no
yes
click update is valid store to DB
create
account
<<UI>
fill
information
no
yes
click create is valid store to DB
Post
* 1 * *
*
Person FeedBack Account Notice
*
+Id:String -Id:int -NoticeNumber:String
-Full Name:String +Email:String +Create() -Date:date
-User Name:String -Date:date +View() -Body:String
1
-password:String +Update() * -Sender Name:String
-Sex:String +Send()
+Disable/Enable() +Post()
-Phone:int +View()
1 +View()
*
View
1
1
1 Registrar Officer
1 Payment
Inland Revenue officer
-Id:String
1 +TIN Number:String
*
Manage -Date:date
+Register()
+Update() +UploadStudentFile()
+View()
+Print()
Fig 2