1

SIX SEMESTER TRAINING PROJECT REPORT ON VAS 4 IT

FCS SOFTWARE SOLUTION NOIDA

SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE MASTER OF COMPUTER APPLICATION OF

UTTARAKHAND TECHNICAL UNIVERSITY,DEHRADUN

SUBMITTED TO: INTERNAL GUIDE Name: Shikha Saraswat Designation: Asst. Professor Cor.Trainee IMS, Dehradun EXTERNAL GUIDE Name: Vikash Tripathi Designation: Company Name: FCS Location: Noida SUBMITTED BY: Sandeep Singh Dogra (10140600107)

INSTITUTE OF MANAGEMENT STUDIES-DEHRADUN

BATCH 2010-2013 ACKNOWLEDGEMENT
We would like to pay sincere gratitude to Honorable Chairman Dr. Pawan Agarwal who created a healthy and technical Environment for the successful completion of the project. We humbly extend our words of gratitude to MCA faculty Vishok Kumar Singh and other faculty members for providing us with their valuable time and help whenever it was required. We would like to take this opportunity to express our sincere and profound thanks to our guides. For their constant encouragement and guidance throughout the project work. They gladly all pains in going through our work, and participated in enlightening and motivating discussions, which were extremely useful. The work of this project started on 18 Feb. Since then a large no of teacher and student have made valuable suggestion, which I have incorporated in this work. And finally, thanks to all those who inspired us directly or indirectly. Sandeep Singh Dogra

CERTIFICATE
I have the pleasure in certifying that Mr. Sandeep Singh Dogra is a confide student of VI th Semester of the Master of Computer Application (Batch 2010-2013), of Institute of Management Studies, Dehradun under Institute Roll No. 10140600107.

He has completed his/her project work entitled VAS 4 IT under my guidance.

I certify that this is his original effort & has not been copied from any other source. This project has also not been submitted in any other Institute / University for the purpose of award of any degree course.

This project fulfils the requirement of the curriculum prescribed for the said course. I recommend this project work for evaluation & consideration for the award of MCA to the student.

Signature Name of the Guide Designation Date

: : Shikha Saraswat : Asst. Professor :

Company Certificate

List of contents
Serial no 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Content TITLE PAGE ACKNOWLEDGEMENT INTERNAL GUIDE CERTIFICATE COMPANY CERTIFICATE LIST OF CONTENTS COMPANY PROFILE ABOUT PROJECT OBJECTIVE OF VAS 4 IT SYSTEM SPECIFICATION SYSTEM ANALYSIS STRUCTURED ANALYSIS E-R DIAGRAM OF DATABASE USE CASE DBMS SYSTEM DESIGN SNAPSHOTS TESTING MAINTANCE FUTURE OF THE PROJECT BIBLIOGRAPHY Page no 1 2 3 4 5 6 7 8 10 11 13 16 17 20 21 25 30 37 42 44

