BUSSINESS CASE

SOFTWARE ENGINEERING PRACTICE

Department of Defence
Defence Science and Technology Organisation
Document Number: SEP-BC2016S201
Word Count: 1622
Submission Date: 04/09/2016
Group: Team Rocket
Participants: Edwin Joseph (U3147839)
Sandesh Shelar (U3136126)
Vinayak Nada r(U3123749)
Sid Chanda (U3103050)
Ketan David (U3149036)

16

SOFTWARE ENGINEERING PRACTICE7169

I. INTRODUCTION/BACKGROUND ........................................................................................3
II. BUSINESS OBJECTIVE ..........................................................................................................3
III. CURRENT SITUATION AND PROBLEM/OPPORTUNITY ...............................................3
IV. CRITICAL ASSUMPTIONS AND CONSTRAINTS ............................................................4
V.

ANALYSIS OF OPTIONS AND RECOMMENDATIONS ...................................................4

VI. PRELIMINARY PROJECT REQUIREMENTS ....................................................................4

VII. BUDGET ESTIMATES AND FINANCIAL ANALYSIS ....................................................5
VIII. SCHEDULE ESTIMATE ......................................................................................................5
IX. POTENTIAL RISKS ...............................................................................................................5
X. EXHIBITS ................................................................................................................................5
XI. APPENDIX ..............................................................................................................................7

Page 1 of 8

SOFTWARE ENGINEERING PRACTICE7169

No
01
02

Date
20/08/2016
22/08/2016

Student ID
U3103050
U3136126,U3123749

03

28/08/2016

U3103050,U3136126

04

30/08/2016

U3123749,U3149036

05
06
07

02/09/2016
03/09/2016
04/09/2016

U3149036, U3147839
U3147839
U3123749

History Table
Description
Document created
Updated Business Objective, Current
Situation/Problem Opportunity
Updated Assumptions and Constraints,
Budget/Financial and Schedule Estimate
Updated Introduction/Background, Preliminary
Requirements
Checked business case for any possible errors
Final document formatting
Uploaded document to moodle

Page 2 of 8

SOFTWARE ENGINEERING PRACTICE7169

I.

Introduction/background
To ensure and propel Australia's key advantages, Defence plans for and conducts operations and
different undertakings as coordinated by the legislature. Creating and keeping up the ability to do
these operations and undertakings is a focal and progressing obligation regarding Department of
Defence.
The suggestions for Defence of the Government's vital necessities are examined and prompt a
progression of undertakings to be modified through the ability improvement process. The point is
to create and keep up the most operationally viable and cost-effective blend of capacities required
accomplishing Government's key destinations. In FY 2014-2015 ventures esteemed around 1.53
billion have been endorsed.
Like whatever other venture portfolio, Defence ventures add to the general Defence ability in ways
that are influenced by the nearness of different undertakings. The exceptionally mind boggling and
complex interdependencies between Defence ventures include a level of many-sided quality to the
arranging and administration of the Defence capacity portfolio. Adjustments can't be made to one
specific territory of the portfolio without conceivably influencing different ranges. Overseeing
venture interdependencies in the Resistance capacity portfolio is exceedingly sought if Defence is
to have the capacity to produce the impacts required by Strategic Direction later on.
In spite of the fact that barrier associations know about interdependency issues, and the effects
interdependencies can have on ventures (e.g. fetched victories, plan deferrals and execution
deficiencies), their deficient treatment seems to remain a basic confinement on viable Portfolio
Management hones in resistance. Subsequently, a framework that can procedure venture
information and viably outline interdependencies can go far in contributing towards the key
objectives of the protection capacity arranging

II.

Business Objective
The centre motivation behind this venture is to build up a solid DSS (Decision Support System) for
the Department of Defence, Australia that would be fit for catching and preparing venture
information, mapping interdependencies between different extends and empowering representation
against current state or developing change. This will encourage a superior visual outline of the
Department portfolio and will thusly bolster basic leadership on various ventures.
The proposed framework will likewise think about the security imperatives empowering the
division to give a controlled access to partners. The framework will fuse modules, for example,
Assets, assets, partners, and venture what's more, program administration. It will permit clients to
include and overhaul ventures, oversee venture assets, demands and financial plan.
It will bolster venture interdependency mapping in view of breakthroughs or dangers as mapping
qualities, which will prepare clients with the capacity to organize, oversee and investigate a few
activities that are useful under the division. This would assist upgrade client perceivability
prompting enhanced prioritization of the most basic applications in the portfolio, driving
advancement inside the association, in the meantime conveying on key execution objectives, for
example, being on time, on spending plan and on target.
Basically, the framework being proposed will guarantee perceivability into tasks and
interdependencies, which will offer assistance partners to upgrade speculations and minimize
dangers on undertakings and help the office to produce the impacts required by Strategic Guidance
and accomplish the normal ROI..

III.

Current Situation and Problem/Opportunity

Customary method for overseeing Department of barrier portfolio for leaders is excessively
unpredictable, making it impossible to fathom and it's hard to envision every one of the
connections between the ventures and related dangers. To successfully settle on choice on
undertakings that are going off track or new activities that will be executed, it is crucial to
Page 3 of 8

