Diploma in Project Management

Semester I
1. Project Management I
2. OOAD & UML
3. Project Management Tool- Agile
4. ERP- Enterprise Resource Planning
Semester II
1. Software Testing Tools-Selenium
2. Project Work

Project Management I 

1. Basics of Project Management: 

1.1Introduction, Need for Project Management,
1.2Project Management Knowledge Areas and Processes,
1.3The Project Life Cycle,
1.4The Project Manager (PM),
1.5Phases of Project Management Life Cycle,
1.6Project Management Processes,   
1.7Impact of Delays in Project Completions,
1.8Essentials of Project Management Philosophy,       
1.9Project Management Principles
  
2. Project Identification and Selection: 
2.1 Introduction,
2.2 Project Identification Process,
2.3 Project Initiation,
2.4 Pre-Feasibility Study,
2.5 Feasibility Studies,
2.6 Project Break-even point
 
3. Project Planning: 
3.1Introduction,
3.2Project Planning,
3.3Need of Project Planning,
3.4Project Life Cycle, Roles,
3.5Responsibility and Team Work,
3.6 Project Planning Process,
3.7Work Breakdown Structure (WBS)

4. Organisational Structure and Organisational Issues: 

4.1Introduction,
4.2Concept of Organisational Structure,  
4.3  Roles and Responsibilities of Project Leader,
4.4 Relationship between Project Manager and Line Manager,
4.5 Leadership Styles for Project Managers,
4.6 Conflict Resolution,
4.7Team Management and Diversity Management,
4.8 Change management
 
5. PERT and CPM: 
5.1Introduction,
5.2Development of Project Network,
5.3Time Estimation,
5.4Determination of the Critical Path,
5.5PERT Model,
5.6Measures of variability,
5.7CPM Model,
5.8Network Cost System

6. Resources Considerations in Projects:    

6.1     Introduction,
6.2 Resource Allocation,
6.3 Scheduling,
6.4 Project Cost Estimate and Budgets,
6.5 Cost Forecasts  
 
7. Project Risk Management: 
7.1Introduction,
7.2Risk,
7.3Risk Management,
7.4Role of Risk Management in Overall Project Management,
7.5Steps in Risk Management,
7.6Risk Identification,
7.7Risk Analysis,
7.8Reducing Risks
 
8. Project Quality Management and Value Engineering: 
8.1 Introduction,
8.2 Quality,
8.3 Quality Concepts,
8.4 Value Engineering
8.5Stages of Software Quality Management
8.6 Quality Planning
8.7Quality Assurance
8.8Quality Control
8.9 Quality Standards
8.10 Tools and Techniques For Quality Control
Enterprise Resource Planning
1. Enterprise
1.1 An Overview:
1.2 Business Functions and Business Processes,
1.3 Importance of Information: 
1.4 Characteristics of information
1.5 Types of information
1.6 Information System
1.7 Components of an information system
1.8 Different types of information systems
1.9 Management information system
1.10 Enterprise Resource Planning
1.11 Business modeling
1.12 Integrated data model
2. Introduction to ERP
2.1 Defining ERP
2.2 Origin and Need for an ERP System
2.3 Benefits of an ERP System
2.4 Reasons for the Growth of ERP Market
2.5 Reasons for the Failure of ERP Implementation
2.6 Roadmap for successful ERP implementation
3. ERP and Related Technologies
3.1 Business Process Re-engineering
3.2 Management Information systems
3.3 Decision Support Systems
3.4 Executive Information Systems
3.5 Advantages of EIS
3.6 Disadvantages of EIS
3.7 Data Warehousing
3.8 Data Mining
3.9 On-Line Analytical Processing
3.10 Product Life Cycle Management
3.11 Supply Chain Management
3.12 ERP Security
2.1ERP Implementation Life Cycle
4.1 ERP Tools and Software
4.2 ERP Selection Methods and Criteria
4.3 ERP Selection Process
4.4 ERP Vendor Selection
4.5 ERP Implementation Lifecycle
4.6 Pros and cons of ERP implementation
4.7 Factors for the Success of an ERP Implementation
5.ERP Modules Structure