Company Profile
FCS Software Solutions Ltd is a leading provider of IT services. The company is engaged in marketing and providing information technology (IT) and information technology enabled services (ITeS) in the United States. They have a huge offshore center in India that caters to a global clientele. The company has two wholly owned subsidiaries, namely FCS Software Solutions America Ltd. and FCS Software Middle East FZE. The company's business is divided into three strategic business units (SBUs), namely IT consulting, education and infrastructure management. The company's IT consulting division provides application maintenance. They also provide ongoing functional and application support for a customer's application maintenance needs. The company operates in three geographical segments India, Middle East and the United States. FCS Software Solutions Ltd was incorporated on May 5, 1993 as a private limited company with the name Fatah Computer Services Pvt. Ltd. In the year 1994, the company acquired a plot at Noida for building their first delivery center. They started construction of building and completed the first phase in the year 1996. They got ISO 9001 certification by KPMG during the year. In the year 1999, the company established competence in Business Workflow Applications (Lotus Domino) and Digital Consulting (MS and Sun technologies). In December 29, 1999, the company was converted into public limited company and the name was changed to Fatah Computer Services Ltd. In April 19, 2000, the name of the company was changed from Fatah Computer Services Ltd to FCS Software Solutions Ltd. In the year 2001, the company established Dedicated IPLC link between Noida and California office and started aggressive Sales and Marketing for their services. They added 24/7 Technical Support Services to their portfolio. In the year 2002, the company bagged and executed Workflow Automation and Digital Consulting projects from Fortune 500 and other companies in Office Automation, Home Appliances. In the year 2004, the company established Center of Excellence to service a large client in India, UK and Asia - Pacific for providing services to clients in all 3 segments, namely Application Development, Elearning and Technical Support. In the year 2005, the company came with Initial Public Offer (IPO) and became listed public company with both the exchanges i.e. BSE and NSE. In November 2005, they started operation in Punchkula (Haryana) in leased premises. In the year 2006, the company acquired plot in Rajeev Gandhi Chandigarh Technology Park, Chandigarh. Also, they acquired a plot in Noida. In June 26, 2006, they started office in Chennai. In October 2006, the company incorporated a subsidiary, namely FCS Software Solutions America Ltd. During the year 2007-08, the company extended their base in a Tier 2 city, i.e., Chandigarh. Also, they also established new development centers in Europe, and also coming up in Singapore. During the year 2008-09, the company also extended their base in a Tier 2 city, i.e., Dehradun. They also developed additional seats in their Noida and Chandigarh centers. During the year 2009-10, the company started operations in their fourth unit at Dehradun to get the benefit of low cost manpower and other tax incentives of Uttarakhand government. They started their new global delivery center in Mumbai in order to strengthen their segment of Banking, Financial Services and Insurance. In October 2009, the company inaugurated its subsidiary in Middle East, Ras Al Khaimah - Free Trade Zone and entered into agreement with MACNES in UAE for promoting and selling its services to their clients. In April 2010, the company entered into agreement with Dewas Udyog, a wholly owned unit of MP State Industries Corp Ltd for work together on mutually exclusive basis for the identified projects. In June 2010, the company secured a three year contract in Middle East. The three year contract includes data center consolidation, commissioning/ decommissioning managed services, space optimization, energy management, network optimization, capacity planning, 24/7 monitoring, latency management, patch, anti virus, back ups, archiving and disaster recovery management as its scope of work. In July 2010, the company launched mobile applications division with Rs 200 million planned investment for providing mobile application services.

ABOUT PROJECT
A value-added service (VAS) is a website which includes popular telecommunications industry term for non-core services, or in short, all services beyond standard voice calls and fax transmissions. However, it can be used in any service industry, for services available at little or no cost, to promote their primary business. In the telecommunication industry, on a conceptual level, value-added services add value to the standard service offering, spurring the subscriber to use their phone more and allowing the operator to drive up their ARPU. For mobile phones, while technologies like SMS, MMS and data access were historically usually considered value-added services, but in recent years SMS, MMS and data access have more and more become core services, and VAS therefore has beginning to exclude those services. A distinction may also be made between standard (peer-to-peer) content and premiumcharged content. These are called mobile value-added services (MVAS) which are often simply referred as VAS. Value-added services are supplied either in-house by the mobile network operator themselves or by a third-party value-added service provider (VASP), also known as a content provider (CP) such as All Headline News or Reuters. VASPs typically connect to the operator using protocols like Short message peer-to-peer protocol (SMPP), connecting either directly to the short message service centre (SMSC) or, increasingly, to a messaging gateway that gives the operator better control of the content. Overview: VAS-IT is a simple Website which provides user interface. In this website, many types of services available like sending Messages by SMPT protocol, VAS-IT based on three-tier architecture which is used for security purpose

OBJECTIVE OF THE VAS 4 IT

Despite being the second largest nation in the world, both in terms of people and mobile phone subscribers, India has nearly the lowest telecom revenue per user (ARPU) in the world. The number of mobile phone subscribers in India, just under one billion, is more than three times what it was in 2008, but it's ARPU is still more than four times less than the ARPU in China, and more than 24 times less than the ARPU in the U.S. While much of this has to do with low call prices due to intense competition between MNOs (India has 13 different telecom operators) Where things start to look brighter is in the new found focus and spending by users on value added services (VAS). Increased Smartphones adoption and growing mobile internet penetration have led operators to increase the value added services they offer to their subscribers. Operators across India now offer mobile services related to:

Health: MNOs have partnered with healthcare companies to help users find hospitals, schedule appointments, get medical advice, and facilitate their treatment. Education: Partnering with various NGOs, MNOs now offer real-time interactive courses, IVR-based education, and additional initiatives aimed at underprivileged children. Commerce: Mobile payment systems have already taken off in India, encouraging telcos to offer other services such as microfinance, retailing, and mobile wallet. Infotainment: Users can subscribe to various infotainment services, receiving everything from sports scores and travel updates, to ringtones and mythological stories, all on their mobile phones. Agriculture: Services for farmers help provide them access to market conditions, commodity prices, weather updates and more.

