Article Reviews

Hostel: Rational Unified Process Essay

Posted on

A project proposal submitted in partial fulfillment for the requirements of the degree of Bachelors of Science in information Technology.

Information Technology Department
Jomo Kenyatta University of Agriculture and Technology

OCTOBER 2013

Supervisor: Name …………………………………………………………………. Signature ……………………. Submission Date ……………………

Table of Contents

1.0 INTRODUCTION
1.1 Background Information
Jomo Kenyatta University of Agriculture and Technology (JKUAT) is situated in Juja, along the Nairobi-Thika Super Highway. It was started in 1981 as a Middle Level College by the Government of Kenya with the generous assistance from the Japanese Government. It was established as a University through the Education Act, 1994 and inaugurated on 7th December 1994. JKUAT started enrolling students that same year and its population has risen to over 50000 throughout the years. The institution consists of many departments where students put much of their effort in school work so as to improve their livelihood in the future. The university also has a house of resident where the students reside but its limited to only the JAB students while other students locate houses outside the institution.

1.2 Problem statement
The university offers housing facilities inside its grounds but they are inadequate to fit the growing number of students forcing some to seek accommodation outside its grounds. JKUAT currently lacks a system to aid such students. The burden of acquiring hostels outside its grounds is thus solely placed on the students. This burden comes with certain difficulties such as walking, knocking doors or making phone calls to locate these hostels and in most cases it involves a wider geographical coverage. This traditional approach is not only tiresome and time consuming but also poses a probability of two or more students booking the same unit as man is to error and it is a manual system. This gives rise to concurrency anomalies. Concurrency is the ability of a system to allow multiple users affect multiple transactions. The main job of concurrency control is to protect transactions issued by different users from the effects of each other. In this instance it is to avoid booking of the same unit by more than one student.

1.3 Proposed Solution

To address the problem stated above I propose an online based real estate project specifically formulated to host hostels available around the university’s environs. The proposed system will offer a form of virtual tour to its users enabling them to easily access and identify hostels suiting their preferred needs without the need of physically moving around the geographical area which can prove to be quite tedious. The user will access the system and input their specifications (a bedsitter, a 1 or 2 bedroomed apartment, singles or doubles, near gate A, B or C, the rent range) and the system will automatically select the hostel suiting the qualifications and also indicate the number of units available for renting. Once payment and booking has been made after selection, the system will constantly update itself to reduce cases of concurrency problems. The main goal of this system is to prevent database updates performed by one user from interfering with database retrievals and updates performed by another. This proposed solution will benefit the student in that it will; Reduce confusion of first time visitors who do not know the area. Booking of
hostels even when not physically present in Juja. Easy data retrieval about hostels.

Improved communication between possible tenants and caretakers. Protect multiple students from booking the same unit.

1.4 Objectives

To carry out research on concurrency control systems.
To collect user requirements for the proposed system.
To documented the system at each development stage.
To test the system to ensure it meets concurrency control requirements.

1.5 Research Questions

What are the concurrency control principles that are used in this hostel booking web application? What are the approaches used in developing concurrency control system? What are the methods and techniques used to achieve concurrency control in this system? What are the standards for implementing concurrency control in this hostel system?

1.6 Scope of the project

These are the expectations made so as to realise the completion of this proposed system. They describe the boundaries that have been set for the study. I look forward to develop a system that will make the process of touring & booking of hostels become simple, accessible, effective and efficient to all its users by giving them:

A variety of choices depending on their preferences, i.e. amount of money to pay, distance, security etc.

Constraints:
Population: My population target is only the students of JKUAT University. This is because targeting other institutions would be tedious and
unachievable because of the geographical coverage.

1.7 The problem Justification

Studies have shown tremendous growth in the use of Information and Telecommunication Technologies (ICT) in the developing countries. This is because businesses and consumers aim at carrying out their transactions with as minimal time as possible. In trying to use these technologies online shopping has become the norm. There are increased online stores, online booking and reservations of airline tickets and car services and the real estate sector is also advancing ahead with new technology. Due to the increasing number of students the system is appropriate because of its affordability as opposed to transport cost in visiting the area. It is also easier to use as it breaches geographical distance between the necessary parties and is applicable since majority of Kenyans now have easy access to the internet.

2.0 Methodology

