windows task manager

8/7/2019 Windows task manager

http://slidepdf.com/reader/full/windows-task-manager 1/55

ADVANCED WINDOW TASK MANAGER

PROJECT REPORT


BY

Kunal S. Bodke

Aakash S. Kanchan

UNDER THE GUIDANCE OF

PROF U. S. SHIRSHETTI

IN PARTIAL FUFILLMENT OF

DIPLOMA IN INFORMATION TECHNOLOGY

2008-2009

SINHGAD TECHNICAL EDUCATION SOCIETY’S

SOU. VENUTAI CHAVAN POLYTECHNIC

PUNE - 411041

1




SINHGAD TECHNICAL EDUCATION SOCIETY’S

SOU. VENUTAI CHAVAN POLYTECHNIC

PUNE-411041

DEPARTMENT OF INFORMATION TECHNOLOGY

THIS IS TO CERTIFY THATKUNAL S. BODKE

AAKASH S. KANCHAN

OF THIRD YEAR DIPLOMA IN INFORMATION TECHNOLOGY

HAVE SUCCESSFULLY COMPLETED

PROJECT


IN PARTIAL FULLFILLMENT OF

ACADEMIC REQUIREMENT FOR THE YEAR 2008-2009

AS PRESCRIBED BY THE

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

Date:

Place: PUNE

Project In-Charge Head of Department Principal

(Prof. U. S. Shirshetti) (Prof. V. G. Nanaware) (Prof. K. C. Salunke)

2




ACKNOWLEDGMENT

We place on record with great pleasure and express our profound sense

of sincere and deep gratitude to the help and encouragement from those who

are responsible for letting us to explore in depth and providing us with the

fountain of knowledge and experience that, we have gained in the completion

of these felicitations project.

We express our deepest gratitude to our guide Prof. U.S.Shirshetti Sir for

his moral and technical support in completion of our project. We also present

sincere thanks to all other faculty members of our college who are instrumental

in helping us in various ways and for providing inspiration throughout the project

work.

We extend our hearty thanks to our dear friends for extending their

helping hands at the time of need.

Last, but not the least, we present our ineptness to our beloved parents

and family members, without whose patience, and unwavering support, this

project would not have been possible.

THANKING YOU ALL

Kunal S. Bodke

Aakash Kanchan

3




Contents

Abstract

Chapter 1 Introduction

1.1 Existing System

1.2 Objectives of New System

1.3 Proposed System

Chapter 2 Preliminary Survey

2.1 Recognition of Need

2.2 Need for Change

2.3 Initial Investigation

Chapter 3 Feasibility Study

3.1 Feasibility Study

3.2 Feasibility Considerations

3.3 Feasibility Report

Chapter 4 Analysis

4.1 System Analysis:

4.2 Data Collection:

4.3 Information Gathering Tools:

4.4 User Requirement Analysis:

4.5 Forming Logical model of the System with the help of Data-Flow

Diagram (DFD)

Chapter 5 System Design

5.1 Input Design:

5.2 Output Design:

5.3 Language Used

5.4 Hardware & Software Specifications

4




Chapter 6 Testing

6.1 Why Testing is required?

6.2 What to test?6.3 Nature of Test Data?

6.4 Reasons behind Testing

6.5 Contents of Test Plan

6.6 Prototype Testing

6.7 Cutover and Parallel Testing

6.8 Impact on User

6.9 User’s Role in Testing and Implementation

6.10 Plan of execution

6.11 Acceptance test procedure

6.12 The aftermath

Chapter 7 Quality Assurance plans

7.1 What is a QA Project Plan?

7.2 Reasons

7.3 Benefits

Chapter 8 User Manual

8.1 Installation & Setup

8.2 User interface

8.3 Input to application

8.4 Output from application

8.5 Error Messages

Chapter 9 Conclusion and Future Scope

9.1 Conclusion

9.2 Future Scope

5




Abstract

ADVANCED WINDOW TASK MANAGER is software which is used to view and control

processes running in computer such a way that user can use the software effectively by

making application user-friendly.

Features of Windows Manager:

This is a project which is used to do many system level activities easily. It is developed usingVisual Basic 6.0. API (Application Programming Interface) have been used to develop this

project. It consists of a MDI window from which we can open Window Manager. This is

similar to Microsoft Widows Task Manager but the Window Manager that we built hasextended functionality and advanced features.

The Window Manager has quite a number of functionality. They are as follows:

• Freezing a window:

Freezing a window refers to totally stopping the user from working onthat window. All menu items are disabled and the working area is locked.

Such type of functionality is used to protect a machine from unauthorized

users.

• Defreezing a window:

Defreezing is just opposite to the Freezing. Where locked process is

unlocked by user.

• Renaming a window:

We can change the name of a window through the window manager.

• Enabling all objects:

We can enable the objects which are already locked.

• Locking all objects:

Locking all objects refers to completely disable the objects so that the

users cannot work on them. Editable area is turned to grey.

• Keeping a window on top:

This is self explanatory for MS Windows users. We can a window

always on top using this functionality.