These services, and more, have led to a steady increase in VAS revenue over the past few years. The VAS market in India is expected to grow roughly $6.6 billion in 2013, a more than threefold increase from 2009. As more Indian consumers gain access to web and inexpensive Smartphone, this number will continue to grow. Now into successful 13th edition - The convention will create India's best VAS forum in India Don't miss this fantastic opportunity to Experience new revenue generating strategies and learn innovative business models! Key topics to be discussed at the event are:

Exploring the possibilities of boosting web site designing VAS revenue generation. Understanding the evolution of web content in India - The realization of exciting new

Revenue streams.

Innovative Mobile VAS offerings & understanding the creation of value added services that sells. Examining effective business models for ensuring profitable VAS offerings in India. Innovating your strategies in creating new revenue streams through the use of web messaging. Understanding the effects of convergence to the dynamic landscape of VAS. The evolution of location based services in India - Opportunities and challenges. Understanding the dynamics of fast changing landscape of mobile entertainment. Maximizing your marketing capabilities through advertising.

SYSTEM SPECIFICATION:

10

The minimum Hardware and Software platforms required to build. This project is summarized as follows. Hardware Specification: 1. Intel Pentium PIII or higher version. 2.256 MB RAM. 3.640 GB HDD. 4. Color Monitor. 5. Standard Keyboard. 6. Optical Mouse.
Operating System:

Windows -98/XP

TECHNOLOGY USED FOR PROJECT DEVELOPMENT

Project VAS 4 IT is a data base management system following technology is used develop this project. S.NO 1. 2. TYPE Front end Back end Name of S/W or Database C# .NET SQL-SERVER

.NET is powerful language, which provides several facilities for developing platform independent software particular. Some of the key features of this language are as follows: .NET support event driven programming. Provides a common programming platform across all Operating System. Offers tool that provides a quick and easy way to develop application. Provides Multithreading and powerful Image and Networking APIs.

Data Storage is the main requirement of the project for which we need a strong Database with large data storage capacity and easy data retrieval. So I choose Sql server 2008 as a data base storage entity. Key feature of sql: Clint/server (distributed processing) environment. Large database and space management.

11

Many concurrent database users.

SYSTEM ANALYSIS
Identification of Need
One must know what the problem in before it can be solve. The basis for a Candidate stem is recognition of a need for improving an information system. Need identified from VAS 4 IT is:To reduce time consuming task of repetitive nature. To provide more security to information regarding personnel. To enhance intellectual distance between the system and exist in real word. To provide more flexibility. To enhance the performance and accuracy.

Feasibility Study Technical Feasibility

Technical feasibility centers on existing computer system (hardware, software) and to what extent it can support the proposed addition. The proposed system is moderately technically feasible. It can seaport the old hardware configuration, but one can feel better performance with RAM capacity of 80 MB RAM, but the software must be changed. The organization must have to install 7.0 SQL and higher version of it to support for the purposed system. The minimum requirements of hardware for proposed system are: RAM minimum 256 MB. Processor Celeron or any Pentium version Hard disk minimum of 512 MB free space So, the proposed system has been evaluated as moderately technically feasible.

Economical Feasibility
Economic analysis is the most frequently used method for evaluating the effectiveness of a candidate system more commonly known as cast/benefit analysis the procedure is to determine the benefits and saving that are expected from a candidate system and compare with cost. If benefit outweighs costs, hens the decision is made to design and implement the system. Otherwise further alteration has to be made.

12

Software Engineering Paradigm

System Requirements Review & Validation

User Requirement Specifications

Software Requirements Review & Validation

Software Requirements

Preliminary Design Review & Validation

Detailed Functional Specifications

Detailed Design Review & Validation

Global Implementation Specifications & Detailed Implementation Specifications

Code and Debugging Review & Validation

Coding & Debugging

Testing Review & Validation

Testing

Maintenance Review & Validation

Maintenance

Fig: Process Engineering of Application Software (Software Development Life Cycle)

13

Structured Analysis
Structured analysis is a set techniques and graphical tools and that allow the analyst to develop a new kind of system specifications that are easily understandable to the user Analyst works primarily with their wits, pencils and paper. Structured analysis considers new goals and structured analysis are:Data Flow Diagram Data Flow Chart ER Diagram

Level 0 DFD:

DETAIL

DETAIL

REPO RT

REPO RT

14

LEVEL 1 DFD:

15

LEVEL 2 DFD:
VAS 4 IT

CONTACT US

HOME

