DUYTAN UNIVERSITY
INTERNATIONAL SCHOOL
Project
Remote Smart Door Systems
(RSDoor System)
Business Case
Mentor:
Nhat Nguyen Minh
Team 10
Members:
HUAN DINH VAN
PHUOC DO HUU
TANG DOAN VAN
HOANG DOAN THI MINH
RSDoor
Use Case
[Version 2.0]
08
RSDoor
Business Case
[Version 3.0]
Team 10
RSDOOR
Business Case
Project ID: RSDOOR
Version: 2.0
assd
Code: RSDoor_BC_2.0
Feb 21th, 2012
[ D u y T a n University]
2012
2
RSDoor
Business Case
[Version 3.0]
Document Approvals: The following signatures are required for approval of this
document.
Executive Sponsor
[Nhat Nguyen Minh]
[nhatnam06@gmail.com]
Signature
[0905125143]
Date
Technology Sponsor
[Tuan Dinh Nguyen] [tuan_dn104@yahoo.com]
[0912258440]
Signature
Date
Project Manager
Huan Van Dinh
Signature
[dinhvanhuan5390@gmail.com]
[0906544253]
Date
Business Case
RSDoor
[Version 3.0]
Revision History
Revision Number
Revision Date
Summary of
Author
Changes
1.0
1/8/2011
Create 1, 2, 3
Huan D.V
2.0
10/8/2011
Modified 3,4,5
Huan D.V
3.0
21/2/2012
Modified 6,7
Tang D.V
3.0
22/2/2012
Modified 5,6,7
Hoang D.T. M
3.0
15/4/2012
Add 5, 7
Reference Documents
Document Name
Version
Author
Making a Business Case for
Template
William E. Conley
Template
Paul K. Hooper
University Projects
FREP Handheld Business
Case
Business Case Template
www.ProjectManagementDocs.com
RSDoor
Business Case
[Version 3.0]
Contents
1. Executive summary........................................................................................................ 1
1.1.
Purpose ................................................................................................................... 1
1.2.
Scope ...................................................................................................................... 1
1.3.
Anticipated outcomes............................................................................................. 1
1.4.
Measurable organizational value (mov): ............................................................... 2
1.5.
Justification: ........................................................................................................... 3
2. Current position ............................................................................................................. 3
3.
Future process ........................................................................................................ 4
3.1.
Process description ................................................................................................. 4
3.2.
Performance measures ........................................................................................... 4
3.3.
Proposed technology environment ......................................................................... 5
3.3.1. Methodology for technology selection .................................................................. 5
3.3.2. Proposed software .................................................................................................. 6
3.3.3. Proposed hardware ................................................................................................. 6
4. Expected risks ................................................................................................................ 7
4.1.
Change analysis: .................................................................................................... 8
5. Cost estimate .................................................................................................................. 8
6. Cost/benefit analysis: ................................................................................................... 11
7. Project schedule: .......................................................................................................... 12
7.1
Project milestones ................................................................................................. 12
7.2 Assumptions: ......................................................................................................... 13
7.3 Constraints............................................................................................................. 14
7.4 Dependencies: ....................................................................................................... 15
Business Case
RSDoor
[Version 3.0]
1. EXECUTIVE SUMMARY
1.1. Purpose
Building a system "controlled the door by mobile phone". Currently the
market has some functional systems but is simple and not common but
demand for products is a lot. So building a system "controlled the door by
mobile phone "with integrated many functions based on the basic functions
that are already on market are necessary and business capabilities is higher
than the old system.
1.2. Scope

Building a system with integrated additional functions based on the
functions availability of the old system on the market.

Initial products are sold in domestic market.
1.3. Anticipated outcomes

Provide information quickly and fully to the manager and the
shareholders to make timely decision.

