printshop workflow automation system rev3sadjadi/teaching/software...fictitious corp. software...

Fictitious Corp. Software Project Plan

Revision 3

Printshop Workflow Automation System

CEN4021 Spring 2010

Professor: Masoud Sadjadi

Paul White

15th April 2010

PWAS Software Project Plan 2/16/2010

2

TABLE OF CONTENTS 1 Overview .................................................................................................................................................................... 4

1.1 Purpose scope and objectives ............................................................................................................................. 4

1.1.1 General Requirements ................................................................................................................................ 4

1.2 Assumptions and constraints. ............................................................................................................................. 4

1.2.1 Assumptions ............................................................................................................................................... 4

1.2.2 Time Constraints ........................................................................................................................................ 4

1.2.3 Budget Constraints ..................................................................................................................................... 5

1.3 Project deliverables ............................................................................................................................................ 5

1.3.1 External deliverables .................................................................................................................................. 5

1.3.2 Internal Deliverables ................................................................................................................................... 5

1.4 Schedule and budget summary ........................................................................................................................... 7

1.4.1 Deliverables and Milestones ....................................................................................................................... 7

1.5 Overview of the document ................................................................................................................................. 7

2 Definitions, acronyms, and abbreviations .................................................................................................................. 8

3 Project Organization ................................................................................................................................................... 9

3.1 Project Personnel ................................................................................................................................................ 9

3.2 Roles and Responsibilities .................................................................................................................................. 9

3.2.1 Project Manager .......................................................................................................................................... 9

3.2.2 Administrative Assistant ............................................................................................................................. 9

3.2.3 Requirements Analyst ................................................................................................................................. 9

3.2.4 Software Architect .................................................................................................................................... 10

3.2.5 Software Developers ................................................................................................................................. 10

3.2.6 Technical Writer ....................................................................................................................................... 10

3.2.7 Test Analyst .............................................................................................................................................. 10

4 Managerial process plans ......................................................................................................................................... 11

4.1 Start-up ............................................................................................................................................................. 11

4.1.1 Estimation ................................................................................................................................................. 11

4.1.2 Staffing ..................................................................................................................................................... 13

4.1.3 Resource Acquisition ................................................................................................................................ 14

4.2 Work planning .................................................................................................................................................. 14

4.2.1 Work activities .......................................................................................................................................... 14


3

4.2.2 Schedule allocation (task allocation) ........................................................................................................ 14

4.2.3 Budget allocation ...................................................................................................................................... 14

4.3 Project Controls ................................................................................................................................................ 15

4.3.1 Requirements control ................................................................................................................................ 15

4.3.2 Schedule control ....................................................................................................................................... 15

4.3.3 Budget control .......................................................................................................................................... 15

4.3.4 Quality control .......................................................................................................................................... 15

4.3.5 Project Reporting ...................................................................................................................................... 15

4.3.6 Metrics collection (metrics for schedule integrity, functional completeness, budget, and product quality) 15

4.4 Risk management plan...................................................................................................................................... 17

4.4.1 Description of Risks ................................................................................................................................. 17

5 Technical process plans ............................................................................................................................................ 17

5.1 Process model (provide adequate and detailed justification for process choice) .............................................. 17

5.2 Methods tools and techniques ........................................................................................................................... 17

6 Appendices ............................................................................................................................................................... 18

6.1 Appendix A - Project Schedule ........................................................................................................................ 18

6.2 Appendix B - Job Descriptions ......................................................................................................................... 26

6.2.1 Project Manager ........................................................................................................................................ 26

6.2.2 Administrative Assistant ........................................................................................................................... 29

6.2.3 Requirements Analyst ............................................................................................................................... 31

6.2.4 Software Architect .................................................................................................................................... 31

6.2.5 Software Developer .................................................................................................................................. 34

6.2.6 Technical Writer ....................................................................................................................................... 37

6.2.7 Test Analyst .............................................................................................................................................. 39


4

1 OVERVIEW The client, XYZ Printing CO., needs a system to help automate the customer order submission, employee workflow and management activities for a “gang run” print shop

1.1 PURPOSE SCOPE AND OBJECTIVES The main purpose of PWAS is to help automate the customer order submission, employee workflow and management activities for the XYZ Printing Co. This will enhance productivity and efficiency by:

Allowing customers to submit and track their orders online Minimize the amount of paper work and manual data entry required Providing a central system for receiving, organizing, and scheduling orders

1.1.1 GENERAL REQUIREMENTS The following general requirements were specified for the proposed system:

The system shall allow customers to place and track orders, utilizing a payment method of their choice.

The system shall allow customers to view their order history and account information. The system shall allow employees to organize, track and complete customer orders. The system shall allow administrators to manage user accounts, customer orders and

printing properties. The system shall have user access control for security and access differentiation.

The requirements will be defined and analyzed completely in the Software Requirements Specification, one of the project deliverables.

1.2 ASSUMPTIONS AND CONSTRAINTS.

1.2.1 ASSUMPTIONS For this project plan we assume that the Requirements Analysis Document has already

been completed and has been approved by XYZ Printing Co. The personnel resources necessary for the project will be hired through Fictitious Corp.

human resources.

1.2.2 TIME CONSTRAINTS


5

All deliverables must be submitted to XYZ Printing as detailed in the Schedule & Budget Summary section of this document.

1.2.3 BUDGET CONSTRAINTS XYZ Printing Co. has agreed to pay a fixed sum at the completion of the proposed system. The proposed system will be determined as complete once the deliverables as described in the Project Deliverables section of this document have been completed and delivered to XYZ Printing Co.. Any changes requested by XYZ Printing Co. to the proposed system requirements after user acceptance of the Software Requirements Specification by XYZ Printing Co. will be considered a change request and will carry additional costs. The cost of implementing a change request will be determined at the time of the request based on the size and complexity of the change.

