Executive summary : Company profile:

The organization I have done project in is ISO 9001:2000 certified organization. Company offering offshore software development services for its customers worldwide and producing own software products. QualSoft has a Vision to become a 'First Choice Partner' with its long-term planning, practical operational experience, capability to deliver, stainless reputation with its Clients. Our well coordinated professional's team and the unique approach of customer's problems solving allow us to create the solutions based on cutting edge of information technologies.

Details of study:

In this project we studied what is the project management .The stages involved in common project management technique. The stages involved in Qualsoft Services project management technique. The documents useful in the project management. And analysis of these project management techniques on the basis of the Questioner.

Objectives: The main objective to carried out this project is to understand the project management technique adopted in I.T. firms like Qualsoft Services. To understand the common project management technique. To understand the Qualsoft Services project management technique. To study the documents useful in the project management.

Findings:

Most of projects completed in the Qualsoft Services with their own project management technique. Many software developers think that the project management technique of Qualsoft services contains all the advanced features. The Qualsoft services project management technique of Qualsoft services helps to reduce the cost, efforts and time. The prototyping model suggested by me could be beneficial to carry out the projects.

Conclusion: The study of the project management technique is important for every I.T professional personnel. The common project management technique is now outdated. The Qualsoft Services project management technique helps to reduce the cost, time and effort. There are some important documents such as SRS, project plan etc. are important to complete the project. The prototyping model can be very useful to carry out the projects.

Chapter1

INTRODUCTION

PROJECT MANAGEMENT What is it?

- Although many of us (in our darker moment) take Dilbert's view of "management", it remains a very necessary activity when computer-based system & products are built. Project management involves the planning, monitoring, & control of people, process, & events that occur as software evolves from a preliminary concept to an operational implementation.

Who does it?

- Everyone "manages" to some extent, but the scope of management activities varies among people involves in a software project. A software engineer manages her dayto-day activities, planning, monitoring, & controlling technical tasks. Project managers plan, monitor, & control the work of team of software engineer. Senior managers coordinate the interface between the business & software professional.

Why is it important?
- Building computer software is a complex undertaking, particularly if it involves many people working over a relatively long time. That's why software projects need to be managed.

What are the steps?

- Understand the four P's people, products, process, & project. People must be organized to perform software work effectively. Communication with the customer & other stakeholders must occur so that product scope & requirements are understood. A process must be selected.

Chapter 2 Company profile:-

ABOUT QUALSOFT SERVICES

QualSoft Services, offshore software development company offering offshore software development services for its customers worldwide and producing own software products. QualSoft has a Vision to become a 'First Choice Partner' with its long-term planning, practical operational experience, capability to deliver, stainless reputation with its Clients. Our well coordinated professional's team and the unique approach of customer's problems solving allow us to create the solutions based on cutting edge of information technologies. For our valued team members, QualSoft is a global company that offers a world of opportunity. With ample training programs (both in-room and online), competitive compensation, performance based bonus, QualSoft is a Growth Center to its team members. QualSoft takes pride in being innovative and in offering one-stop services to its clients. Whether you are looking for an end-to-end software solution or a specific technical component for your business, QualSoft has the answer. This expertise makes us a reliable partner to take up application development projects that address business situations. A combination of world-class experience, customer-centric processes and best practices, allows us to deliver high-quality solutions to our clients "on time in budget". All in all, QualSoft is committed to exceeding the expectations of our customers, shareholders, and employees, day in and day out. In fact, all of us are committed to living our brand : "Building Solutions Globally"

Why QualSoft : One Stop Service:

With your arrival at QualSoft your are ensured of all your software service needs including Product life cycle management. We have the breadth of services to act as one-stop shop for all your software requirements. Our team members has a rich experience of top notch software companies with sound academic background.

Technical Expertise :
We aim to offer best-of-breed solutions to our clients through our established processes and systems. Our team has remarkable experience in almost all the leading technology platforms to develop various business applications. Technology? just leave it to us.....

Faster ROI :
With a significant cost saving of 70% we ensure our client has a faster return on investment. With a low Operating Cost and a Zero Capital cost to our client enjoys a long term business association with us. Experience cost saving for your project.

Proven Methodology :
Our well-defined and established methodologies make sure that the solutions we deliver are high quality, delivered on time and at lowest costs through appropriate leverage from offshore teams based in India.

Time to Value :
While keeping pace with the changing business needs of our clients and dynamism of technology, we have established record for delivering solutions quickly and on time. 6

Commitment :
Our are professionally committed to offer a best customer service by applying our skills, expertise, experience and resources. Its our practice to deliver well within time and on budget. Programmers are professionals in the true sense of the word. We are committed to growth of our client.

Ready to deploy :
To meet the growing needs of client's software we have a ready to deploy resource. What we just need is your expansion scope and we will offer you the resource pool to suffice your business needs. Our resource management team will take care of resource planning and deployment.

