Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Software Project Management

to be corrected, completed and refined.
by

Pierre C.

on 27 August 2011

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Software Project Management

Develop iterativly
Manage requirements
Employ component-based architecture
Model Visually
Continuously verify quality
Control change Product Cycle Management > dispatches and follow issues
> handles configuration
> defines versions perimeter Inward Supervision > reviews overall design
> perform any internal test and controls
> throws inward issues Outward Supervision > primo-experiments system
> rolls qualification plan
> throws outward issues Operations Management > defines, assigns and follows work packages
> anticipates technical risks
> analyses and consolidate issues Product Insurance Project Insurance > delivers qualication plan
> defines inward tests and controls policy
> manages reviews > defines project best endeavour
> defines, follows and reports indicators
> conducts audits & "root cause analysis"
> acknowledges reviews Project Directoring > manages team
> reports to direction
> reports to client
> acknowledges client issues > defines components and responsibilities
> architects interactions between users
> specifies underlying data Product Management > midwifes system requirements
> specifies mockups
> structures requirement tree > specifies S/H components implementation
> specifies tests data and mocks Production Procurement Outsourcing Specification Design Deployment > find and buy
> interacts with procurers A Rational Unified Process
Implementation Rational Unified Process :
a framework
to be made your own Project
Loop Product
Control Product
Definition Pierre Cariou - ISAE A(nother) Method
to Handle
Your Software Project > writes scope statement
> finds outsourcers
> interacts with outsourcers Implementation > guarentees component
> writes end-user and operationnal documentation > provides with all S/H configurations
> snapshots and packages versions deliverables
> performs inward and outward automatic tests > codes functionnalities
> packages parameters
> prepares data Product Flow Design Review Specification Review Production Review Qualification Review Client
Loop Models Mockups System Definition > expresses his needs
> analyses project technical feedbacks System Operation > throws issues
> asks for assistance Plans Requirements System Issues Plans Qualification Development Nominal Product
Realisation Validation Plans Justification Experimentation Functionnal Software
&
Hardware Documentation Operation Installation Maintenance Roadmap Configuration Design satisfies component based architecture and shall expose hierarchical Components Diagrams with implemented and required interfaces and required data.
Interfaces are categorised "user" or "component" depending on kind of actor to be interacting with them. Management Quality
Insurance Review
&
Test Describes how to conduct reviews so as to ensure system quality and consistency
Includes model reviews and code reviews.

Describes unitary tests and integration tests Describes high level testing scenarios so as to provide with a complement to validation to any requirement which is not subject to a unitary functionnal test - see Justification Plan. Describes how to test (tools, protocol, context, inputs and outputs) any single requirement whose validation is ensured by a unitary functionnal test. Describes high level testing scenarios so as to provide with a complement to validation to any requirement which is not subject to a unitary functionnal test - see Justification Plan. Use Cases Describes how system responds to any requirement that would not be validated by a single test :
- use case delegation
- conversion into functionnal requirement
- conversion into best endeavour requirement Gives a list of any issue that raised by "Product Quality" or "Client"
Each issue has a description, a resolution status, the version number it had been raised in.
Information of Product Spring phase and in/outward concerns should also appear Consolidates all system requirements.

Some are direct retranscription from client, some are implied or derived by first order requirements Consolidates all system requirements.

Some are direct retranscription from client, some are implied or derived by first order requirements Links each requirement and each issue to a version to be implemented/corrected in. Gives a hand to any person that would have to dive down in the implementation.
Includes code commenting, reference to S/W model and any other required documentation Gives a hand to any person that would have to deploy system.
Includes code compilation procedures in a separate part in case setups are delivered. Gives a hand to any person that would operate the system.
It explains each User or Component Interface published at the boundary of the system Documentation User Consolidates all system requirements.

Some are direct retranscription from client, some are implied or derived by first order requirements Production Work Package a component
- all implemented interfaces
- all interfaces ports
- all sub-components integration seen as black-boxes design
conception
realisation
deployment issues MetaWork Package
Full transcript