The management and shareholders can view information about employee
or company’s situation at all times.
Page | 1
Business Case
RSDoor
[Version 3.0]
1.4. Measurable Organizational Value (MOV):
Criterion
Create
Hardware
And
Software
2800 USD
Buy
Hardware
and Create
Software
3000 USD
Financial
Initial Investment cost
Organizational
Alignment with
Strategic Objectives
Achieving likelihood
of project's MOV
Availability of skilled
team members
Maintainable
Time to Develop
Risk
9.0
9.0
9.0
9.0
8.0
6.0
4.0
5 month
2.0
6.0
3 month
3.0
Senior satisfaction
Shareholder
satisfaction
Increased market
share
10
10
10
10
6
8
6
8
Project
External
Total Score (Each bold
number will get into a
point total score)
Choose: Buy Hardware and Create Software
Page | 2
RSDoor
Business Case
[Version 3.0]
1.5. Justification:
Justification:
YES / NO Detail
Creating new products for the Yes
With the new system, the company
company.
will have more new products into
their production systems. This is
old product however integrates
new multiple.
Competition in the market.
Yes
The system is improved add more
functions so the competition is
very high.
Increase quality of service to
Yes
the company.
Save time and costs for
customers.
Can add the service after products
sold to customers.
Yes
The automated system will bring
convenient and reduce costs.
2. CURRENT POSITION
Currently, most used keys to open doors. A small number of remaining open
automatically by remote control, but this controller we must always take it too
inconvenient, and the cost are high and security is not high.
Page | 3
Business Case
RSDoor
[Version 3.0]
3. FUTURE PROCESS
3.1. Process description
o
The first time to use:
Users enter the number of Series (confidential) per product. The number
used to distinguish these series phone users with the others. Then enter the
user ID and Password. Users can set automatic login if they wish.
o
Open the door:
The phone uses open software RSDoor. The software will automatically
open the Bluetooth, and detection equipment controlled automatic doors. The
software displays the main interface; users select “Open." Software would
signal "open" to the control device of automatic doors and it will control the
door open.
o
Close the door:
The phone uses open software RSDoor. The software will automatically
open the Bluetooth, and detection equipment controlled automatic doors. The
software displays the main interface, users select "Close". Software would
signal "Close" to the control device of automatic doors and it will control the
door open.
3.2. Performance measures
Process/ Service Performance Measure
RSDoor system
Collect feedback of customer by two ways as direct and online.
Page | 4
Business Case
RSDoor
[Version 3.0]
3.3. Proposed technology environment
3.3.1. Methodology for Technology Selection
Options
Challenge
Vendors
Compare
Bluetooth
low security, can’t
Directly
connection
connect more than 10m
connected to
away
the gate so
fast and
convenient
Internet
priced, insecure, low
Internet
connection
security, error-prone
access should
be prone to
error, low
security
GSM
Expensive and
Telecommunications
Fast signals,
connection
complicated than going
companies such as
high security,
through
Viettel, Mobifone, Vina,
but cost and
telecommunications
Sphone, VNmobile,
complexity
companies.
Beeline
Page | 5
Business Case
RSDoor
[Version 3.0]
3.3.2. Proposed Software
Software
Description
RSDoor on
Software is written in Java functions automatically to connect
mobile phone
automatic door controllers and pure signal for opening and
closing. This software support for the operation system
Android 1.5 or high
RSDoor on
Signal processing requirements of mobile phones and
automatic door
commanded closed, open.
controller
3.3.3. Proposed Hardware
Hardware
Description
Automatic door controller
A GSM receiver circuit and a microprocessor to
process information.
Unit automatically opening
Electronic organ opening and closing function of
and closing and door
receiving commands from the controller
Mobile phone
Mobile phone supports Operation System
Android 1.5 or high
Page | 6
Business Case
RSDoor
[Version 3.0]
4. EXPECTED RISKS
RISK
RISK LEVEL
Low/Medium/
High
(L/M/H)
THE
PRIORIT
Y
(%)
Mitigation Strategy
- Plan clear, have a specific
Project Schedule
H
75%
schedule.
- Accurately estimate the
start and end time of project
Cost
H
80%
- Schedule clear, details and
accurate
- Selected information and
Information
documentary
M
40%
documentary is accurate.
- Information must be clear,
there are reliable sources
Knowledge of all
member in project
Workgroup
M
30%
L
20%
- Training and reality
practice
- Unity, working on
teamwork spirit.
- A meeting of all team
Communication
M
35%
members in order to sharing
experiences, learning
methods, work….
Page | 7
Business Case
RSDoor
[Version 3.0]
4.1. CHANGE ANALYSIS:
o Required software:
 RSDoor software on Smart phone
 C or Assembly for RSDoor on Automatic door controller