Methodology : "Stepping Beyond The Normal Practices......"

Our rich experience of partnering, mainly with our US based clientele has made us evolve a highly effective form of work-style for the rapid analysis, design, development, implementation and maintenance of applications and customized solutions. Effective real-time communication has been the key to the success of such half-way-around-the-globe-partnerships. Understand : We understand the customer's business objective, operational needs and technical expectations. Meeting is held with our functional and technical experts for a smooth flow of information in bilateral direction. Systematic tools & mechanism brings the thorough understanding of our client's need. Validations through requirement clarifications produces refinement of purpose.

Propose : At this level we have qualified requirements to propose Business, Functional and Technical plans. Validation of same by customer initiates the project. We also plan our resources to meet the crucial deadlines set by client by our ready to deploy resources.

Corporate Statements

Vision : To become the First Choice Partner. Mission : We aspire to give an Unique Customer Experience to all our partners by keeping Transparent relations, Commitment, Dedication and Capability to deliver. Produce the Deliverables that will count for us. Goal : Develop a Global pool of Clients. Deliver most cost effective and creative solutions. Win the confidence of our Customers. Make QualSoft as a Place of Wish to Work for our Team. Arrange the world-class resources and facilities. Value : Customer the First Build business integrity and trust Respect for individual Strive for excellence Continuous improvement

Chapter-3 objectives:
1.To understand the concept of project management. 2.To understand the common project management technique. 3.To study Qualsoft Services project management technique. 4.To find out which project management technique is more beneficial. 5.To study the documents used in the project management. 6.To find out other alternative project management techniques.

chapter 4 DATA ANALYSIS

Common project management technique STAGES:

OVERVIEW The six stages of the SDLC are designed to build on one another, taking the outputs from the previous stage, adding additional effort, and producing results that leverage the previous effort and are directly traceable to the previous stages.This topdown approach is intended to result in a quality product that satisfies the original intentions of the customer. 1. Project Planning

2. Requirements Definition

3. Design

4. Development

5. Integration& Test

6. Installation& Acceptance

1. PLANNING STAGE:

The planning stage establishes a bird's eye view of the intended software product, and uses this to establish the basic project structure, evaluate feasibility and risks associated with the project, and describe appropriate management and technical approaches.

The most critical section of the project plan is a listing of high-level product requirements, also referred to as goals. All of the software product requirements to be developed during the requirements definition stage flow from one or more of these goals. The minimum information for each goal consists of a title and textual description, although additional information and references to external 10

documents may be included.

The outputs of the project planning stage are the configuration management plan, the quality assurance plan, and the project plan and schedule, with a detailed listing of scheduled activities for the upcoming Requirements stage, and high level estimates of effort for the out stages.

2. REQUIREMENTS DEFINITION STAGE:

The requirements gathering process takes as its input the goals identified in the high-level requirements section of the project plan. Each goal will be refined into a set of one or more requirements. These requirements define the major functions of the intended application, define operational data areas and reference data areas, and define the initial data entities.

Major functions include critical processes to be managed, as well as mission critical inputs, outputs and reports. A user class hierarchy is developed and associated with these major functions, data areas, and data entities.

Each of these definitions is termed a Requirement. Requirements are identified by unique requirement identifiers and, at minimum, contain a requirement title and textual description. These requirements are fully described in the primary deliverables for this stage:

The Requirements Document and the Requirements Traceability Matrix (RTM). The requirements document contains complete descriptions of each requirement, including diagrams and references to external documents as necessary. Note that detailed listings of database tables and fields are not included in the requirements document. The title of each requirement is also placed into the first version of the RTM, along with the title of each goal from the project plan. The purpose of the RTM is to 11

show that the product components developed during each stage of the software development lifecycle are formally connected to the components developed in prior stages.

In the requirements stage, the RTM consists of a list of high-level requirements, or goals, by title, with a listing of associated requirements for each goal, listed by requirement title. In this hierarchical listing, the RTM shows that each requirement developed during this stage is formally linked to a specific product goal. In this format, each requirement can be traced to a specific product goal, hence the term requirements traceability.

The outputs of the requirements definition stage include the requirements document, the RTM, and an updated project plan.

3.DESIGN STAGE

The design stage takes as its initial input the requirements identified in the approved requirements document. For each requirement, a set of one or more design elements will be produced as a result of interviews, workshops, and/or prototype efforts.

Design elements describe the desired software features in detail, and generally include functional hierarchy diagrams, screen layout diagrams, tables of business rules, business process diagrams, pseudo code, and a complete entity-relationship diagram with a full data dictionary. These design elements are intended to describe the software in sufficient detail that skilled programmers may develop the software with minimal additional input. When the design document is finalized and accepted, the RTM is updated to show that each design element is formally associated with a specific requirement. The outputs of the design stage are the design document, an updated RTM, and an updated project plan.

12

4. DEVELOPMENT STAGE:

