The document outlines an assignment for a software project to develop a newspaper delivery system for a small town. It includes objectives to manage the delivery of newspapers and magazines to customers and generate automatic bills. It discusses major functions of the software including managing customer records and publications, an automated billing system, and using geographic information. It also includes sections on project organization, scheduling, risk assessment, and supports needed. The overall aim is to accurately and efficiently deliver publications to customers.

1. ASSIGNMENT NO 2
NEWS PAPER DELIVERY SYSTEM
1

2. Department of IME
Indian Institute of Technology Kanpur
NAME OF INSTRUCTOR
ASSIGNMENT NO 2
Dr Subhas C Misra, PhD (Carleton), PDF (Harvard) ADVISOR,
Indo Canada Education Council ASSOCIATE PROFESSOR, IME
Department, IIT Kanpur NSERC Fellow 2008, Harvard
University, USA Former Visiting Scientist, Harvard University,
USA WARDEN, STUDENTS HALL OF RESIDENCE III, IIT Kanpur
SEMINAR CONVENER, IME Department, IIT Kanpur
NAME OF STUDENTS
16101013 SQN LDR INDERJEET SINGH
17203269 ARVIND VISHAVKARMA
Dr S C Mishra
2

3. PREVIEW
 OBJECTIVES
 MAJOR FUNCTIONS BY SOFTWARE
 GIS
 PROJECT STAFFING
 BUDGET & INITIAL TIME ESTIMATE
 GANTT CHART
 RESOURCE ALLOCATION
 ACTIVITY ON ARROW DIAGRAM
 ACTIVITY ON NODE DIAGRAM
 SOFTWARE PROCESS
 PROJECT RISK
 RISK ASSESSMENT
 SCHEDULING
 SUPPORTS
 WAY AHEAD & CHALLANGES
3

4. PART 1
16101013
SQN LDR INDERJEET SINGH
4

5. OBJECTIVES
• Intended to Manage
o Delivery System of newspaper & Magazines in a
small town – IIT KANPUR
o Intended for use by newsagents who were casual
users of computer system
5

6. • Software project management is an art of planning & leading software
projects
• Our group – considered this project as a live project & worked over it – for
days & nights
• Name of the company – “XYZ PVT LTD”
• Company logo -
OVERVIEW
6

7. MAJOR FUNCTIONS OF SOFTWARE
• Print list of publications to be delivered at different addresses on a daily
basis
• Automatic bills generation – Monthly & delivering it to customers along
with newspaper
• Functionality of having a Holiday
• Delivery on a non regular basis, as & when required by the customer
• Able to manage the Geographic Information so that it prints information
for the delivery person in the order of delivery
7

8. FUNCTIONALITY
• Record of Publications to be delivered each day
• Customer records – subscribed newspaper, magazines, billing information
• Automated billing system – Monthly
• Occasional delivery of magazines, journals
• Managing simple geographic information
• Exception conditions – customers on holidays
• Applications & Database working in tandem
• Accurately & efficiently reaching out to customers in most responsive way & provide
Master Schedule
• List of addresses & corresponding newspaper/publication delivered at a particular
address
8

9. FUNCTIONALITY
• Billing on – pre decided fixed date
• End to end monitoring & tracking tool right
• All servers & clients system work in tandem & co-ordination
• Central server to control other systems – with a backup
• When customers subscribe for a publication on irregular basis – their names would be included in
the daily list
• Holidays – few or all newspapers & publications would not be delivered
• Geographic Information enabled systems – prints information for the delivery person – in order of
delivery
9

10. GIS
10

11. 11

12. Feasibility study (A1)
Requirement and
Analysis(A2)
Design and Software
project plan(A3) Implementation(A4)
Testing Plan(A5)
Staff training(A6)
Project Planning

13. Project Organization

14. • Project Manager
Project managers have the responsibility of the planning, organising, the execution
and closing of a project. It is up to them to gather and allocate the necessary
resources for the project, gather the right people with the correct skills for the
project, overseeing, monitoring the design of the projects output and serving as a
liaison with his superiors and the recipient of the final output.
• Business Analyst
A Business Analyst is a person who will deal with customers and specify the
direction to the software project. This person will analyze the requirements, work out
the project strategy and write documentation.
• Software Developer
A developer is in charge of developing the code and implementing the design
specification to the definitions outlined in the requirements.
Project Organization

15. • Software Architect
A designer is in charge of drawing up the architecture of the system and the specifics of
how the many modules contained in the project will interconnect with each other at a
high level of development. He is in charge of making sure that the various requirements
of the project are taken into account before proper coding of the system begins.
• Software Tester
A software tester's job is to “break” the software he is testing. This unearths potential
problems with the software and helps the design process along by ensuring a near
faultless product at every step. When familiarity with the software is achieved, a tester
would also help with functional testing, scalability testing and integration testing.
• Requirements Engineer
A requirements Engineer is in charge of working with the projects stakeholders and end
users to elicit, understand, analyse, and document the requirements for a system in
order to solve a given business problem.
Project Organization

16. 17-Feb 19-Feb 21-Feb 23-Feb 25-Feb 27-Feb 01-Mar 03-Mar 05-Mar 07-Mar
Requirement Gathering
Database Design
Geographical Information
System
User Interface Design
Testing And Implimentation
Requirement GatheringDatabase DesignGeographical Information SystemUser Interface DesignTesting And Implimentation
STARTING DATE 17-Feb20-Feb27-Feb27-Feb04-Mar
DAYS TO COMPLETE 37432
GANTT CHART
16

17. 0
1
2
DUBEY
SHARMA
RESOURCE ALLOCATION
REQUIREMENT
GATHERING DATA DESIGN GIS
USER INTERFACE
DESIGN
TESTING &
IMPLEMENTATION
17

