Placement and Training

INTRODUCTION
PROJECT DEFINITION

Online Auction System is basically a website for auctioning the software on Internet; it is a bridge between buyer and coder. The main three parts of this website is buyer, coder and Administrator.

ORGANIZATION: These are the users of this website who wants to develop any software application for

their personal use or for their organization. The software application may be website, stand-alone application, client server application etc. They post there Project Definition on website. That definition is view by the other user of this website. After the last date of Bidding boundary buyer will check all bid posted on his/her project and after that select the coder to develop application.

CODER: These are the users of this website who may be any organization or any programmer

wants to actually develop the software application. They view the definition posted on the website and if he/she may be interested than post their bid on that project. When buyers select coder than the selected coder start working on the project and complete the project in the day specified by him.

ADMINISTRATOR:
This is most responsible person of the website who actually looks back for rule and regulation is followed by any user or not. He/she is responsible for money transaction from Buyer to Coder. When buyer selects the bid at that time he/she windrow amount from the buyer account using credit card and deposits in his/her own account. After the successful completion of the project administrator transfer that amount from his/her account to Coder account. 1

Placement and Training

SYSTEM REQUIREMENT

Hardware Requirements : The configuration of hardware for education of the project is as mention below. Pentium IV Processor (Minimum Pentium II-450Mhz (Pentium III-650Mhz recommended))

21 color Monitor 104 Keyboard swichies 500MB free on the drive where the OS is installed (usually C:\) and 2.5 Gigs free on the installation drive (where VS.NET will be installed). RAM : 512 MB (128 MB recommended) for Windows 2000 Professional, and 192MB (256 MB recommended) for Windows XP Professional.

Software Requirements : The necessary Operating system used to execute the project. Windows 2000 (Server or Professional), Windows XP, or Windows NT 4.0 Server. The necessary Software used in developing the project is as mentioned below. Front End Tool: - ASP .Net Back End Tool: - SQL Server 2000, Code behind C#. Net

Placement and Training

SYSTEM ANALYSIS
FEATURES OF TOOLS USED

About Microsoft .NET:

Introduction to .NET and ASP.NET : Its being touted as the next big thing. Microsoft has invested millions in marketing, advertising, and development to produce what it feels is the foundation of the future Internet. Its a corporate initiative, the strategy of which was deemed so important, that Bill Gates himself, Microsoft Chairman and CEO, decided to oversee personally its development. It is a technology that Microsoft claims will reinvent the way companies carries out business globally for years to come. In his opening speech at the Professional Developers Conference (PDC) held in Orlando Florida in July of 2000, Gates stated that a transition of this magnitude only comes around once every five to six years. What is this show-stopping technology? Its .NET. What is .NET? . NET is the result of a complete makeover of Microsofts software development products, and forms part of the companys new strategy for delivering softwares a service. The key features that .NET offers include: .NET Platform: The .NET platform includes the .NET Framework and tools to build and operate services, clients, and so on. ASP.NET, the focus of this book, is a part of the .NET Framework. .NET Products: .NET products currently include MSN.NET, Office. NET, Visual Studio. NET, and Windows Server 2003, originally known as Windows .NET Server. This suite of extensively revised systems provides developers. With a friendly, usable environment in which they may create applications. 3

Placement and Training

With a range of programming languages including C++. NET, Visual Basic. NET, ASP.NET, and C#. Because all these products are built on top of .NET, they all share key components, and underneath their basic syntaxes. Youll find they have much in common. .NET My Services An initiative formerly known as "Hailstorm", .NET MY Services is a set of XML Web Services1 currently being provided by a host of Partners, developers, and organizations that are hoping to build corporate services and applications for devices and applications, as well as the Internet. The collection of My Services currently extends to passport, messenger, contacts, email, calendars, profiles, lists, wallets, location, document stores, application settings, favorite Websites, devices owned, and preferences for receiving alerts. What is ASP.NET? The site to access and change the information. Many different programming Technologies and supported languages have been developed to create Web applications; PHP, JSP (using Java), CGI (using Perl), and ColdFusion (using CFML) re just a few of the more popular ones. Rather than tying you to a specific technology and language, however, ASP.NET lets you write Web applications using a variety of familiar programming languages. Finally, ASP.NET is based on the Microsoft .NET Framework. The .NET Framework collects all the technologies needed for building Windows applications, eb applications, and Web Services into a single package with a set of more than twenty programming languages. To develop Websites with ASP.NET, youll need to download the .NET Framework Software Development Kit, which Ill guide you through in the next few sections. Even with all the jargon demystified, youre probably still wondering: what makesASP. NET so well? Compared with other options for building Web applications, ASP.NET has the following advantages: ASP.NET lets you use your favorite programming language, or at least one Thats really close to it. The .NET Framework currently supports over twenty Languages, four of which may be used to build ASP.NET Websites.

