Software projects Management & Development

1. Software projects Management & Development Alireza Saebi http://Saebi.ir rsoftmio@gmail.com

2. Lecture outline • Software projects ? • What is project ? • What is project management ? • Project fail reasons . . . • Project development tools (Mental power ;) ) • Project management tools (MS Project , …) • Professional resources vs. Amateur

3. Software project • Target (System ? / software ? ) • Benefits • Just automation ? • Workflow definition ? • Cost reduction ? • Customer care ? • Any other or WHAT IS THE TARGET ? • KPI / CSF definitions

4. IS Development principles • Project phasing • Top-down definition • Walking on project based on methodology • Patterns • Estimations • Tasks • Deliverables • Notice to success histories

5. IS Development skills • IS Project required skills : • Analysts • Technical men • Managers • QA / QC • Consultants • Developers • Logistic manager

6. IS Development standards • Methodology • Tasks & assignments • Deliverables & QA → QC • Estimations • Project progress control & management

7. Getting start . . . • Select methodology • Confirming terms of agreements between project development team and customer • Interact with one customer team • Try to install some common expressions • Try to get all of ideals of customer and document them • Try to walk under scheduling or program

8. Project management • Project management dividing into : • Project initiation • Project planning • Project executing • Project close-down (or cut over)

9. Project Initiating Project ID and Selection Proj. Initiation & Planning Analysis LogicalDesign Maintenance PhysicalDesign Implementation Systems Development Life Cycle (SDLC)

10. Analysis / business plan • Collect detailed business information • Construct business data model • Construct detailed business function model • Construct system function model • Create system process model

11. Analysis / Technical arch. • Define detailed system operational req. • Develop distribution architecture • Develop recovery and fallback strategy • Develop security and control strategy • Develop some other plans like capacity plan / user interface style definitions / HW and SW foundation definitions / data conversion strategy / …

12. IMPORTANT • Define cut-over strategy • Define draft transition strategy • Confirm cut-over plan with assigned customer agent in the project

13. Analysis key deliverables • Business data models • Detailed business function models • System process models • System data / function model • Business indicators & CSF (s)

14. Design / Technical arch. • Create capacity plan • Determine performance issues • ready for answering : • What KPI is covered by what function ? • Who resolve what problem ? • What KIP is improved and how much ?

15. Design / Technical arch. • Module design • SW architecture documents • Design audit facilities • Define building standards • DB design and it’s tasks • Document all tasks and decisions

16. Testing . . . • Developing test strategy (in the project analysis) • Document test scenario and plan • Unit testing • Integrity testing • System testing • Prepare test environment • Perform system test • Support acceptance test

17. Transition stage • Prepare transition strategy • Develop transition environment • Develop installation plan • Prepare production environment • Go production . . .

18. Summary (project phases) • Definition • Analysis • Design • Build • Transition • Production

19. Summary (project steps) • Business requirement definitions • Existing system examination • Technical architecture • Database design and build • Module design and build • Data conversion • Documentation • Testing • Training • Transition • Post-system support

20. Tanx 4 your attention Alireza Saebi http://Saebi.ir rsoftmio@gmail.com