The development stage takes as its primary input the design elements described in the approved design document. For each design element, a set of one or more software artifacts will be produced. Software artifacts include but are not limited to menus, dialogs, data management forms, data reporting formats, and specialized procedures and functions. Appropriate test cases will be developed for each set of functionally related software artifacts, and an online help system will be developed to guide users in their interactions with the software.

The RTM will be updated to show that each developed artifact is linked to a specific design element, and that each developed artifact has one or more corresponding test case items. At this point, the RTM is in its final configuration.

The outputs of the development stage include a fully functional set of software that satisfies the requirements and design elements previously documented, an online help system that describes the operation of the software, an implementation map that identifies the primary code entry points for all major system functions, a test plan that describes the test cases to be used to validate the correctness and completeness of the software, an updated RTM, and an updated project plan.

5.INTEGRATION & TEST STAGE:

During the integration and test stage, the software artifacts, online help, and test data are migrated from the development environment to a separate test environment. At this point, all test cases are run to verify the correctness and completeness of the software. Successful execution of the test suite confirms a robust and complete migration capability.

During this stage, reference data is finalized for production use and production users are identified and linked to their appropriate roles. The final reference data (or links to reference data source files) and production user list are compiled into the Production Initiation Plan. 13

The outputs of the integration and test stage include an integrated set of software, an online help system, an implementation map, a production initiation plan that describes reference data and production users, an acceptance plan which contains the final suite of test cases, and an updated project plan.

6.INSTALLATION & ACCEPTANCE STAGE:

During the installation and acceptance stage, the software artifacts, online help, and initial production data are loaded onto the production server. At this point, all test cases are run to verify the correctness and completeness of the software.

Successful execution of the test suite is a prerequisite to acceptance of the software by the customer. After customer personnel have verified that the initial production data load is correct and the test suite has been executed with satisfactory results, the customer formally accepts the delivery of the software.

The primary outputs of the installation and acceptance stage include a production application, a completed acceptance test suite, and a memorandum of customer acceptance of the software. Finally, the PDR enters the last of the actual labor data into the project schedule and locks the project as a permanent project record. At this point the PDR "locks" the project by archiving all software items, the implementation map, the source code, and the documentation for future reference.

14

Qualsoft services project management technique

There are eight stages in Qualsoft services project management technique-

1 2 3 4 5 6 7 8

Requirement analysis. Estimation. Project planning. Design. Development. Testing. Deployment. Maintenance.

15

1-Requirement Analysis-Software Requirement Specification (SRS) is made in this stage. -The contract between the client and the development team is made in this stage. -Basis for system design for development team. -Bench mark for project manager. -Source for formulating test plans for Quality Assurance (QA) and testing teams. -Basis for evolving requirement over the project life span.

Requirement Analysis in input-process-output form-

Input

Process

Output

Initial scope Document Discussion with Client, Existing system

Requirement Analysis Analysis Data flow Diagram Client Analysis

SRS, Data flow Diagram, Prototypes

Requirement Analysis is Design and Development Input for the Quality Management System (QMS).

16

2-EstimationSoftware is the most expensive element of virtually all computer-based systems. For complex, custom systems, a large cost estimation error can make the difference between profit and loss. Cost overrun can be disastrous for the developer. Software cost and effort estimation will never be an exact science. Too many variables-human, technical, environmental, political-can affect the ultimate cost of software and effort applied to develop it. However, software project estimation can be transformed from a black art to a series of systematic steps that provide estimates with acceptable risk. To achieve reliable cost and effort estimates, a number of options arise:

1. Delay estimation until late in the project.

2. Base estimates on similar projects that have already been completed.

3. Use relatively simple decomposition techniques to generate project cost and effort estimates.

4. Use one or more empirical models for software cost and effort estimation.

Unfortunately, the first option, however attractive, is not practical. Cost estimates must be provided "up front". However, we should recognize that the longer we wait, the more we know, and the less likely we are to make serous error in our estimates.

The second option can work reasonably well, if the current project is quite similar to past efforts and other project influences are roughly equivalent. Unfortunately, past experience has not always been a good indicator of future results.

The remaining options are viable approaches to software project estimation. Ideally, the techniques noted for each option should be applied in tandem; each used as a cross-check for the other. Decomposition techniques take a "divide and conquer 17

approach to software project estimation. By decomposing a project into major functions and related software engineering activities, cost and effort estimation can be performed in a stepwise fashion. Empirical estimation models can be used to complement decomposition techniques and offer a potentially valuable estimation approach in their own right.

Each of the viable software cost estimation options is only as good as the historical data used to seed the estimate. If no historical data exist, costing rests on a very shaky foundation.

Estimation in input-process-output form-

Input

Process

Output

SRS, Requirement Traceability Matrix (RTM)

Estimation

Functionality Matrix

Estimation is in the Design and Development input for Quality Management System (QMS).

18

