a discussion of how well your project plan, risk p

a discussion of how well your project plan, risk plan, requirements specification and design document matched reality

The primary theme of the paper is a discussion of how well your project plan, risk plan, requirements specification and design document matched reality in which you are required to emphasize its aspects in detail. The cost of the paper starts from $109 and it has been purchased and rated 4.9 points on the scale of 5 points by the students. To gain deeper insights into the paper and achieve fresh information, kindly contact our support.

The quality assurance requires the following deliverables: 

• A project plan that incorporates
  
  
  • The objectives and constraints for the project
  • Project organisation
  • Hardware and software requirements
  • Work breakdown structure
  • Schedule
  • A risk plan
  • Monitoring and reporting mechanisms

• Progress reports

• A requirements specification that incorporates 
  • A list of functional and non-functional requirements
  • Specification of use cases in both UML and text form
  • Mapping of requirements to use cases

• A design document that incorporates
  • Software architecture
  • View layer design (class diagram + GUI mockups)
  • Presentation/Controller layer design (class diagram)
  • Model layer design (class diagram)
  • Database design
  • Layer interface specifications (V/P, P/M, M/database). That is, the methods by which a given layer can be accesssed by other layers.
  • Mapping of requirements to design (sequence diagrams for each use case)

• A documented implementation that incorporates
  • a working NetBeans project (or related platform) with source code adequately documented
  • any SQL scripts needed to populate the database
  • a brief user manual showing how to achieve basic functions

• A project review that incorporates
  • a discussion of how well your project plan, risk plan, requirements specification and design document matched reality
  • a reflection on what you have learnt from the project

At the end, a final report including all software development processes (documents above) should be submitted. An oral presentation is required.

These correspond to assessment items. Refer to the assessment criteria in the course profile for a guide as to how the document deliverable might be structured.

The work breakdown structure in the project plan is to be ideally at the level of individual tasks for team members, although it is accepted that this may not be possible for all tasks. This will require teams to break deliverables down into sub-deliverables which are the responsibility of individual team members, but may involve other team members. All team members must contribute to all deliverables - having one person solely responsible for say, documentation or coding is not acceptable. For each deliverable, a statement must  be submitted detailing what the contribution each team member made to the deliverable. Note also that this is a software development project with the bulk of the effort focused on software design and implementation. This should be reflected in your WBS - i.e having single design and implementation activity is not acceptable. At the very least, the WBS for these activities should reflect the layers of the system to be built.

The weekly reports will report progress against these sub-deliverables and the associated schedule. Note that it is most likely that during the project, you will need to refine your initial WBS and modify your schedule. When this occurs, the modified WBS and schedule are to be submitted with your weekly progress report.

The role of project manager is to be rotated between the team members so that each team member is manager for the same period of time. The time spent by the team members on the scheduled tasks, as well as the degree of task completion must be reported on a weekly basis. The manager is responsible for lodging these reports, as per the schedule. Templates for these reports will be provided on the course website.

In week 1, teams will be assigned by your campus lecturer, or by the course coordinator if you are a Flex student. The team allocation process will take into account any preferences that you might have in terms of team structure, but there is no guarantee that any particular request will be satisfied. Teams will consist of either three or two members; three will be the preferred size. Note that two member teams will have less time allocated to the project (24 days versus 36 days) - this will be reflected in the scope of the project that they undertake.

Assessment Resources

For your weekly progress reports, you need to provide a summary of progress against your project schedule and an updated risk plan. Use the the following templates:

For your project review (and other document deliverables), use the assessment criteria in the course profile for the document structure.

Submission 

When submitting assessments, note that there is only one submission per group. The project manager at the time of the submission is responsible for the submission and for the dissemination of the marked assessment item to the other group members.