• Not keeping a window on top:This is opposite to the previous one. When the user clicks on other

windows the focused window will be behind the window on whichuser clicks.

• Enabling menu items:

Using this feature we can enable the disabled menu items.

• Disabling menu items:

7




Using this feature we can disable all menu items of a particular

window.

• Maximizing a window:

Using this feature we can maximize a particular window, i.e.the

window which is present in task bar.

• Minimizing a window:Using this feature we can minimize a window.

• Keeping a window with its normal size:

Using this feature we can keep the window with its normal size

• Highlighting a window:

Using this feature we can highlight a particular window.

• Hiding a window:

Using this feature we can hide a window.

• Showing a window:

Using this feature we can show a hidden window.

• Terminating a window:

With this feature we can terminate a window so that it is removedfrom memory.

• Shifting the focus to a particular window:

Using this feature, we can shift the focus from one window to another.

• Showing a list of visible windows:

This list shows all visible windows.

• Showing a list of invisible windows:

This list shows all invisible windows

• Showing a list of all running processes:

This list shows all the running processes like Windows Task Manager

• Terminating a running process:

Using this feature, we can terminate a process which is running.

8




1. Introduction

1.1 Existing System

The existing system is only task manager built in with OS that shows all the processes

running simultaneously. In such application we can only view and terminate particular

application. The user must have in-depth knowledge of processes and must differ user

and system processes. Sometime he/she doesn’t know about the process relating to

which application. The user cannot use task manager to control processes.

1.2Objectives of New System

The new system should software based. It is used to operate, view and control the

system processes. New system is user friendly. This system also provides special

approach towards system security.

1.3 Proposed System

The new system is software based. It provides easy way to operate, view and control to

enhance the performance. We can add a feature in which the application can be

multithreaded so that time required for enhancing the image will be reduced.

The new system is, thus, more efficient, secure, user-friendly, fast, and provides a

better means for communication to its users. The system covers for all the drawbacks

of existing system.

9




2. Preliminary Survey

2.1 Recognition of Need

Recognition of need is the process of finding the drawbacks of existing system and

getting the user expectations for the new system. In the preliminary survey and

feasibility study, the analyst is learning from the user what is expected is new

information system. The analyst uses technical skills and knowledge to provide

alternatives to be considered for implementation.

2.2 Need for Change

Now-a-days, customers need a system which is user friendly. Also a system which gave

us multiple application. However we want to provide various services to the customers.

2.3 Initial Investigation

During initial investigation we found that the user wants to view the activity on its own

machine as he wants. The software should provide the feature of controlling, viewing

and enhancing the performance. Also user wants user friendly system. The proposed

system is able to solve the problem.

10




3. Feasibility Study

3.1 Feasibility Study

Feasibility study is procedure that describes and evaluates system and selects the best

system for completing the job. Feasibility study focuses on following questions:

1. What are the user’s needs?

2. Is there a Better system to do the job? If yes, how does it work?

3. What resources are available for new system?

4. Is the new System feasible?

5. What is the impact of the new system on the organization?

All projects are feasible, given unlimited time & resources. Unfortunately

development of the computer-based system is likely to be plagued by scarcity of

resources difficult delivery dates. It is both necessary & to evaluate the feasibility

of project at the earliest possible time.

The detailed study was carried out to check the workability of the proposed system.

So feasibility is a system proposal regarding to it's workability, impact on the

organization, ability to meet the user needs, effective use of resources.

Thus, when a new application progresses, it normally goes through a feasibility study

before it is approved for development. Feasibility & risk analysis are related in many

ways.

If project risk is great, the feasibility of producing quality software is reduced. Thus

during feasibility analysis of this project, the following primary areas of interest were

required to consider very carefully.

11




The following are the feasibility considerations to be carried out:

1. Technical Feasibility:

A study of resource availability may affect the ability to achieve an acceptable

system. Technical feasibility is frequently the most difficult areas at this stage

because objectives, functions & performances somewhat hasty, anything seems

impossible if the right assumptions are made. The considerations those are normally

associated with technical feasibility of the organization, where the project is to be

developed & implemented.

A. Hardware Requirement

• 3GHZ processor

• 512 MB RAM

• 40 GB Hard Disk

B. Software Requirement

• Windows 98 operating system

• Visual Basic 6 .0

• Windows Help Workshop

• Package and Deployment Wizard for VB 6.0

12




As all the above Hardware and Software requirements can be fulfilled easily the

system is Technically Feasible.

2. Operational Feasibility:

Data entry operators are already operating on office automation packages. The same

was also employed to enter data for the system. Initial training was also provided to

the operators on how to operate the system. The system is on-line i.e. the details are

entered as and when the transaction takes place.

3. Economical Feasibility:

Economical analysis is the most frequently used method for the evolution of

effectiveness of the proposed system. Cost/Benefit is the most commonly used

procedure for this feasibility where benefit and saving are determined from the

expected system and are compared with the cost. The different types of costs that were

considered are Manpower cost, Hardware cost and Operation cost.

3.3 Feasibility Report:

The feasibility Report is a formal document for management use, brief enough and