Placement and Training

ASP.NET pages are compiled, not interpreted. Instead of reading and interpreting your code every time a dynamic page is requested, ASP.NET compiles dynamic pages into efficient binary files that the server can execute very quickly. This represents a big jump in performance when compared with the technologys interpreted predecessor, ASP. ASP.NET has full access to the functionality of the .NET Framework. Support for XML, Web Services, database interaction, email, regular expressions, and many other technologies are built right into .NET, which saves you from having to reinvent the wheel. ASP.NET allows you to separate the server-side code in your pages from the HTML layout. When youre working with a team composed of programmers and design specialists, this separation is a great help, as it lets programmers modify the server-side code without stepping on the designers carefully crafted HTMLand vice versa.

About MS SQL
MS SQL is the most widely used database in the world. It runs virtually on every kind of computer, and functions identically on all machines. MS SQL is a relational database. This concept is an extremely simple way of thinking about and managing the data used in a business. It is nothing more than a collection of tables of data. SQL was developed and defined by IBM Research, and has been refined by then ANSI as the standard language fir relational database. SQL is a non-procedural language because it: Processes sets of records rather than just one at a time. Provides automatic navigation to the data

Rather than manipulating single records, you can manage sets of records. The most common form of a set of record is a table. All SQL statements accept sets as input and all SQL statements return sets as output. The set property of SQL allows the results of one SQL statement to be used as input to another SQL statement. SQL provides statements for a variety of tasks including Querying data Inserting, updating and deleting rows in a table 5

Placement and Training

Creating, modifying and deleting database objects

Controlling access to the database and database objects Guaranteeing database consistency

Placement and Training

REQUIREMENT ENGINEERING PROCESS

Description: Requirement Engineering process

Feasibility study Requirement analysis Feasibility report System models Specification of requirements Requirement documents Requirement definition Requirements

specification

Specification of requirements

The description of the service and the constraints are the requirements of the system and the processes involved in the requirement engineering are Finding out Analyzing Documenting and Checking these services and constraints

General Constraints: This system is web-based and will run on system having Windows 95/98 or higher version.

Placement and Training

REQUIREMENT ANALYSIS

Requirements definition and specification Requirement validation

Domain understanding Process Entry Requirements collection Requirement

Prioritization

Requirement Analysis Process

Conflict Resolution

Functional Requirement:

Placement and Training

1) Input: The Organization/Coder details. The Project Details. The Bid Details.

2) Process: The Organization will post the requirement of his project to develop, after this the coder will place the bid on to the project as per his choice. Then the administrator of our website will allow to assign the project whose bid is lowest. 3) Output: The Project will be assigned to the coder and when it will complete the coder will get the money from our website administrator through either the credit card transaction or cheque transaction.

PROCESS MODEL

LINEAR SEQUENTIAL MODEL The Linear Sequential Model for software engineering is illustrates in figure. This model is sometimes called the "classic life cycle " or the "waterfall model," the linear sequential model suggests a systematic, sequential approach to software development that begin at the system level and progresses through analysis, design, coding, testing and maintenances. Modeled after the conventional engineering cycle, the linear sequential model encompasses the following activities:

System/Information Engineering
Analysis Design Code Process Entry

Placement and Training

System/Information Engineering and Modeling: Software is always part of a larger system (or business), work begins by establishing requirements for all system elements and then allocating some subset of these requirements to software. This system view is essential when software must interface with other elements such as hardware, people, and analysis encompasses requirements gathering at the system level with a small amount of top-level analysis and design. Information engineering encompasses requirements gathering at the strategic business level and at the business area level. Software Requirements Analysis: The requirements gathering process is intensified and focused specifically on software. To understand the nature if the program to be built, the software engineer ("analyst") must understand the information domain for the software, as well as required function, behavior,
performance, and interfacing. Requirements for both the system and the software are documented and reviewed with the customer.

Design: Software design is actually a multi step process that focuses on four distinct attributes of a program: data structure, software architecture, interface representations, and procedural (algorithm) detail. The design process translates requirement into representation of the software that can be assessed for quality before code generation begins. Link requirements, the design is documented and becomes part of the software configuration. Code generator: The design must be translated into a machine-readable form. The code generation step performs this task. if design is performed in a detailed manner, code generation can be accomplished mechanistically. Testing: Once code has been generated, program testing begins. The testing process focuses on the logical internals of the software, assuming that all statements have been tested, and on the functional externals that is, conducting tests to uncover errors and ensure that defined input will produce actual results that agree with required results. 10