ABOUT

REGISTRATI

BLOG

VIEW REGISTER

LOGIN

YES

NO RECOR D

NO

IF REGIS TER

ER-Diagram of Database RECORD

VIEW

16

Blog BlogID int Blog Discp varchar(100) BlogImg varchar(100) DateTime datetime Name varchar(100) Value varchar(100)

BlogComment Comment id int BlogID int SubComment varchar(100) DateTime datetime IsDelete bit

BlogCommentNe w CommentId int BlogId int SubComment varchar(100) UserId varchar(100) Datetime datetime IsDelete bit

WhatSaying

Id Discp varchar(100) Author varchar(100)

int

ContactUs Fname varchar(22) Email varchar(34) Mobile varchar(20) City varchar(22) AreaCode varchar(22) Comment varchar(22)

NewsLatter NewlettId int Name varchar(50) EmailId varchar(22) Status varchar(200) Create Date Time datetime Fname varchar(22) Phoneno varchar(22) Institution varchar(22) Address varchar(22) PostalCode varchar(22) Country varchar(22) Email varchar(22)

Registration

USE CASE

17

A use case is a set of scenarios that describing an interaction between a user and a system. A use case diagram displays the relationship among actors and use cases. The two main components of a use case diagram are use cases and actors.
Name of use case:

Adding the record in the data base or register in data base the people in the data base.

Description: Admin register Primary actor: Admin Preconditions: Admin Normal flow of events:

already login

The Admin will select the category of user or enter the name, Address, City, State, Country, Pin Code, Date of Birth, Reminder, Anniversary etc. After registration user will get unique Entry number.
Alternative flow of events:

Register in data base and get unique Entry number. Post condition: After this act the company employee will be register.

Name Address Email and Phone details Admin Date of Birth, Anniversary,Reminderother etc.
Name of use case: Description:

change password.

Admin change the password admin

Primary actor:

CODE EFFICIENCY

18

In an effort to maintain computational efficiency and to allow the eventual adaptation of the algorithm to face tracking applications, intense optimization of the code has been performed. Although further development is in progress, the algorithm is currently fast and compact enough to run interactively on most generic platforms. First the sequential hierarchical search which proceeds from large scales to small scales. This allows a rapid convergence if the face is dominant in the image. Furthermore, the algorithm does not always flow through the complete loop. It stops as soon as one of the modules reports a failure and loops back to an earlier stage. For example, we do not search for a mouth if no eyes are found. In this case, no time is wasted in the mouth module. Additionally, we utilized special programming techniques to reduce the run-time. For instance, wave propagation is used to generate the symmetry maps. This provides a computational efficiency that makes the symmetry operator a practical tool. The 3D normalization algorithm is also extremely efficient and uses look-up tables and minimal calculations for increased speed. The execution times are measure on an SGI Indy machine which has a rating equivalent to that of a 1996 home personal computer. The efficiency of the code allows a face to be found in an image in less than 1 second if it is the dominant structure. However, we loop through all objects in the scene in an attempt to find all possible faces. Thus, the algorithm's loop is traversed multiple times even though a face could have been detected in an earlier iteration of the loop.

Optimization Of Code

19

Optimization refers to increase in the throughput of the system with minimal use of effort and system resources. It also includes faster response through better system design practices including optimal utilization of code, normalized database structures and their use in the code. The very first instance that stands for optimization of this application is the choice of the second alternative of the Feasibility study, that is, as specified earlier would prove to be most favorable and best possible for the progress in the working of the company. The other criteria that ensure the optimization of this software application are enlisted as under: Use of modular design structure of application development. Use of Normalized Database Structures-Database Optimization. Use of code modules extensively-Code Optimization. Use of minimum number of code lines for maximum processing of input data. Allocating/de-allocating memory for the objects used in the code as and when required. Garbage collection Re-use of similar input forms/output reports wherever necessary to reduce the overall size of the application.

DBMS (DATABASE MANAGEMENT SYSTEM)

20

DATABASE MANAGEMENT SYSTEM

Between the data base itself (i.e. where the data is actually stored) and the User of the system is a layer of software called DBMS. All requests from the users for access to the database from hardware level details. All database management systems allow users to create containers (i.e. relation and tables) for data storage and management.

ADVANTAGES OF DBMS:
In brief advantages of DBMS are as follows: * Centralized management and control over the data. * Reduction of redundancies. * Data can be shared. * Data integrity can be maintained. * Security Restriction can be applied. * Data Inconsistency can be avoided * Data Independency can be obtained.

