ICT50715 – Assignment 01 – Task 2 – Process for Procurement Policy – SSDM (APA).2200

ICT50715 ASSIGNMENT – Procurement Policy

ASSIGNMENT 1 – Systems/Software Development Methodologies (2)

TASK 2 – Process for Procurement

AUTHOR: William A Hambly

INSTITUTION: Upskilled Training (RTO, Australia)

COURSE: ICT50715 - Diploma of Software Development

Section 2 | CONTENTS HAMBLY 2/25

Contents

Abstract ............................................................................................................................... 4

ASSIGNMENT 1 – Systems/Software Development Methodologies (2) .......................... 5

Introduction ....................................................................................................................... 5

Outline for Task 2 ........................................................................................................... 5

Purpose of this Document ............................................................................................... 6

Rationale for the Assignment. ..................................................................................... 6

Project Management Plan ............................................................................................... 6

Stakeholder List (Key Contacts) ...................................................................................... 7

Core Business Objectives ................................................................................................. 8

The Proposal ...................................................................................................................... 9

Proposal and Procurement Report .................................................................................. 9

Reasons for the Selection ................................................................................................ 9

RUP phases. ................................................................................................................ 9

Best Practices. ............................................................................................................. 9

Project phases.............................................................................................................. 9

Procedure to Determine Procurement ........................................................................... 10

Formalise profitability. .............................................................................................. 10

Research into Development Tools .................................................................................11

Tools Researched. ......................................................................................................11

Business Case................................................................................................................ 12

Reason for Rational Unified Process. ....................................................................... 12

Section 2 | CONTENTS HAMBLY 3/25

Methodology .................................................................................................................... 13

Steps in Practice ............................................................................................................ 13

Pricing, lead-times and steps for procurement .............................................................. 13

Technical Review and Signoff ........................................................................................ 14

Technical Review .......................................................................................................... 14

SIGNOFF – DOCUMENT APPROVAL ....................................................................... 15

Conclusion ....................................................................................................................... 16

References / Bibliography................................................................................................. 17

Footnotes/Endnotes ........................................................................................................... 20

Appendix A: UML Products by Platform ................................................................... 21

Appendix B: Computing Model ..................................................................................... 22

Appendix C: Iterations of RUP ..................................................................................... 23

Appendix D: Lifecycle of the Enterprise Unified Process (EUP) ............................... 24

ENDNOTES ..................................................................................................................... 25

3 | ICT50715 ASSIGNMENT – PROCUREMENT POLICY HAMBLY 4/25

Abstracti

This document provides a process for procurement by promoting the methodologies of RUP and

UML, to complement the existing company policy of OO. The paradigm of UML has swiftly

established itself as the de facto standard for object-oriented analysis and design. While meeting

one of the key criteria for a methodology — communicating the project design to stakeholders -

UML alone has no facilities for managing the project lifecycle; to achieve this it has to be used in

conjunction with a project methodology such as Rational's Objectory or any RUP. (Goodwin,

2001)


ASSIGNMENT 1 – Systems/Software Development Methodologies (2)

Introduction

Outline for Task 2

The business represented is “Skippy Banking Enterprises” – a leading software

development house of 50 individuals, providing quality software products, modern practices, and

partnered with & certified by major companies – e.g. Microsoft, VMware, Symantec, Cisco, and

HP Business.

In 2016 the culture of Skippy Banking Enterprises was open to change, which was a huge

benefit. Management is open-minded and willing to try new techniques, hence the decision to

embrace RUP. The developers are experienced & eager to work with new technologies.

The approach is to pilot the RUP on a small project – of seven developers, one manager,

one senior manager and four users - over a period of seven months. The project is of mid-level

importance; it would be noticeable if it failed but it wouldn't put the company at risk. It will be

their first real J2EE project, and the team would be fairly typical: two mid-level Java developers;

a senior consultant experienced in EJB; another senior developer with a C++, OMT, and UML

background; an experienced business analyst new to use cases and object-oriented development;

a DB2 database administrator (DBA) learning Oracle; and a good QA/tester person with some

Java testing background.

The company uses Microsoft Visual Studio1 & Eclipse2 as their development platforms.

For this section, assume that the 3 SDM’s have been presented & addressed in Part I of

the assignment, and the organisation is confident enough to move forward & consider the

proposed platform (RUP).

1 Copyright © 2016 Microsoft MSDN platforms 2 Copyright © 2016 The Eclipse Foundation