3. Project planningLack of planning is a primary cause of schedule slippage, cost overruns, poor quality, and high maintenance costs for software. Careful planning is required for both the development process and the work products in order to avoid these problems. It is often said that early planning is impossible because precise information concerning project goals, customer needs, and product constraint is not available at a beginning of a software project, but a major purpose of the planning phase is to clarify goals, needs, and constraints. The difficulty of planning should not discourage this most important activity.

A software product becomes better understood as it progresses through analysis, design, and implementation; however, a software project should not be commissioned until enough information is available to permit preliminary planning. It must be recognized that preliminary plans will be modified as the work products evolve; planning for change is one of the key aspects of successfully planning.

The steps required to plan a software project are listed and discussed in subsequent sections of this chapter.

Project planning in the input - process - output form

Input

Process

Output

Functionality Matrix

Project planning

Quality Assurance Plan, Project Schedule

Project plan is the input for the design and development input for Quality Management System Life Cycle.
19

4. DESIGNExternal design of software involves conceiving, planning out, and specifying the externally observable characteristics of a software product. These characteristics include user displays and report formats, external data sources and data sinks, and the functional characteristics, performance requirements, and high level process structure for the product. External design begins during the analysis phase and continues into the design phase. In practice, it is not possible to perform requirement definition without doing some preliminary design. Requirement definition is concerned with specifying the external, functional, and performance requirement for a system, as well as exception handling the other items listed. External design is concerned with refining those requirements and establishing the high level structural view of the system. Thus, the distinction between requirements definition and external design is not sharp, but is rather a gradual shift in emphasis from detailed "what" to high level "how". External design involves conceiving, planning out, and specifying the internal structure and processing details of the software product. The goals of external design are to specify internal structure and processing details, to record design decisions and indicate why certain alternatives trade-offs were chosen, to elaborate the test plan, and to provide a blueprint for implementation , testing, and maintenance activities. The work products of internal design include a specification of architectural structure, the details of algorithms and data structures, and the test plan.

20

Design Stage in the input-process-output form-

Input

Process

Output RTM, High level design document, Low level design document, Database design document, Test plan, Test cases.

SRS

Design

Design stage is the Output for design and development stage of the Quality management life cycle.

21

5. DevelopmentSoftware development is concerned with translating design specification into source code. The primary goal of development is to write source code and internal documentation so that conformance of the code to its specifications can be easily verified, and so that debugging, testing, and modification are eased. This goal can be achieved by making the source code as clear and straightforward as possible. Simplicity, clarity and elegance are the hallmark of the good programs; obscurity, cleverness, and complexity are indicators of inadequate design and misdirected thinking. Source-code clarity is enhanced by structured coding techniques, by good coding style, by appropriate supporting documents, by good internal comments, and by the features provided in modern programming languages. In this chapter, structured coding techniques, coding style, program unit notebooks and internal documentation of source code are discussed. Production of high-quality software requires that the programming team have a designating leader, a well- defined organizational structure, and a through understanding of the duties and responsibilities of each team member.

Development stage in input-process-output form-

Input Database design Document

Process

Output Test cases

Development

Development stage is the input for the quality management life cycle.

22

6. Testing-

Before giving the system to the customer we have to do many types of testing. Some tests depend upon the testing of a component of a system. Group of component, or the whole system and some test depends upon that how the system is working: Is the system working correctly according to the requirement for the design? Testing involves several stages in the development of a system. Initial each program is isolated tested. Such testing is known as unit testing. Module testing or the component testing. When the components are tested on its own then we test the two or more than two components together and that is known as Integration testing. In integration testing we check that the components, properly work together as described in the system or not. After integration testing, we test the system to assure that it has the desired functionality or not and this testing is known as function testing and then we check the performance of the system by applying performance test and before accepting the system the customer can test the system and that testing is known as acceptance testing.

Testing phase in the input- process- output form:

Input

Process Testing

Output Test logs Working application

Test cases

Testing is the verification of design development stage in the Quality Management System (QMS)

23

7. DeploymentDeployment makes the system available for the customer for use. It includes the delivery of the system also. The documents for deployment areReadme.txt DeployementRunbook.doc Usermanual.doc

Deployment stage in the input- process- output form:

Input

process

output

Working application deployment

Deployment

Successful Beta testing

Deployment is the validation in design and development stage of Quality Management System (QMS).

24

8. MaintenanceThe term of "software maintenance" is used to describe the software engineering activities that occur following delivery of a software product to the customer. The maintenance phase of the software life is the tine period in which a software product performs useful work. Typically, the development cycle for a software product plans 1 or 2 years, while the maintenance phase spans 5 to 10 years. Maintenance activities involve making enhancement to software products, adapting to the new environments, and correcting problems. Software product enhancement may involve providing new functional capabilities, improving user displays and modes of interaction, upgrading external documents and internal documentation, or upgrading the performance characteristics of a system. Adaptation of software to a new environment may involve moving the software to a different machine, or for instance, modifying the software to accommodate a new telecommunications protocol or an additional disk drives. Problem correction involves modification and revalidation of software to correct errors. Some errors require immediate attention, some can be corrected on a scheduled, periodic basis, and others are known but never corrected.