This part involves the method that one uses in coming up with a system.It is the most crucial phase in the development of a system. The methodology that will be used to develop this system is the Rational Unified Process which enhances team productivity, by providing every team member with easy access to a knowledge base with guidelines, templates and tool mentors for all critical development activities. The Rational Unified Process activities create and maintain models. Rather than focusing on the production of large amount of paper documents, the Unified Process emphasizes the development and maintenance of models—semantically rich representations of the software system under development. The software lifecycle is broken into cycles, each cycle working on a new generation of the product. The Rational Unified Process divides one development cycle in four consecutive phases. Inception phase

During the inception phase, you establish the business case for the system and delimit the project scope. Elaboration Phase
The purpose of the elaboration phase is to analyze the problem domain, establish a sound architectural foundation, develop the project plan, and eliminate the highest risk elements of the project. In the elaboration phase, an executable architecture prototype is built in one or more iterations, depending on the scope, size, risk, and novelty of the project.

Construction Phase
During the construction phase, all remaining components and application features are developed and integrated into the product, and all features are thoroughly tested. The construction phase is, in one sense, a manufacturing process where emphasis is placed on managing resources and controlling operations to optimize costs, schedules and quality. Transition Phase

The purpose of the transition phase is to transit the software product to the user community. Once the product has been given to the end user, issues usually arise that require you to develop new releases, correct some problems, or finish the features that were postponed.

JUSTIFICATION OF METHODOLOGY
Rup is an object oriented language.
High level of reuse-The reuse of code is easy and faster.
It is highly beneficial since updates can be done at any stage of the development. Since it provide a specific plan for each step of the development process, it helps prevent resources from being wasted and reduces unexpected development process. Raining is readily available –The online version of RUP walks user through the process in a step by step tutorial manner.

3.0 Resource requirements

The following are the proposed hardware and software resources which will be used in the development of the proposed system. 3.1 Hardware

•2.0GHz processor speed or higher
•Pentium IV or higher
•80GB hard disk or more
•2GB RAM or higher
•Internet connection

3.2 Software

•Microsoft windows XP or a later version
•Visual studio 2012
•Net beans 6.8 java software
• Wamp Server application for hosting the website
• MySQL for Database creation and Manipulation
•Dreamweaver
•Ms Office

4.0 Budget and Budget Justification

Budget
This is a proposed estimate or budget for the system.
Item number
Item name
Number of Units
Cost per Unit(Ksh)
Total Cost
1
Computer(Laptop)
1
35000
35000
2
1GB Flash disc
2
800
1600
3
Cd’s
4
20
80
4
modem (Orange unlimited)

990
990
5
Antivirus software
1
1000
1000
6
Ms Office
1
3000
3000
7
Visual studio 2012
1
2000
2000
8
Ms windows 7 or 8
1
3500
3500
9
Digital Camera
2
3500
7000
10
Dreamweaver

1500
1500
11
Internet subscription
1 month
3000
3000

Total Cost(Kshs)
48670

Figure 1: project budget

5.0 Project Time Plan

5.1 Project Schedule
Task
Description
No of hours
Expected
Start date
Actual
Start date
Expected
End date
Actual
End date
deliverables
1
Preliminary
9

Project ideas
2
Proposal writing
30
23/09/2013
23/09/2013
04/10/2013
07/10/2013
proposal
3
Proposal presentation
1
08/10/2013

08/10/2013

Approved proposal
4
Research
90
10/10/2013

18/10/2013

5
Data collection

19/1/2014

23/1/2014

Requirement specification
7
Data Analysis
10
24/1/2014

25/1/2014

Requirement
8
Feasibility study
20
28/1/2014

30/1/2014

Requirement report
9
Literature Review
50
02/2/2014

17/2/2014

Document findings
10
System Design
50
18/2/2014

28/2/2014

System design specification
11
Implementation
40
01/3/2014

10/3/2014

12
Testing
30
11/3/2014

16/3/2014

Test report
13
Documentation
14
17/3/2014

24/3/2014

System documentation
14
Presentation
1
April

Figure 2: project schedule

5.2 Task Schedule (GANT CHART)

Sept 2013
Oct.
2013
Nov.
2013
Dec.
2013
Jan. 2014
Feb
2014
March
2014
April.
2014
Week Ending
4
11
18
25
1
8
15
22
29
6
13
20
27
3
10
17
24
31
7
14
21
28
5
12
19
26
2
9
16
23
30
7
14
21
28
Activity
No. of hours

A
6

B
10

C
30

D
5

E
15

F
2

KEY
Estimated Time A-Project identification B-Writing project proposal
C-Data collection/system development D-Testing Actual TimeE-Documentation F-Final project presentation

Figure 3: Time Schedule (Gantt chart)