5.1 Finance
5.2 Sales and Distribution
5.3 Manufacturing and Production Planning 
5.4 Material and Capacity Planning
5.5 Shop Floor Control
5.6 Quality Management
5.7 JIT/Repetitive Manufacturing
5.8 Cost Management
5.9 Engineering Data Management
5.10 Engineering Change Control
5.11 Configuration Management
5.12 Serialization / Lot Control
5.13 Tooling
5.14 Human Resource
5.15 Plant Maintenance
5.16 Preventive Maintenance Control
5.17 Equipment Tracking
5.18 Component Tracking
5.19 Plant Maintenance Calibration Tracking
5.20 Plant Maintenance Warranty Claims Tracking
5.21 Quality Management   
5.22 Functions of Quality Management
5.23 CAQ and CIQ; Materials Management
5.24 Pre-purchasing; Purchasing
5.25 Vendor Evaluation
5.26 Inventory Management and Invoice Verification and Material
Inspection

6. ERP – A Manufacturing Perspective

6.1 Role of Enterprise Resource Planning (ERP) in manufacturing

6.2 Computer Aided Design/Computer Aided Manufacturing
(CAD/CAM)
6.3 Materials Requirement Planning (MRP)
6.4 Master Production Schedule (MPS)
6.5 Bill of Material (BOM)
6.6 Inventory Records
6.7 Closed Loop MRP
 6.8 Manufacturing Resource Planning (MRP-II)
6.9 Manufacturing and Production Planning Module of an ERP System
6.10 Distribution Requirements Planning (DRP)
6.11 Just-in-Time(JIT) & KANBAN - Kanban
6.12 Benefits of JIT
6.13 Potential Pitfalls of JIT
6.14 Kanban
6.15 Product Data Management (PDM)
6.16 Data Management
6.17 Process Management
6.18 functions of PDM
6.19 Benefits of PDM
6.20 Manufacturing Operations
6.21 Make-to-Order (MTO) and Make-to-Stock (MTS)
6.22 Assemble-to-Order (ATO)
6.23 Engineer-to-Order (ETO)
6.24 Configure-to-Order (CTO)

7. ERP: A Purchasing Perspective

7.1 Role of ERP in Purchasing 

7.2 Purchase Module
7.3 Features of purchase module
7.4 Benefits of purchase module
7.5 ERP Purchase System

8. ERP: Sales and Distribution Perspective

8.1 Role of ERP in Sales and Distribution

8.2 Sub-Modules of the Sales and Distribution Module
8.3 Master data management
8.4 Order management
8.5 Warehouse management
8.6 Shipping and transportation
8.7 Billing and sales support 
8.8 Foreign trade
8.9 Integration of Sales and Distribution Module with Other Modules

9. ERP: An Inventory Management Perspective

9.1 Role of ERP in Inventory Management: 

 9.2 Features of ERP inventory management system;
9.3 Benefits of ERP inventory management system;
9.4 Limitations of ERP inventory management system, 
9.5 Importance of Web ERP in Inventory Management, 
9.6 ERP Inventory Management Module,
9.7 Sub-Modules of the ERP Inventory Management Module,
9.8 Installation of ERP Inventory Management System,
9.9 Failure of ERP Inventory Installation
  10. ERP: An CRM Perspective
10.1 Role of ERP in CRM,
10.2 Concept of CRM:
10.3 Objectives of CRM;
10.4 Benefits of CRM;
10.5 Components of CRM,
10.6 Types of CRM: 
10.7 Operational CRM,
10.8 Analytical CRM,
10.9 Sales intelligence CRM,
10.10 Collaborative CRM,
10.11 Sub-Modules of CRM:
10.12 Marketing module;
10.13 Service module;
10.14 Sales module

11.ERP: A HR Perspective:
11.1 Role of ERP in Human Resource Management:
11.2 Workflow of ERP human resource management system;
11.3 Advantages of ERP human resource management system, 
11.4 Human Resource Management Module: 
11.5 Functions of human resource management module;
11.6 Features of human resource management module;
11.7 Benefits of human resource management module, 
11.8 Common Sub-Modules of Human Resource Management Module:
11.9 Personnel management;
11.10 Organisational management;
11.11 Payroll management;
11.12 Time management;
11.13 Personnel development