SOFTWARE ENGINEERING PRACTICE7169

comprehend a task's interdependencies from alternate points of view particularly when there is
forcing change, or developing danger, which as of now is a test for the division.
Henceforth another framework that can check different interdependencies, for example, sharing of
assets, dangers, benefits, costs, and so on. to give an all encompassing perspective of ventures to
the partners is key. The proposed framework with permit leaders to imagine the connections and
dangers related through different ventures and help with making educated choices.
IV.

Critical Assumptions and Constraints

The proposed framework will be a profitable advantage for Defence Department and its Decision
producers. It won't just give more control over activities additionally fundamentally diminish
many-sided quality of current representation of venture information. The office must organize and
bolster this task to have the capacity to move its Decision Support System with a specific end goal
to viably illuminate current fundamental issues being confronted. The expense of building up this
undertaking might pay off in range of 6 months by viably overseeing assets of various undertakings
being done by Defence Department. It will require least specialized backing and will be more easy
to use than past framework.
A portion of the limitations basic to the task will be:
1. Staffing Constraints: Project will be hampered if there should be an occurrence of loss of key
staff.
2. Spending Constraints: Government may cut the financing on the task, bringing about deferral or
end of the venture.
3. Time Constraint: The undertaking may augment the stipulated time span of 3 months.
4. Specialized Constraints: Difficulty in securing required hardware or programming.

V.

Analysis of options and recommendations

There are three ways to deal with the above expressed issues:
1. Add more human asset to deal with the expanding multifaceted nature of undertaking
information and manual work.
2. Buy existing arrangements, which may not completely cook the requirements and may not be
perfect with current innovation framework.
3. Start the undertaking for the proposed framework and build up the framework in-house. Closing
all talks inside the group, we trust choice 3 is most attainable in current circumstance.

VI.

Preliminary project requirements

The accompanying are the abnormal state useful necessities of the framework:
1. To catch and process venture information, including entering, change and erasure of undertaking
points of interest
2. To guide interdependencies for Program, Project and Portfolio
3. To registers assets, partners, resources, venture components
4. To empower fit-for-reason perception of venture undertakings and interdependencies
Non Functional Requirements:
1. To bolster information respectability and consistency

Page 4 of 8

SOFTWARE ENGINEERING PRACTICE7169

Tasks

Resources week1

Week2

week3

week4

week5

week6

week7

week8

week9

Total
Hours

2. Framework will have the capacity to work inside limited guard environment empowering
security requirements.
3. Framework will hold fast to government and safeguard rules.
VII.

Budget estimates and financial analysis

A preparatory appraisal of time for the whole venture is 9 weeks. The work breakdown and the
quantity of hours designated to various periods of the venture have been recorded underneath:
Stage
Hours

VIII.

1. Arranging and Analysis

24

2. Plan

20

3. Documentation

50

4. Survey

36

5. Execution

70

6. Testing

32

Schedule Estimate
The backer might want to see the venture complete inside 9 weeks given no adaptability in the
calendar as this is the time span of the semester assets will take a shot at the undertaking. In the
event that the undertaking is coming up short on time, colleagues will be required to put in
additional hours than assessed amid the given time period to get the venture to finish. We expect,
once the new framework is conveyed it will be a one-time arrangement helpful for every one of the
activities and can be reached out to different divisions if required.

IX.

Potential risks
There are a few dangers influencing achievement component of this venture:
1. One of the greatest danger is changing clients starting with one known interface then onto the
next, which may make perplexity if legitimate preparing is not gave to end-clients of this
framework.
2. Another danger is relocation of current information, as this framework holds tight principles on
information respectability and may not create valuable bits of knowledge whether there is a
missing information from old/current framework..

X.

Exhibits
Financial analysis shows the estimated value in working hours per type of work not the real or
expected dollar value.

Page 5 of 8

SOFTWARE ENGINEERING PRACTICE7169

Analyzing and
Planning

24

Sandesh

Edwin

Siddhartha 4

Ketan

Vinayak

Siddhartha 1

Vinayak

Edwin

Sandesh

Siddhartha

Vinayak
Managing

Development

36

48

Ketan

Deployment

Siddhartha

33

Ketan
Sandesh
Testing

Edwin

Vinayak

Total Hours per week 168

Page 6 of 8

24

SOFTWARE ENGINEERING PRACTICE7169

XI.

Appendix

Kevin O'Shea, Peter Pong and Gary Bulluss, 2015, Fit-for-Purpose Visualisation of Architecture to support
Defence Capability Decision-Making'
Available at: http://www.dsto.defence.gov.au/sites/default/files/publications/documents/DSTO-TN1098%20PR.pdf [Accessed 28 August 2015].

Team participation
No
01
02
03
04
05

Student ID
U3147839
U3136126
U3123749
U3103050
U3149036

Description
Worked on a section(s) 1,2,3,6 amount of overall time 20%
Worked on a section(s) 1,4,5,7 amount of overall time 20%
Worked on a section(s) 5,8,9,10 amount of overall time 20%
Worked on a section(s) 10,11,7, 8 amount of overall time 20%
Worked on a section(s) 8,6,10,4 amount of overall time 20%

Page 7 of 8