Newspaper Delivery System

Digital management of the delivery of newspapers and magazines

Introduction

The Newspaper Delivery System is a user interactive computer system designed specifically for a newspaper and magazine distributor.

Objective will be to manage existing and potential new customers, publications, carriers, routes, and billing information and summary reports as required by this type of business in today's market

A graphical or windows interface will guide the users through the functions described by the users to keep the newspaper service running smoothly.

Sections and their functioning Printing Press: Printing required units of newspaper/magazine according to the plan

Transporter: Transport of newspapers through trucks.

Distribution Centre: It receives copy from contractors and hand over to agents.

Agents: They receive the stocks at distribution center and manage distribution to hawkers

Hawkers: Responsible for the supply of newspapers to the customers.

Billing - generates bills for all households on the system. Acts as the accounting for the business, keeping track of all financial transactions and status of customer accounts

Summary Reports - used to generate summary reports for specified primary and secondary search keys such as a listing of households that subscribe to one particular publication

Project planning and Analysis

Staff AssigningPerson Task

Sarvesh Project Management

Rishi Back End Lead, Expert Opinion

Pandit Content management

Shobhit GUI Design

Suraj Testing

Saptarshi GUI, Interface Developer

Requirements

Print publication

Customerdatabase

Bills delivered

Delivery address

Manager

Delivery date Print for newsagent

User interfacedistributor

Routes

newsagentPrinter Security

Order statement Hardware

Reliability

Geographic information

Message passing

Project Planning

Feasibility study (T1) Requirement and Analysis(T2)

Design and Software project plan(T3) Implementation(T4)

Testing Plan(T5) Staff training(T6)

Timeline and dependenciesTask Timeline Dependencies

T1 5 days

T2 15 days T1

T3 15 days T2

T4 5 days T3

T5 5 days T4

T6 7 days T4,T5

Defining Milestones

• Stage 1- Core product development and testing.

• Stage 2- Windows based GUI and storage.

• Stage 3- Complete installation package with user friendly pdf having procedures.

Gantt Chart

1/6 5/6 10/6 15/6 20/6 25/6 30/6 5/7 10/7 15/7

20/7 25/7

T1

T2

T3

T4

T5

T6

Start

Finish

Supports

• Hardware - Windows Server 2008 (Enterprise Edition ),VM Workstation (Dev ).

• Java 1.7 , Apache Tomcat,UML ,AMXL,XML,Post Gre SQL, Adobe flex .

• Tortoise SVN (File Sharing),ITIL Support Application ( Bug Tracking ).

• CVS –Branched Head (under Separate Lead )

• Network Protocol - IPsec (RFCs 2401, 2406, 2409, 2411)

Metrics

• Code Standards – SOX Complaint , ITIL

• Encoding – UTF – 8 and Unicode Stds

• Code Metrics – Source Lines , Number of Class , Number of Methods

• Developer Time – Coding , Designing ,Testing , Emails , Team Bonding ( usually with Co Developer )

Graphical User InterfaceNewspaper Delivery -x

New Record

Name of customer

Address

City

State ZipDetailed Address and info

Mobile

Remarks

Email

Owes

Money Due

Amount paid

Date last payment

Group 4 Newspapers

Printed Bill

Implementation

Printing Press

Region 1 Region 2 Region 3

Bulk Order

Agent 1

Agent 2

Agent 3

Agent 4

Unloading

Pamphlet Insertion

Batch Formation

Bulk Order

Hawker 1

Hawker 2

Hawker 3

Deliver 2

Deliver 1

Deliver 3

Deliver 4

Deliver 5

Physical Structure of system

• The software will provide user the ability to quickly and easily create and manage schedule of delivery of newspaper.

• The software will provide the user agent to create the master schedule for all the delivery of newspaper as a default.

• The user agent will able to change the schedule and details according to him

• Three versions i.e. Version 1, Version 2 & Version 3 would be made and tested..!

Stages

• Stage 1

This will focus on the completion of the fundamental working of the system reserving most of the work on the graphical user interface until stage 2 . The purpose for this is to keep the focus on making software correct before making the interface product quality. Following members are involved in this iteration:

• Stage 2

Stage 2 will lead to the completion of the software product with the help of stage 1 and user manual and testing with the help of following members.

• Stage 3

This stage will lead with user manual making and plan testing

