2010 SP1 - RMIT CPT230 - Assignment 3 - Technical & Project Management

RMIT CPT230 SP1 2010

Assignment 3 Technical & Project Management

Andrew Cole S3220162 May 2010

Andrew Cole i

CPT230 S3220162 May 2010

Table of Contents A. XYZ User Acceptance Test Plan ....................................................................................................... 1

A.1. Test Data ....................................................................................................................................... 1

A.2. Test Plan ....................................................................................................................................... 2

B. Development Method & Schedule ................................................................................................. 6

B.1. Waterfall Project Schedule ........................................................................................................... 7

B.2. RUP Project Schedule ................................................................................................................... 8

B.3. Schedule Comparison ................................................................................................................... 9

C. Project Management 101 ............................................................................................................. 10

C.1. What is a Project Charter? .......................................................................................................... 10

C.2. What is a Statement of Work? ................................................................................................... 10

C.3. What is the Pareto Principle in a project management context? .............................................. 10

C.4. What is PMP? .............................................................................................................................. 10

C.5. What is PMBOK? ......................................................................................................................... 10

Bibliography .......................................................................................................................................... 11

Table of Figures

Table 1 - Smith Family Invoice Data ........................................................................................................ 1

Table 2 - Jones Family Invoice Data ........................................................................................................ 1

Table 3 - Williams Family Invoice Data ................................................................................................... 1

Table 4 - Brown Family Invoice Data ....................................................................................................... 1

Table 5 - User Acceptance Test Plan ....................................................................................................... 5

Table 6 - Waterfall Project Schedule....................................................................................................... 7

Table 7 - Rational Unified Process Project Schedule .............................................................................. 8

Andrew Cole 1

CPT230 S3220162 May 2010

A. XYZ User Acceptance Test Plan

A.1. Test Data The following tables present the sample data that is assumed to be present in the application before

testing commences.

Date: Todays Date

Account Number: 1234

Guardian/Parent: Jack Smith

Children: Mia Smith

Total Cost: $100

Benefits: $nil

Discounts: $nil

Nett Payable: $100 Table 1 - Smith Family Invoice Data

Date: Todays Date


Guardian/Parent: Chloe Jones

Children: William Jones

Total Cost: $100

Benefits: $20

Discounts: $nil

Nett Payable: $80 Table 2 - Jones Family Invoice Data

Date: Todays Date


Guardian/Parent: Isabella Williams

Children: Lachlan Williams Emily Williams

Total Cost: $200

Benefits: $nil

Discounts: $20

Nett Payable: $180 Table 3 - Williams Family Invoice Data

Date: Todays Date


Guardian/Parent: Joshua Smith

Children: Olivia Smith Cooper Smith

Total Cost: $200

Benefits: $40

Discounts: $16

Nett Payable: $144 Table 4 - Brown Family Invoice Data

Andrew Cole 2

CPT230 S3220162 May 2010

A.2. Test Plan

Test No.

Test Name

Step No.

Step Description

Sample Data

Expected Results

Exec- uted

1 Create a single invoice for a family with one child and no government benefits.

1.1. Log on to the system as a center administrator.

CenterAdmin / Password01

System logs on; Main menu is displayed.

1.2. Select Invoices -> Create. The Create Invoices window appears.

1.3. In the Start Date text box, enter a starting date for the invoices being generated.

January 1, 2010

1.4. In the Finish Date text box, enter a finish date for the invoices being generated.

January 30, 2010

1.5. In the Accounts list box, select a single family. Smith Family

1.6. Click the Create Invoices button. One invoice is created and displayed, with the information as per Table 1 - Smith Family Invoice Data.

1.7. Click the Close button. The invoice is closed; The main menu is displayed.

2 Create a single invoice for a family with one child and some government benefits.






January 1, 2010


January 30, 2010

2.5. In the Accounts list box, select a single family. Jones Family

2.6. Click the Create Invoices button. One invoice is created and displayed, with the information as per Table 2 - Jones Family Invoice Data.


Andrew Cole 3

CPT230 S3220162 May 2010

Test No.

Test Name

Step No.

Step Description

Sample Data

Expected Results

Exec- uted

3 Create a single invoice for a family with multiple children and no government benefits.






January 1, 2010


January 30, 2010

3.5. In the Accounts list box, select a single family. Williams Family

3.6. Click the Create Invoices button. One invoice is created and displayed, with the information as per Table 3 - Williams Family Invoice Data.


4 Create a single invoice for a family with multiple children and some government benefits.






January 1, 2010


January 30, 2010

4.5. In the Accounts list box, select a single family. Brown Family

4.6. Click the Create Invoices button. One invoice is created and displayed, with the information as per Table 4 - Brown Family Invoice Data.


Andrew Cole 4

CPT230 S3220162 May 2010

Test No.

Test Name

Step No.

Step Description

Sample Data

Expected Results

