Page 50 - DCAP304_DCAP515_SOFTWARE_PROJECT_MANAGEMENT

Software Project Management

Notes Name Description
Project Charter Document identifying how the project will be managed
Business Requirement Specification Document identifying the requirements for the project
Weekly Reports Status reports to be issued weekly
Prototypes x 3 Three prototypes will be allowed for in the development.
Etc.

Define the Functionality

Another method is to define the functionality. This should not be either a lengthy or detailed
process. Usually, depending on project size, the exercise can be completed in a one hour to half-
day seminar. A good system is to use a functional decomposition. If using a spreadsheet and a
projector, a scribe can make the scope as it is discussed. Remember to start all functionality with
a verb. It is valuable to do the functional decomposition in conjunction with a data definition.
If this is unfeasible, once the scope is discussed, it will become reasonably clear what data is
required.
The Project Manager can conclude if there are any situations that need to be clarified with the
users, and finalize the scope definition. If for example, in defining the functionality it becomes
apparent that considerable information will need to be move from a legacy system, which is
known to be inaccurate, data cleansing can be factored into the scope.

Task External deliverables are things the project delivers to the users. Analyze

Example Functional Decomposition

1.0 Capture License details

1.1 Set up companies
1.2 Set up products

1.3 Create licenses
1.4 Modify licenses
1.5 Delete licenses

2.0 Generate payments
2.1 Create payment report

2.2 Authorise payments
2.3 Notify accounts
Etc.

It can also be defined as a diagram:

44 LOVELY PROFESSIONAL UNIVERSITY