The document presents information on a proposed zoo information system, including: 1) A chart comparing tasks, effort, duration, and dependencies for the project. 2) Estimates that the lines of source code will be around 285,636 based on estimates of effort. 3) Ten requirements for the system, including allowing different user types to perform certain actions. 4) Three use cases for new employees, new animals, and special ticket purchases. 5) Details on code design including getters/setters and hidden manager menus. 6) A sample test case for adding a new employee.

1. 1
Zoo Information System Presentation
Milton G. Zalduondo

2. 2
2
Chart Comparison
Table vs Bar Chart
2
TASK EFFORT DURATIO
N
DEPENDENCI
ES
T1(Requirement Gathering) 15 10
T2(General Planning) 8 15
T3(Database Design) 20 20 T2(M1)
T4(Internal Site Design) 5 15 T3(M2)
T5(Customer Site Backend Design) 5 10 T2(M1)
T6(Customer Site Frontend
Design)
10 10 T5(M3)
T7(Development Phase 1) 75 25 T2,T4(M4)
T8(Review) 10 10 T7(M5)
T9(Development Phase 2) 50 25 T5,T6(M6)
T10(Review) 10 10 T9(M7)
T11(Testing) 20 15 T7,T9(M8)
T12(Revisions) 10 10 T11(M9)
T13(Deployment) 10 7 T7,T9(M10)

3. 3
3
Lines of Source Code
Effort = A x Size ^ B x M
A (Constant factor of local organizational practices) = 2.94
Size (code assessment) = 4,000
B (Complexity) = 1.15
M (Attribute factor) = 7
SLOC = 285,636
3

4. 4
Requirements Part 1
• 1. The system shall allow only managers to add new employees
• 2. The system shall allow only managers to delete animals from the
database
• 3. The system shall allow employees to only add new animals
• 4. The system shall allow customers to purchase tickets
• 5. The system shall only allow managers to change the price on tickets

5. 5
5
Requirements Part 2
• 6. The system shall allow managers to log in to a separate menu with an
appropriate code
• 7. The system shall require animals to be entered with all parameters
(name, id, etc.)
• 8. The system shall allow anyone to logout at any time
• 9. The system shall allow customers to pay online or at the booth
• 10. The system shall allow the manager to decide certain privileges in the
system for different employees

6. 6
Use Cases
New Employee
Once an employee, their info
needs to be entered to the
system to print their badge.
New Animal
Will work similar to adding a new
employee. Object can be
extended to disable animal
entries if the animal is transferred
(happens frequently in zoos).
Special Purchase Event
The Manager can create
discounted tickets for the
ticketing system as well tickets
for special events.

7. 7
Code Design
Setters and Getters
Getter used for logging in conjunction with searching through the employee/customer/animal arrays. Only one setter for
Manager Price Change
Hidden Manager Menu
Taken from Walgreens register keypad codes.

8. 8
8
Zoo_2 Test Case
Pre-conditions: Employee must be added to the
database in order to test
Dependencies: Zoo_1 must be completed (adding
a new employee)
8
Post-conditions:
The system alerted the employee that only
managers can delete managers however provides
the ability for managers to enter the correct key
code
Step Test Steps Test Data
Expected
Result
Actual Result Status
(Pass/Fail)
Notes
1 Employee logs in Emp id no. (123)
Employee is logged
in
Employee is logged
in
Pass There is
no
password
functionalit
y
2
Employee deletes
animal Option 3 (delete)
System alerts
employee
System prompts
“enter key code”
Fail
3
Employee enters
wrong key code 8008
System alerts
employee
System alerts
employee
Pass

9. 9
THANK YOU