Placement and Training

Maintenance: Software will undoubtedly undergo change after it is delivered to the customer (a possible exception is embedded software). Change will occur because errors have been encountered, because the software must be adapted to accommodate changes in its external environment (e.g., a change required because of a new operating system or peripheral device), or because the customer requires functional or performance enhancements. Software maintenance reapplies each of the preceding phases to an existing program rather than a new one. The linear sequential model is the oldest and the most widely used paradigm for software engineering. However, criticism of the paradigm has caused even active supporters to question its efficacy.

11

Placement and Training

PROJECT PLANNING
TIME-LINE CHART

When creating a software project schedule, the planner begins with a set of task. If automated tools are used, the work breakdown is input as task network of task outline. Effort, duration, and start date are then input for each task. In addition, tasks may be assigned to specific individuals.

As a consequence of this input, a timeline chart also called a Gantt chart is generated. A timeline chart can be developed for the entire project. Timeline chart depict a part of a software project schedule.

All project tasks are listed in the left hand column. The horizontal bar indicates the duration of each task. When multiple bars occur at the same time on the calendar, tasks concurrency is implied. The diamonds indicate milestones.

Once the information necessary for the generation of a timeline chart has been input, the majority of software project scheduling tools produce project tables a tabular listing of all project task, their planned and actual start and end table dates and variety of related information. Used in conjunction with the timeline chart, project table enable the project manager to track progress.

12

Placement and Training

Timeline chart depicting the progress of project during 21ST August to 30th October, 2008.

Date: 21st July, 2008 to 31st July, 2008 Task Project Objectives Project Planning Requirement Analysis System Analysis System Design Interface Design Coding Testing 21 22 23 24 25 26 27 28 29 30 31

Date: 1st Aug, 2008 to 15th Aug, 2008 Task Project Objectives Project Planning Requirement Analysis System Analysis System Design Interface Design Coding Testing 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

Date: 16th Aug, 2008 to 31st Aug, 2008 Task Project Objectives Project Planning Requirement Analysis System Analysis System Design Interface Design Coding Testing 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

13

Placement and Training

Date: 1st Sep, 2008 to 15th Sep, 2008 Task Project Objectives Project Planning Feasibility Study Requirement Analysis System Analysis System Design Interface Design Coding Testing 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

Date: 16th Sep, 2008 to 30th Sep, 2008 Task Project Objectives Project Planning Feasibility Study Requirement Analysis System Analysis System Design Interface Design Coding Testing 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

Date: 1st Oct, 2008 to 15th Oct, 2008 Task Project Objectives Project Planning Feasibility Study Requirement Analysis System Analysis System Design Interface Design Coding Testing 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

14

Placement and Training

Date: 16th Oct, 2008 to 30th Oct, 2008 Task Project Objectives Project Planning Feasibility Study Requirement Analysis System Analysis System Design Interface Design Coding Testing 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

RESOURCE CHART

15

Placement and Training

WORK TASK

PLANNED START

ACTUAL START

PLANNED COMPLETE

ACTUAL COMPLETE

ASSIGNED PERSON

1.1 Identify needs & benefits Identify needs & project constraints Establish project statement Milestone: Project scope defined 1.2 Assess risks Project risks Technical risks 1.3 Define desired input/output/control Insertion of data Output of the service Selection of services Define the budget for each service Total estimate Confirmation of payment 1.4 Research For database management For Client/Server Software For form designing Milestone: Technologies identified 1.5 Define the function & behavior Static pages about information Forms for Insertion Form for services Forms for selection of services & its Budget Forms for estimates & payment Review OCI definition Revise OCI as required Milestone: OCI definition complete 1.6 Merger of software elements Milestone: Software Combined 1.7 Feasibility check Technical Feasibility Business Feasibility Milestone: Feasibility assessed 1.8 Make quick estimate of size 1.9 Testing & Evaluation 1.10 Review the product for changes

M1,D1 M1,D4

M1,D1 M1,D4

M1,D3 M1,D7

M1,D3 M1,D7

M1,D8 M1,D8 M1,D16 M1,D21 M1,D24 M1,D27 M2,D1 M2,D5 M1,D8 M1,D8 M1,D12

M1,D8 M1,D8 M1,D20 M1,D21 M1,D24 M1,D27 M2,D1 M2,D5 M1,D8 M1,D8 M1,D12