25

Quality Management System (QMS) of Qualsoft services:

A quality management system may be defined as the organizational structure, responsibilities, procedures, processes, and resources for implementing quality management [ANS87]. Quality management systems are created to help organizations ensure their specifications. ISO 9000 describes a quality management system in generic terms that can be applied to any business regardless of the products or services offered.

To become registered to one of the quality management system models contained in ISO 9000, a company's quality system and operations are scrutinized by third-party-auditors for compliance to the standard and for effective operation. Upon successful registration, a company is issued a certificate from a registration body represented by the auditors. Semiannual surveillance audits insure continued compliance to the standard.

26

Some important documents used in project management are as follows:

Software Requirement Specification (SRS) :

SRS is written at the end of requirement elicitation and analysis modeling. The SRS is written in a text narrative, supported by graphical models, system charts and high level pseudo programs in natural English language. SRS should be written for all requirements, small, large, simple or complex, including the obvious ones. SRS is based on approved RDD. A good SRS document has certain characteristics that must be present to qualify as a good. The characteristics areclarity, completeness, Correctness, Consistency, Modifiability Traceability,

Feasibility, Testability.

Relationship between SRS and SDLCSRS is very important in SDLC. SRS gives the idea about the requirement of the software which gives the idea about the software which we are going to make in the SDLC.

27

SRS
Chapter / Section
1

Topic
Introduction

1.1 1.2
1.3 1.4 1.5

Background Purpose of the document

Structure of this document Terminology used Convention used in this document

1.6 2 2.1 2.2

2.3 2.4 3

Other documents referred System description Current situation overview Problem faced in current system
Goals of the proposed system Assumption mode Function requirements

3.1 3.2 3.3 3.4 3.5

Partitioning of the functionality Function module one Goals activated Function module two Goals activated

28

PROJECT PLAN:
Project plan is the planning which is related to the software development. Before starting the development process it is necessary to make a project plan which helps the manager of the project to estimate the cost of the project and the time taken by staff to completely develop a software. There are many reasons for planning a project e.g. Information is vital resource so it must be managed. Project plan consist of cost estimation ,scheduling, team structure, software quality assurance plan, project monitoring plans etc. The future course software development is depend on the project plan.

Relation between Project plan and SDLCThe project plan clearly define the various stages in SDLC. Project plan also give the idea about in what sequence the stages should be occur. Project plan also gives the idea about the time to complete the SDLC.

Project plan
Scheduling Team structure Cost estimation

Project Plan

Software quality Assurance plan

Project monitoring Plan

29

Schedule:
Schedule is the document in which the big activities are broken down in small activities, then the time is allotted for each activity and the order in which these activities should carried out is also mentioned in the schedule. scheduling divides the total work into number of activities and then judging the time required to complete these activities. Some of these activities are carried out in parallel.

Gantt chart : Gantt chart uses a calendar-oriented chart to represent the schedule and project. Each activity is represented as a horizontal bar. Starting from starting data of activity and ending at the last data for that activity. the start & end of each activity become milestones for that activity.

Relationship between Schedule and SDLCScheduling make the SDLC very good and beneficial. Scheduling breaks the bigger activities in the SDLC into the smaller activities so that the work is become simple and fast. Scheduling also gives the idea about the time requirement of each activity so that we can calculate the time required for the SDLC.

GANTT CHART

Activity

Test Slack Time

30

Estimates :
Estimation is important job to do before to start the development of the software. A mathematical formula calculate the cost of the project is based on estimates of project size, number of developer and project factors .

Software cost estimation: The cost of the software is depend upon the following components ; -Personal costs -Hardware & Software costs -Communication, travel and Stay Costs -Training Costs -Outsourcing Costs -Marketing Costs -Administrative Costs

CoCoMo Model:
In this model the data is collected from the different Software projects, then analyzing it to discover the accurate formula for the calculation or estimation of cost. this model does not depend on single variable , it depends on many factors, which depends upon the size and then adjusting the estimates based on other variable. This model also estimates the total effort in terms of person-months. It does not include the cost of secretarial staff. It includes development, management cost.

Relationship between Estimate and SDLCEstimates gives the idea about the requirement of people and money in SDLC. Estimates helps to calculate the cost of the software. It also gives the idea about other requirements of SDLC.

31

32

TEST PLAN:
Test planning helps us to design and organizing the tests. It gives the general idea about the scope and schedule of testing. as well as identifying the test items for the entire testing process, so that we are confident that we are testing appropriately and thoroughly. It can be done before the actual testing commences and can done in parallel with the coding and design phases.