sufficiently non technical to be understandable. Report consists of the following:

Statement of problem:

The existing systems are not able to provide better security so that the software that

provides better security and also software is much flexible as compare to others.

13




Summary of Findings:

In this step, a list of the major findings of the study of current is made. It is ideal for

the one who requires quick access to the results of the analysis if the system under

study. Conclusions are stated, followed by recommendations and the justification of

them.

Details of Findings:

An outline of the methods and procedures undertaken by the existing system, followed

by coverage of objectives and procedures of the candidate system. Included are also

discussion of output reports, file structures and costs and benefits of the candidate

system.

Recommendations and Conclusions:

Specific recommendations regarding the candidate system, including the personnel

assignments, costs, project schedules and target dates.

Cost estimate:

Cost analysis (also called economic evaluation, cost allocation, efficiency assessment,

cost-benefit analysis, or cost-effectiveness analysis by different authors) is currently a

somewhat controversial set of methods in program evaluation. One reason for the

controversy is that these terms cover a wide range of methods, but are often used

interchangeably.

14




4. Analysis

4.1 System Analysis:

Analysis is the study of the system and finding solution to the problem-using

computer based system.

Analysis is a detailed study of various operation performed by the system and their

relationship within and outside the system. It answers what must be done to solve the

problems performed in analysis are:

• Defining the boundaries of the system.

• Determining whether a candidate system should consider other related system.

During analysis data are collected on available files, decision points and transaction

handled by the present system. Analysis is the heart of the system development. It is the key

component of first two phases of the system development.

Phase one focuses on problem definition and initial investigation, where the analysis

help to understand present system while, feasibility study goes into detailed study of present

system and determining potential solution.

Analysis of the system can be divided into following 3 phases.

• Structured Analysis

• Package Selection

• System Specifications

15




4.2 Data Collection:

Aim of analysis is to develop an understanding of the problem facing a user and the

nature of the operation. Understanding how each activity works requires access to the

information. Information gathering is an art and a science. The approach and manner in

which information is gathered require persons with sensitivity, common sense and

knowledge of what and when to gather and what channel to use in securing information.

The methodology and tools for information gathering require training and experience.

Thus data collection is not easy task and requires much preparation, experience and

training.

Sources of Information:

Information can be gathered from two major sources:

1. Internal sources.

2. External sources.

1. Internal sources:

Primary internal sources include:

• Personal Staff.

• Professional Staff.

• System Documentation or manuals.

• Reports and Transaction Documents.

2. External Sources:

Primary External sources include:

• Vendors.

• Experienced developers

• Newspapers and Professional Journals.

• Internet

• Network Guides/books/articles.

16




4.3 Information Gathering Tools:

Information must be gathered accurately, methodically, under the right condition and

with minimum interrupt to user personal.To achieve this various information gathering tools have been developed. Following

are information-gathering tools that we have used for information gathering:

1. Review of Existing Procedures and forms:

Very few system problems are unique. Searching information through

professional references and procedure manuals, textbooks, company studies,

publications provide valuable data. Manuals and forms describe the format and

functions of present system. They describe system requirement that help to determine

the format and function of present system. They describes system requirement that

help to determine how the objectives are meet in present system. Up to-date manuals

save hours of information gathering time. Printed forms are widely used for capturing

information.

2. Interviews:

An interview is face-to-face interpersonal role situation in which a person

called “Interviewer” asks questions to person being interviewed, to gather the

information about the problem. The interview is the oldest and most often used

method for data collection.

In an interviewer since designer and the person interviewed meet face to face,

there is an opportunity for flexible information gathering. The interview should be

arranged so that the physical location, time of the interview and order of the

interviewing assure privacy and fix duration should be allotted.

17




3. Questionnaires

This is the process of preparing a list of questions, mostly objective type, and

letting each user answer them independently. This has the added advantage of the

user letting out his thoughts more freely. The answers that users give to these

questions can be then analyzed to find out the exact area that is lacking the user

requirement and then a change can be made accordingly.

4.5 User Requirement Analysis:

Requirement analysis is the software engineering task that bridges the gap

between the software designs. It is the process of discovers, refinement, modeling and

specification.

Requirements establish an understanding of the user’s needs, and also provide

the final yardstick against which implement success is measured. In requirement

analysis phase we deal with requirement of company related to project features,

platform used for development, language etc.

The following tools are use for the development of the software:

• Visual Basic 6.0

• MSDN

18




4.5 Forming Logical model of the System with the help of Data-Flow

Diagrams (DFD):

System analysis is done with the help of DFD (Data Flow Diagram)

DFD is also known as "BUBBLE CHART". DFD overcomes the drawbacks of flow chart as ituses small number of symbols to reduce complexity. It is used to clarify system requirements and

identify important processes that will become programs in the system design stage. So the

starting point of the design that decomposes the user requirements to the lowest level of details is

called DFD.

Rules for constructing DFD:

1. Meaningful name should be chosen for the symbol in diagram

2. Processes should be consistently numbered

3. Top down approach should be followed

4. The data flows coming into a process and going out of the same process at one level must