Purpose of this Document

Rationale for the Assignment. The three SDM’s (Software Development

Methodologies) discussed in assignment 1 are:

i. Waterfall model

ii. Agile modelling

iii. RUP

This assignment has selected the Rational Unified Process in Part I, and proposed a procurement

policy in this document (Part II).

Software industries are progressively adopting the agile development practices of

customized models such as Extreme Programming (XP) or Scrum or Rational Unified Process

(RUP). Scrum and Extreme Programming (XP) are frequently used agile models, whereas

Rational Unified Process (RUP) is one popular classic plan driven software development

methodology. (Sharma & Wadhwa, 2015)

Project Management Plan

A Project Management plan that defines a Risk Management plan, Steering Committee,

Project Schedule, Stakeholder Engagement (etc.) would be drawn up subsequent to this proposal.


Stakeholder List (Key Contacts)

Name Position Role / interest in this project

Mary Poppins CEO, Chairman, Chairperson Company Founder

Alfred E. Neumann Director, Operations (IT) IT Strategy

Clint Eastwood CIO Enterprise Architect

Billy The Kidd CFO Bean counter


Core Business Objectives

Objective

ID number

Core business

Objective

Business Owner Business importance

(Mandatory/High

Priority/Optional)

1. To increase company

profitability from

software products

I T Manager Mandatory

2. To produce software

products to market

faster, within budget

CFO Mandatory

3. To enhance the

company’s reputation in

the market

CEO Discretionary


The Proposal

Proposal and Procurement Report

This document proposes to adopt UML and RUP as modern strategies for software development,

and support the company’s ongoing strategy of OO principles, to procure the Enterprise

Architect (EA) tool and use it to develop software products.

Reasons for the Selection

Since 2010, the company has adopted the architectural design principles of OO – and UML for

defining project requirements and identifying use cases for software programs. This document

seeks to promote design patterns and unified modelling language (UML) tools, including class

and sequence diagrams, and to use the selected tool to convert the diagrams into code, thus

effecting rapid & solid product development.

RUP phases. Similar to waterfall, RUP has fixed phases as inception, elaboration,

construction and transition. But unlike waterfall, RUP is an iterative process. See Appendix C:

Iterations of RUP

Best Practices.

RUP captures six best practices of software engineering-

i. iterative development,

ii. managing requirements,

iii. component-based architecture,

iv. visual modelling,

v. continuous verification and

vi. management of changes. (RUP: Best Practices for Software Development Teams, 1998)

Project phases. Enterprise Architect (EA) is a well-established tool in the software

industry, and allows the team to define a project in these important phases:

a. Identify key system functions

b. Define candidate solutions

c. Define assessment criteria

d. Assign weights to the criteria

e. Define utility curves

f. Determine measures of effectiveness

g. Determine solution (Graham John Bleakley (PhD), 2009)

See Appendix D: Lifecycle of the Enterprise Unified Process


Procedure to Determine Procurement

Formalise profitability. Document expected returns from investments into tool, IT

strategy.

- Feasibility studies in 2015 have concluded that this company has several clients in the

global market who have IT & business projects estimated at AU$1.5 billion. The co. has a solid

reputation with several of these clients. The estimated revenue (if the company were to win 2 or

more development contracts in 2016) would be at least $75 million.

For this reason, the IT department has been allocated a budget of $1.25 million to

purchase new software development tools and develop a pilot project within the next 8 months.


Research into Development Tools

Although there are many modern SDMs and models as discussed in part I, there isn’t one

solution that’s right for any one culture or project. There is a large array of tools available today

for software development. For a list of researched UML tools, please see Appendix A: UML

Products by Platform

Tools Researched. After careful research, the following tools have been considered as

appropriate for this company’s development schema.

There are open-source tools at no cost, but these don't necessarily provide complete

functionality for software development.

Rational Rose. Considered IBM-Rational Rose -- more

expensive than it's worth? http://rational-rose-2000-

enterprise-edition.software.informer.com/

US $5,170 (July, 2015)

Rational Rhapsody. IBM Rational Rhapsody Developer

(fixed-term lic. + subscription & support 12 Months) US $7,630.00 (IBM List)

TogetherSoft. TogetherSoft Control Centre isn't just a

UML modelling tool, it’s a full development platform for

SDLC process from requirements through testing.

However, as the company is using Microsoft Visual

Studio IDE, it was decided to promote a UML tool only.

US $3,495

Enterprise Architect (Sparx). Enterprise Architect (EA) -