Inputs for generating the test plan are as following: 1.Project plan : Project plan is needed to ensure that testing schedule matches that of the project plan and test plan is consistent with the overall plan for the project. 2.Requirement and design documents : Through there documents we select the test unit and deciding the approaches to be used during the testing. 3.Test case specification : It is major activity in testing the overall approach stated in the plan is refined into specific test techniques that should be followed and into the criteria to be used for evaluation. Test case specification gives, for each unit to be tested ,all test cases, inputs to be used in the test case and outputs expected for those test cases. 4.Test case execution and analysis : To execute test case we may required the driver, modules, environment as stated in the test plan ,data etc. Only after all these are ready can the test cases be executed.

Project plan

Req uirement an d d esign d ocument

Test plan

Test case sp ecification

Test case execution and an alysis

33

Test cases :
Test cases are those cases which are used for testing. Good test cases are that which have revealing the presence of faults and they must be used for successful testing. We have to select the test cases which must be error free. It is correct to say that testing is as good as its test cases. we have to select the test cases such that its cost is minimum and it detects the maximum number of errors. as these two are contradictory ,the problem of selecting the right set of test cases becomes more complex. The goal of selected test cases is to ensure that there no error in the program and if it is so then it should be immediately depicted. Ideal test casement be contain all inputs to the program. this is often called exhaustive testing.

There are two criteria for the selection of test cases that are : 1. Specifying a criterion for evaluating a set of test cases. 2. Generating a set of test cases that satisfy a given criterion.

ALPHA & BETA Testing:

Alpha test: It is conducted at the developer's site by a customer. It is conducted in a controlled environment. Software is used in natural setting with the developer looking over the shoulder of the user and recording errors and usage problems. Beta test : It is conducted at one or more customer sites by the end user of the software. It is a live application an environment the cannot be controlled by the developer.

34

Entity-Relation Diagrams (E-R Diagram)

Entity-Relation diagram gives the idea about the relationship between the entities. In SSAD, entities are the key elements. they carry data and have relation with other entities .On analysis and modeling, these are identified and modeled in an E-R diagram. The E-R diagram is issued for relation modeling.

E-R Diagram
Generates Delivery Note Invoices

Generates Mailed To

Order

Places

Customer

E-R Diagram

Above figure shows the E-R diagram for requirement R 9. The entities involved in R 9 invoicing are Delivery note, order, customer and invoice. The relationship between these entities are given belowDelivery note may generate more than one invoice; the relationship between delivery and invoice therefore is one to many. The invoice is meant for a customer; hence, the relationship is one to one between invoice and customer. The customer may raise a number of orders. hence, the customer- order relationship is one to many. An order may generate several delivery notes and a delivery note may combine order quantities from more than one order. Hence, relationship between Order and Delivery Note is many to many. 35

Test ScenarioAlthough the success of a computer based system or product is measured in many ways , user satisfaction resides at the top of the list. If software engineers understand how end- users want to interact with a system, the software team will better able to properly characterize requirements and built meaningful analysis and design models. hence , analysis modeling with UML begins with the creation of scenarios in the form of use-cases , activity diagrams , and swim lane diagrams A use-case captures the interaction that occur between producers and consumers of information and the system itself. In this section , we examine how usecases are develop as a part of the analysis modeling activity. The concept of a use-case is relatively easy to understand - describe a specific usage scenario in straightforward language from the point of view of a defined actor. But how do we know what to write about , how much to write about it , how detail to make our description , and how to organize the description? These are the questions that must be answered if use-cases are to provide value as an analysis modeling tool.

36

Results of Questioner:
1. Do you think that Qualsoft services project management technique is more beneficial than common project management technique ? Answer

Yes No

23 2

92% 8%

100%
90%

80% 70% 60% 50% 40%

30% Yes

No

20% 10% 0% Yes No

2. Do you think that in these days of completion the project can be conducted by common project management technique? Answer Yes No 3 22 12% 88%

3. Do you think that the Qualsoft services project management technique contains all the advanced features? Answer Yes No 17 8 68% 32%

37

4. Do you think that Qualsoft project management technique helps to reduce the cost? Answer Yes No 20 5 80% 20%

5. Do you think that Qualsoft project management technique helps to reduce the efforts? Answer Yes No 19 6 76% 24%

6. Do you think that Qualsoft project management technique helps to reduce the time? Answer Yes No 16 9 64% 36%

7. Do you think that Stages involved in the Qualsoft services project management technique is enough to carry out any project totally? Answer Yes No 23 2 92% 8%

8. Are the documents listed by me are enough to complete the project totally? Answer Yes No 22 3 88% 12%

38

9. Do you think that study of project management technique is important rather than study of only languages? answer Yes No 24 1 96% 4%

10. Do you think that the quality management system of Qualsoft services is good? Answer Yes No 25 0 100% 0%

11. Do you think that the prototyping model suggested by me is beneficial to carry out projects in the company? Answer Yes No 23 2 92% 8%

12. Do you want to suggest some other alternative project management technique to the Qualsoft services? Answer Yes No 3 22 12% 88%

39

CHAPTER-5