correspond to the data flows coming in and going out at the next lower level.

5. Process symbols with inputs but without outputs should be avoided.

The idea behind DFD is to design a system at high conceptual levels and then into more and

more details of sub-sequent diagrams. Thus the DFD use top down approach of structured

programming. DFD require only four diagrams making them easy to create and use. Symbols

for Construction of a Data-Flow Diagram (DFD)

19




DATA FLOW DIAGRAM

LEVEL 1

20




Window

Manager

EDIT

VIEW

Admin

Specify

Process

Freeze

Defreeze

21




5. SYSTEM DESIGN

The most creative and challenging phase of the System Development is system

design. The design describes a final system and the process by which it is developed. It refersto the technical specification that will be applied in implementing the candidate. It also

includes the construction of program testing.

The design covers the following tasks:

1. Review the current physical system: i.e. Data flows, file contents, volumes,

frequencies etc.

2. Prepares output specification: Determines format, content and frequency of reports

including terminal specification and location.

3. Prepare input specification: Defines format, content and the input functions.

Determines flow of document from input data source to actual input location.

4. Prepare edit, security and control specification: Specifies rules for edit correction,

backup procedures and controls file processing and integrity.

5. Specifies the implementation plan.

6. Prepare logical design.

7. Review benefits, cost and target date and system constraints.

Input Design:

It is the process of converting the user-oriented input into the computer-based format.

Input data are collected and organized into a group of similar data.

Following are the goals of input design:

• To make data flow easy, logical and error free.

• To display and represent data properly.

• To provide ease for addition of data.

22




5.2 Output Design:

It determines how outputs are to be produced and in what format. This is the part,

which interests the user. It should meet the user requirements and should be according to his

convenience. A major form output design is its Hard copy from the printer. To fulfill user’s

requirements, expensive user survey must be conducted to find out the user’s need and how

they use the information.

Following are the goals of output design:

• Flexibility:

Including maximum details in output can provide maximum output flexibility. From

these details, summary reports can be generated according to the individual user

requirements.

• Clarity:

The user must easily understand heading and format.

• Titles:

The field title must be clear and descriptive. If any portion is difficult to understand,

then footnote must be included to explain what it means.

• Error Messages:

Polite error message must be provided when error occurs.

• Response Time:

Response time should be adequate and backup should maintain as user depends

heavily on output

.

• User Participation During Output Design:

These will improve users understand of output.

23




Language Used

• Visual Basic 6.0

Visual Basic provides an ease to the task of programming. It is often said to

be RAD that is, it provides the means for Rapid Application Development. It

provides more than a million features and also provides an interface for using

the ActiveX controls. It has the ability to make programs having a nice GUI and

also makes them user-friendly. Apart from this, it has connectivity with a

number of databases. Thus we found Visual Basic very useful for thedevelopment of our application.

• MSDN

MSDN, the Microsoft Developer Network, is the essential reference for

developers who use Microsoft development tools or target any Windows or

Internet platform. It contains Visual Studio documentation, SDK

documentation, technical articles, conference and seminar papers, and technical

specifications.

5.4 Hardware & Software Specifications

A. Hardware Specification:

• 3GHZ Processor

• 512 MB RAM

• Keyboard

24




B. Software Specifications:

• Windows 98

• Visual Basic 6

• Windows Help Workshop

• Package & Deployment Wizard for VB 6.0

25




6. Testing

6.1 Why Testing is required?

Testing is required for success of the system. It has logical assumption that all

parts of the system are correct when the goal will be successfully achieved.

A) The main objectives of program testing are as follows:

• To make sure that the program during operation will perform as per the

specification lay down initially at the time of system analysis.

• To make sure that the control incorporated in the program and the system function

as intended.

• To ensure that during the operation, incorrect inputted data and processing will be

detected.

B) If system is not tested following problems are created:

• If problem appears after a long time interval then it will become very complicated for

solving.

• A small error if overlooked breakup in to a large problem.

• Small errors have the potential of closing down entire system.

26




6.2 What to test?

Systems are tested for following factors:

1. Online Response:

Response time for online system should be less. Inputting transaction

on as many CRT screens maximum load and then calculating response to each

online function tests its.

2. Volume:

In this test as many records are created to verify that hardware and

software function properly. User provides test data.

3. Stress Testing:

Its purpose is to prove that candidate system doesn’t malfunction.

Under the peak loads, here the system is subjected to high volume of data over

a short time period.

4. Recovery And Security:

In this a system is forced to fail to test backup and recovery procedure.

Inaccurate data is inputted to examine response of system in terms of error

detection and correction.

5. Usability Documentation and Procedure:

It verifies User-friendliness of the system which is one of the aspects

of this complete documentation, which guide user to determine how the

system works.

6. Unit Testing:

This is testing each unit of system for known errors. They are as

follows:

• Data Consistency :-

All fields to which entries were to made was checked for the

entries corresponding to the date types they represents in the

database.

27




For example: A user was prohibited form entering characters

in the date field, which would always be a number .

• Size Constraints :-

For some fields size constraints have been specified, like

the phone number should not be greater than 10 digit. So checks

