RMIT CPT230 SP1 2010

Assignment 3
Technical & Project Management

Andrew Cole S3220162
May 2010

Table of Contents
A. XYZ User Acceptance Test Plan ....................................................................................................... 1 A.1. Test Data ....................................................................................................................................... 1 A.2. Test Plan ....................................................................................................................................... 2 B. B.1. B.2. B.3. C. C.1. C.2. C.3. C.4. C.5. Development Method & Schedule ................................................................................................. 6 Waterfall Project Schedule ........................................................................................................... 7 RUP Project Schedule ................................................................................................................... 8 Schedule Comparison ................................................................................................................... 9 Project Management 101 ............................................................................................................. 10 What is a Project Charter? .......................................................................................................... 10 What is a Statement of Work? ................................................................................................... 10 What is the Pareto Principle in a project management context? .............................................. 10 What is PMP?.............................................................................................................................. 10 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 S3220162

i

CPT230 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: Account Number: Guardian/Parent: Children: Total Cost: Benefits: Discounts: Nett Payable: Date: Account Number: Guardian/Parent: Children: Total Cost: Benefits: Discounts: Nett Payable: Date: Account Number: Guardian/Parent: Children: Total Cost: Benefits: Discounts: Nett Payable: Date: Account Number: Guardian/Parent: Children: Total Cost: Benefits: Discounts: Nett Payable: Todays Date 1234 Jack Smith Mia Smith $100 $nil $nil $100 Todays Date 1235 Chloe Jones William Jones $100 $20 $nil $80 Todays Date 1236 Isabella Williams Lachlan Williams Emily Williams $200 $nil $20 $180 Todays Date 1237 Joshua Smith Olivia Smith Cooper Smith $200 $40 $16 $144

Table 1 - Smith Family Invoice Data

Table 2 - Jones Family Invoice Data

Table 3 - Williams Family Invoice Data

Table 4 - Brown Family Invoice Data

Andrew Cole S3220162

1

CPT230 May 2010

A.2. Test Plan
Test Test No. Name 1 Create a single invoice for a family with one child and no government benefits. Step No. 1.1. 1.2. 1.3. 1.4. 1.5. 1.6. Step Description Log on to the system as a center administrator. Select Invoices -> Create. In the Start Date text box, enter a starting date for the invoices being generated. In the Finish Date text box, enter a finish date for the invoices being generated. In the Accounts list box, select a single family. Click the Create Invoices button. Sample Data CenterAdmin / Password01 January 1, 2010 January 30, 2010 Smith Family One invoice is created and displayed, with the information as per Table 1 Smith Family Invoice Data. The invoice is closed; The main menu is displayed. System logs on; Main menu is displayed. The Create Invoices window appears. Expected Results System logs on; Main menu is displayed. The Create Invoices window appears. Executed

1.7. 2 Create a single invoice for a family with one child and some government benefits. 2.1. 2.2. 2.3. 2.4. 2.5. 2.6.

Click the Close button. Log on to the system as a center administrator. Select Invoices -> Create. In the Start Date text box, enter a starting date for the invoices being generated. In the Finish Date text box, enter a finish date for the invoices being generated. In the Accounts list box, select a single family. Click the Create Invoices button. CenterAdmin / Password01 January 1, 2010 January 30, 2010 Jones Family

2.7.

Click the Close button.

One invoice is created and displayed, with the information as per Table 2 Jones Family Invoice Data. The invoice is closed; The main menu is displayed.
CPT230 May 2010

Andrew Cole S3220162

2

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

Step No. 3.1. 3.2. 3.3. 3.4. 3.5. 3.6.

Step Description Log on to the system as a center administrator. Select Invoices -> Create. In the Start Date text box, enter a starting date for the invoices being generated. In the Finish Date text box, enter a finish date for the invoices being generated. In the Accounts list box, select a single family. Click the Create Invoices button.

Sample Data CenterAdmin / Password01 January 1, 2010 January 30, 2010 Williams Family

Expected Results System logs on; Main menu is displayed. The Create Invoices window appears.

Executed

3.7. 4 Create a single invoice for a family with multiple children and some government benefits. 4.1. 4.2. 4.3. 4.4. 4.5. 4.6.

Click the Close button. Log on to the system as a center administrator. Select Invoices -> Create. In the Start Date text box, enter a starting date for the invoices being generated. In the Finish Date text box, enter a finish date for the invoices being generated. In the Accounts list box, select a single family. Click the Create Invoices button. CenterAdmin / Password01 January 1, 2010 January 30, 2010 Brown Family

One invoice is created and displayed, with the information as per Table 3 Williams Family Invoice Data. The invoice is closed; The main menu is displayed. System logs on; Main menu is displayed. The Create Invoices window appears.

4.7.

Click the Close button.

One invoice is created and displayed, with the information as per Table 4 Brown Family Invoice Data. The invoice is closed; The main menu is displayed.

Andrew Cole S3220162

3

CPT230 May 2010

Test Test No. Name 5 Create and save a single invoice.

Step No. 5.1 5.2 5.3. 5.4. 5.5. 5.6.

Log on to as a administrator. Select Invoices -> Create. In the Start Date text box, enter a starting date for the invoices being generated. In the Finish Date text box, enter a finish date for the invoices being generated. In the Accounts list box, select a single family. Click the Create Invoices button.

Step Description the system