o Required hardware:

Smart phone Support Android OS 1.5 or higher.
 Setup electronic circuit connected GSM on the Automatic door
 Automatic door
5. COST ESTIMATE
Cost/ hour: 4$
Work
RSDoor Project Plan v1.0
RSDoor Project Plan v2.0
1. Preparation
1.1. Research Scrum Process
1.2. Requirements described
1.2.1. Gathering requirements
1.2.2. Analysis of requirements
1.3. Research on Hardware
1.4. Research on Software
Hours
504
460
180
24
32
16
16
32
32
Cost ($)
2016
1672
720
96
128
64
64
128
128
1.4.1. Research on programming
Microcontrollers
16
64
1.4.2.
Mobile
16
64
4
4
52
6
16
16
208
24
Research Android & Window
1.5. Determine Hardware
1.6. Determine Software
1.7. Planning
1.7.1. Project Management
Page | 8
RSDoor
Business Case
[Version 3.0]
1.7.1.1.
Project Scope/High Level
Requirements
2
8
1.7.1.2.
Update Project Plans
1.7.1.3.
Commit Decision
1.7.2. Release Planning
1.7.2.1.
Establish work priorities
1.7.2.2.
Release Planning Baseline
1.7.2.3.
Release Planning Session
1.7.2.4.
Deliverables
2
2
46
4
2
2
4
8
8
184
16
8
8
16
1.7.2.5.
Structure
4
16
6
4
20
178
4
2
2
16
24
16
4
4
120
14
2
8
4
0
146
4
2
24
16
80
712
16
8
8
64
96
64
16
16
480
56
8
32
16
0
584
16
8
Work Breakdown
1.7.2.6.
Risk Assessment
1.7.2.7.
Product Backlog
1.7.2.8.
Test Plan
2. Sprint 1
2.1. Iteration Planning
2.1.1. Iteration Planning
2.1.2. Detailed Iteration Task List
2.2. Environments Set Up
2.3. Design for sprint 1
2.3.1. Architectural Designs
2.3.2. System Design Documents
2.3.3. Design Details sprint 1
2.4. Programming
2.5. Testing
2.5.1. Unit Test Code
2.5.2. Unit Test Execution
2.5.3. Test Case Specifications
2.6. Delivered First release
3. Sprint 2
3.1. Iteration Planning
3.1.1. Iteration Planning
Page | 9
RSDoor
Business Case
3.1.2. Detailed Iteration Task List
3.2. Design Details for sprint 2
3.3. Programming
3.4. Testing
3.4.1. Unit Test Code
3.4.2. Unit Test Execution
3.4.3. Test Case Specifications
3.5. Delivered Second release
4. Sprint 3
4.1. Iteration Planning
4.1.1. Iteration Planning
4.1.2. Detailed Iteration Task List
4.2. Design for sprint 3
4.3.1. Update Architectural Designs
4.3.2. Update System Design Documents
4.3.3. Design Details sprint 3
4.3. Programming
4.4. Testing
4.4.1. Unit Test Code
4.4.2. Unit Test Execution
4.4.3. Test Case Specifications
4.5. Delivered Third release
5. Sprint 4
5.1. Iteration Planning
5.1.1. Iteration Planning
5.1.2. Detailed Iteration Task List
5.2. Design for sprint 4
5.3.1. Update Architectural Designs
5.3.2. Update System Design Documents
5.3.3. Design Details sprint 4
5.3. Programming
5.4. Testing
[Version 3.0]
2
7
120
14
2
8
4
0
183
5
3
2
23
7
4
12
140
15
3
8
4
0
190
4
2
2
16
7
3
10
120
13
8
28
480
56
8
32
16
0
732
20
12
8
92
28
16
48
560
60
12
32
16
0
612
16
8
8
64
28
12
40
480
52
Page | 10
RSDoor
Business Case
5.4.1. Unit Test Code
5.4.2. Unit Test Execution
5.4.3. Test Case Specifications
5.5. Delivered fourth release
6. Sprint 5
6.1. Iteration Planning
6.1.1. Iteration Planning
6.1.2. Detailed Iteration Task List
6.2. Design for sprint 5
6.3.1. Update Architectural Designs
6.3.2. Update System Design Documents
6.3.3. Design Details sprint 5
6.3. Programming
6.4. Testing
6.4.1. Unit Test Code
6.4.2. Unit Test Execution
6.4.3. Test Case Specifications
6.5. Delivered fifth release
[Version 3.0]
2
7
4
0
87
4
2
2
16
2
1
8
60
7
2
3
2
0
8
28
16
0
328
16
8
8
44
8
4
32
240
28
8
12
8
0
5.1 Estimates hardware cost
Buy electronic circuit: 100$
6. COST/BENEFIT ANALYSIS:
Cost/benefit analysis is an integral part of evaluating the impact of the proposed
project. Note that this is only a preliminary estimate as a specific cost estimate
cannot usually be developed at this point.
Benefits focus on opportunities to increased revenues, decrease expenses, or
avoid costs. In this section, identify specific benefits associated with the successful
implementation of the project. Where appropriate, classify benefits by company,
business unit, or audience.
Page | 11
Business Case
RSDoor
[Version 3.0]
Benefits tend to fall into four major classifications:
 Intuitive benefits - these benefits “makes sense”, for example, not to have