were put on those fields to prevent out of bound size or size

errors.

• Predetermined Formats :-

Some of the fields to which entries were made had a

predetermined formats, so this entries were tested for it. For

example the email field should always contain a @ character, so

care was taken for it.

• Human Errors :-

At the time testing the need was evolved to take care of errors that

might occur due to clicking or a submission of a form by mistake. So

checks are put on edition or deletion of records, and the user was

prompted about the results or consequences of his action, giving him

opportunity to rectify the mistake.

6.4 Nature Of Test Data:

The proper choice of test data as itself, it test data are not valid then reliability

of the output is suspicious. The data can be artificial (created solely for test purpose) or

live (taken the user’s actual file.) Properly created artificial data should provide all the

combination of value and format make it possible to test all logic and transaction part

subroutine extreme values for the limits of candidate system.

28




6.4 Reasons Behind Testing:

Systems are tested to verify the following qualities of the system:

1. Correctness:

The extent to which a program meet system specification and user objectiveness.

2. Reliability:

The degree to which the system performs its intended function over a time.

3. Efficiency:

The amount of computer resources required by a program to perform a function.

4. Usability:

The efforts required for learning and operating the system.

5. Maintainability:

The ease with program error are located and corrected.

6. Testability:

The efforts required for testing a program one-hardware configuration to another.

7. Portability:

The ease for transporting a program from one hardware configuration to another.

8. Accuracy:

The required precision in input editing, computation and output.

9. Error Tolerance:

Error detection and correction versus error avoidance.

10. Expandability:

Ease of handling the existing database.

29




6.5 Contents of Test Plan:

Activities included in test plan are:

• Prepare the test plan.

• Specify condition for user acceptance testing.

• Prepare test data for program testing.

• Prepare test data for transaction path testing.

• Plan user training.

• Compatible/Assemble programs.

• Prepare job performance aids.

• Prepare optional documents.

6.6 Prototype Testing:

In prototype testing data is given to a program and result is compared with existing

result. Thus the normal output is compared with the output of software i.e. Hardcopies of the

program. If the result of the testing is acceptable, only then prototype logic is finalized, else

changes are suggested.

6.8 Cutover and Parallel Testing:

Cutover Testing:

The direct cutover method the system is abruptly changed from old to new

over a weekend or even overnight here, if the analyst ensures that the users can directly

shift to the new system, he can use this method. No parallel activities or fall back

present in this method. Not having a fall back ca also prove a disadvantage if any

serious problem occurs new system.

The organization may have to stop working to correct the problem aroused.

After correcting the problem the user may not reply on new system also, time requires

30




careful planning, training session must be scheduled and maintained. The installation of

all equipments must be on time.

Parallel Testing:

In parallel testing both systems Old & New run in parallel. User operates both

old and new system. If any problem arises in new system, old system working can be

continued without loss of time. However costs double since systems run in parallel.

6.8 Impact on User:

In this the focus is on the added flexibility that can be from the information

technology. One group of custom service personnel, were dissatisfied with a new system

because while providing better customer service for majority of customer, the system reduce

physical mobility of representatives and interface with social relationship in office.

Instead of working around to obtain information, the representatives now work at

terminals and thus gain very less opportunity to interact with co-workers

Designers can take several actions to encourage users towards constructive use of

system and successful implementation. First it is important to plan carefully for training.

More users involved in design and testing of the system, the better it is because thisinvolvement service as the training investment.

6.9 User’s Role in Testing And Implementation:

Participation helps user retain control over processing. If users have in designing

procedures for system, they should understand them better to use system; they understand

them, to use the system. Participation can create commitment to change.

If an individual or work group investment some of itself in a new system’s success,

this provides ego rewards.

If individual and workgroup participate, they make enough chances consistent with

their own system. Participation also creates familiarity with system and contributes to

training.

31




6.10 PLAN OF EXCUTION

# Tasks Days Start Finish

1 Beginning Phase 4 8/1/2008 8/6/2008

2 Market survey to determine the

present need of the enterprise

world

4 8/1/2008 8/6/2008

3 To determine the extent upto

which the needs can be

completed to satisfy the

company’s requirement

1 8/6/2008 8/6/2008

4 StartUp Phase 12 8/13/2008 8/28/2008

5 Primary Objectives 2 8/13/2008 8/14/2008

6 Establish Communications 4 8/15/2008 8/20/2008

7 Develop Project Plan 3 8/20/2008 8/22/20088 Develop Initial Documentation 3 8/23/2008 8/27/2008

9 Finalize Documentation 1 8/28/2008 8/28/2008

10 Scoping Phase 9 8/29/2008 9/10/2008

11 Establish Project Scope 4 8/29/2008 9/3/2008

12 Develop Project Specifications 3 9/4/2008 9/6/200813 Establish Project Goals 2 9/7/2008 9/10/2008

14 Analysis Phase 15 9/11/2008 10/1/2008

15 Evaluate Systems 5 9/11/2008 9/17/200816 Establish Engineering

Requirements

3 9/18/2008 9/20/2008

