Projects

Development of a split screen application for the data entry of the shipments.

 

Title of the project

 

Development of a split screen application for the data entry of the shipments.

 

Abstract of the project

 

This project is aimed at developing an online data entry system that will enable image assisted data entry for the shipment for the courier logistics. The scanned image if available will be displayed on the left side of the screen when the Airway Bill Number (AWB) is entered on the right side. This is a POC (Proof Of Concept) assignment, which can be showcased to any organization where chunk of the work is paper-based.

 

Keywords

 

Generic Technology keywords

 

Databases, Network and middleware, Programming

 

Specific Technology keywords

 

MS-SQL server, WebLogic application server, Java Server Pages

 

Unix, Shell, C, Oracle

 

Project type keywords

 

Analysis, Design, Implementation, Testing, User Interface

 

Functional components of the project

 

Following is a list of functionalities of the system. More functionalities that you find appropriate can be added to this list. And, in places where the description of functionality is not adequate, you can make appropriate assumptions and proceed.

 

Pre-condition:

 

Scan some sample images and save the scanned image files. Database table will store the full path where the images are stored. Shipments basic data is already created and present in the table.

 

There are authorized users of the system. Some users are of supervisor privileges. A supervisor can see few reports.

 

  1. A person should be able to

 

  • login to the system through the first page of the application

 

  • Based on the priority of the shipment, highest priority incomplete shipment should be displayed.

 

  • User can enter the data for the shipment in the form being displayed on the screen.

 

  • Save the data/defer the data entry for himself

 

  • User can stop the process

 

  1. If the user is supervisor then he can change the priority settings. He can see the reports as user performance, deferred shipment report.

 

Steps to start-off the project

 

There are couple of alternatives to implement such a system.

 

A. Microsoft platform: The system is developed using Active Server Pages as the

     front end and SQL Server as the back end.

 

B. The system can be developed using Java server pages as the front end and any  

     relational database (eg  Oracle )

 

It will be more effective if the tasks of pre-conditions are automated with the shell scripts. i.e. uploaded basic data with loader scripts, update the data for the image full path etc.

 

The following steps will be helpful to start off the project.

 

  1. Study and be comfortable with technologies such as
    1. Active Server Pages/HTML and SQL server.
    2. Unix commands, Shell programming, Tools like AWK, Java server pages, oracle SQL etc.

            Some links to these technologies are given in the ‘Guidelines and References’ 

            section of this document

 

  1. Make a database of people at different levels with their roles and form a hierarchy of them, like which role reports to which particular role. Decide on the various levels of privileges and if needed you can assign higher features for the individual roles.

 

  1. Assign a Admin who will create user-ids for the people in the intranet of  your lab or in the internet. These ids will be used for application. The Admin will also take care of assigning the logins to the users of the system

 

  1. Create the front-page of the system as login page and also give a brief description about the system and a login box

 

Requirements

 

Hardware requirements

 

Number

Description

Alternatives (If available)

1

PC with 2 GB hard-disk and 256 MB RAM

Not-Applicable

2

 

 

 

Software requirements

 

Number

Description

Alternatives (If available)

1

Windows 95/98/XP with MS-office

Not Applicable

2

MS-SQL server

MS-Access

3

Linux

Not Applicable

4

Oracle database system

Informix

 

Manpower requirements

 

4 students can complete this in 3.5 months if they work fulltime on it.

1 lead, 2 GUI, 1 DBA

 

Milestones and Timelines

 

Number

Milestone Name

Milestone Description

 

 

Timeline

 

Week no. 

from the start

of the project

Remarks

 

 

1

Requirements Specification

Complete specification of the system (with appropriate assumptions) including the identification of the fields that makes data entry complete.

A document detailing the same should be written and a presentation should  be made.

1-2

Better if you can add some more functionality related to those mentioned.

2

Technology familiarization

Understanding of the technology needed to implement the project.

3-4

The presentation should be from the point of view of being able to apply it to the project, rather than from a theoretical perspective.

3

Database creation

A database of atleast 25 records of users  should be created. Three of them should be with supervisor privileges.

5-6

It is important to finalize on the database at this stage itself so that development and testing  can proceed with the actual database itself.

4

Design Document

Prepare flow-charts to  represent the data  navigations.

Give the technical, functional overview.

Write the pseudo-code.

7-9

The scenarios should map to the requirement specification (ie, for each requirement that is specified, a corresponding scenario should be there).

5

Implementation of the front-end of the system

Implementation of the main screen giving the login, screen that follows the login giving various options, screens for each of the options.

10-12

During this milestone period, it would be a good idea for the team (or one person from the team) to start working on a test-plan for the entire system. This test-plan can be updated as and when new scenarios come to mind.

6

Integrating the front-end with the database

The front-end developed in the earlier milestone will now be able to update the database.

12-13

 

7

Integration Testing

The system should be thoroughly tested by running all the testcases written for the system (from milestone 5).

14

Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged.

8

Final Review

Issues found during the previous milestone are fixed and the system is ready for the final review.

15

During the final review of the project, it should be checked that all the requirements specified during milestone number 1 are fulfilled (or appropriate reasons given for not fulfilling the same)

 

Guidelines and References

 

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnasp/html/asptutorial.asp (ASP tutorial)

 

http://www.functionx.com/sqlserver/ (SQL-server tutorial)

 

http://heather.cs.ucdavis.edu/~matloff/UnixAndC/Unix/CShellII.html (Shell script introduction)



Tags :
0
Your rating: None