1.3 PROJECT DELIVERABLES

1.3.1 EXTERNAL DELIVERABLES The following items will be delivered to XYZ Printing Co. according to the time table in the Schedule and Budget Summary section of this document:

Requirements Analysis Document - Lists the client and contractor approved functional and non-functional requirements that the proposed system must accomplish to be determined complete. Will be provided as an Adobe Acrobat PDF file emailed to the XYZ Printing Co. POC.

Executable Code - The set of all files and data needed for XYZ Printing Co. to operate the proposed system on their own computer systems. Will be provided as a Windows compatible CD-ROM disk.

User’s Guide - The User Guide is a printable document that details how to install and operate the proposed system. Will be provided as an Adobe Acrobat PDF file emailed to the XYZ Printing Co. POC.

1.3.2 INTERNAL DELIVERABLES The following are the internal deliverables that will not be submitted to the client, but will be used for internal measurement and tracking of progress.

Project Plan - This document, which outlines the plan for this software project. Quality Assurance Plan – Documents the plan for the systematic monitoring and

evaluation of the various aspects the project to ensure that standards of quality are being met. The Quality Assurance Plan defines processes and standards to follow during the development process such as requirements definition, software design, coding, source code


6

control, code reviews, change management, configuration management, testing, release management, and product integration.

Test Scenarios & Test Data – Built from the RAD, defines the set of scenarios and sample data which can be used to verify that the proposed system meets the requirements.

Design Document – Created by the Software Architect, documents the design for the program and database and all associated systems for the project.

QA Test Reports – Report of the current status of the quality of the software and if it meets the goals defined in the Quality Assurance Plan.

Source Code – The source code is the implementation of the design, written by the Software Developers and tested by the Test Analysts.

User Acceptance Report – Once the User Acceptance Report has been completed and the client agrees that the project has been completed and meets the requirements the project is complete and enters the Maintenance phase.

Change Requests – Once the project has entered the Maintenance phase, any feature requests or changes must be submitted as a change request and is outside the scope of the original project.


7

1.4 SCHEDULE AND BUDGET SUMMARY

1.4.1 DELIVERABLES AND MILESTONES

Client Deliverable Internal Deliverable Milestone

Stage of Development

Stage Completion Date

Deliverable Deliverable Completion Date

Requirements Definition

2/01/2010 Requirements Analysis Document Final Complete Stage Completion

Planning 3/22/2010 Project Plan 3/15/2010 Quality Assurance Plan 3/22/2010 Stage Completion 3/22/2010

Design 4/12/2010

Draft Design Document 4/8/2010 Test Scenarios & Test Data 4/10/2010 Design Document Final 4/12/2010 Stage Completion 4/12/2010

Development 6/21/2010 Draft Source Code 6/20/2010 User Guide 6/21/2010 Stage Completion 6/21/2010

QA & Testing 7/20/2010 QA Test Reports 7/16/2010 Source Code Final 7/20/2010 Stage Completion 7/20/2010

Installation & Acceptance

8/10/2010

Executable Code Final 7/30/2010 User Guide Final 7/30/2010 User Acceptance Report 8/10/2010 Stage Completion 8/10/2010

Maintenance Never Change Requests Never Stage Completion Never

1.5 OVERVIEW OF THE DOCUMENT


8

2 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS Administrator: A member of the company, who has all the rights of a regular Employee plus

other administrative rights such as deleting a user, editing a user's information, etc. Customer: A client of the company, who can submit orders for printing, pay those orders, and

track the orders as well. Company: Specifically, XYZ Printing Co. Customer Service: A member of the company who can take an order on behalf of a customer

– to act as a proxy for an offline customer. Worker: A member of the company, who has all the rights of any User plus other rights such as

create print runs, add orders to print runs, etc. Finishing: The part of the company workflow where the cutting and resizing process is taking

place. Order: A User can create an order and save it into the system, which contains specifications

regarding printing details, a file to be printed, and payment information. POC: Point of contact Portal: Web-based interface presented to customer and employees. Printing: The part of the company workflow where the print-manufacturing process is taking

place. Print Run: A single file created by an employee, which is sent to printing. PWAS: Printshop Workflow Automation System, the name of the proposed system System: PWAS is considered the system, and it entails all the software that takes care of the

workflow management.


9

3 PROJECT ORGANIZATION

3.1 PROJECT PERSONNEL Job Title Number Needed

Project Manager 1

Administrative Assistant 1

Requirements Analyst 1

Software Architect 1

Software Developer 3

Technical Writer 1

Test Analyst 1

3.2 ROLES AND RESPONSIBILITIES The general duties and responsibilities for the required personnel are described below. A complete job description to be used for resource acquisition can be found in the Appendix.

3.2.1 PROJECT MANAGER The Project Manager is overall in charge of the project and is the main POC for the client, XYZ Printing Co. Some of the Project Manager’s responsibilities include:

Developing the project plan Communicating with the project stakeholders Managing the project team Managing the project risk Managing the project schedule Managing the project budget Managing the project conflicts

3.2.2 ADMINISTRATIVE ASSISTANT The Administrative Assistant will provide administrative support to the project team and/or Manager. Duties include general clerical, receptionist and project based work. Project a professional company image through in-person and phone interaction.

3.2.3 REQUIREMENTS ANALYST


10

The Requirements Analyst is responsible for eliciting, analyzing, and recording the functional requirements and the non-functional requirements. Some responsibilities of the Requirements Analyst include:

Conducting interviews with the client during requirements elicitation Developing use cases and scenarios for the proposed system Developing the Software Requirements Specification