17 Function Point Estimation 2 9/21/2008 9/24/2008

18 Determining the economical

feasibility

2 9/25/2008 9/26/2008

19 Determining the technical

feasibility

3 9/27/2008 10/1/2008

20 Estimating Phase 11 10/1/2008 10/15/2008

21 Establish Training Requirements 2 10/1/2008 10/2/2008

22 Survey Potential Users 4 10/3/2008 10/8/200823 Estimate Costs, Savings and /or

Revenues

4 10/9/2008 10/12/2008

24 Purchase Materials 1 10/15/2008 10/15/2008

25 Design Phase 15 10/16/2008 11/5/2008

26 Develop Preliminary Designs 7 10/16/2008 10/24/200827 Develop Prototype 8 10/25/2008 11/5/2008

28 Negotiating Phase 4 11/8/2008 11/13/200829 Negotiating with the customer 4 11/8/2008 11/13/2008

32




over the module to be developed

which proves to be feasible for

entire team as well as for the

customer

30 Review Phase 9 11/21/2008 12/3/200831 Make changes as per customer

needs.

4 11/21/2008 11/26/2008

32 Make the changes compatible

with our system.

5 11/27/2008 12/3/2008

33 Approval Phase 1 12/4/2008 12/4/2008

34 After negotiating with the

customer finalize the Design &

Modules to be developed.

1 12/4/2008 12/4/2008

35 Coding/Development Phase 30 12/27/2008 2/6/200936 Actual implementation of all the

diagrams coding carried out

26 12/27/2008 1/31/2009

37 Making of different modules as

and when required

25 12/28/2008 1/31/2009

38 Finalizing amongst different

modules developed and merging

them

4 2/1/2009 2/6/2009

39 Engineering Phase 8 2/7/2009 2/18/2009

40 Merging these modules to

complete the system

8 2/7/2009 2/18/2009

41 Inspection Phase 8 2/18/2009 2/27/200942 To check for errors 5 2/18/2009 2/22/2009

43 Check out for any kind of

shortcomings

5 2/18/2009 2/22/2009

44 Determining various aspects that

would improve the systems

performance

3 2/25/2009 2/27/2009

45 Debugging Phase 12 3/3/2009 3/18/200946 Getting rid of any bugs,

errors,shortcomings.

12 3/3/2009 3/18/2009

47 Review Phase 4 3/19/2009 3/24/2009

48 Determining the actual ability of

the system whether it is actually

4 3/19/2009 3/24/2009

33




satisfying the corporate need.

49 Finishing Phase 5 3/25/2009 3/31/200950 Run Performance Tests 3 3/25/2009 3/27/2009

51 Finalize Testing 2 3/28/2009 3/31/2009

52 Close-Out Phase 1 3/31/2009 3/31/2009

53 Complete deployment of the project (i.e. The System

developed)

1 3/31/2009 3/31/2009

Lead-In Sections

i. The following sections are at the beginning of the Acceptance Test Plan. They are

described in more detail in the Documentation Format Guideline.

a. Objectives

b. Scope

c. References

d. Outstanding Issues

e. Approvals.

Test Responsibilities

i. Customer's responsibilities in preparing for and performing acceptance test.

ii. Department X' responsibilities in preparing for and performing acceptance test.

Testing Approach

i. The types of tests which will be performed (e.g. stress testing, timing tests,

compliance tests, capacity testing).

34




36




Test Cases:-

a) Test Case Identifier

A unique reference number assigned to the Test Case.

b) Requirements Traceability

Cross references to applicable requirements as identified in the Requirements

Specification.

c) Description of Test

A brief overview of the test.

d) Test Initialization

i. Hardware and software configuration.

ii. Preset hardware conditions.

iii. Preset software conditions.

e) Test Inputs

Describe test inputs

f) Test Procedure

Detailed steps used to perform the test.

g) Expected Results

. The expected outcome of the test or a description of the type of result which the tester

should check for.

J) Special Instructions

Anything that the tester needs to be aware of when running the test e.g. another Test

Case must be run first, the test produces a large quantity of printout.

37




• Simplicity: “The less there is no test, he more quickly we can test it”.

• Stability: “The fewer the changes, the fewer the disruptions to testing”.

• Understandability: “The more information we have, the smarter we will test”.

•

A good test has following attributes defined:• A good test has a high probability of finding an error

• A good test is non-redundancy. A good test should be “best of breed”. A good

test should be neither too simple nor too complex

Software Testing Strategy:-

The software engineering process may be viewed as a spiral. A strategy for

software testing may also be viewed in the context of spiral unit testing begins at the vortexof the spiral and concentrates on each unit of the software as implemented in source code.

The testing progresses by moving outward along the spiral to integration testing, where the

focus is on design and the construction of the software architecture. Dealer Chain

Management System supports black box testing. Black box testing is done on the functional

requirements of the software. That is black box testing enables software engineer to derive

sets of input conditions that will fully exercise all functional requirement for a program.

Black box testing is not an alternative to white box testing. Rather it’s a complementary

approach that is likely to uncover the different flaws of error than white box method.

Black box testing attempts to find the errors in following categories:-