- robust/affordable. A few team members have

experience with Sparx Systems, so it was decided to

promote this as it’s a very good Design & Build

platform, and is reasonably priced.

US $799 per seat (Ultimate

Edition Standard License)

US $199 (Corporate Edition

Standard License)

Some tools are considered too expensive, up to $10,000 per licence.

http://rational-rose-2000-enterprise-edition.software.informer.com/

http://rational-rose-2000-enterprise-edition.software.informer.com/


Business Case

This proposal demonstrates how the company will achieve and measure policy outcomes,

strategic objectives and benefits.

Reason for Rational Unified Process. RUP and Enterprise Architect (EA) allows the

company to define & plan around processes – i.e. project activities, artefacts, workers and

workflows. (RUP: Best Practices for Software Development Teams, 1998)

Trade Analysis: The proposed tool allows the project team to conduct trade studies before

engineering anything, to accurately define the project space so that a proposed solution fits the

business requirements best/closely. This is a huge advantage in software design. (Rational

(Graham Bleakley, PhD), 2009)

- Powerful functionality to fully explore the design space to ensure that a proposed

solution fully meets conflicting performance and cost parameters. (Graham John

Bleakley (PhD), 2009)

See Appendix B: Computing Model


Methodology

Steps in Practice

The following steps would be carried out in practice (not included in this paper):

• Evaluate IT Strategy. Evaluate this proposal…sign off.

• Engage Customers. Formalise project, engage customers, negotiate with

stakeholders.

• Setup Project Team. Budget, engage team members with relevant skills.

• Project Design. Use Enterprise Architect (EA) tool to define project, create

design.

• Develop Phase 1. Develop, unit testing, UAT, validation, release, customers

UAT

• Assess Progress. Assess customers’ satisfaction, company reputation

Pricing, lead-times and steps for procurement

TOOL: Enterprise Architect (Sparx)

US $799 per seat (Ultimate Edition Standard

License)

$799 x 7 developers = $5,593 p.a.

Lead times to order 7 days

Steps to procure Order online

Payments by P/O – 30 days

Development trial – 30 days

Project committal: 60 days

Pilot project estimated duration Six months (180 days)

ROI evaluation Seven months after start (200 days)

4 | REVIEW AND SIGNOFF HAMBLY 14/25

Technical Review and Signoff

Since this is a proposal (RFC) to management, the change management assessment

(CAB) of the RFC would not include a review of the technical content of this change. In

subsequent steps, the proposed changes would undergo a technical review including the

following steps:

Technical Review

1. Correctness of all technical information, including preparation, implementation,

verification, and back-out procedures.

2. Completeness of change, testing procedures, and documentation.

3. Feasibility of the change.

4. Potential side effects and impact on other services or infrastructure.

5. Worst-case impact (both change and back-out procedure fail).

(CISCO, 2008)

(Quick Tips for Requirements Sign-off, 2014)

4 | REVIEW AND SIGNOFF HAMBLY 15/25

SIGNOFF – DOCUMENT APPROVAL

Name Position Title Signature Date

Mary Poppins CEO, Chairman, Chairperson

Alfred E. Neumann Director, Operations (IT)

Clint Eastwood CIO

A J Soapstone Project Manager

Julius Caesar Roman Emperor

5 | CONCLUSION HAMBLY 16/25

Conclusion

The development strategies of the Unified Process especially RUP, and indeed all Agile-

type models. are clearly beneficial & essential to the future of IT businesses. Of the tools

considered, the selected tool Enterprise Architecture has a very established Customer base and a

solid reputation in the industry: 350,000 licenses, 230 partners in 160 countries. (EA – Ultimate

Design & Build Platform, 2016)

It is clear that the company needs to consider new initiatives & drive. The adoption of a

new software development methodology is not only essential to the company’s growth &

strategy, but it will also benefit the company from reputation and financial viewpoints. The

quality of developed products from a well-defined & reliable process methodology will be

essential to survival in the 21st century.

A further idea would be that as RUP enhances the co.’s reputation, this will allow

management to consider working in different industry sectors, procuring new clients and

pursuing new business directions.

Trust that management will see this a clear tactical perspective and promote the new

technology for the company. The IT department is excited about this proposal and awaits the

outcome with keen anticipation.

6 | REFERENCES | BIBLIOGRAPHY HAMBLY 17/25

References / Bibliography

Allardice, S. (2012, 5 22). Foundations of Programming: Object-Oriented Design. Retrieved