3.2.4 SOFTWARE ARCHITECT The Software Architect is responsible for designing the software solution for the proposed system. They will report to the Project manager. Some responsibilities of the Software Architect include:

Designing the overall architecture of the software and database scheme Choosing the Development Process Model for the project Recording the proposed system design in Unified Modeling Language Developing the Design Document

3.2.5 SOFTWARE DEVELOPERS Software Developers are responsible for implementing the design as specified by the Software Architect. The Software Developer will develop the algorithms, and write the source code for the proposed system. A Senior level Software Developer will manage two lower level developers and will assign them tasks.

3.2.6 TECHNICAL WRITER The Technical Writer will develop the documentation associated with the software solution. This includes the User Guide, Help System, and Installation Guide.

3.2.7 TEST ANALYST Responsible for identifying and defining the required tests, monitoring detailed testing progress and results in each test cycle and evaluating the overall quality experienced as a result of testing activities.


11

4 MANAGERIAL PROCESS PLANS

4.1 START-UP

4.1.1 ESTIMATION For this project used time, effort, and cost estimations from previous projects completed by Fictitious Corp as a baseline. Factoring in the complexity of this project we obtain the following estimate of work.

Task Name Work

PWAS Project 1,428 hrsRequirements Definition 8 hrs

Determine project scope 8 hrsScope complete 0 hrs

Planning 112 hrsPreliminary Project Plan 40 hrsBegin requests for personnel 24 hrsPreliminary Quality Assurance Plan 32 hrsResource Acquisition 16 hrs

Design 80 hrsReview preliminary software specifications 8 hrsDevelop design specifications 40 hrs

Subsystem Decomposition 4 hrsHardware/Software Mapping 4 hrsPersistent Data Management 4 hrsAccess Control & Security 4 hrsGlobal Software Control 4 hrsBoundary Conditions 4 hrsObject Design Trade-offs 4 hrsPackaging 4 hrsClass Interfaces 8 hrs

Review design specifications 16 hrsIncorporate feedback into design specifications 8 hrsObtain approval to proceed 8 hrsDesign complete 0 hrs


12

Development 508 hrsReview design specifications 4 hrsIdentify modular/tiered design parameters 16 hrsAssign development staff 16 hrsDevelop code 288 hrsDeveloper testing (primary debugging) 184 hrsDevelopment complete 0 hrs

Testing 232 hrsDevelop unit test plans using product specifications 16 hrsDevelop integration test plans using product specificati 16 hrsUnit T esting 112 hrs

Review modular code 40 hrsTest component modules to product specifications 16 hrsIdentify anomalies to product specifications 24 hrsModify code 16 hrsRe-test modified code 16 hrsUnit testing complete 0 hrs

Integration Testing 88 hrsTest module integration 40 hrsIdentify anomalies to specifications 16 hrsModify code 16 hrsRe-test modified code 16 hrsIntegration testing complete 0 hrs

Documentation 384 hrsDevelop Help specification 8 hrsDevelop Help system 120 hrsReview Help documentation 48 hrsIncorporate Help documentation feedback 16 hrsDevelop user manuals specifications 24 hrsDevelop user manuals 120 hrsReview all user documentation 32 hrsIncorporate user documentation feedback 16 hrsDocumentation complete 0 hrs


13

4.1.2 STAFFING Table below shows the number of staff necessary during the different stages of the project according to the work break down structure.

Personnel Needed

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

Project Manager

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

Administrative Assistant

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

Requirements Analyst

1

Software Architect

1 1 1

Developers

1 1 3 3 3 3 1 1 1 1 1 1 1

Technical Writer

1 1 1 1 1 1 1 1

Test Analyst 1 1 1 1 1

pPilot 80 hrs

Identify test group 16 hrsDevelop software delivery mechanism 8 hrsInstall/deploy software 8 hrsObtain user feedback 40 hrsEvaluate testing information 8 hrsPilot complete 0 hrs

Deployment 24 hrsDetermine final deployment strategy 8 hrsDevelop deployment methodology 8 hrsDeploy software 8 hrsDeployment complete 0 hrs


14

4.1.3 RESOURCE ACQUISITION Human resources will be notified to hire consultants according to people hiring matrix below.

Week/ Staff

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

Project Manager

X X X X X X X X X X X X X X X X X

Administrative Assistant

X X X X X X X X X X X X X X X X

Requirements Analyst

X

Software Architect

X X X

Snr. Software Developer

X X X X X X X X X X X X X


X X X X


X X X X

Technical Writer

X X X X X X X X

Test Analyst X X X X X

4.2 WORK PLANNING

4.2.1 WORK ACTIVITIES See Appendix A for the full work breakdown structure and schedule.

4.2.2 SCHEDULE ALLOCATION (TASK ALLOCATION)

4.2.3 BUDGET ALLOCATION Below is detailed the cost for the personnel resources for this project. The rate for each employee is derived from current stand wages as determined by Fictitious Corp human resources.

Employee Work hrs Rate/hr Cost

Project manager 228.00 $50.00 $11,400.00

Analyst 0.00 $45.00 $0.00

16967

Typewritten Text

See Appendix A - Project Schedule


15

Snr. Software Developer 252.00 $50.00 $12,600.00

Software Developer 1 160.00 $45.00 $7,200.00

Software Developer 2 160.00 $45.00 $7,200.00

Software Architect 48.00 $55.00 $2,640.00

Test Analyst 200.00 $50.00 $10,000.00

Technical Writer 344.00 $40.00 $13,760.00

4.3 PROJECT CONTROLS

4.3.1 REQUIREMENTS CONTROL Any changes to the requirements by the customer must be reviewed by the project manager to determine if they are within the original scope of the agreement. Any change to the requirements by team members must be reviewed by the project manager and communicated to the customer if the change affects the user experience.