12.ERP: An Finance Perspective:

 12.1 Role of ERP in Finance,
12.2 Accounting and Finance Processes:
12.3 Cash management;
12.4 Capital budgeting,
12.5 Features of ERP Financial Module,
12.6 Benefits of ERP Financial Module,
12.7 Sage Accpac ERP – A Financial ERP Tool

 
 Object Oriented Modeling and Design usung UML
INTRODUCTION
a. An overview - Object basics
b. Object state and properties,
c. Behavior,
d. Methods,
e. Messages.
f. Object Oriented system development life cycle.
g. Benefits of OO Methodology.
1. Overview of Prominent OO Methodologies:
1.1The Rumbaugh OMT.
1.2The Booch methodology.
1.3Jacobson's OOSE methodologies.
1.4Unified Process.
1.5Introduction to UML.
1.6Important views & diagram to be modelled for system by UML.
2. Factional view(models):
2.1Use case diagram
2.1.1 Requirement Capture with Use case.
2.1.2 Building blocks of Use Case diagram – actors, use case guidelines for
use case models.
2.1.3 Relationships between use cases - extend, include, generalize.
2.1.4 Activity diagram
2.1.5 . Elements of Activity Diagram –
2.1.4.1 Action state,
2.1.4.2 Activity state,
2.1.4.3 Object. node,
2.1.4.4 Control and Object flow,
2.1.4.5 Transition (Fork, Merge, Join)
2.2 Guidelines for Creating Activity Diagrams.
2.3 Activity Diagram - Action Decomposition (Rake ).
2.4 Partition - Swim Lane.
3. Static structural view (Models):
3.1Classes, values and attributes,
3.1.1 operations and methods,
3.1.2 responsibilities for classes,
3.1.3 abstract classes,
3.1.4 access specification(visibility of attributes and operations).
3.2 Relationships among classes:
3.2.1 Associations,
 3.2.2 Dependencies.,
3.2.3 Inheritance - Generalizations,
3.2.4 Aggregation.

3.3 Adornments on Association:

3.3.1 association names,
3.3.2 association classes,
3.3.3 qualified association,
3.3.4 n-ary associations,
3.3.5 ternary and reflexive association.
3.4 Dependency relationships among classes, notations
3.5Notes in class diagram,
3.4.1 Extension mechanisms,
3.4.2 Metadata,
3.4.3 Refinements,
3.4.4 Derived ,
3.4.5 data,
3.4.6 constraint,
3.4.7 stereotypes,
3.4.8 Package & interface notation.
3.6 Object diagram notations and modeling, relations among objects
(links).
4. Class Modeling and Design Approaches:
5.1Three approaches for identifying classes - using
4.1.1 Noun phrases,
4.1.2 Abstraction,
4.1.3 Use Case Diagram.
5.2 Comparison of approaches.
5.3 Using combination of approaches.
5.4Flexibility guidelines for class diagram:
4.4.1 Cohesion,
4.4.2 Coupling,
4.4.3.1 Forms of coupling
4.4.3.2 identity,
4.4.3.3 representational,
4.4.3.4 subclass
4.4.3.5 inheritance
 4.4.3 class Generalization,
4.4.4 class specialization versus aggregation.
5. Behavioral (Dynamic structural view):