18. 30 50
40
Task Name
ES DR EF
LS TF LF
Critical path activity
Normal activity
ES = Earliest start
EF = Earliest finish
LS = Latest start
LF = Latest finish
DR = Duration
TF = Total Float
Dummy Normal activity
Dummy Critical path activity
LEGENDS
18

19. 21 3
A B
73
4
4
6
E
2
ACTIVITY ON ARROW DIAGRAM
19

20. ACTIVITY ON NODE DIAGRAM
20

21. SOFTWARE PROCESS
• We used Spiral Model for processing of the data (changed as per our requirements)
• Risk management at regular stages – in development cycle
• Spiral model – spirals down to a number of iterations
• Fourth quadrant represents following activities :-
 Formulates plan to
 Identify software targets
 Selected to implement the program
 Clarify the project development restrictions
 Risk Analysis – Analytical assessment of selected programs & how to identify and eliminate risk
 Implementation of Project – Implementation of software development & verification
 Customer Evaluation
Evaluation to development work
 Proposal of amendments
 Plans to formulate the next step
21

22. SOFTWARE PROCESS
22

23. PROJECT RISK
• Two prong process
1. Risk Assessment (what risks are? & what to focus on?)
a. Preparing list of potential dangers affecting project
b. Assessing probability of occurrence & potential loss of each item listed
c. Ranking items (from most to least dangerous)
2. Risk Control
a. Come up with techniques & strategies to mitigate highest ordered risks
b. Implementing strategies to resolve the highest order risk factors
c. Monitoring effectiveness of strategies & changing levels of risk throughout the project 23

24. RISK ASSESSMENT
RISK CATEGORIES
Schedule OperationalBudget Technical Programmatic
• When project tasks
& schedule not
addressed
• Possibilities
 Wrong time
estimation
 Resources not
tracked
properly
 Failure to
identify
complex
functionalities
 Unexpected
project scope
expansion
• Wrong budget
estimation
• Cost overruns
• Project scope
expansion
• Improper process
implementation, failed
system or external event
risk
• Causes
 Failure to address
priority conflicts
 Failure to resolve
responsibilities
 Insufficient resources
 No resource planning
 No communication in
team
• Continuous changing
requirements
• No advanced technology
available
• Product is complex to
implement
• Difficult project modulus
integration
• Incomplete
understanding of
requirements
• Loss of data due to
corruption
• Building simple and
user friendly
software
24

25. PROJECT RISK : PROBABILITY & IMPACT
CATEGORY RISKS PROBABILITY IMPACT (1 MOST SERIOUS &
4 IS LEAST SERIOUS)
SCHEDULE RISK PROJECT RUNNING OUT OF SCHEDULE & NOT
MEETING DELIVERY DATES
35% 1
BUDGET RISK COST OVERRUN 20% 1
OPERATIONAL RISK RISK OF LOSS DUE TO IMPROPER PROCESS
IMPLEMENTATION, FAILED SYSTEM OR SOME
EXTERNAL EVENTS RISKS
15% 2
TECHNICAL RISK FAILURE OF FUNCTIONALITY &
PERFORMANCE
10% 2
PROGRAMMATIC RISK INCOMPLETE UNDERSTANDING OF
REQUIREMENT, LOSS OF DATA – CORRUPTION
ETC
10% 3
TECHNOLOGY RISK OBSOLETE TECHNOLOGY 5% 2
BUSINESS IMPACT PRODUCTION MAY HARM BUSINESS 5% 3 25

26. SCHEDULING PRINCIPLES : AVOID DELAYS
1. Compartmentalization
a) Divides project in several tasks
b) Makes project manageable
c) Becomes easier to prepare project schedule according to tasks
2. Interdependency
a) Task interrelationship
b) Interdependency of one or more activities or tasks on each other
3. Time allocation
a) Assigns work units
b) Estimated start date & end date on a full time or part time basis
26

27. 4. Effort validation
a) Made sure resources are available
b) Project management teams have defined member of team members
c) Allocation must be according to effort & time required to complete task
5. Defined responsibilities
a) People assigned with duties to perform
b) According to skills & abilities – perform assigned task
6. Defined outcomes
a) Each task to have an output
b) Achieved after completion of task
c) Outcomes in form of product & these products are combined in deliverables
SCHEDULING PRINCIPLES : AVOID DELAYS
27

28. SUPPORTS
1. CENTRAL SERVERS
2. LAN SYSTEMS
3. DATABASE SERVERS
4. WEB SERVERS
5. MAIL SERVERS
6. BACK-UP TAPES/DISKS
7. BACK - UP SERVERS
1. DATA SUPPORT SOFTWARE
2. HIGH LEVEL LANGUAGE
ENVIRONMENT
3. NETWORK PROTOCOL
4. WEB TECHNOLOGY
5. GUI SOFTWARE
6. TESTING SOFTWARE
7. DEVELOPMENT TOOL
8. SYSTEM REQUIREMENTS
HARDWARE
1. Managing / defining user access to
system
2. Maintenance of website / updation to
include newer features
3. Maintenance of back end servers
4. Creation & regular updation of servers
& disks
5. Ensure 27X7 LAN connectivity
PERSONNELSOFTWARE
28

29. WAY AHEAD & CHALLANGES
• Use of drones for newspaper delivery – long term benefits
• Use of ECS for billing – Paytm etc – (cashless economy)
• Use of recycling the old news papers / donation of old
magazines / periodicals to under privileged (Swaach Bharat
Abhiyaan)
FUTURE & WAY AHEAD
• Use of print media – environment friendly (Connect India)
• With time need to cope up with the present day to day
advancements & technologies
• Targeting small towns / villages (Target market)
CHALLANGES
29

30. Thank You
30

31. ANY QUESTIONS
31