M1,D15 M1,D15 M1,D20 M1,D23 M1,D27 M1,D31 M2,D4 M2,D7 M1,D15 M1,D15 M1,D15

M1,D15 M1,D15 M1,D20 M1,D23 M1,D27 M1,D31 M2,D4 M2,D7 M1,D15 M1,D15 M1,D15

M1,D8 M1,D21 M1,D24 M1,D27 M2,D1 M2,D8 M2,D11

M1,D8 M1,D21 M1,D24 M1,D27 M2,D1 M2,D8 M2,D11

M1,D15 M1,D23 M1,D27 M2,D7 M2,D11 M2,D15 M2,D18

M1,D15 M1,D23 M1,D27 M2,D7 M2,D11 M2,D15 M2,D18

M2,D19 M2,D27 M2,D27 M3,D8 M3,D13 M3,D24

M2,D19 M2,D27 M2,D27 M3,D8 M3,D13 M3,D24

M2,D26 M3,D7 M3,D3 M3,D12 M3,D23 M3,D31

M2,D26 M3,D7 M3,D3 M3,D12 M3,D23 M3,D31

16

Placement and Training

SYSTEM DESIGN
INTRODUCTION TO SYSTEM DESIGN

Definition :

System design is a process of preparing of input process and the result detail procedure. After gathering the facts through various techniques such as questionnaires, interviews, analysis of documents and observation into all existing system and recording these collected information in the proper format using DFDs decision table, flowcharts etc. The next step is to define the system in terms of user requirements. This is referred to as logical design and then converted into physical design.

Logical design :

When the system analyst prepares the logical design of system, which contains the details of the users requirements. The information flowing in and out of the system and the required data resources. The logical design contains the following information: Specification about input data. The source of input data the document from which it will be derived and the process of data preparation from the documents.Specification about output reports the data contains in the reports, its formats and frequency of generation of report. Specification about data to be stored permanently in the system and its format.Specifications about edit correction, backup procedures and data security arrangement. Specification about implementation plans. Brief information about current logical and physical system.

17

Placement and Training

Brief information about the benefit of the new system, its constraints and required resources to implement it.

Physical design of system Once the agreements are reached between the user and about the logical design of the system, the system analysis can start with the physical design of the system.Physical design of the system means the designing the computer part of the information system. The physical design of the computer system involves the following aspects.

Stored data Physical storage of data is on the secondary storage device like floppy disk, hard disk and Magnetic tapes. The data is stored in the database. A database is a collection of tables. Table is collection data items organized in the terms of collection of rows. Table contains the stable information about the entities. When row is added or deleted from a table, table affected, is said to be updating of table. In online transaction processing system, the table is updated as soon as transaction occurs but in a batch processing system table will be updated after transaction performed. Input and output The major step is the system design is the preparation of input data format and the design of output repots. The input design is the process of designing the input data in a computerbased format. While designing the input, try to produce the cost effective method and to make sure that it is acceptable to the user and also the accuracy of data is to be achieved because if the input data entered is not correct, the output will be not correct. Computer procedure design When the management accepts the input/output design proposal, the next step to follow is the design of computer procedures. The analyst has to specify to programmer, the input/output and processing details that are needed to the design the specifying the computer procedures. These tools are flowcharts, data flow diagrams etc. 18

Placement and Training

USE-CASE DIAGRAM

ADMINISTRATOR AND EXISTING STUDENT:name address

id

Pn.no.

result.

PLACEMENT MANAGER:-

Retrive student information

Give the company detail

19

Placement and Training

CLASS DIAGRAM

20

Placement and Training

SEQUENCE DIAGRAM

21

Placement and Training

ACTIVITY DIAGRAM

22

Placement and Training

STATE DIAGRAM

23

Placement and Training

TESTING
INTRODUCTION TO TESTING AND DEBUGGING

The phase of system development life cycle tests system design. Testing of system decides whether the newly designed system works properly or not. After the development of documentation manually about the system this stage is checked. And if the system working properly then it will be considered for implementation and if isnt then system analyst is informed to find out generated errors or problems and to find out its solutions. This process is known as debugging. For any software system testing means to check out its coding. If there is not any problem in the coding then that code is proper and efficient to design. If we are not getting proper or required output then we have to debug the system coding. So, the debugging is also a subpart of the testing section. If the system runs correctly during testing then there is no need to debug. During the testing of our project we have to face different types of errors. Especially, database errors annoyed us but at last we solved it, successfully. Some of the errors are listed below with their cause and solution.

Testing Principles
Following are the testing principles, which are used, All tests should be traceable to user requirements. Tests should be planned long before testing begins. Testing should begin in small and progress toward testing in Exhaustive testing is not possible. To be most effective testing should be conducted by an independent third party. 24 the large.