4.3.2 SCHEDULE CONTROL Daily status reports will be utilized to collect metrics to check for schedule integrity. The details of the metrics being collected is detailed in section 4.3.6 Metrics Collection.

Should the metrics show that the team is falling behind schedule corrective measures will be taken. This may include requiring additional working hours from personnel, reassignment of tasks to other personnel or additional resources assigned to the lagging task(s).

4.3.3 BUDGET CONTROL Any changes to the budgeted costs associated with the project must be reviewed with the Project Manager and company Management. This includes requests for additional resources(personnel or otherwise), overtime, etc…

4.3.4 QUALITY CONTROL To ensure that the customer requirements are being met weekly meetings will be held with the customer as well as regular email contacts.

Peer code review will be performed throughout the development process to ensure that all code is documented well for future extensibility as well as to check for correctness and efficiency.

4.3.5 PROJECT REPORTING

4.3.6 METRICS COLLECTION (METRICS FOR SCHEDULE INTEGRITY, FUNCTIONAL

COMPLETENESS, BUDGET, AND PRODUCT QUALITY)


16

The following forms will be filled out daily by the appropriate groups during the different stages of the project to ensure schedule integrity, functional completeness, budget, and product quality.

Status report – Design Tasks (indicate the percent complete / hours worked / roadblocks) Subsystem Decomposition: Hardware/Software Mapping: Persistent Data Management: Access Control & Security: Global Software Control: Boundary Conditions: Object Design Trade-offs: Packaging: Class Interfaces: Status report – Development Tasks (indicate the name of each module worked on / percent complete / hours worked / roadblocks) Module 1 name: Module 2 name: Module 3 name: Module # name: Peer code review: (indicate the modules you reviewed today and indicate if quality goal was met) Status report – Testing Reported problems Problem level Problems found Problems closed High Medium Low


17

4.4 RISK MANAGEMENT PLAN

4.4.1 DESCRIPTION OF RISKS Business Impact Risk: If the software produced does not achieve its goals or meet the requirements of the customer. Customer Risks: Unwillingness of the client to help the software development team. If the client fails to attend meeting regularly and fails to respond to requests for information in regards to the requirements of the system. Development Risks: Error in estimation of difficulty, problems in design and implementation which could impact the project’s schedule integrity. Employee Risk: Unplanned loss of an employee due to various reasons can affect the project schedule, as well as inability of the employee to complete a given task in the given time. Product Size: Misjudgment on behalf of the customer or the software development team. If the customer fails to provide the represent the requirements of the product that is to be developed it will cause major problems for the completion of the project. If software development team misjudges the size and scope of the project, team may be too small or large for the project thus going over budget or not finishing project at all because of shortage of finances.

5 TECHNICAL PROCESS PLANS Introduce the technical process plans (one or two paragraphs).

5.1 PROCESS MODEL (PROVIDE ADEQUATE AND DETAILED JUSTIFICATION FOR PROCESS

CHOICE)

5.2 METHODS TOOLS AND TECHNIQUES


18

6 APPENDICES

6.1 APPENDIX A - PROJECT SCHEDULE See next page.

ID Task Name Duration Start Finish Predecessors

0 PWAS Project 90 days Tue 2/2/10 Mon 6/7/101 Requirements Definition 1 day Tue 2/2/10 Tue 2/2/10

2 Determine project scope 1 day Tue 2/2/10 Tue 2/2/10

3 Scope complete 0 days Tue 2/2/10 Tue 2/2/10 2

4 Planning 14 days Wed 2/3/10 Mon 2/22/10

5 Preliminary Project Plan 5 days Wed 2/3/10 Tue 2/9/10 3

6 Begin requests for personnel 3 days Wed 2/10/10 Fri 2/12/10 5

7 Preliminary Quality Assurance Plan 4 days Mon 2/15/10 Thu 2/18/10 6

8 Resource Acquisition 2 days Fri 2/19/10 Mon 2/22/10 7

9 Design 9.5 days Tue 2/23/10 Mon 3/8/10

10 Review preliminary software specifications 1 day Tue 2/23/10 Tue 2/23/10 8

11 Develop design specifications 5 days Wed 2/24/10 Tue 3/2/10 10

12 Subsystem Decomposition 0.5 days Wed 2/24/10 Wed 2/24/10 10

13 Hardware/Software Mapping 0.5 days Wed 2/24/10 Wed 2/24/10 12

14 Persistent Data Management 0.5 days Thu 2/25/10 Thu 2/25/10 13

15 Access Control & Security 0.5 days Thu 2/25/10 Thu 2/25/10 14

16 Global Software Control 0.5 days Fri 2/26/10 Fri 2/26/10 15

17 Boundary Conditions 0.5 days Fri 2/26/10 Fri 2/26/10 16

18 Object Design Trade-offs 0.5 days Mon 3/1/10 Mon 3/1/10 17

19 Packaging 0.5 days Mon 3/1/10 Mon 3/1/10 18

20 Class Interfaces 1 day Tue 3/2/10 Tue 3/2/10 19

21 Review design specifications 2 days Wed 3/3/10 Thu 3/4/10 11

22 Incorporate feedback into design specifications 1 day Fri 3/5/10 Fri 3/5/10 21

23 Obtain approval to proceed 4 hrs Mon 3/8/10 Mon 3/8/10 22

24 Design complete 0 days Mon 3/8/10 Mon 3/8/10 23

25 Development 24.5 days Mon 3/8/10 Fri 4/9/10

26 Review design specifications 0.5 days Mon 3/8/10 Mon 3/8/10 24

27 Identify modular/tiered design parameters 2 days Tue 3/9/10 Wed 3/10/10 26

28 Assign development staff 2 days Thu 3/11/10 Fri 3/12/10 27