SYSTEM DESIGN

21

Designing is the most important part of software development. It requires a careful planning and logical thinking on the part of the system designer. Designing the software means to plan how the various parts of the software are going to meet the software goals. It should be done with care because if the phase contains any error then it is going to effect the performance of the system as a result it may take more processing time, more of coding and extra load System design involves two steps. Logical design. Physical design LOGICAL DESIGN: When formulating the logical design of a system, the detailed specification for the new system is written. All it is features like outputs, inputs, file design, databases and procedures are described in a manner that meets the project requirements. The statement of this feature is termed as the design specification of the system. The logical design of a system shows the major features and how they are related to one another. Specifications describe methods to enter data, run reports, copy files and detect and handle errors if and when they occur. The following steps were followed for the lo9gical design of the system Design of the new information. Identification of entity, attributes & entity relationships. Preparation system file design

22

Study of feasibility of the system. Division the system into subsystems. Determination of the sub system requirements. The overall design of the system is depicted pictorially in system flowchart. The specification of the subsystems is presented with the help of data flow diagrams. PHYSICAL DESIGN: The physical design involves the development of the system with the help of the logical design. The physical features of the system, via the hardware, the input forms and outputs, the software to be developed are considered in theirs phase. The file structures, their characteristics, storage structure and media area also determined. The program modules are written to meet the subsystem requirements. At the end of this system will be ready for testing and implementation purposes. The system design involves following three phase: A. Design of output B. Design of input C. Design of files

A. DESIGN OF OUTPUT: Output is the most important and direct source of information to the user. Efficient, intelligible output design should improve the system, relationships with the user and help in decision making. A form for output is a hardcopy from the printer. The user can take

23

hardcopies of all reports from the prints from the prints option in the file menu of the browse4r used. When designing the outputs the following steps were given special attention. Determination of the information contents of the outputs Decisions as to whether to display or print the information and selection of the output medium. Arrangement for the presentation of information in acceptable format. Decision as how to distribute the output to the intended recipients. B. DESIGN OF INPUT/FORMS:Inaccurate input data are the most common cause of error in the data processing. Errors entered by the data entry operator can be controlled by the input design. Input design is the process of converting user originated inputs to computer based formats. The goal of designing input data is to make data entry as easy, logical and free from errors as possible. In entering data, operator need to know the following. In this we decide the following input design details:

What data to input What medium to use How the data should be arranged or coded The dialogue to guide users in providing input Data items and transactions needing validation to detect errors Methods for performing input validation and steps to follow when errors occur

24

The design of input also includes specifying the means by which end-users and system operators direct the system in which actions to take. Inaccurate input data are the most common use of error in data processing, errors entered by the data entry operator can be controlled by the input design is the process of converting user originated inputs to a computer based format. The goals of designing input data are to make a data entry as easy as possible, logical and free from errors. In entering data operators need to know the following points Allocated space for each field Field sequence, which must match in the source documents The format in which data fields are entered .The data may be of different formats but the user might be required to enter it only one format. DESIGN OF FILES: Design of files may be considered, as the backbone of the web based status monitoring system of cics. It is this area than any other which will be handling more data. How efficiently the system is able to handles to retrieve data, Process it and put it back depends on how well the database has been designed for the proposed system.

SNAPSHOTS OF THE OF PROJECT

25

Home

Page

There will be a home page. It is basically landing page of the site. It will look like this.
In top navigation link there should be About Us, Contact Us, Login and Registration Link

Login Page
Login Page will have following fields o o o o User Id Password Sign In Sign Up

26

About Us Page

27

28

Contact Us Page
This page will have following fields to contact the site administrator. o o o o o o o First Name Mobile Area Code Comment Here FOR COMMENT Email City

29

Registration Page
On this page there will be following fields to register to the site. o o o o o o o Name Email Mobile Password Confirm Password Address Register Button

30

TESTING
Systems testing are an expensive but critical process that can take as much as 50 percent of the budget for program development. The common view of testing held by users is that it is performed to prove that there are no errors in the program. Testing is the process of executing a program with the explicit intention of finding errors that is, making the program fail. A successful test, then, is one that finds an error. Test the modules thoroughly- cover all the access paths. Generate enough data to cover all the access paths arising from conditions. Test the modules by passing wrong data. To test the different access paths, look at the conditional statement. Enter some data in the test file which would satisfy the condition and again test the script. Repeat this process many times. After each test, analyze the log file to ensure proper, understandable and useful messages are present in the log file. Test for locking by invoking multiple concurrent processes.

