Project Description

Problem Statement

Facility Maintenance ’Sub-optimal facility maintenance

Management System ’Lost/damaged items went unnoticed.
’Difficulty in procurement of equipment.
’Under-depreciated equipment value.
’Poorly-maintained equipment leading to lower
Jeremias Tanamal
Yudha Sanyoto use-life expectancy.
L. Didi Andrianto
A. Sasmito Adibowo
Moh Aditya MH

Project Description Project Description

Proposed Solution Additional Benefits

’Computerized information system targeted for
facility management
’For use by janitors, students, staffs, and
managers
’To be sold as a commercial product
’Identification and aggregation of skilled people
that work within the university.
’Better brand recognition of the university in the
field of computerized information systems.
’Financial benefits obtained from the system's
licensing and training services.

Project Stakeholders Project Stakeholders

Project Sponsors Resource Providers

’University of Indonesia's Rectorate ’Faculty of Computer Science

’Quality for Undergraduate Education ’Faculty of Engineering
’Indonesian Directorate of High Education ’Faculty of Psychology
’Faculty of Economics
 Project Stakeholders Project Team
Candidate Users
’Project Manager
’Maintenance Staff ’Technical Writer
’Administrative Staff ’System Analyst
’Management Staff ’System Architect
’Students ’Programmers
’Testers
’Trainers

Project Schedule Project Schedule

Gannt Overview Milestones

ID
1
Task Name
Meetings
March
02-03 30-03
May
27-04 25-05
July
22-06 20-07
September November January March
17-08 14-09 12-10 09-11 07-12 04-01 01-02 29-02 28-03
May
25-04 23-05
July
20-06
18-07
27-02
’Start: April 21, 2003
14 Product Documentation
19
24
32
Requirements
Training/Orientation
Preliminary Design/Prototyping
’Final Requirements Document: August 8, 2003
’Final Design Document: October 17, 2003
35 Detailed Design
42 Construction
50 Change Management
54 Deployment

’Code Complete: February 26, 2004

57 Closeout
61 Project Complete 22-06

’Team Certification: June 16, 2003

’Final Product Documentation: March 18, 2004
’Project Complete: June 22, 2004

Quality Plan Quality Plan

Policies Quality Assurance

’Properly documented system architecture. ’Ensure that the programmers properly document their
code.
’Properly documented source code - hypertext
document with detailed descriptions for all classes, ’Ensure a System Description document exists and easily
properties, and methods. understandable.
’Properly documented database schema. ’Ensure the requirements specifications are complete
and concise.
’The system will be user-friendly.
’Ensure the database design is properly documented.
’The user's manual will be separated into several parts:
tutorial, reference, and system administration. ’Performs user test often.
’Reviews the manuscripts for the user manuals.
 Communication Plan Communication Plan
Project Sponsor Project Manager
’Message/Information Need
’ Project Manager must receive input from Project Team members about
’Message/Information Need the progress of the project. He also needs information from internal and
’ Project sponsor needs infornation from project manager about external stakeholders about their information and communications
requirements, determine the best and most cost effective way in which
project documents and also about progress report. the requirements can be met, and record the information in a formal,
’Delivery Vehicle approved document.
’ By Courier ’Delivery Vehicle
’ By courier and meeting
’Frequency
’Frequency
’ Weekly
’ Weekly
’Feedback ’Feedback
’ Provide other stakeholder about what other stakeholder need ’ Communicate with other stakeholder and coordinate with project team
member

Communication Plan Communication Plan

Project Team Member Other Stakeholders
’Message/Information Need
’Message/Information Need ’ Needs information especially on project progress
’ Project Team Member needs the detailed task from Project report, and other informations
manager and material from other stakeholder
’Delivery Vehicle ’Delivery Vehicle
’ By meeting ’ By meeting and Courier
’Frequency ’Frequency
’ Weekly ’ Weekly
’Feedback
’ Provide information to project manager and other stakeholder ’Feedback
about the progress has been made. ’ Provide data and other informations to other
stakeholder

Risk Identifications Risk Identifications

’ImpactEstimated size of project in LOC or FP
’Lack of needed specialization increases defects
and reworks
’Unfamiliar areas of the product take more time
than expected to design and implement
’Does the environment make use of a database
’Components developed separately cannot be
integrated easily, requiring redesign
’Development of the wrong software functions
requires redesign and implementation
’Development of extra software functions that
are not needed
’Strict requirements for compatibility with
existing system require more testing, design, and
implementation than expected
 Risk Identifications Thank You

’Operation in unfamiliar software environment Any Questions?

causes unforeseen problems
’Team members do not work well together
’Key personnel are available only part-time