Académique Documents
Professionnel Documents
Culture Documents
PREPARED BY: CHERE LEMMA ESKINDIR DEMELASH MERON TESHOME ZEMENU AGUMAS ZERIHUN TADESSE RCS 015/08 RCS 021/08 RCS 034/08 RCS 052/08 RCS 054/08
PROGRAM OF COMPUTER SCIENCE SCHOOL OF MATHEMATICAL AND COMPUTER SCIENCE DILLA UNIVERSITY
1. Introduction
1.1 Background Dilla University is one of governmental higher educational institute in Ethiopia.
Property Administration is one part of DU which has the mission of properly managing and controlling every property of the University to facilitate the education process run inside the University. It was established in October 28, 1989E.C. Even though there was a gradual change from time to time, until now there are problems and still the system almost all runs manually and partially use Microsoft Access. As result, it is slow and prone to errors.
1.6 Methodology
1.6.1 Data gathering techniques An interview : We use this technique to allow the informants to respond in any manner and the interviewers to observe verbal and non-verbal behavior of the respondents. Observation : we conducted physical observation to see how data are handled and information of property kept in the system. Secondary document analysis technique to review various documents. 1.6.2 Design Methodology Object oriented approach
1.6.3 Implementation Methodology A) Hard ware: Desktop computer with 500MB RAM and above as well as 80GB Hard Disk Device and above to install different software we use to develop the system. Network cable, CD and Flash disk to take backup B) Software: Front end: - VB.Net 2008 Back end: - SQL server 2002 Documentation: Adobe Photoshop, Star UML, MS office 2007
B) Integration testing we use this testing method to verify the interfaces between components against a software design.
C) System testing This another technique we use by completely integrating the system to verify that to ensure if it meets its requirements. Alpha testing: is simulated by the developer of the system Beta testing: is stimulated by clients
10
2.1.2 Problem of Existing System Security Problem Time wastage Manpower Balancing Problems Lack of Immediate data retrieval Lack of immediate updating of record about the property
12
2.1.3 Weakness and strength A) Weakness: There is no available organized document that shows work flow of the system Security problem Work load and time consumption Less satisfaction of users by the service they get B) Strength: To make auditing easy, they use Bin card Give receipt for customer when issuing goods and return goods after usage Cross check request of user with their proposal Use decentralized management system for controlling and ensuring the proper uses of the properties
13
2.1.4 Business Rule Every goods/properties of the University must be registered If the head of department allows and signs, any staff member has the right to withdraw Non-exhaustive goods. Only head of department or secretary have the right to withdraw exhaustive goods. If user loses the property he/she pay based on duration of service of the goods When properties are loaned if the borrowed bodies do not return the goods within specified date they shall penalized 50 Birr per day. When user leaves the University he/she shall return any Non-Exhaustive goods
14
Recording proposal Registration of inflow goods, outflow goods and user Checking availability of goods in the store Calculating balance of inflow and outflow of goods Searching , Updating and deleting records when necessary Generating report when necessary Controlling return date of loaned and expiration date of exhaustive goods and alarming Enable the Head (Administrator) to know activities of Recorder on daily basis Restrict unauthorized person from accessing the system
15
2.2.2 Non-Functional Requirement User Interface Timeliness: The software helps to give timely information for the user. Error Handling: Security issues Quality Issues System Modifications Resources Management Issues 1. Backups: It should be undertaken on a daily basis 2. System Installation: Project team will be responsible for the installation 3. System Maintenance: System administrator will be responsible for this task
16
2.2.3 Systems Requirement 1) Hard ware requirement Processor: - with speed of greater than 3.0GHz 1GB RAM and above 150GB Hard Disk Device (HDD) and above to for data storage Printer 2) Software requirement Operating system: - Windows XP/2000 and any higher version Microsoft SQL server 2005:- for data base storage
17
18
3.2 Assumptions It is assumed that compatible computers will be available before the system is installed. It is assumed that the DUPA will have enough trained staff to take care of the system The users have sufficient knowledge of computers. The users know the English language, as the user interface will be provided in English The product can access the university purchase system database
19
4. System Modeling
4.1 Use case Diagram
System
Returned goods Registiration Non-Exhaustive goods
<<extend>>
Purchased goods Registiration
<<extend>>
Exhaustive goods
<<extend>> <<extend>>
Inflow goods Registiration Donated goods Registiration
<<include>>
Recording Proposal Borrowed goods Registiration
Organization
<<include>>
Login Loaned goods Registiration Recorder Update record
<<include>>
<<include>>
<<include>>
Inservice goods Registiration
<<include>> Auditor
Employee
User registration
Cleanrance Employee
<<include>>
Search Recorder
<<include>>
<<include>>
Report generat ion
Login
<<include>>
View Notification
<<include>> <<include>>
User account
Head
Login btn
Login control
Main window
submit() create()
submitted() validate()
x
View()
X
create()
22
x
fill() submit() submitted()
view()
23
Message
click()
create()
create() select()
selected() create()
x
fill() submit()
X x
24
: Head : Recorder
Sreach Button
Search control
Search form
Table : Record
Record
x
submitted()
X
Validate() fetchrecord() dispaly() view()
X X
25
view()
26
: Head
Notification Button
Notification control
Database
Notification
x
dispaly()
view()
print()
X
27
RECORDER +1 Register 1..* +getCreate() +getChange() +getRemov e() GOODS +Item Name: String +Serial: String +Item Rank: String +Item Description: String +Balance: Integer +Unit Price: Double +Total Price: Double +Measurement: String +Quantity: Integer +getRegister() +getUpdate() +getSearch() +getDelete() +Calculate_balance() PURCHASED NON EXHAUSTIVE GOODS PURCHASED INFLOW EXHAUASTIVE GOODS +Expeired Date: Date
cross check
1..*
PROPOSAL +Department name: string +Item Name: string +Item Type: string +Quantity: Integer 1..* +Balance: Integer +Acadamic Year: Integer +Calculate_ balance() +getRecord() +getSearch() +getDelete() +getUpdate() OUT FLOW GOODS +Date Out: Date +Quantity out: Integer
Record
OUTFLOW NON EXHAUASTIVE GOODS +ID No.: String +Remark: String +Serv ice duration: Integer
OUTFLOW EXHUASTIVE GOODS INFLOW GOODS 1..* +Date in: Date +Quantity in: Integer
Withdraw +1 INSERVICE GOODS 1..* Withdraw +1 USER(EMPLOYEE) +User Name: String +User ID: String RETURNED GOODS +Position: String +Departement: String +ID No.: String +1 Return +Address: String +Remark: String 1..* +Serv ice Duration: String +Goods ID: String +Education Lev el: String +getRegister() +getSearch() +getDelete() 1..* Loan Donate DONATED GOODS +Experied Date: Date 1..*
1..* Borrow +1 ORGANIZATION +Organization +Organization +Organization +Organization Name: String Type: String Address: String +1 location: string
+1
28
5. System Design
5.1 Design Goal The following goals were kept in mind while designing the system: Make system user-friendly Security Performance (Response Times) Usability (Human Factor) Reliability (Frequency of Failure) Timeliness Reducing error System Modifications
29
Record
Application
<<Subsystem>>
Database Subsystem
User Interface
Administiration
Application
Database
Record Edition
Information
31
Pk
Goods IdNo Item description Item category Item rank Measurement unit Quantity in Total quantity in Date in Durability Balance Remark
32
Donated goods Fk Organization name Date in Item description Item category Measurement unit Unit price Total price
Organization pk Organization name Organization type Location User Id User name Department Position Sex
Loaned goods pk good IdNo Fk Organization name Item description Item category Measurement unit Quantity out Date out Unit price Total price In-service goods Pk ID No(serial) Fk User ID Item description Item category Measurement unit Quantity out Date out Status Pre-service duration Unit price Total price
33
Borrowed goods
pk Fk good IdNo Organization name Item description Item category Measurement unit Quantity out Date out Unit price Total price
Address Outflow exhaustive goods Fk User ID Item description pk Item category Measurement unit Quantity out Total quantity out Date out Unit price Status Pre-service duration Total price
User user ID User name Department Education level Position Sex Address
Auditor
View()
View()
5.6 User Interface Design Login window Proposal record window Exhaustive inflow goods registration window Exhaustive outflow goods registration window Non-exhaustive inflow goods registration window This includes purchased goods , Returned goods, Borrowed goods and Donated goods registration window Non-exhaustive outflow goods registration window This includes Loaned goods and Inservice goods registration window User Administration window Search window Delete window Update window
35
THANK YOU!!!!!
36