Process We plan to use the following software process to manage the source code that we will

create

Check in/out (login)

To perform multiple users working simultaneously on the same software , we will make use of a software versioning tool called CVS as part of our configuration management.

Build

To build system we plan to use for each operating system is as follows:

1. Visual C++ 6.0

2. Build script to checkout software. The scripts must be scheduled to run at definite times

MeasurementSLOC-Source Lines Of Code

We plan to take a source lines of code metric at each build (weekly) to help indicate progress. The metric should be included in the build script for automation purposes.

Count of number of Classes

A count of the number of classes will be taken at each build to indicate overall system growth. The metric should be included in the build script.

Number of methods

Enable to guide the complexity.

Time taken by developer

Time spent doing design and re-design

Time spent on testing

Time spent on communicating with the group

Requirement Document

Requirements Document

• 1. What is newspaper delivery system?

• This system is an application to manage the delivery of newspapers and magazines in some small town or area of a larger town. It is intended for use by newsagents who are only casual users of computer systems and should run on a PC or similar hardware.

2. Major Features:● Master Schedule creation● Daily Schedule Creation● Employee information storage.● Customer and publication information storage.● Billing information.● List of employee , customer and publication availability● Holiday and closed day information● Address and geographical region information.● Secure login.

3.How does it work?

● This application works by allowing user to create and edit a master schedule from which daily schedules are derived.

● It involves creating individual employee schedules and assigning them all customers of a particular geographical area.

● Information of publications to be received by each customer daily is entered and sorted by area.

● User can add / delete details of customers, employees and publication on bases of holidays and non working days from master schedule.

● Customer wise bills are prepared by adding up all newspapers and publication received by customer in a month.

Using application.

● This application is easy to use because information is gathered in dialog based format.

● Create master schedule by entering name and area assigned to all news agents.

● For each area, enter customer details and address and weekly schedule of publications received per day.

● Enter details of dates of non availability of consumers and non working days.

Testing Plan

OverviewWe will conduct a series of different tests to fully exercise the Newspaper delivery system. The primary purpose of these tests is to uncover the system’s limitations and measure its full capabilities.

Unit Test

• The objectives of unit test are to:

• Identify unit-level defects by causing corresponding failures to occur.

• Determine if the unit is complete and ready to be submitted for integration as part of delivery procedures.

Integration Test

• The objectives of integration test are to:

• Cause failures involving the distribution of newspaper through the delivery system.

• Confirm that the group of components can be fully integrated to satisfy requirements.

System Test

• The system tests will test the whole system and verify that it meets the requirements defined in the requirements document.

Functional Test

• The objective of this test is to ensure that each element of the application meets the functional requirements.

Performance test

• These tests ensure that the newspaper delivery system provides acceptable response times and does not exceed the specified performance criteria. During these tests, we will measure response.

Security Test

• Security tests will determine how secure the newspaper delivery system is. The tests will try some practice drills to check weather it is done properly.

Recovery Test

• Recovery tests will force the system to fail in a various ways and verify the recovery is properly performed. It is vitally important that all customer information & scheduling data is recovered after a system failure and no corruption of the data occurred.

User Acceptance Test

• Once the system is ready for implementation, user representatives will perform User Acceptance Testing. The purpose of these tests is to confirm that the system is developed according to the specified user requirements and is ready for operational use.

Test Staffing

Unit Testing is the responsibility of the Development Team

Integration Test is the responsibility of both Development and Test Team

System Test is the responsibility of Test Team

User Acceptance Test is the Responsibility of the User Representatives

The test team is responsible for:

writing the detailed plan for the test

supervising the execution of the test

providing resources for the test

documenting the results of the test

updating the plan as a result of the test

Testing the riskRequirements

• The test plan and test schedule are based on the current Requirements Document. Any changes to the requirements could affect the test schedule

Time

• The schedule for each phase is very aggressive and could affect testing. A delay in one of the other phases could result in a subsequent delay in the test phase. Project management support is required to reduce the risk and meet the forecasted completion date.

Hardware/Software

• The Server and PCs (with specified hardware/software) as well as the test database need to be available during normal working hours. Any downtime will affect the test schedule.

Personnel

• It is very important to have experienced testers on this project to develop, perform and validate tests. They should be familiar with the testing tools. Unexpected turnovers can impact the schedule.

The test team will also need the following resources available: developers and test users.