RESEARCH METHODOLOGY

METHODOLOGY OF STUDY:Research can be defined as systemized effort to gain new knowledge. A research is carried out by different methodologies which have their own pros and cons. Research methodology is a way to solve research in studying and solving research problem along with logic behind them are defined through research methodology. Thus while talking about research methodology we are not only talking of research methods but also considered the logic behind the methods. We are in context of our research studies and explain why it is being used a particular method or technique and why the others are not used. So that research result is capable of being evaluated either by researcher himself or by others.

RESEARCH METHODOLOGY:To achieve a goal successfully, one needs to sketch a perfect roadmap or adopt methodology to the destination and also need to follow the path strictly. Research methodology is away of systematically solve the research problem. It may be understood as a science of studying how research is done systematically. In the various steps that are generally adopted by a researcher in studying his research problem along with the logic behind them.

Types of method:
The study under the category of Descriptive types of research and fact finding inquiries of different kind. It is the description of the state of affairs , as it exist at the presence. The main character of this method is the research has no control over the variable he can only report what has happened or what happening. This method of research used in this study was research method. As a descriptive method, the research has defined clearly what he wants to measure and has used quantitative and qualitative method for measuring it along with clear-cut definition of population he wants to study the procedure be used has been clearly planned. 40

Data source:1.Defining the objectives:-

The aim of this project as has already been mentioned was to "Study Project Management Techniques Adopted in small I.T. Firms."

2.Developing the Research Plan:-

This step called for decision on the data sources, sampling plan and contact methods.

* Data Sources

Data was collected from primary and secondary data. The various sources are:

1.Primary Data.

2.Secondary Data.

1.Primary Data

This type of data does not exist ; it is originated by primary sources like personal interaction or field back forms, questionnaires that act as tools for collecting data.

2.Secondary Data

This type of data already exist, And used to generate information as required. We collect the secondary data through Internet, books, journals, and magazines of the company, various company broachers, talking with people.

41

*Research Approach

The research approach adopted here was the observation method. But other approaches also used such as survey research.

3.Collecting the Information

With respect to primary and secondary data, the information is collected. Primary data tells us to asking the question to the person personally to become an adviser. Secondary data means that to get the data from the internet company magazines ,talking with people and convince them.

42

CHAPTER6 FINDINGS:
1.According to the questioner 92% software developers think that Qualsoft services project management technique is more beneficial than common project management technique.

2.The projects can not be conducted by the common project management technique in these days of competition.

3.Many software developers think that the project management technique of Qualsoft services contains all the advanced features.

4.The Qualsoft services project management technique of Qualsoft services helps to reduce the cost, efforts and time.

5.The stages involved in Qualsoft services project management technique is enough to carry out the modern projects.

6. The 88% of software developers think that the documents listed by me are enough to carried out any project totally.

7.The prototyping model suggested by me could be beneficial to carry out the projects.

43

8.2 The Documents used in the company during the project management are as follows1.Software Requirement Specification (SRS).

2.Project plan.

3.Schedule.

4.Estimates.

5.Test plan.

6.Test cases.

7.Alfa and Beta test.

8.Entity-relation diagram.

9.Test scenario.

44

Chapter 7 Recommendations Prototyping model What is Prototyping?

Prototyping is the process of building a model of a system. In terms of an information system, prototypes are employed to help system designers build an information system that intuitive and easy to manipulate for end users. Prototyping is an iterative process that is part of the analysis phase of the systems development life cycle. During the requirements determination portion of the systems analysis phase, system analysts gather information about the organization's current procedures and business processes related the proposed information system. In addition, they study the current information system, if there is one, and conduct user interviews and collect documentation. This helps the analysts develop an initial set of system requirements. Prototyping can augment this process because it converts these basic, yet sometimes intangible, specifications into a tangible but limited working model of the desired information system. The user feedback gained from developing a physical system that the users can touch and see facilitates an evaluative response that the analyst can employ to modify existing requirements as well as developing new ones. Prototyping comes in many forms - from low tech sketches or paper screens(Pictive) from which users and developers can paste controls and objects, to high tech operational systems using CASE (computer-aided software engineering) or fourth generation languages and everywhere in between. Many organizations use multiple prototyping tools. For example, some will use paper in the initial analysis to facilitate concrete user feedback and then later develop an operational prototype using fourth generation languages, such as Visual Basic, during the design stage.

45

Some Advantages of Prototyping: Reduces development time. Reduces development costs. Requires user involvement. Developers receive quantifiable user feedback. Facilitates system implementation since users know what to expect. Results in higher user satisfaction. Exposes developers to potential future system enhancements.

Some Disadvantages of Prototyping Can lead to insufficient analysis. Users expect the performance of the ultimate system to be the same as the prototype. Developers can become too attached to their prototypes Can cause systems to be left unfinished and/or implemented before they are ready. Sometimes leads to incomplete documentation.

46