29 Develop code 16 days Mon 3/15/10 Mon 4/5/10 28

30 Developer testing (primary debugging) 12 days Thu 3/25/10 Fri 4/9/10 29FS-50%

31 Development complete 0 days Fri 4/9/10 Fri 4/9/10 30

32 Testing 34 days Mon 3/15/10 Thu 4/29/10

33 Develop unit test plans using product specifications 2 days Mon 3/15/10 Tue 3/16/10 24

34 Develop integration test plans using product specifications 2 days Wed 3/17/10 Thu 3/18/10 33

35 Unit Testing 15 days Thu 3/25/10 Wed 4/14/10

36 Review modular code 5 days Thu 3/25/10 Wed 3/31/10 33,29FS-50%

37 Test component modules to product specifications 2 days Thu 4/1/10 Fri 4/2/10 36

38 Identify anomalies to product specifications 3 days Mon 4/5/10 Wed 4/7/10 37

Management

2/2

S M T W T FJan 31, '10

Task

Split

Progress

Milestone

Summary

Project Summary

External Tasks

External Milestone

Deadline

Page 1

Project: PWAS ProjectDate: Thu 4/22/10

ID Task Name Duration Start Finish Predecessors

39 Modify code 3 days Thu 4/8/10 Mon 4/12/10 38

40 Re-test modified code 2 days Tue 4/13/10 Wed 4/14/10 39

41 Unit testing complete 0 days Wed 4/14/10 Wed 4/14/10 40

42 Integration Testing 11 days Thu 4/15/10 Thu 4/29/10

43 Test module integration 5 days Thu 4/15/10 Wed 4/21/10 41

44 Identify anomalies to specifications 2 days Thu 4/22/10 Fri 4/23/10 43

45 Modify code 2 days Mon 4/26/10 Tue 4/27/10 44

46 Re-test modified code 2 days Wed 4/28/10 Thu 4/29/10 45

47 Integration testing complete 0 days Thu 4/29/10 Thu 4/29/10 46

48 Documentation 46 days Fri 3/19/10 Fri 5/21/10

49 Develop Help specification 1 day Fri 3/19/10 Fri 3/19/10 24

50 Develop Help system 15 days Thu 3/25/10 Wed 4/14/10 49,29FS-50%

51 Review Help documentation 3 days Thu 4/15/10 Mon 4/19/10 50

52 Incorporate Help documentation feedback 2 days Tue 4/20/10 Wed 4/21/10 51

53 Develop user manuals specifications 3 days Thu 4/22/10 Mon 4/26/10 52

54 Develop user manuals 3 wks Tue 4/27/10 Mon 5/17/10 53

55 Review all user documentation 2 days Tue 5/18/10 Wed 5/19/10 54

56 Incorporate user documentation feedback 2 days Thu 5/20/10 Fri 5/21/10 55

57 Documentation complete 0 days Fri 5/21/10 Fri 5/21/10 56,52

58 Pilot 8 days Mon 5/24/10 Wed 6/2/10

59 Identify test group 2 days Mon 5/24/10 Tue 5/25/10 57

60 Develop software delivery mechanism 1 day Mon 5/24/10 Mon 5/24/10 57

61 Install/deploy software 1 day Tue 5/25/10 Tue 5/25/10 47,60,57

62 Obtain user feedback 1 wk Wed 5/26/10 Tue 6/1/10 61

63 Evaluate testing information 1 day Wed 6/2/10 Wed 6/2/10 62

64 Pilot complete 0 days Wed 6/2/10 Wed 6/2/10 63

65 Deployment 3 days Thu 6/3/10 Mon 6/7/10

66 Determine final deployment strategy 1 day Thu 6/3/10 Thu 6/3/10 64

67 Develop deployment methodology 1 day Fri 6/4/10 Fri 6/4/10 66

68 Deploy software 1 day Mon 6/7/10 Mon 6/7/10 67

69 Deployment complete 0 days Mon 6/7/10 Mon 6/7/10 68

S M T W T FJan 31, '10

Task

Split

Progress

Milestone

Summary

Project Summary

External Tasks

External Milestone

Deadline

Page 2


nt

Project manager

Project manager

Project manager

Project manager

Software Architect

Software Architect

Software Architect

Software Architect

Software Architect

Software Architect

Software Architect

Software Architect

Software Architect

Software Architect

Management

Management

Management,Project manager

3/8




Test Analyst

Test An

S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F SFeb 7, '10 Feb 14, '10 Feb 21, '10 Feb 28, '10 Mar 7, '10 Mar 14, '10

Task

Split

Progress

Milestone

Summary

Project Summary

External Tasks

External Milestone

Deadline

Page 3


Tec

S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F SFeb 7, '10 Feb 14, '10 Feb 21, '10 Feb 28, '10 Mar 7, '10 Mar 14, '10

Task

Split

Progress

Milestone

Summary

Project Summary

External Tasks

External Milestone

Deadline

Page 4


Snr. Software Developer,Software Developer 1,Software Developer 2

Software Developer 1,Software Developer 2,Snr. Software Developer

4/9

nalyst

Test Analyst

Test Analyst

Test Analyst

S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S SMar 21, '10 Mar 28, '10 Apr 4, '10 Apr 11, '10 Apr 18, '10 Apr 25, '10 May

Task

Split

Progress

Milestone

Summary

Project Summary

External Tasks

External Milestone

Deadline

Page 5



Test Analyst

4/14

Test Analyst

Test Analyst

Snr. Software Develo

Test Analyst

4/29

chnical Writer

Technical Writer

Technical Writer,Project manager

Technical Writer

Technical Writer

S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S SMar 21, '10 Mar 28, '10 Apr 4, '10 Apr 11, '10 Apr 18, '10 Apr 25, '10 May