TESTING OBJECTIVES Testing is a process of executing a program with the intent of finding an error. A goal test case is one that has a probability of finding an as yet undiscovered error. A successful test is one that uncovers an as yet undiscovered error.

31

TESTING PRINCIPLE All tests should be traceable to customer requirements. Test should be planned long before testing begins. The testing should begin in the small and progress towards testing in the large. Exhaustive testing is not possible. To be most efficient, testing should be conducted by an independent third party.

CHARACTERISTICS OF A GOOD TEST A good test has a high probability of finding an error. A good test is not redundant. A good test should be best of breed. A good test should be neither too simple nor too complicated.

TESTING STRATEGIES Test cases are devised with the purpose to find errors in mind. A test case is a set of data that the system will process as normal input.

There are two general strategies for testing software: Code Testing

The code-testing strategy examines the logic of the program. In this kind of testing, analyst develops test cases that result in executing every instruction in the program or module; that is,

32

every path through the program is tested. A path is a specific combination of conditions that is handled by the program. However, even if code testing can be performed in its entirety, it does not guarantee against software failures. This testing strategy does not indicate whether the code meets its specifications nor does it determine whether all aspects are even implemented. Code testing also does not check the range of data that the program will accept.

Specification Testing

To perform specification testing, the analyst examines the specifications stating what the program should do and how it should perform under various conditions. Then test cases are developed for each condition or combination of conditions and submitted for processing. This strategy treats the program as if it were a black box; we do not look into the program to study the code and is not concerned about whether every instruction or path through the program is tested. In that sense, specification testing is not complete testing.

TESTING TECHNIQUES
Regardless of which strategy the analyst follows, there are preferred practices to ensure that the testing is useful. The levels of tests and types of test data, combined with testing libraries, are important aspects of the actual test process.

TYPES OF TESTING

33

WHITE BOX TESTING

BLACK BOX TESTING

WHITE BOX TESTING:

White Box testing which is performed early in the testing process is also called glass-box testing. Using white box testing, the software engineer can derive test cases that Guarantee that all the independent paths within the module have been exercised at least once. Exercise all logical decisions on their true and false sides. Execute all loops at their boundaries and within their operational bounds. Exercise internal data structure to assure their validity.

BLACK BOX TESTING:

Black box testing to be applied during later stage of testing. Black box testing, focuses on the functional requirement of the software. Black box testing enables the software engineer to derive sets of input conditions that will fully exercise the functional requirement of a program. Black box testing enables to find error in the following categories: Incorrect or missing functions. Interface errors. Errors in the data structure or external database access. Performance errors.

34

Initialization and termination errors

By applying Black box testing a set of test cases that satisfy the following criteria - Test cases that reduce, by a count that is greater than one, the number of additional test case must be designed to achieve reasonable testing. Test cases that tell us something about the presence or absence of classes of errors, rather than associated only with the specific test at hand. In order to uncover the errors in the system, a series of test steps Unit, Integration, Validation and System level tests were planned and executed. The following criteria and corresponding tests were applied for all test phases:Interface integrity: Internal and external interfaces were tested as each module is incorporated into the structure. Information content: Tests designed to uncover errors associated with local or global data structures are conducted. Performance: Tests designed to verify performance bounds established during software design were conducted.

Unit Testing:
It was carried out simultaneously along with the coding of the system code modules. In this type of testing: The module interface was tested to ensure that information properly flows into and out of the program unit under test.

35

The local data structures were examined to ensure that data stored temporarily maintains its integrity during all steps in algorithms execution.

Boundary conditions were tested to ensure that the module operates properly at boundaries established to limit or restrict processing.

All independent paths (basis paths) through the control structure were exercised to ensure that all statements in a module have been executed at least once.

All error handling paths were tested. The Main Menu and the other related code modules were used as respective driver and stubs for the module under test consideration. The White-Box testing method of unit testing Control Structure testing was used for developing the test cases for testing the different conditions, Data Flows and Loops in each of the code modules.

Integration Testing:
The objective of this testing was to take the unit tested modules and build a program structure that has been dictated by design. A Top-Down Incremental integration approach was chosen, i.e., Modules were integrated by moving downward through the control hierarchy, beginning with the main control module (main menu). The modules subordinate to this main control module were incorporated into the structure in dept-first manner. At the end of each step in module integration test, Regression testing was also conducted so as to avoid any new error that might have been introduced.

