{{{credits}}}
| L | T | P | C |
| 3 | 0 | 0 | 3 |
- To learn the key aspects of managerial process in software organization.
- To apply the practices followed in project planning, estimation, and scheduling
- To be familiar with the overall project activities in Agile and DevOps
- To study the various issues in people management
- To distinguish between security and risk activities related with software development.
{{{unit}}}
| UNIT I | PROJECT PLANNING | 9 |
Project Management: Project management life cycle – Project evaluation and programme management – Project planning; Process Models: Waterfall – Spiral – Prototyping – Incremental delivery – DSDM – Agile – Scrum –XP; Software Development: Lean software development – Process model selection.
{{{unit}}}
| UNIT II | ESTIMATION AND SCHEDULING | 9 |
Effort Estimation Techniques: Expert judgement – FPA – FP mark II – COSMIC – COCOMO II – Cost estimation; Scheduling: Project schedules – Network model – Identifying critical activities.
#+begin _comment …Included scheduling in Unit II instead of having it in AU-Unit III…
{{{unit}}}
| UNIT III | AGILE AND DEVOPS | 9 |
Scrum: Organization – Estimation – Planning – Changes in scrum – Risk in scrum – Product backlog – Sprint backlog – Release – Identifying stories and preparing to build;
DevOps: Motivation – Cloud as a platform – Operations – Deployment pipeline.
#+begin _comment …New process model is added in syllabus which is not provided in AU…
{{{unit}}}
| UNIT IV | SECURITY AND RISK MANAGEMENT | 9 |
Cloud Security: Cloud information security objectives – Cloud security services – Secure development practices;
Risk Management: Risk culture – Risk managementprocess – Risk attributes – Risk identification – Types of risk analysis – Responding to risk – Risk tracking – Risk models.
#+begin _comment …Added security topic in syllabus, which is not provided in AU… …Added risk in Unit IV instead of AU-Unit III…
{{{unit}}}
| UNIT V | MONITORING AND ORGANIZING TEAMS | 9 |
Visualizing Progress: Relationship between people and effort – Task set and network – Earned value analysis – SCM – Managing contracts – Working in teams – Developing metrics on a software development program – Evaluating performance.
#+begin _comment …Included monitoring topics in Unit V instead of AU-Unit IV…
Upon completion of the course, the student should be able to:
- Select a process model for software development (K2)
- Estimate cost to manage the software development (K3)
- Develop a project using agile and devops software development practices (K3)
- Identify the activities of security and risk in various types of software projects (K3)
- Recognize management skills and techniques to develop commercial software projects (K2).
- Bob Hughes, Mike Cotterell, Rajib Mall, “Software Project Management”, 6th Edition, Tata McGraw Hill, 2018.
- Ravindranath Pandian, “Applied Software Risk Management A Guide for Software Project Managers”, Auerbach Publication, 2007.
- Roger S Pressman, “Software Engineering – A Practitioner’s Approach”, 7th Edition, Mc Graw-Hill International Edition, 2010.
- Rajib Mall, “Fundamentals of Software Engineering”, 3rd edition, PHI Learning Pvt. Ltd., 2009.
- Tridibesh Satpathy, “A Guide to the Scrum Body of Knowledge (SBOK Guide)”, 2016 edition, SCRUMstudy, Phoenix, Arizona 85008 USA.
- Len Bass, Ingo Weber and Liming Zhu, “DevOps: A Software Architect’s Perspective”, Pearson Education, 2016.
- Ronald L Krutz, Russell Dean Vines, “Cloud Security – A comprehensive Guide to Secure Cloud Computing”, Wiley-India, 2010.
| PO1 | PO2 | PO3 | PO4 | PO5 | PO6 | PO7 | PO8 | PO9 | PO10 | PO11 | PO12 | PSO1 | PSO2 | PSO3 | ||
| CO1 | 2 | 2 | 2 | |||||||||||||
| CO2 | 3 | 2 | 2 | 3 | 3 | 3 | 2 | |||||||||
| CO3 | 3 | 2 | 2 | 3 | 3 | 3 | 2 | |||||||||
| CO4 | 2 | 2 | 2 | |||||||||||||
| CO5 | 2 | 2 | 2 | |||||||||||||
| Score | 6 | 10 | 10 | 6 | 6 | 6 | 10 | |||||||||
| Course Mapping | 3 | 2 | 2 | 3 | 3 | 3 | 2 |