Exec- uted

5 Create and save a single invoice.

5.1 Log on to the system as a center administrator.



5.2 Select Invoices -> Create. The Create Invoices window appears.


January 1, 2010


January 30, 2010

5.5. In the Accounts list box, select a single family. Brown Family

5.6. Click the Create Invoices button. One invoice is created and displayed, with the information as per Table 4 - Brown Family Invoice Data.

5.7 Click the Save as PDF button. The Save as PDF window appears.

5.8 Navigate to a temporary folder and click the Save button.

The Save as PDF window closes; The previously created invoice is still open.


5.10. Using Windows Explorer, view the above temporary folder.

Invoice-TodaysDate-Brown.pdf exists.

Andrew Cole 5

CPT230 S3220162 May 2010

Test No.

Test Name

Step No.

Step Description

Sample Data

Expected Results

Exec- uted

6 Create and save multiple invoices.

6.1 Log on to the system as a center administrator.



6.2 Select Invoices -> Create. The Create Invoices window appears.


January 1, 2010


January 30, 2010

6.5. In the Accounts list box, select multiple families.

Smith Family Williams Family

6.6. Click the Create Invoices button. Two invoices are created and displayed, with the information as per Table 1 - Smith Family Invoice Data and Table 3 - Williams Family Invoice Data.

6.7 Click the Save as PDF button. The Save as PDF window appears.

6.8 Navigate to a temporary folder and click the Save button.

The Save as PDF window closes; The previously created invoice is still open.


6.10. Using Windows Explorer, view the above temporary folder.

Invoice-TodaysDate-Williams.pdf and Invoice-TodaysDate-Smith.pdf exist.

Table 5 - User Acceptance Test Plan

Andrew Cole 6

CPT230 S3220162 May 2010

B. Development Method & Schedule The following pages outline two sample schedules for development of the XYZ Childcare Management System.

Andrew Cole 7 CPT230 S3220162 May 2010

B.1. Waterfall Project Schedule

Activity # Task Duration Dependencies

Business Engineering 1 Interviews with customer to determine business requirements 3d

2 Develop Software Requirements Specification for product 1d 1

3 Review developed SRS against business requirements with customer 1d 2

Requirements 4 Develop functional diagrams for product 1d 3

5 Review developed functional diagrams with customer 1d 4

Analysis & Design 6 Establish architecture of product 1d 5

7 Develop structural diagrams of product 1d 6

Implementation 8 Develop beta version 3d 7

Test 9 Test beta version against SRS and functional diagrams 1d 8

Implementation 10 Develop Release Candidate version 1d 9

Analysis & Design 11 Update Structural UML Diagrams 2d 9

Implementation 12 Develop 1.0 version 1d 11

Test 13 Test 1.0 version against SRS and Functional Diagrams 1d 12

Deployment 14 Deploy 1.0 version of software to customer 1d 12, 13 Table 6 - Waterfall Project Schedule

Andrew Cole 8 CPT230 S3220162 May 2010

B.2. RUP Project Schedule

Phase Iter-ation

Activity # Task Dur-ation

Dependen-cies

Inception Prelim Business Engineering 0.1 Interviews with customer to determine business requirements 3d

Requirements 0.2 Develop Software Requirements Specification for product 1d 0.1

Implementation 0.3 Develop functional diagrams for product 1d 0.1

Elaboration 1 Business Engineering 1.1 Review developed SRS against business requirements with customer 1d 0.2

Requirements 1.2 Review developed functional diagrams with customer 1d 0.3

Analysis & Design 1.3 Establish architecture of product 1.5d 1.1, 1.2

Implementation 1.4 Develop structural diagrams of product 1.5d 1.3

Construction 2 Implementation 2.4 Develop beta version 3d 1.4

Test 2.5 Test beta version against SRS and functional diagrams 1d 2.4, 1.2, 1.1

Deployment 2.6 Deploy beta version to customer for verification 1d 2.4

3 Business Engineering 3.1 Interviews with customer to confirm function of beta version 1d 2.6

Requirements 3.2 Update Software Requirements Specification 0.5d 3.1

Analysis & Design 3.3 Update Functional UML Diagrams 0.5d 3.2

Implementation 3.4.1 Update Structural UML Diagrams 0.5d 3.1

3.4.2 Develop Release Candidate version 1d 3.4.1

Test 3.5 Test Release Candidate version against SRS and Functional Diagrams 0.5d 3.2, 3.3, 3.4.2

Deployment 3.6 Deploy Release Candidate version of software to customer 1d 3.4.2

Transition 4 Business Engineering 4.1 Interviews with customer to confirm function of Release Candidate version 1d 3.6

Requirements 4.2 Update Software Requirements Specification 0.5d 4.1

Analysis & Design 4.3 Update Functional UML Diagrams 0.5d 4.2

Implementation 4.4.1 Update Structural UML Diagrams 0.5d 4.1