Validation Testing:
Once the software was completely assembled as a package; interface errors uncovered and corrected, final series of software tests for validity of the software was carried out. The

36

Software Validation was carried out through a series of black-box tests such as Equivalence Partitioning and Boundary Value analysis. The Module interfaces (Graphical User Interfaces developed in a Visual Environment) were also tested for proper working of the windows, pull-down menus, mouse operations, data entry using these interfaces, and the report formats. A series of these acceptance tests of the system were carried out at the place where this software system was developed (Alpha Testing) in a natural setting and in a controlled environment. The client was called over for testing the software and by looking over the shoulder of the client/user of the system, all the errors and usage problems were recorded and corrected. Later this software application was put on live testing (Beta Testing) for the client in its original environment. (i.e., at the office of the company) During this phase, it was ensured that all elements of the software configuration have been properly developed, are catalogued, and have the necessary detail to support the maintenance phase of the software life cycle (Configuration Review).

System Testing:
The primary purpose of this phase was to fully exercise the computer-based system; so as to verify that all system elements have been properly integrated and perform allocated functions. On conducting different system tests of forcing the system to fail, it was ensured that the system is fault tolerant and that the recovery is properly performed (Recovery Testing), i.e., the system can resume processing on small errors such as during data entry; and in case of fatal errors such as during data access or other system processing, this software system can gracefully exit the application. Also it was ensured that no other person, other

37

that the designated users of the system can use this software application (Security Testing). Finally, during this testing phase, a criteria listing was also prepared (as given under heading Performance Criteria of this report) to ensured that the system performs smoothly even at peak loads of data processing (Stress & Performance Testing)

MAINTENANCE
Once the system is delivered and installed, there is a brief warranty period during which time the sales unit is responsible for maintenance. The last part of the system development life cycle is system maintenance which is actually the implementation of the post-implementation review plan. When systems are installed, they are generally used for long periods. However, this period of use brings with it the need to continually maintain the system. The study on the maintenance requirement for the information system revealed that: a) 60-90 per cent of the overall cost of software during the life of a system is spent on maintenance. b) In documented cases, the cost of maintenance, when measured on the basis of writing each instruction in coding form, is more than 50 times the cost of developing a system. c) The software demand is increasing at faster rate than supply. Many programmers are devoting more time on systems maintenance than on new software development. There is a backlog of new development work.

38

The maintenance can be classified as corrective, adaption or perfective. Corrective maintenance means repairing, processing or performance failures or making alteration s because of previously ill-defined problems. Adaption maintenance means changing the program functions. Enhancing the performance or modifying the programs according to users additional or changing needs are included in perfective maintenance. Maintenance covers a wide range of activities including correcting coding and design errors, updating documentation and test data and upgrading user support. The keys to reduce the need for maintenance while making it possible to carry on with essential tasks more efficiently are as follows: a) More accurately defining the users requirement during systems development. b) Preparation of system documentation in a better way. c) Using more effective ways for designing processing logic and communicating it to project team members. d) Making better use of existing tools and techniques. e) Managing the systems engineering process effectively.

An addition factor in the success of the maintenance programmer is the work environment. Maintenance programmers have generally been paid less amount and receive less recognition than other programmers. Maintenance demands more orientation and training than any other programming activities, especially for entry-level programmers. The environment must recognize the needs of the maintenance programmer for tools, methods and training.

A system engineer has enormous responsibility towards the successful completion and implementation of a software project. He has to perform a set of duties to do this task effectively. A system engineer basically performs the analysis in which he finds out the objectives and

39

responsibilities of the project to be completed. Later he gets involved in the design stage, in which he alone with other designers. Created a set of designs which help the programmers to develop the programs. Then he instructs people involved in testing process also. System engineers can be recruited from the customers place, if possible. He can also be selected from the software development place. Or he can be recruited from and independent third party also. Each alternative has its own pros and cons. Which are as follows:If the software engineer is from the customer place, then the primary advantage is that he understands the system more clearly than any other person. He has been working in the environment for quite some time, so has knowledge about the tasks which have to be accomplished by the system being developed. Requirements and objectives are already very clear in this mind. He has already association with other employees of the customer place. So id needed, he can get the information from the people concerned, in less time without any problem. The employees also will be more willing to provide information to a person who is one among them, rather than to a person who is from outside. So analysis of requirements and the system, itself can be done better be a system engineer, if he is one of the employees of the client place. But, the employee of the client place may not be well-versed with the software development process. He may not have sufficient technical skill. He may not know the process which is undertaken to develop the software product. He may not be useful in design, coding and testing phase. One more disadvantage is that, the employee of clients place, may try to force the development people to implement the project not only with necessary set of requirement, but also with a set of optional and unnecessary requirements. He may try to take undue advantage of his position by asking the developers to incorporate a large set of requirements. This is not