• Incorrect or missing functions.

• Interface error.

• Errors in data structure.

• Performance error.

• Initialization and termination error.

Unlike white box testing its performed early in the testing process,

black box testing tends to be applied during later stages of testing. Because black box

39




testing purposely disregards control structures, attention is focused on the information

domain. Tests are designed to answer the following question.

• How is functional validity tested?

• What classes of input will make good test cases?

• Is the system particularly sensitive to certain input values?

• How are the boundaries of a data classes isolated?

• What data rate and data volume can system tolerate?

• What effect will specific combination of data have on system operation?

By applying black box techniques we derive a set of test cases that

satisfy the following criteria.

• Test cases that reduces by a count i.e. greater than 1, the number of additional

test cases that must be designed to achieve reasonable testing.

• Test case that tells us about the presence of classes of errors rather than errors

associated with the specific test at hand.

GUI Testing:-

GUI testing (graphics user interface) testing are the testing guidelines

for specialized environments, architectures and application that are commonly

encountered by software engineer. Because of reusable components , provided as part

of GUI development environments, the creation of the user interface has become less

time consuming and more precise . But the complexity of GUIs has also grown

leading to more difficulty in design and execution of test cases. As modern GUIs

have the same look and feel series of standard test can be derived. In GUI testing ,

checklist was developed against which each GUI component to be verified. The list

covered all possible interaction that may or may not apply to a particular component .

In addition to the GUI components , the GUI standards were used to ensure that the

internal rules of construction are followed to achieve the desired level of consistency.

40




This was done by following the coding standards which was developed during the

designing phase . Some of the GUI standard which were verified are :

Forms enterable and display only formats.

Wording of alerts , error messages and help features.

Screen layout.

Thus through testing a wide range of errors were encountered which enabled us to

understand the system as well broadened our knowledge of Java language.

Task Testing:-

Task testing is the basic of all kinds of testing related to software. In

task testing we will check whether the system is performing the allocated task

correctly or not, if yes well and good if not then test cases will be designed to

improve the performance of the system.

Inter-Task Testing:-

Inter-task testing basically deals with testing whether the interactions

between different modules of the system is properly working, in other words, we can

say that inter-task testing deals with testing of interrelationship between modules. In

system, testing is performed between Sales and Spare parts module as well as

between Administrator and Sales and Spare parts..

41




42




6.10 Acceptance Test Procedure (ATP)

A crucial stage in the lifecycle of any computer system procurement is the

point at which the customer accepts the system. This paper examines the significance of the

acceptance milestone in the context of supplying software. From this examination, it is

revealed that there may be potential for conflict between the commercial considerations

which may be pertinent in drafting an appropriate acceptance testing procedure, and the

Terms which may be imposed upon that procedure by virtue of statutory provision? With

this in mind, the function and scope of acceptance testing is considered from two contractual

positions: express provisions which may be laid down in the software contract and terms

which may be implied into the contract by law.

6.10.1 Objectives

This standard defines the content of the Acceptance Test Plan and Test Cases.

6.10.2 Scope

This standard only applies if Department X is playing a role in the

development of the Acceptance Test Plan. If the customer is assuming full responsibility for

developing the Acceptance Test Plan, then this standard does not apply.

6.10.3 Approvals

Development Manager.

6.10.4 Responsibilities

The Project Manager (see Acceptance Testing Procedure) is responsible for

ensuring that an Acceptance Test Plan and Test Cases are produced.

The Project Manager is responsible for ensuring that the Acceptance Test Plan

and Test Cases are updated when requirements change.

43




Sr.No. ACCEPTANCE TESTS RESULT

1. The system must be installed in a Windows environment.

2. The system must be implemented in a given configuration.

3. There should be an administrator console having all

administrator functions with a password authentication

login.

4 The system should involve provision for storing the entire

database on server and accessing this database through

various clients.

5 The display must contain awards & rewards given to

company employees.

12. The system must also display various articles related to

SAFETY, QUALITY,QUANTITY,DELIVERY, etc.

Table1: Acceptance Test Points Based On Our System Traceable With Customer

Requirements

44




7. Quality assurance plans

What is a QA Project Plan?

A QA Project Plan describes the activities of an environmental

data operations project involved with the acquisition of environmental information whether

generated from direct measurements activities, collected from other sources, or compiled

from computerized databases and information systems.

What is the purpose of the QA Project Plan?

The QA Project Plan documents the results of a project’s technical planning

process, providing in one place a clear, concise, and complete plan for the environmental

data operation and its quality objectives and identifying key project personnel.

What are the benefits of a QA Project Plan?

The benefits of a QA Project Plan are to communicate, to all parties, the

specifications for implementation of the project design and to ensure that the quality

objectives are achieved for the project. It does not guarantee success every time, but

the prospects are much higher with a QA Project Plan than without one.

Up-front planning eliminates approaches that do not work well (or not at all),

which has the potential to reduce the cost of lost time and rework. Implementation as

prescribed, with appropriate QC practices employed, increases efficiency and provides for

early detection of problems, either in the field or in the laboratory. This again can save time