from Lynda.com: http://www.lynda.com/Java-tutorials/Reviewing-software-

development-methodologies/96949/106057-4.html

Ambler, S. W. (2005). Agile Modeling and the Rational Unified Process (RUP). Retrieved from

agilemodeling.com: http://www.agilemodeling.com/essays/agileModelingRUP.htm

Australian Govt DOF. (2013, Oct). Information Sharing Lessons Learned from Gateway

Reviews. Retrieved from Australian Govt DOF:

http://www.finance.gov.au/sites/default/files/Gate_1_-_Lessons_Learned.pdf

CISCO. (2008, March 10). Change Management: Best Practices. Retrieved from Cisco.com:

http://www.cisco.com/c/en/us/products/collateral/services/high-

availability/white_paper_c11-458050.html

EA – Ultimate Design & Build Platform. (2016). Retrieved from Sparx Systems:

http://sparxsystems.com/

Goodwin, C. (2001, October). Development methodology in under 10 minutes. Retrieved from

ComputerWeekly.com: http://www.computerweekly.com/feature/Development-

methodology-in-under-10-minutes

Graham John Bleakley (PhD). (2009, June). Smarter system development: a systems engineering

trade study to support green initiatives with model-driven development. Retrieved from

IBM White Paper:

ftp://ftp.software.ibm.com/software/emea/de/rational/neu/Smarter_system_development_

EN_2009.pdf


ISACA.org. (2012, July 1). Calculating Cloud ROI: From the Customer Perspective. Retrieved

from ISACA.org: http://www.isaca.org/Knowledge-

Center/Research/Documents/Calculating-Cloud-ROI_whp_Eng_0712.pdf

Last Name, F. M. (Year). Article Title. Journal Title, Pages From - To.

Last Name, F. M. (Year). Book Title. City Name: Publisher Name.

Margaret Rouse. ( 2014, September). Behavior-driven development (BDD). Retrieved from

TechTarget: http://searchsoftwarequality.techtarget.com/definition/Behavior-driven-

development-BDD

Quick Tips for Requirements Sign-off. (2014, March 8). Retrieved from

http://businessanalystlearnings.com/blog/2014/3/6/3-quick-tips-for-obtaining-

requirements-sign-off

Rational (Graham Bleakley, PhD). (2009, May). Smarter system development: a systems

engineering trade study to support green initiatives with model-driven development.

Retrieved from Bitpipe.com: http://www.bitpipe.com/detail/RES/1242325543_346.html

RUP: Best Practices for Software Development Teams. (1998). Retrieved from Rational

Software:

https://www.ibm.com/developerworks/rational/library/content/03July/1000/1251/1251_b

estpractices_TP026B.pdf

Sharma, N., & Wadhwa, M. (2015, Nov). eXSRUP: Hybrid Software Development Model

Integrating Extreme Programing, Scrum & Rational Unified Process. TELKOMNIKA

Indonesian Journal of Electrical Engineering, 377-388. Retrieved from TELKOMNIKA

Indonesian Journal of Electrical Engineering:

http://iaesjournal.com/online//index.php/TELKOMNIKA/article/viewFile/8436/4325


http://www.itinfo.am/eng/software-development-methodologies/

http://www.agiledata.org/essays/differentStrategies.html

http://www.itinfo.am/eng/software-development-methodologies/

http://www.agiledata.org/essays/differentStrategies.html

7 | FOOTNOTES HAMBLY 20/25

Footnotes/Endnotesii

8 | APPENDIX HAMBLY 21/25

Appendix A: UML Products by Platform3 4 5

3 Copyright © 1999-2005 Objects by Design, Inc. 4 Updated: 15-Oct-2005 5 The site provides a list of Unified Modelling Language (UML) software tools, over 100 (+/-117)

http://www.objectsbydesign.com/tools/umltools_byCompany.html

http://www.objectsbydesign.com/tools/umltools_byCompany.html


Appendix B: Computing Model


Appendix C: Iterations of RUP

(Ambler, 2005)


Appendix D: Lifecycle of the Enterprise Unified Process (EUP)

(Ambler, 2005)

9 | ENDNOTES HAMBLY 25/25

ENDNOTES

ICT50715 – Assignment 01 – Task 2 – Process for Procurement Policy – SSDM (APA).2200

Documents

Transcript of ICT50715 – Assignment 01 – Task 2 – Process for Procurement Policy – SSDM (APA).2200