40

recommended in WIN-WIN model. Both the parties should win. Here only customer is in the winning position. If the software engineer is from the software development place, then the advantage is that he is an expert in the development process. He has experience of dealing with this type of tasks. He has sound analytical and technical skill. He knows the difference between the achievable and nonachievable requirements of a project being undertaken. His position in the company depends in his work performance. So he is totally motivated to excel in the work which he does-the development of efficient software. But, the software engineer from the software development place, may have a problem in dealing with people at the client place, for gathering the requirements. This is because he is not fully aware of the environment of the client place, not aware of the business practices following by the client, not aware of the internal politics of the client company etc. All these play a major role in performing analysis smoothly. But he can become aware of all this, at the cost of time. Personal at the client place, may not be completely side person, to get the right information from them. If the software engineer is from an independent third party, then the advantage is that, he does not try to win against the other person, as is possible, in the above two situations. He tries to perform his job in an non partial manner, which is beneficial to both the partied. And, since we recruit from a reputed company, he may have excellent knowledge of how to heel with the software development process and his expertise can be used for the advantage if the client. But, the only disadvantage is that, he may conduct the development process, by keeping all other things in his mind as constant. He may not be aware of the capability of the development team and the loop holes present in both client and the development side. Both parties may not believe the software

41

engineer, because he is an outside person, and may also try to influence him to take decisions, for their own advantage. An ideal system engineer is a person who gives importance to the quality of the project from a long-run point of view. He should take care of documentation, user-interface design which is generally not given much important. But these small things make the software to have high quality. He should always be doing his work in a proper time schedule. Time becomes the most important factor, and he should take decisions basing on this only. He would always follow the entire cycle of design principles, without omitting anything. Testing should be conducted from the start to end of the no. of people required to complete the project. He should try to reduce the overheads, by recruiting less no of people initially, and try to add persons to the project late. Validation and verification should be conducted from time to time, for all the components individually and also collectively.

FUTURE SCOPE OF THE PROJECT

42

DISTRIBUTION AND MANAGEMENT SYSTEM (DMS): With the proposed software of HUMAN AND RESOURCE MANAGEMENT ready and fully functional the client is now able to manage and hence run the depot work in a much better, accurate and error free manner. It foreseen that the client is bound to experience the following advantages/benefits and future business expansion scope upon installation of this automated solution-HUMAN AND RESOURCE MANAGEMENT. The system is executed on the Windows2000 server and Sql Server 8i. Faster processing of information as compared to the current system with high accuracy and reliability. Automatic and error free report generation as per the specified format. Automatic calculation and generation of correct and precise Bills-thus reducing much of the workload on the accounting staff and the errors arising due to manual calculations. As such the system is at present going to be implemented on site of the Pepsi satisfying the needs of handling the distribution of beverages, right from beverages going out from the depot against each salesman and would be implement. With a fully automated solution, lesser staff, better space utilization and peaceful work environment, the company is bound to experience high turnover. Better vigilance of the Salesmen and tracking of carats is now possible. Better Employee management is foreseen with the a few enhancements in this application. A future application of this system lies in the fact that the proposed system would remain relevant in the future. In case there be any additions or deletion of the products, addition or deletion of any salesman in the any type of modification in future can be implemented easily. The data collected all things will be maintained even in case the system

43

by the DMSP will be useful because it has been developed on the basic structure of the distribution management. All these result in high client-satisfaction, hence, more and more business for the company that will scale the company that will scale the company business to new heights in the forthcoming future.

BIBLIOGRAPHY
The Bibliography contains references to all the documents that relate to the software engineering document, Databases technical references, vendor literature, and standards.

44

Steve Brown, .NET complete reference, BPB Publication Elmasri, Ramez & Navathe, Shamkant B. Fundamental Of Database System, 2/e Petric Norton .NET I.T. Hawryszkiewycz, Introduction to System Analysis & Design, Prentice Hall of India, Roger S. Pressman, Software Engineering, a practitioners Approach, Fourth Edition, 1997. Bipin Desai, An Introduction to Database Systems, Galgotia Publications (West Publishing) 1991. C.J. Date, an Introduction to Database Systems, Volume I, Addison Wesley (Fifth Edition), 1994.

--XX--