and money from the rework and enable the ability to make decisions more expeditiously. For

example, following calibration procedures will help to assure

the credibility and usability of data generated by laboratory instruments.

46




CONTENT OF A QA PROJECT PLAN:-

What is generally contained in a QA Project Plan?

The QA Project Plan is divided into four basic element groups: Project

Management; Data Generation and Acquisition; Assessment and Oversight; and Data

Validation and Usability. Each group consists of standard elements, 24 in all, that pertain to

various aspects of the project.

A QA Project Plan that addresses the basic elements will define and describe

the following:

• Who will use the data?

• What the project’s goals/objectives/questions or issues are;

• What decision(s) will be made from the information obtained;

• How, when, and where project information will be acquired or generated;

• What possible problems may arise and what actions can be taken to mitigate their

Impact on the project;

• What type, quantity, and quality of data are specified;

• How “good” those data have to be to support the decision to be made; and

• How the data will be analyzed, assessed, and reported.

DQIDefinition Example Determination

Methodologies

Accuracy A measure of the overall

agreement of a measurement to a

known value; includes a

combination of random error (precision) and systematic error

(bias) components of both

sampling and analyticaloperations.

Analyze a reference material or

reanalyze a sample to which a

material of known concentration

or amount of pollutant has beenadded; usually expressed either as

percent recovery or as a percent

bias.

Representativeness A qualitative term that expresses

“the degree to which data

accurately and precisely

represent a characteristic of a population, parameter variations

at a sampling point, a process

condition, or an environmental

Evaluate whether measurements

are made and physical samples

collected in such a manner that

the resulting data appropriatelyreflect the environment or

condition being measured or

studied.

47




condition.”

Comparability A qualitative term that expressesthe measure of confidence that

one data set can be compared to

another and can be combined for the decision(s) to be made.

Compare sample collection and

handling methods, sample preparation and analytical

procedures, holding times,stability issues, and QA protocols.

Completeness A measure of the amount of

valid data needed to be obtainedfrom a measurement system.

Compare the number of valid

measurements completed(samples collected or samples

analyzed) with those established

by the project’s quality criteria(Data Quality Objectives or

performance/acceptance criteria).

Table A QA Project plan

7.4 Staffing

Staffing involves finding the right people, with the right skills, abilities, and

fit, who may be hired or already working for the company (organization) or may be working

for competing companies. Staffing deals with a comprehensive term for all operative

functions namely recruiting, placing, appraisal, rewarding, assessing, developing performed

in HR management.

In knowledge economies, where talent becomes the new capital, this

discipline takes on added significance to help organizations achieve a competitive advantage

in each of their

marketplace.

48




Parameter Average Complex

Number of user inputs 01* 5 3 7 05

Number of user output 01* 5 4 7 05

Number of user enquiries 02 * 4 5 6 08

Number of files NA NA NA NA NA Number of external

interface02* 5 7 10 10

Count total 28

* Multiply, _ Multiplication Factor, NA:Not Applicable.

Table.3:- Table for Computing function point

To compute function point (FP), following relationship is used:

FP=count total* [0.65+0.01* fi ]

The Fi (I=1 to 14) are complexity adjustment values based on response to the

following questions:

1. Does the system require reliable backup and recovery?

Ans: 5

2. Are data communications required?

Ans: 0

3. Are there distributed processing functions?

Ans: 5

4. Is performance critical?

Ans: 5

5. Will the system run in existing, heavily utilized operation environment?Ans: 2

6. Does system require on line data entry?

Ans: 0

7. Does on line data entry require the input transaction to be building over multiple screens

or operations?

50




Ans: 5

8. Are the master files updated on line?

Ans: 0

9. Are the inputs, outputs, files, or enquiries complex?

Ans: 0

10. Is the internal processing complex?

Ans: 4

11. Is the code designed to be reusable?

Ans: 3

12. Are the conversion and installation included in design?

Ans: 3

13. Is the system designed for multiple installations in different organization?

Ans: 4

14. Is the application designed to facilitate change and ease of use by the user?

Ans: 5

FPestimated =28*[0.65+0.01*41]

FPestimated =28*0.99

FPestimated =30.52

The organizational average productivity for such systems is 6.5 FP/pm.Based on Labor rate

2000Rs. per month, the cost per FP is approximately 3000/6.5=461.53=Rs. 462

So based on the FP estimate and productivity data, the total estimated project cost is

30.52*462=Rs. 14,100/-.

8. User manual

51




The project has been design so that the software is user friendly and also has a look and

feel of any other windows program.

The main window of the project i.e. the manager window when the application is

loaded consists of the process window showing all the running processes.

52




This bibliography contains all the book’s and articles that are referred in this project .

It provides the list of books with complete author and publication information. For

programming purpose we have used the following books:

1. Mastering Visual Basic 6.0 by Evangelos Petroutsos.

2. Microsoft Visual Basic 6.0 step by step.

3. M.S.D.N. Library 2000

4. Visual Basic 6.0 Programming black Book – Steven Holzner

5. Alias M.Awad “System Analysis and Design”.