Task

Split

Progress

Milestone

Summary

Project Summary

External Tasks

External Milestone

Deadline

Page 6


M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M 2, '10 May 9, '10 May 16, '10 May 23, '10 May 30, '10 Jun 6, '10 Jun 13, '

Task

Split

Progress

Milestone

Summary

Project Summary

External Tasks

External Milestone

Deadline

Page 7


oper

t

Technical Writer

Technical Writer,Project manager

Technical Writer

5/21

Project manager



Project manager

Project manager

6/2

Project manager



6/7

M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M 2, '10 May 9, '10 May 16, '10 May 23, '10 May 30, '10 Jun 6, '10 Jun 13, '

Task

Split

Progress

Milestone

Summary

Project Summary

External Tasks

External Milestone

Deadline

Page 8



26

6.2 APPENDIX B - JOB DESCRIPTIONS

6.2.1 PROJECT MANAGER Under direction, applies technical expertise and project management experience to manage project teams on conventional and unconventional projects. Also performs the basic project functions of production coordination, planning, organizing, directing, controlling, financial management and marketing assistance. Functions as a mentor to associate project managers and technical professionals to assist in their technical training and development.

Job Duties

- Coordinates and participates in contract negotiations with clients and subcontractors, and drafts complex professional service agreements and addenda for review by senior management.

- Directs project team and client compliance with contract terms and monitors subcontractors' compliance with contractual commitments.

- Prepares project work plan, scope, schedule and budget, and communicates these to project team members; monitors/manages project production for compliance with schedule, budget and quality objectives.

- Monitors reports and schedules to ensure appropriate charging of manhours, costs and expenses to projects, and to communicate project progress/status to senior management.

- Establishes and maintains project account files on the computerized project management information system, and periodically reviews project reports for accuracy and completeness.

- Monitors client billings, assists in obtaining payment from clients, and resolves client disputes, adjusting project billing records as required.


27

- Monitors subconsultants' progress and performance, reviews and approves subconsultant and vendor invoices, and resolves payment and project disputes.

- Schedules and coordinates project meetings with the project team, regulatory agencies, the client, and others involved with the projects.

- Reports financial status of projects to technical managers.

- Identifies new business opportunities for the firm, coordinates and participates in project presentations to clients and other external groups, and promotes firm's capabilities, marketing its services among existing and prospective clients.

- Participates in project opportunity evaluation, consultant selection, and the preparation of firm's qualification/experience statements.

- May supervise technical professionals, associate project managers and design staff including workload and staffing management.

- Performs such other duties as the supervisor may from time to time deem necessary.

Scope

Complexity (Variety or uniqueness of tasks; relative difficulty or importance of work performed; size of unit supported, etc.):

Project management assignments at this level typically involve routine projects, characterized by changing conditions and requirements, challenging client/agency demands, or difficult project coordination.

Decision-making (Supervision received; independent judgment or initiative; consequence of error):

Supervision and guidance relate largely to overall objectives, critical issues and policy matters. Consults with supervisor concerning unusual problems and developments. Participates in project "go/no go" and consultant selection decisions. Selects/reviews project sub consultants and vendor invoices.

Work direction given to others (Titles and number of personnel; type of direction


28

given):

Guides, reviews, supervises and/or coordinates the work of a multi-disciplinary project team.

Internal contacts (Required interaction/relationship with others within the organization):

Interfaces with senior technical professionals, technical managers, and administrative staff and managers as necessary.

External Contacts (Required interaction/relationship with others outside the organization):

Represents the organization to clients, regulatory agencies and the general public. Maintains contact and visibility within professional, civic, and other organizations to promote the firm and elicit new business.

Minimal Requirements

Education and experience:

Bachelor's degree in field(s) of practice. Graduate degree desirable. Management coursework and/or MBA a plus. This level may be achieved with 8 years experience in project production and technical professional activities, two of these working as a Sr. Technical Professional or Associate Project Manager.

SPECIAL SKILLS

Strong interpersonal skills; good public speaking ability; strong project financial management skills; knowledge of production support systems and personal computer proficiency.

Competencies:

General Competencies expected of all Professionals and Managers are as follows: Client Service, Commitment, Communication, Innovation & Continuous Improvement,


29

Professionalism, Quality, and Teamwork.

Other :

Ability to process paper/electronic documents and utilize computer equipment; ability to communicate effectively both orally and in writing; ability to visit project sites if necessary. Job also requires ability to plan, prioritize and review project plans and documents, evaluate alternatives, and devise appropriate solutions. Ability to work under the pressure of multiple projects.

6.2.2 ADMINISTRATIVE ASSISTANT Provides basic secretarial and clerical support to team of professionals and managers. May function as a receptionist for department or office and be responsible for collecting, sorting and distributing mail to department or office personnel.

Job Duties

- Types forms, letters, memos and other documents from written sources and/or transcription tapes, using personal computer and appropriate word processing software.

- Answers phones and transmits messages.

- Opens, date stamps, sorts and distributes incoming mail.

- Files documents and correspondence.

- Makes travel and meeting arrangements, as instructed.

- Makes photocopies and sends or receives e-mails, fax transmissions and other electronic communications.

- Maintains recurring internal reports, such as timesheets, overtime logs, etc.

- May do light bookkeeping and other basic accounting-related or project-related tasks.


30

- Performs such other duties as the Supervisor may from time to time deem necessary.

Scope


Applies basic skills to somewhat varied tasks, usually following standard procedures.


Work is performed under close supervision and is usually reviewed for errors.

Work direction given to others (Titles and number of personnel; type of direction given):

No work direction given to others.


Internal contacts usually consist of local office personnel.

External contacts (Required interaction/relationship with others outside the organization):