4.4.2 Develop 1.0 version 1d 4.4.1

Test 4.5 Test 1.0 version against SRS and Functional Diagrams 0.5d 4.2, 4.3, 4.4.2

Deployment 4.6 Deploy 1.0 version of software to customer 1d 4.4.2 Table 7 - Rational Unified Process Project Schedule

Andrew Cole 9

CPT230 S3220162 May 2010

B.3. Schedule Comparison The waterfall schedule can be said to be analysis heavy initially, with little in the way of functionality

delivered until the end of the development processes. This contrasts with the Rational Unified

Process and its multiple iterations, which delivers working code for the customer to review in as little

as two weeks. However this large amount of customer interaction may be seen as a disadvantage in

many projects, as the customer may become frustrated during this.

Reviewing the two developed schedules the major benefit of the Rational Unified Process schedule

is immediately apparent – the RUPs emphasis on delivering functionality in small increments allows

a much larger amount of testing, both internal and with the customer, than the non-incremental

waterfall method schedule. This one advantage alone makes the Rational Unified Process the

preferred option for this project, given the customers vagueness around the requirements of the

software being developed.

Andrew Cole 10

CPT230 S3220162 May 2010

C. Project Management 101

C.1. What is a Project Charter? A Project Charter in a project management context can be any one of the following, or a

combination thereof:

Another term for a Statement of Work (SOW), which outlines and limits the scope of the

project;

An expansion on a SOW, including additional details on risks and budget; or

An instrument authorising the project.

C.2. What is a Statement of Work? As mentioned above, a SOW outlines and limits the scope of a project. A complete scope statement

should define the projects objectives, deliverables, milestones, technical requirements, limits and

exclusions, and should be reviewed by both the team undertaking the work and the customer (Gray,

2008). Often included in SOW are commercial offers and terms and conditions of the offer.

C.3. What is the Pareto Principle in a project management context? The Pareto Principal is the 80/20 rule, which in a project management context states that the top

80% of errors are caused by the top 20% of bugs. Also known as the law of the vital few, or the

principle of factor sparsity.

C.4. What is PMP? PMP can have either of the following meanings in a project management context:

Project Management Professional, a certification offered by the Project Management

Institute. Certification is gained by passing an exam on six performance domains, being

Project Initiation, Planning, Execution, Monitoring and Controlling, Closing, and Professional

and Social Responsibility.

A Project Management Plan, is a document outline project execution. The exact layout of a

PMP is not prescribed, but generally covers execution, risk, budget, monitoring, controlling,

and in particular scope.

C.5. What is PMBOK? PMBOK is an abbreviation for the Project Management Body of Knowledge, as outlined in a

whitepaper by the Project Management Institute (A Guide to the Project Management Body of

Knowledge, also known as the PMBOK Guide).

The PMBOK outlines a methodology for project management; it recommends a standard approach

for managing projects. PRINCE2 is a similar industry methodology.

Andrew Cole 11

CPT230 S3220162 May 2010

Bibliography Booch, G 1993, Object-Oriented Analysis and Design with Applications (2nd Edition), Addison-Wesley

Professional, Reading Massachusetts

Rational Software Corporation, 1998, Rational Unified Process: Best Practices for Software

Development Teams, Rational Software Corporation, Cupertino California

Norris, M & Rigby, P 1992, Software Engineering Explained, John Wiley & Sons, New York.

Guntamukkala, V, Wen, HJ & Tarn, JM 2006, ‘An empirical study of selecting software development

life cycle models’, Human Systems Management, vol. 25, pp. 265–278.

Bhalerao, S, Puntambekar, D & Ingle, M 2009, ‘Generalizing Agile Software Development Life Cycle’,

International Journal on Computer Science and Engineering, vol. 1, no. 3, pp. 222‐226.

Boehm, BW 1988, ‘A spiral model of software development and enhancement’, IEEE Computer, vol.

21, issue 5, pp. 61‐72.

Gray, CF & Larson, Erik W 2008, Project Management: The Managerial Process, McGraw-Hill/Irwin,

New York

Pfleeger, S & Atlee, J 2010, Software Engineering (4th Edn.), Pearson Education, New Jersey

Leslie, BS 2010, e-mail, May 2010, <[email protected]>

Thinkbabynames.com, 2008, Top Australian Baby Names for girls, retrieved May 15, 2010, from

<http://www.thinkbabynames.com/popular/0/australia>

Thinkbabynames.com, 2008, Top Australian Baby Names for boys, retrieved May 15, 2010, from

<http://www.thinkbabynames.com/popular/1/australia>

About.com, 2010, Common Australian Surnames & Their Meanings, retrieved May 15, 2010, from

<http://genealogy.about.com/od/australia/tp/common_surnames.htm>

Documents

2010 SP1 - RMIT CPT230 - Assignment 3 - Technical & Project Management