to re-key data.
 Direct benefits – these benefits are quantification of the intuitive benefits.
 Indirect and Strategic – these benefits tend to have the greatest impact.
Table: Project Benefits
Area
Direct benefits
Indirect benefits
Development Team
Complete capstone
More knowledge and
project
experience in software
development
Information Services
More effectively
Increased system
integrated systems
availability
Ease of support
Availability of more
accurate
Information
Customer Service
Convenience
Saving time, saving
without using manpower
money
7. PROJECT SCHEDULE:
Provide schedule information that demonstrates how project management controls
will be implemented.
7.1 PROJECT MILESTONES
Describe the project’s preliminary major milestones, deliverables, and target dates
Page | 12
Business Case
RSDoor
[Version 3.0]
Table— Project Milestones:
Deliverable
Responsibility
Start Date
End Date
Collect and
Communication with
8-8-2011
30-8-2011
analysis
customer and collect them
requirements
requirements, analysis and
1-9-2011
23-9-2011
23-9-2011
13-10-2011
10-2-2012
10-3-2012
10-3-2012
10-4-2012
10-4-2012
6-5-2012
given product concept
Sprint 1
Plan, implementation a
product life cycle, end.
Sprint 2
Plan, implementation
continue product life cycle,
end.
Sprint 3
Plan, implementation new
life cycle for product, add
new function, end.
Sprint 4
Plan, implementation new
life cycle for product, add
new function, end.
Sprint 5
Plan, implementation new
life cycle for product, add
new function, end.
7.2 ASSUMPTIONS:
List and describe any assumptions relevant to the business case and the impact they
may have.
Table— Assumptions
Page | 13
Business Case
RSDoor
Ref. #
1
Assumptions
[Version 3.0]
Impact
Hardware ( devices GSM
Problem buy or not buy the hardware
reception)
in the market will lead to success or
failure of the project.
2
Technical support from the
Embedding technique depends of the
hardware sale
hardware and technical support staff of
technique depends of the hardware and
technical support staff for project
development teams
7.3 CONSTRAINTS
Summarize constraints, such as the affordability of the proposal, existing
contractual commitments. List and describe any constraints or limitations that are
being recommended to achieve the anticipated business outcomes.
Table — Constraints
Ref.
Constraint
Impact
Hardware
Principle of operation of the hardware,
#
1
integrating hardware with software.
Page | 14
RSDoor
2
Technical
Business Case
[Version 3.0]
Embedded to electronics
7.4 DEPENDENCIES:
The project depends on investors to be able to meet the development costs. Project
development team was a student, not have much experience in developing
software, will depend on many factors such as mentor, time, knowledge is learned.
Page | 15