External contacts with clients, contractors and governmental agency personnel are usually limited to taking or relaying messages. May contact vendors and delivery personnel to obtain supplies or services.

Minimal Requirements


High school with secretarial and/or business coursework or equivalent training/experience. Two years of secretarial/clerical experience.

Special skills:


31

Good command of English grammar and spelling. Basic organizational skills. Minimum word processing speed of 45 wpm. Basic knowledge of MS Word, Outlook and Excel.

Professional registrations:

None

Competencies

General Competencies expected of all employees are as follows: Client Service,Commitment, Communication, Innovation & Continuous Improvement, Professionalism, Quality and Teamwork. (Note that "Clients" may be internal managers and staff.)

Other

Job requires ability to process paper/electronic documents and operate computer keyboard. Ability to retrieve and file folders. Ability to communicate effectively, both verbally and in written form.

6.2.3 REQUIREMENTS ANALYST The Requirements Analyst is responsible for eliciting, analyzing, and recording the functional requirements and the non-functional requirements. Some responsibilities of the Requirements Analyst include:

Conducting interviews with the client during requirements elicitation Developing use cases and scenarios for the proposed system Developing the Software Requirements Specification

6.2.4 SOFTWARE ARCHITECT Lead in the creation, enhancement, and maintenance of database-driven transactional web application architectures, using all facets of the systems development lifecycle. Multi-disciplinary technical role which requires strong object-oriented design skills, relational database design skills and Web application architecture framework skills. Understand and consistently apply the attributes and processes of current application development methodologies.

Job Duties


32

- Leads technical design and development of application/database systems using existing and emerging technology platforms.

- Develops programming and development standards and procedures as well as programming architectures for code reuse.

- Has in-depth knowledge of state-of-the-art programming languages and object-oriented approaches in designing, coding, testing and debugging programs.

- Designs the end-to-end architecture of the Core Services, Application Services, Presentation Services, and Security Layer components.

- Proposes database architectures, working closely with Sr/Lead Developer and Database Administrator to ensure that database efficiency, performance and tuning practices are ongoing.

- Analyzes application/database systems and defines actions necessary to change logic functions; produces specifications to solve application problems.

- Develops enterprise level application and custom integration solutions including major enhancements and interfaces, functions and features.

- Determines specifications, then plans, designs and develops the most complex and business critical software solutions, utilizing appropriate software engineering processes.

- Assists in the most difficult support problems, serving as the lead technical expert.

- Performs other such duties as the supervisor may from time to time deem necessary.

Scope


Work consists of design, development, documentation, analysis, creation, testing


33

and modification of applications and database systems or programs, using existing and emerging technologies.


Consistently exercises independent judgment on regular assignments, analyzing problems and selecting solutions. Proposals and recommendations for database/application architectures are regularly viewed as knowledgeable and given considerable weight.


May supervise a group of application developers and/or report writers.


Regular interaction with clerical, professional, and management staff in same or other departments.


Vendors and Contractors as necessary.

Minimum Requirements


Bachelor of Science degree in related major or equivalent combination of formal education and experience. Seven years of solid experience with application architectures, software development and infrastructure, systems integration, package implementation, and interaction design. Experience in relational database design and modeling is required. Strong background in software configuration, change management and performance tuning. Proven experience in securing internet web applications.

Special skills:


34

Excellent object-oriented analysis design skills and knowledge of UML required. Expertise required with Visual Studio, Visual Interdev 6.0, and Visual SourceSafe administration, COM and COM+, as well as the following software and programs: ASP, JavaScript, VB, XML/XSL, Access, SQL Server, .NET, Security, Networking, Windows 95/98/2000/XP. Knowledge and understanding of Unified Dimensional Modeling (UDM). Requires advanced to expert level knowledge and understanding of architecture, application systems designs and integration.

Professional registrations

None.

Competencies

General Competencies expected of all Professionals and Managers are as follows: Client Service, Commitment, Communication, Innovation & Continuous Improvement, Professionalism, Quality, and Teamwork.

Other

Job requires ability to access and understand technology materials and ability to operate computer keyboard. Ability to communicate clearly both orally and in writing. Must be able and willing to deal with interruptions in current work in progress to handle priority jobs. Overtime work is required as workload and deadlines demand.

6.2.5 SOFTWARE DEVELOPER Applies full competency in software development, demonstrating broad knowledge of current database technology and computer systems. Under direction, plans and implements software development solutions to detailed phases of major projects. Duties at this level require mastery of specialized techniques, ingenuity, and ability to apply an analytical approach to the solution of a wide variety of problems.

Job Duties

- Develops customized applications or modifies existing applications through documented code in the applicable environment.

- Recommends solutions to problems.


35

- Conducts database design, conversion, and assembly of data in a variety of formats.

- Prepares data documentation or metadata for application development projects.

- Participates in and/or conducts client needs analyses.

- Monitors and coordinates quality control efforts and/or provides direction on quality control efforts within area of responsibility.

- Develops and evaluates plans and criteria in terms of quality assurance and quality control.

- Maintains continued knowledge of technology developments in the field and use of applicable programming languages.


Scope

Complexity (variety or uniqueness of tasks; relative difficulty or importance of work performed; size of unit supported, etc.):

Performs work which involves conventional practice but may include a variety of complex features such as conflicting client needs, unsuitability of available software programs or conventional solutions, or difficult coordination requirements.

Decision-making (supervision received; independent judgment or initiative; consequence of error):

Most assignments are performed independently, making decisions on technical problems and methods. Receives approval on proposed plans for projects and general direction as to results expected or unusual problems.

Work direction given to others (titles and number of personnel; type of direction given):

Coordinates with, guides and/or reviews the work of junior professionals, technicians, and others who assist in specific assignments.

Internal contacts (required interaction/relationship with others within the organization):