5.1State Diagram
5.1.1 notations,
5.1.2 events
5.1.2.1 signal events,
5.1.2.2 change events,
5.1.2.3 Time events
5.2State Diagram states
5.2.1 composite states,
5.2.2 parallel states,
5.2.3 History states,
5.2.4 transition and condition,
5.2.5 state diagram behavior
5.2.5.1 activity
5.2.5.2 effect,
5.2.5.3 do-activity,
5.2.5.4 entry and exit activity
5.2.5.5 completion transition,
5.2.5.6 sending signals.
5.3 Interaction diagrams:
5.3.1 Sequence diagram –
5.3.1.1 Sequence diagram notations and examples,
5.3.1.2 iterations,
5.3.1.3 conditional messaging,
5.3.1.4 branching,
5.3.1.5 object creation and destruction,
5.3.1.6 time constraints,
5.3.1.7 origin of links,
5.3.1.8 Activations in sequence diagram.
5.3.2 Collaboration diagram –
5.3.2.1 Collaboration diagram notations and examples,
5.3.2.2 iterations,
5.3.2.3 conditional messaging,
5.3.2.4 branching,
5.3.2.5 object creation and destruction,
5.3.2.6 time constraints,
5.3.2.7 origin of links,
5.3.2.8 activations in sequence diagram.
6. Approaches for developing dynamic systems:
6.1Top - down approach for dynamic systems.
6.2Bottom - up approach for dynamic systems.
6.2.1 Flexibility Guidelines for Behavioral Design –
6.2.2 Guidelines for allocating and designing behaviors that lead to more fexible
design.
7. Architectural view:
7.1Logical architecture: dependency, class visibility, sub systems.
7.2Hardware architecture:
7.2.1 deployment diagram notations,
7.2.2 nodes,
7.2.3 object migration between node
7.3Process architecture:
7.3.1 what are process and threads and their notations in UML,
7.3.2 object synchronization,
7.3.3 invocation schemes for threads
7.3.4 UML notations for different types of
invocations
7.4Implementation architecture: component diagram notations and examples.
8. Reuse: Libraries, Frame works components and Patterns:
8.1 Reuse of classes.
8.2 Reuse of components.
8.3 Reuse of frameworks, black box framework, white box frame.
8.4 Reuse of patterns: Architectural pattern and Design pattern.

Term Work / Assignment: Each candidate will submit an approximately 10-page

written report on a case study or mini project.
Students have to do OO analysis & design for the project problem, and develop
use case
model, analysis model and design model for it, using UML.

Reference books:
1. Designing Flexible Object Oriented systems with UML - Charles Ritcher
2. Object Oriented Analysis & Design, Sat/.inger. Jackson, Burd Thomson
3. Object oriented Modeling and Design with UML – James Rumbaugh.
Micheal Blaha (second edition)
4. The Unified Modeling Language User Guide - Grady Booch, James
Rumbaugh, Ivar Jacobson.
5. Object Oriented Modeling and Design - James Rumbaugh
6. Teach Yourself UML in 24 Hours - Joseph Schmuilers
7. Object-Oriented Analysis and Design: using UML Mike O'Docherty Wiley
Publication
 Software Testing And Quality Assurance

Class Duration : 16 Weeks with 4 Hours a week = 48 Hrs

MARKS THEORY 80 + INTERNAL ASSESSMENT 20 = 100

UNIT I 12hrs

1.1 Software testing background:

What is a bug: terms for software failures,
1.1.1 software bug: formal definition,
1.1.2 why do bugs occur, cost of bugs,
1.1.3 software development process:
1.1.4 software development life cycle model: big bang model,
1.1.5 code and fixed model,
1.1.6 waterfall model,
1.1.7 spiral model,
1.1.8 Examining the specification:
1.1.9 white box: Static and Structural testing.
1.2 Testing Fundamentals:
1.2.1 Black box testing:
1.2.2 What is black box testing?
1.2.3 Why black box testing?
1.2.4 When to do black box testing?
1.2.5 Requirements based testing, boundary value analysis,
1.2.6 decision tables,
1.2.7 equivalence partitioning,
1.2.8 state based or graph based testing, c
1.2.9 ompatibility testing, user documentation testing,
1.2.10 domain testing.

UNIT II 12 hrs

2.1 Integration testing:

2.1.1 Top-Down,
2.1.2 Bottom-up,
2.1.3 Bi-directional,
2.1.4 system integration.
 2.1.5 System Testing:
2.1.6 System and Acceptance Testing:
2.1.7 Acceptance criteria, s
2.1.8 electing test cases for acceptance testing,
2.1.9 executing acceptance tests.
2.2 Performance testing:
2.2.1 Methodology for performance testing:
2.2.2 Collecting requirements,
2.2.3 writing test cases,
2.2.4 automating test cases,
2.2.5 executing test cases.
2.2.6 Regression testing.
2.2.7 Usability testing: user interface testing,
2.2.8 configuration testing:
2.2.9 isolating configuration bugs.

