Project 1

software project

Dwarakesh Sarvanabavan

Muhammad Nahidul Alam

Contents

Software Project Management plan

Prepared By

INTRODUCTION

PROJECT OVERVIEW

M/s J.Goyal (Project Client) is currently running one of the successful and fast growing online book store based of e-bay. Most of her products are catered for young kids aged 3-6 years. Her products are of wide variety from books which engages the child like colouring activities or drawing scraps to educational books such as simple mathematics and even entertainment books like stories and fiction.

Organisation Chart detailing hierarchical structure of stakeholders of the project.
Gantt chart stating which team is working on what part of this application project.
Scope Statement explaining information about the project like project name, charter, owner, sponsors, stakeholders, goals, objectives, requirements, deliverables, milestones and cost estimates.
WBS (Work Breakdown Structure) is representation of the project that is in broken down into different levels.
Schedule listing the project’s tasks that are to be completed with start and end dates.
Detailed Budget off all expenses expected for the project.
Milestone Report tasks that are required to be finished before the following task can be finished.
Team Meeting Minutes of what was discussed in the team’s meetings.
Status Reports of all the work the team members have completed for the project.
Network Diagram of all independent and dependent tasks with the appropriate milestones and completion dates and times.
Lessons Learned Report of the mistakes that have occurred and how it can be avoided in future.

RAM (responsibility assignment matrix) of the contribution in carrying out tasks for the project.
Risk management plan estimating the impact to the project.

REFERENCE MATERIALS 

Ramachandran, V., & Nandi, S. (n.d.). Detecting ARP Spoofing: An Active Technique. Ghuwati.

Manwani, S. (2003, dec). ARP Cache Poisoning Detection and Prevention. Retrieved jun 4, 2014, from www.cs.sjsu.edu: http://www.cs.sjsu.edu/faculty/stamp/students/Silky_report.pdf

Nachreiner, C. (2011). Anatomy of an ARP Poisoning Attack. Retrieved Jun 4, 2014, from watchguard: www.watchguard.com

• SPMP - Software Project Management Plan

• SRS - Software Requirements Specification

• UML - Unified Modelling Language

• CVS - Concurrent Version System

• CLO - Client Liaison office

PROJECT ORGANISATION

ORAGANISTAIONAL STRUCTURE

Organisational structure is used in the software project management plan (SPMP) to minimize the different kinds of risks, which might be attached to a project. If these risk will not be minimized on the timely basis it can affect the feasibility of the project ion adverse manner. There might be many projects in which the subjectivity is involved, so the software project management plan (SPMP) can be used to minimize the effect of the subjectivity on the feasibility of the project. The project team can use the Software Project Management Plan (SPMP) in order to increase the efficiency and effectiveness of all components of a project during the project management (ieee.org, 2015)

ORAGANISTAIONAL BOUNDARIES AND INTERFACES

• Project strategy

• Business case.

• Support and benefits realization.

• Project close (Lai, 2013).

PROJECT RESPONSIBILITIES

MANAGERIAL PROCESS

MANAGEMENT OBJECTIVES AND PRIORITIES

ASSUMPTIONS, DEPENDENCIES, AND CONSTRAINTS

Refer to appendix 3, 4 and 5.

RISK MANAGEMENT

Refer to appendix 6.

• Ensure outcomes of meeting met objectives

  • Action items assigned

A weekly Status report on the project that helps us to see which milestones are complete, which ones are in progress, and which ones are coming up next. This is planed so that we are able to detect a problem in the project and its overall health very early. As a team we want to be contributing to early detection and solution to the issue.

The report will address the status of

• Details about each issue discovered until that point and the action meted with it.

• • SCHEDULE AND BUDGET UPDATES

Updates on documentation as and when required is done in controlled manner by the change control process.

STAFFING PLAN

TECHINICAL PROCESS

The project will be managed by the method of iterative waterfall, which is referred to in 5 phases;

1. Requirements analysis and specification: problem understanding, defining the problem (what is required), representing the problem (formally stating the problem def.), decomposing the problem, defining the constraints of the problem (what can’t be done).

Iterative waterfall model is that all requirements are completed before the previous activity but equally provides feedback paths of each phase that precedes the phase as shown in Fig. Feedback paths allow for correction of errors during a detected as and when they made later stage phase. (MALL, 2009)Figure Iterative waterfall model

TOOLS

Project Planning: Software Project Management Plan (SPMP) -

Requirements Analysis: Requirements Analysis Document (RAD) -

Reviews: Review Presentation Slides -

Implementation and Unit Testing: Code -

WORK PACKAGES, SCHEDULE, AND BUDGET

WORK PACKAGES

External interfaces.

Internal interfaces.

RESOURCE REQUIREMENTS

Please refer to Tools in page 8

APPENDICES 

1. ORGANIZATIONAL CHART PROJECT E-BOOK STORE

Definitions

S Sign-off Required Must sign-off the appropriate document

3. THE BUDGET FOR EACH WORKFLOW IS AS FOLLOWS:

5. PROJECT ROLES AND RESPONSIBILITIES:

6. PROJECT RISKS