Interfaces with senior technical professionals and technical managers.

External contacts (required interaction/relationship with others outside the


36

organization):

Routinely interfaces with clients and regulatory agencies.


Education and experience

B.S. or B.A in Computer Science or other IT major, or relevant computer programming experience after degrees in Geography, Planning, Engineering, or other related disciplines. This level may be achieved by practitioners with 4 years of experience since related Bachelor's degree or 1 year since Master's degree if such academic program provided opportunity to acquire relevant software development experience. Typical incumbent has 6-8 years' experience.

Special skills

Must demonstrate experience with design and development of applications, as well as programming skills and extensive experience with current object-oriented programming techniques and internet application development tools. Experience with relational database management systems required. Should demonstrate good interpersonal, technical writing and communications skills.

Professional registrations

An industry recognized certification, i.e., Certified Visual Basic Programmer preferred, or professional registration desired if incumbent is an Engineer or Planner.

Competencies

General Competencies expected of all Professional and Managers are as follows: Client Service, Commitment, Communication, Innovation & Continuous Improvement, Professionalism, Quality and Teamwork.

Other

Job requires ability to access and understand technology materials and ability to operate computer keyboard. Ability to communicate effectively both orally and in writing. Incumbent must be able and willing to deal with interruptions in current work in


37

progress to handle priority jobs. Ability to interpret data, and plan and prioritize tasks.

6.2.6 TECHNICAL WRITER Produce instructional materials, reference manuals, and project proposals that relate to the objectives of internal or external clients.

Job Duties

- Writes, rewrites and edits technical literature.

- Translates business operations and procedures into technical requirements.

- Prepares instructional materials, reference and maintenance manuals, training materials, and technical reports for a wide range of users.

- Studies data and conducts in-depth interviews with Subject Matter Experts (SME) to understand projects or procedures.

- Documents and updates standards and protocols for database nomenclature, coding, and documentation.

- Evaluates needs in relation to projects and information updates and maintains project timelines to meet these needs.

- Creates and edits screen text and navigation for web applications and the corporate intranet.

- Edits, standardizes, and revises material prepared by other writers or personnel.

- May perform such other duties as the supervisor may from time to time deem necessary.

Scope


Moderately complex, relatively standardized tasks requiring knowledge of technical


38

language and ability to translate it into understandable English.


Works under immediate supervision; typically reports to a supervisor or manager. Relies on limited experience and judgment to plan and accomplish goals.


None


Regular and frequent job-related contact with professional staff in the same department.


None



Bachelor's degree in related field or equivalent combination of formal education and hands-on experience. With degree, one year of relevant experience, including block diagram/flow chart experience. High proficiency in Microsoft products. Familiarity with standard technology concepts, practices, and procedures.

Special skills:

Job requires creativity and solid writing skills, with ability to interpret information and communicate clearly both orally and in writing. Ability to translate technical language into understandable and correct English.


39


None

Competencies

General Competencies expected of all employees are as follows: Client Service, Commitment, Communication, Innovation & Continuous Improvement, Professionalism, Quality and Teamwork.

Other

Job requires ability to access and understand technical materials and ability to operate computer keyboard. Ability to communicate clearly both orally and in writing. Incumbent must be able and willing to deal with interruptions in current work in progress to handle priority jobs. Overtime work is required as workload and deadlines demand.

6.2.7 TEST ANALYST Drives the testing process through development and execution of test scenarios and scripts as well as regression testing, performance testing, functional testing, client acceptance testing, user interface testing , and production support testing of various software products using the plans, tools, and scripts developed. Participates in design specification reviews and technical documentation reviews. Creates testing and performance summary reports clearly communicating to management and clients all testing results. Helps prioritize defects to be fixed using an understanding of the business requirements and the needs of the customer.

Job Duties

- Contributes to the entire software development life cycle from initial business requirements to deployment and production support.

- Designs and implements test scenarios and cases.

- Creates and implements test plans and test scripts.

- Designs and develops testing tools for test automation and support.

- Provides production support of software products by investigating and re-creating reported defects.


40

- Works with multiple database interfaces and is familiar with standard web architectures.

- Assists in implementation of QA standards and continuous improvement activities.


Scope


Applies standard techniques and established procedures and criteria in carrying out a sequence of somewhat complex and diversified quality assurance tasks. Detects and solves problems by adapting standardized procedures to meet client needs or project direction.


Receives direct supervision on new aspects of assignments. Consistently exercises independent judgment on regular assignments, making preliminary selections, minor modifications, and adaptation of alternatives for quality assurance activities.


None.


Regularly meets with Supervisor to receive direction. Occasionally interacts with users within Fictitious Corp.



41

None.



B.S. or B.A in Computer Science or Information Technology or related area, plus minimum four (4) years total relevant experience as outlined below, or equivalent combination of education and experience. Four (4) years total relevant experience includes minimum of two (2) years experience in systems specifications analysis, testing methodology and test plan formulation; experience in Software Development Life Cycle; experience in Quality Assurance practices and procedures; experience in functional testing techniques including system, acceptance and regression testing; experience with automated test tools for functional and performance testing. Minimum of two (2) years working with ASP, .NET, Oracle/MS SQL Server, and the ability to read, write, debug and follow ASP/.NET code, VB.NET/ C#, PL/SQL, TSQL.

Special skills:

Exceptional analytic and problem solving skills are required, as are strong multi-tasking and time-management skills, and the ability to communicate clearly both orally and in writing to technical and non-technical audiences. Should have good interpersonal skills and ability to work in a team environment.


None.

Competencies

General Competencies expected of all Professionals and Managers are as follows: Client Service, Commitment, Communication, Innovation & Continuous Improvement, Professionalism, Quality and Teamwork.