Sample Data center CenterAdmin / Password01 January 1, 2010 January 30, 2010 Brown Family

Expected Results System logs on; Main menu is displayed. The Create Invoices window appears.

Executed

5.7 5.8

Click the Save as PDF button. Navigate to a temporary folder and click the Save button. Click the Close button. Using Windows Explorer, view the above temporary folder.

5.9. 5.10.

One invoice is created and displayed, with the information as per Table 4 Brown Family Invoice Data. The Save as PDF window appears. The Save as PDF window closes; The previously created invoice is still open. The invoice is closed; The main menu is displayed. Invoice-TodaysDate-Brown.pdf exists.

Andrew Cole S3220162

4

CPT230 May 2010

Test Test No. Name 6 Create and save multiple invoices.

Step No. 6.1 6.2 6.3. 6.4. 6.5. 6.6.

Log on to as a administrator. Select Invoices -> Create. In the Start Date text box, enter a starting date for the invoices being generated. In the Finish Date text box, enter a finish date for the invoices being generated. In the Accounts list box, select multiple families. Click the Create Invoices button.

Step Description the system

Sample Data center CenterAdmin / Password01 January 1, 2010 January 30, 2010 Smith Family Williams Family

Expected Results System logs on; Main menu is displayed. The Create Invoices window appears.

Executed

6.7 6.8

Click the Save as PDF button. Navigate to a temporary folder and click the Save button. Click the Close button. Using Windows Explorer, view the above temporary folder.

6.9. 6.10.
Table 5 - User Acceptance Test Plan

Two invoices are created and displayed, with the information as per Table 1 - Smith Family Invoice Data and Table 3 - Williams Family Invoice Data. The Save as PDF window appears. The Save as PDF window closes; The previously created invoice is still open. The invoice is closed; The main menu is displayed. Invoice-TodaysDate-Williams.pdf and Invoice-TodaysDate-Smith.pdf exist.

Andrew Cole S3220162

5

CPT230 May 2010

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

Andrew Cole S3220162

6

CPT230 May 2010

B.1. Waterfall Project Schedule
Activity Business Engineering # 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Task Interviews with customer to determine business requirements Develop Software Requirements Specification for product Review developed SRS against business requirements with customer Develop functional diagrams for product Review developed functional diagrams with customer Establish architecture of product Develop structural diagrams of product Develop beta version Test beta version against SRS and functional diagrams Develop Release Candidate version Update Structural UML Diagrams Develop 1.0 version Test 1.0 version against SRS and Functional Diagrams Deploy 1.0 version of software to customer Duration 3d 1d 1d 1d 1d 1d 1d 3d 1d 1d 2d 1d 1d 1d Dependencies 1 2 3 4 5 6 7 8 9 9 11 12 12, 13

Requirements Analysis & Design Implementation Test Implementation Analysis & Design Implementation Test Deployment
Table 6 - Waterfall Project Schedule

Andrew Cole S3220162

7

CPT230 May 2010

B.2. RUP Project Schedule
Phase Inception Iteration Prelim Activity Business Engineering Requirements Implementation Business Engineering Requirements Analysis & Design Implementation Implementation Test Deployment Business Engineering Requirements Analysis & Design Implementation Test Deployment Business Engineering Requirements Analysis & Design Implementation Test Deployment
Table 7 - Rational Unified Process Project Schedule

# 0.1 0.2 0.3 1.1 1.2 1.3 1.4 2.4 2.5 2.6 3.1 3.2 3.3 3.4.1 3.4.2 3.5 3.6 4.1 4.2 4.3 4.4.1 4.4.2 4.5 4.6

Task Interviews with customer to determine business requirements Develop Software Requirements Specification for product Develop functional diagrams for product Review developed SRS against business requirements with customer Review developed functional diagrams with customer Establish architecture of product Develop structural diagrams of product Develop beta version Test beta version against SRS and functional diagrams Deploy beta version to customer for verification Interviews with customer to confirm function of beta version Update Software Requirements Specification Update Functional UML Diagrams Update Structural UML Diagrams Develop Release Candidate version Test Release Candidate version against SRS and Functional Diagrams Deploy Release Candidate version of software to customer Interviews with customer to confirm function of Release Candidate version Update Software Requirements Specification Update Functional UML Diagrams Update Structural UML Diagrams Develop 1.0 version Test 1.0 version against SRS and Functional Diagrams Deploy 1.0 version of software to customer

Elaboration

1

Construction

2

3

Transition

4

Duration 3d 1d 1d 1d 1d 1.5d 1.5d 3d 1d 1d 1d 0.5d 0.5d 0.5d 1d 0.5d 1d 1d 0.5d 0.5d 0.5d 1d 0.5d 1d

Dependencies 0.1 0.1 0.2 0.3 1.1, 1.2 1.3 1.4 2.4, 1.2, 1.1 2.4 2.6 3.1 3.2 3.1 3.4.1 3.2, 3.3, 3.4.2 3.4.2 3.6 4.1 4.2 4.1 4.4.1 4.2, 4.3, 4.4.2 4.4.2

Andrew Cole S3220162

8

CPT230 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 S3220162

9

CPT230 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 S3220162

10

CPT230 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, <Brian.Leslie@au.unisys.com> 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>

Andrew Cole S3220162

11

CPT230 May 2010

Sign up to vote on this title
UsefulNot useful