DCRUST SYLLABUS
CSE404C SOFTWARE PROJECT MANAGEMENT
CATEGORY : ENGINEERING SCIENCE COURSE
Course Objectives:
- To explain needs for software specifications and to study different types of software requirements gathering techniques.
- To convert the requirements model into the design model and demonstrate use of software and user interface design principles.
- To justify the role of SDLC in Software Project Development and to study risks associated with a project.
- To generate project schedule and can construct, design and develop network diagram for different type of Projects.
Unit I
Introduction to Software Project Management (SPM): Definition of a Software Project (SP), SP Vs. other types ofprojects activities covered by SPM, Fundamentals of Software Project Management (SPM), Need Identification, Vision and Scope document, Project Management Cycle, SPM Objectives, project as a system, management control, requirement specification, information and control in organization, Project management and CMM.
Stepwise Project planning: Introduction, selecting a project, identifying project scope and objectives, identifyingproject infrastructure, analyzing project characteristics, identifying project products and activities, estimate efforts each activity, identifying activity risk, allocate resources, review/ publicize plan.
Click on any topic to read about the topic.
Unit II
Project Evaluation & Estimation:- Cost benefit analysis, cost benefit evaluation techniques, risk evaluation. Selection of an appropriate project approacht;, structured methods, rapid application development, water fall-, V-process-, spiral-models. Prototyping, delivery. Albrecht function point analysis.
Project Scheduling:- Objectives of activity planning, project schedule, projects and activities, Identifyingactivities, sequencing and scheduling activities, network planning model, Network Diagrams, CPM, representation of lagged activities, backward and forward pass, identifying critical path, activity throat, shortening project , precedence networks.
Risk Management:- Introduction, the nature of risk, managing risk, risk identification, risk analysis,reducing the risks, evaluating risks to the schedule, calculating the z values.
Click on any topic to read about the topic.
Unit III
Project Monitoring & control:- identifying resource requirements, scheduling resources, PERT, GanttCharts, Earned Value Analysis, Earned Value Indicators: Budgeted Cost for Work Scheduled (BCWS), Cost Variance (CV), Schedule Variance (SV), Cost Performance Index (CPI), Error Tracking, Software Reviews, Types of Review: Inspections, Deskchecks, Walkthroughs, Code Reviews, Pair Programming.
Managing contracts and people-: Introduction, types of contract, stages in contract, placement, typicalterms of a contract, contract management, acceptance, Managing people and organizing terms: Introduction, understanding behavior, organizational behavior: a back ground, selecting the right person for the job, instruction in the best methods, motivation, working in groups, becoming a team, decision making, leadership, organizational structures, conclusion, further exercises.
Unit IV
Software quality Assurance and Testing:- Testing Objectives, Testing Principles, Test Plans, Test Cases, Types of Testing, Levels of Testing, Test Strategies, Program Correctness, Program Verification & validation, Concept of Software Quality, Software Quality Attributes, Software Quality Metrics and Indicators, The SEI Capability Maturity Model CMM), SQA Activities, Formal SQA Approaches: Proof of correctness, Statistical quality assurance, Clean room process.
Software Project Management Tools:- CASE Tools, Planning and Scheduling Tools, MS-Project.
Click on any topic to read about the topic.
TEXT /REFERENCE BOOKS:
- Software Project Management (2nd Edition), by Bob Hughes and Mike Cotterell, 1999, TMH
- Software Engineering – A Practitioner’s approach, Roger S. Pressman (5th edi), 2001, MGH
- Software Project Management, Walker Royce, 1998, Addison Wesley.
- Project Management 2/c. Maylor
- Managing Global software Projects, Ramesh, 2001, TMH.
- S. A. Kelkar, Software Project Management, PHI Publication.
Course Outcomes: After successful completion of the course students will learn the following:-
- Explain needs for software specifications and different types of software requirements gathering techniques.
- Convert the requirements model into the design model and demonstrate use of software and user interface design principles.
- Justify the role of SDLC in Software Project Development and identify the risks associated with a project.
- Generate project schedule and can construct, design and develop network diagram for different type of Projects.