UNIT III 12 hrs

3.1 Applying testing skills:

3.1.1 testing the documentation:
3.1.2 types of software documentation,
3.1.3 importance of documentation testing,
3.1.4 automation,
3.1.5 goals of test case planning,
3.1.6 test case planning overview:
3.1.6.1 test design,
3.1.6.2 test cases,
3.1.6.3 test procedures,
3.1.6.4 test case organization
3.1.6.5 and tracking,
3.1.7 software quality assurance:
3.1.8 software testing,
3.1.9 quality assurance,
3.1.10capability Maturity Model(CMM), ISO 9000.
 3.2 Software test automation:
3.2.1 what is test automation,
3.2.2 terms used in automation,
3.2.3 skills needed for automation,
3.2.4 scope of automation,
3.2.5 design and architecture for automation,
3.2.6 selecting a test tool?
3.2.7 Test metrics and Measurements:
3.2.7.1 Why metrics in testing,
3.2.7.2 types of metrics,
3.2.7.3 project metrics:
3.2.7.4 Effort variance,
3.2.7.5 Schedule variance,
3.2.7.6 effort distribution across phases.
3.2.7.7 Progress metrics:
3.2.7.8 test defect metrics,
3.2.7.9 development defect metrics.

Text Book:

1: Software Testing: Srinivasan Desikan

2: Software Testing : Ron, Patton Publisher

UNIT IV Practicals
1. Introduction Introduction
1.1 Software Testing
1.2 Testing methods
1.3 Testing levels
1.4 Methods of Software Testing
2. Test Scenarios
3. Test Case:
3.1Writing Test Cases
3.2Test case execution
4. SCENARIOS
4.1 SCENARIO TO LOG IN TO FLIGHT APPLICATION
4.2 SCENARIO TO LOG OUT
4.3 SCENARIO TO BOOK A TICKET
 4.4 SCENARIO TO UPDATE THE ORDER
4.5 SCENARIO TO DELETE AN ORDER
4.6 SCENARIO TO OPEN AN ORDER
4.7 SCENARIO TO VIEW AGENTS REPORTS
4.8 SCENARIO TO VIEW TOTAL NUMBER OF TICKETS SOLD
5. Test Cases:
5.1 Flight Reservation:
5.2 Functional test cases Integration Test cases System test cases
6. AUTOMATION- QTP
6.1Introduction to QTP
6.2Record, Run and Analyzing Test.
6.3Perform multiple actions.
6.4Inserting checkpoints.
6.1.1 Standard Checkpoint
6.1.2 Image Checkpoint
6.1.3 Table Checkpoint
6.1.4 Text Checkpoint
6.1.5 Text Area Checkpoint
6.1.6 Bitmap Checkpoint
6.1.7 Database Checkpoint
7. Working with Data Tables

PROJECT WORK

Teaching Duration of Marks

Title Teachin Hrs/Week Exam(Hrs)
Subjec g
t Code IA Dissertation Viva Project Min.for
Th. Pr. max. Min. pass
6 Project CS - 24 03 60 100 40 28 40
BCA1 work
Total - 24 200

Project Guide Lines

  Maximum 2 students shall be allowed to take up a project.
 Each student will have to work for 24 hours per week whether in the college
premises or outside. If a student opts for industrial outside project, a college
teacher has to be an internal guide. In this case the student has to
report/present his/her progress twice in a week.
 Guiding one project shall be considered as 4 hours of practical per week as
the work load for hte concerned internal guide.
 Each student shall submit his/her project synopsis to the concerned guide
within 15 days in consultation with internal guide from the commencement
of the respctive semester.
 Each student has to carry out 2 project seminars compulsorily in project
duration.
 Each seminar will be considered for thier internal assessment.
Scheme of Valuation -200 marks

- IA – 60 Marks
o Synopsis - 20 Marks
o Seminar 1 - 20 Marks
o Seminar 2 - 20 Marks
- Dissertation -100 Marks
o Documentation - 40 Marks
o Presentation / Demonstration - 60 Marks

- Viva - 40 Marks
Note: During the practical examination maximum 5 projects have to be evaluated
in a batch