Placement and Training

TESTABILITY
Software testability is simply how easily a computer program can be tested. The checklist that follows provides a set of characteristics that lead to testable software. Operability. Observable. Controllability. Decomposability. Simplicity. Stability. Understandability.

Following are the attributes of the good test: A good test has a high probability of finding an error. A good test is not redundant. A good test should be best of breed. A good test would be neither too simple nor too complex.

25

Placement and Training

MODEL OF TESTING
There are several models for testing module some of them are as follows: White Box Testing:As per our project, we have used white Box Testing Model because independent paths of PHP files and loops are the cornerstones of the vast majority of all algorithms implemented in the software. There are five different classes of the loops, which can be defined as follows. Simple Loops. Nested Loops. Concatenated Loops. Unstructured Loops. Continuous Loops.

As per our project, we have used Simple Loops. The Concatenated loops can be tested with the different PHP files of the project; all are independent of each other.

Black Box Testing:Black-box testing attempts to find errors in the following Categories: Incorrect or missing function. Interface errors. Errors in fetching external data. Behavior or performance errors. Initialization and termination error. 26

Placement and Training

Black-box testing is implementing on our project through test each and every independent PHP file. For dependent files, we check the dependency and interface after TEST integrating all the files. For behavior or performance testing we first made demo give it to our project guide and some employees to use and check performance.

TEST STRATEGY
A strategy provides a road map that describes the steps to be undertaken, and how much effort, time and resources will be required. A testing strategy must incorporate test planning, test design, test execution, and resultant data collection and evaluation. The testing strategy followed by us constituted the following component parts as: To accomplish this there are some methods defined. They are: Graph based Testing: In this method a graph of all objects with their relationship with each other is created as Nodes and Links. Then each of the relationship is studied separately so that a test case can be derived. In this study, all the attributes of relationship like transitivity, symmetry and reflexivity is tested. Care should be taken that no node and relationship remains uncovered. Equivalence partitioning: This method divides the input domain of a program into classes of data from which test cases can be derived. These classes, Known as Equivalence Classes, represent a set of valid or invalid input conditions. It helps in a manner that one test case alone uncovers number of errors that might otherwise require more number of test cases. Boundary value analysis: As the name suggests boundary value analysis leads to selection of test cases that exercise on boundary values for a software module i.e. if an input condition pertains to a range bounded by 2 values an upper and a lower, then test cases should be designed with values just above and just below these values. TEST STRATEGIES : Testing is a set of activities that can be planned in advance and conducted systematically, for this reason a template for software testing, consisting a set of steps into which we can place specific test cases & testing methods, should be defined. Testing is just like assurance to review of software product and related documents for correctness, completeness, reliability, and maintainability. And it includes assurance that the 27

Placement and Training

system meets the specification and requirements for its intended use and performance. The common view of the testing is to prove that are no error. System testing is too much expensive as well as it is not possible for analyst to prove that software is free and clear of error.

CONCLUSION
CONCLUSION
This system is basically a website that works as a bridge between buyer and coder. The person who needs a soft ware according to his prescribed demand, he can choose one from a group of coders to fulfill the desired features for his software. Administrator is the most responsible person for the website who actually looks back for rule and regulation is followed by any user or not. Buyer wants to develop any software application for either a personal use or for an organization. He posts his Project Definition and requirements on website which is viewable to other users. Coder views this definition and if interested he posts his bid for that project. Buyer will check all the bids posted on the project and select the most suitable bid. The selected coder starts the project and completes it within the days specified by him. Administrator is responsible for money transaction between Buyer and Coder. When buyer selects the bid, administrator withdraws amount from the buyer account and deposits in his/her own account. After the successful completion of the project administrator transfers that amount to Coders account.

28

Placement and Training

USER MANUAL

To install the software 1. Copy Folder from CD. 2. Run Setup.Exe and provide necessary information as setup needs. Before you start Setup be sure that, a. Your IIS (Internet Information Services is Well Configured. b. .Net Framework (Version 1.1 or version 2.0) is already installed. c. Local Area Network is Well Configured.

REFERNCES
1. The Ultimate VB.NET and ASP.NET Code Book By: Karl Moore 2. ASP.NET Web Developers Guide. By: Syngress Press 3. ASP.NET Unshielded By : Stephen Walther

4. ASP.NET Website Programming, Visual Basic .NET Edition: Problem, Design, Solution By : Marco Bellinaso and Kevin 5. Software Engg. By : Pressman.

29