If sophisticated software prototypes (4th GL or CASE Tools) are employed, the time saving benefit of prototyping can be lost.

Because prototypes inherently increase the quality and amount of communication between the developer/analyst and the end user, its' use has become widespread. In the early 1980's, organizations used prototyping approximately thirty percent (30%) of the time in development projects. By the early 1990's, its use had doubled to sixty percent (60%). Although there are guidelines on when to use software prototyping, two experts believed some of the rules developed were nothing more than conjecture.

In the article "An Investigation of Guidelines for Selecting a Prototyping Strategy", Bill C. Hardgrave and Rick L. Wilson compare prototyping guidelines that appear in information systems literature with their actual use by organizations that have developed prototypes. Hardgrave and Wilson sent out 500 prototyping surveys to information systems managers throughout the United States. The represented organizations were comprised of a variety of industries - educational, health service, financial, transportation, retail, insurance, government, manufacturing and service. A copy of the survey was also presented to a primary user and a key developer of two systems that the company had implemented within the two years of the survey.

There were usable survey results received from 88 organizations representing 118 different projects. Hardgrave and Wilson wanted to find out how many of the popular prototyping guidelines outlined in literature were actually used by organizations and whether compliance affected system success (measured by the user's stated level of satisfaction). It should be noted that, although not specifically stated, the study was based on the use of "high tech" software models, not "low tech" paper or sketch prototypes.

Based on the results of their research, Hardgrave and Wilson found that industry followed only six of the seventeen recommended in information system literature. The guidelines practiced by industry whose adherence was found to have a statistical effect on system success were:

47

Prototyping should be employed only when users are able to actively participate in the project. Developers should either have prototyping experience or given training. Users involved in the project should also have prototyping experience or be educated on the use and purpose of prototyping. Prototypes should become part of the final system only if the developers are given access to prototyping support tools. If experimentation and learning are needed before there can be full commitment to a project, prototyping can be successfully used. Prototyping is not necessary if the developer is already familiar with the language ultimately used for system design.

Instead of software prototyping , several information systems consultants and researchers recommend using "low tech" prototyping tools (also known as paper prototypes or Pictive), especially for initial systems analysis and design. The paper approach allows both designers and users to literally cut and paste the system interface. Object command and controls can be easily and quickly moved to suit user needs.

Among its' many benefits, this approach lowers the cost and time involved in prototyping, allows for more iterations, and gives developers the chance to get immediate user feedback on refinements to the design. It effectively eliminates many of the disadvantages of prototyping since paper prototypes are inexpensive to create, developers are less likely to become attached to their work, users do not develop performance expectations, and best of all, your paper prototypes are usually "bugfree" (unlike most software prototypes)!

48

CONCLUSION: The study of the project management technique is important for every I.T professional personnel. The common project management technique is now outdated. The Qualsoft Services project management technique helps to reduce the cost, time and effort. There are some important documents such as SRS, project plan etc. are important to complete the project. The prototyping model can be very useful to carry out the projects.

49

Annexure

1. Do you think that Qualsoft services project management technique is more beneficial than common project management technique ? Answer

Yes No

2. Do you think that in these days of completion the project can be conducted by common project management technique? Answer Yes No

3. Do you think that the Qualsoft services project management technique contains all the advanced features? Answer Yes No

4. Do you think that Qualsoft project management technique helps to reduce the cost? Answer Yes No

50

5. Do you think that Qualsoft project management technique helps to reduce the efforts? Answer Yes No

6. Do you think that Qualsoft project management technique helps to reduce the time? Answer Yes No

7. Do you think that Stages involved in the Qualsoft services project management technique is enough to carry out any project totally? Answer Yes No

8. Are the documents listed by me are enough to complete the project totally? Answer Yes No

9. Do you think that study of project management technique is important rather than study of only languages? answer Yes No

51

10. Do you think that the quality management system of Qualsoft services is good? Answer Yes No

11. Do you think that the prototyping model suggested by me is beneficial to carry out projects in the company? Answer Yes No

12. Do you want to suggest some other alternative project management technique to the Qualsoft services? Answer Yes No

52

The project completed by the Qualsoft Services successfully by using different project management techniques: The total number of projects completed by the company: 958. These projects are carried out by the following techniques:
The number of projects completed by using Qualsoft Services own project management technique The number of projects completed by using Common project management technique The number of projects completed by using prototyping model 710 76 172 74.12% 7.94% 17.96%

Total

958

100%

No. of prjects completed

By Qualsoft P.M.T By common P.M.T By prototyping

This pie chart shows that most of the project are carried out by Qualsoft services own project management technique.

53

BIBLIOGRAPHY:

BOOKS:
SOFTWARE PRESSMAN SOFTWARE ENGINEERING: RITESH AND VANDAVA RASTOGI ENGINEERING PRACTIONER APPROACH: ROGER

WEBSITES:
WWW.GOOGLE.CO.IN WWW.SLIDESHARE.NET

54