SYNOPSIS

The project entitled Production Planning System is a computerized system for production Department of the company. It is developed using vb.net as front end and Microsoft SQL server as back end. This system is used to handle the Raw materials stock, Produced products stock legibly for their business order, the stores quality engineers are verifying the incoming raw materials and they are updating the stock throw Goods Received Note and Purchase Return Entry. For making one product lot or raw materials in the different level of ratio are required. This should be planned before the production start. So this system will generate the required raw materials list, depends upon the estimated production. For production unit, after getting this Required Raw Materials list for producing products, automatically the required raw materials will be released from the store. After production or products, the quality engineers passing the produced products to store for sales after the quality check. The product stock is updated whenever the sales department updates the customer invoice based on the job order. So this computerized system will help the company to perform the entire above-mentioned task easily.

II

1.INTRODUCTION
The production planning system is used in the motor production unit to record its day-to-day transactions like purchase of the raw materials, customer details, supplier details, finished products, sales details, stock of the raw materials etc. And finally the reports can be generated for various options. This project has five modules, in each and every module a specific task is done. For example in the customer details module the details of the customer are maintained.

MODULES DESCRIPTION: The various modules of this project are: 1. Supplier details 2. Stock details 3. Sales 4. Customer details 5. purchase details.

Supplier Details: In this module the details of the supplier is maintained. The address of the customer and the type of raw material they supply etc are stored. Stock details: In this module the received raw materials from the supplier are maintained in this table. And whenever the raw material is sent to the production unit the stock is reduced in the store room. When the new raw material is purchased it is referred by its id number and added to old stock

Sales details: In this module the sales details are maintained like to which company the products are soled and in which date the products are delivered and the total amount details are maintained. Customer details: In this module the details of the customer like address, city and the type of delivered goods are maintained. Then the amount balance details are also provided in this module.

Purchase details In this module the details of the supplier name, supplier id, item code,purchase date are maintained.the amount details are also maintained in this module.

1.1 ORGANIZATION PROFILE SRI KALAI APPARELS has started in 1987 located in tripur. The Partner has a wide range of knowledge in the field of garment manufacturing and has an experience of more than 10 years in the garment industry. The partner plays an active role in production process which helps our buyers to get quality products. Our Team The team has dedicated professionals in all departments and is self driven and executes their responsibilities accurately. Labors are more skilled in their respective fields and very cooperative with the management team. There is no employ of child labors or any other mean of forced manpower. Our Quality Standards In this competitive market, quality is one of the important factors which should be considered more in production process. The organization takes a major care in the quality department, to meet out customers satisfaction. Continuous work on improving the quality every time adopting the latest methods and technology available in the market is also done.

1.2 SYSTEM ENVIRONMENT

The system has been developed using front end and back end as the platform. HARDWARE CONFIGURATION Processor Ram Hard Disk Keyboard Monitor Printer Floppy Drive : : : : : : : Pentium IV 128MB 40GB 105 Keys SVGA color Hp Laser Printer 1000 series 1.44MB

SOFTWARE CONFIGURATION Operating System Front-end Back-End : : : Windows XP VB.Net SQL server2000

1.3 SOFTWARE FEATURES

Introduction to VB.NET Visual Basic .NET is a pillar of the .NET Framework, and yet another step forward in evolution of the languages. It is a high-level programming language for the .NET Framework, and provides the easiest point of entry to the Microsoft .NET platform. Features of vb.net VB.NET is an object-oriented language It supports more than 30 languages like Microsoft Visual Basic, Microsoft C++, and Microsoft Jscript, ASP, Microsoft C#, XML etc. It has enhanced features like inheritance, interfaces, and overloading, common language specification (CLS) compliance, delegates and others. Visual Basic also now supports structured exception handling, and custom attributes. Visual Basic supports multithreading. Its the ability to assign individual tasks to separate processing threads.

Visual basic .net reflects the following design principles: It is recognizably the descendant of Visual Basic. An existing Visual Basic programmer will feel immediately familiar with the language. Its syntax and semantics are simple, straightforward, and easy to understand. The language avoids unintuitive features. It gives developers the major features of the .NET Framework and is consistent with the framework's conventions. It is reasonably up gradable from Visual Basic: Because the .NET Framework explicitly supports multiple computer languages, it works well in a multi language environment. It is as compatible with previous versions of Visual Basic as possible. Whenever practical, Visual Basic .NET has the same syntax, the same semantics, and the same run-time behavior as its predecessors. These principles complement the original design principles of Visual Basic: It is as safe a language to write in as possible. In general, Visual Basic tries to balance reliability, ease of use, and efficiency in the definition of the language. It is an extremely approachable language. It enables rapid program development, while not compromising reliability. It produces predictable and efficient code. 6

Microsoft SQL Server 2000

Microsoft SQL Server2000 extends the performance, reliability, quality, and ease-of-use of Microsoft SQL Server version 7.0. Microsoft SQL Server 2000 includes several new features that make it an excellent database platform for large-scale online transactional processing (OLTP), data warehousing, and e-commerce applications. The OLAP Services feature available in SQL Server version 7.0 is now called SQL Server 2000 Analysis Services. The term OLAP Services has been replaced with the term Analysis Services. Analysis Services also includes a new data mining component. The Repository component available in SQL Server version 7.0 is now called Microsoft SQL Server 2000 Meta Data Services. References to the component now use the term Meta Data Services. The term repository is used only in reference to the repository engine within Meta Data Services.

MICROSOFT WINDOWS XP
Windows XP is a line of operating systems produced by Microsoft for use on personal computers, including home and business desktops, notebook computers, and media centers. Windows XP is known for its improved stability and efficiency over the 9x versions of Microsoft Windows. It presents a significantly redesigned graphical user interface, a change Microsoft promoted as more user-friendly than previous versions of windows. The two major editions are Windows XP Professional contains advanced features that the average home user would not use. However, these features are not necessarily missing from XP home. Windows XP features a new task-based graphical user interface. The start menu and search capability were redesigned and many visual effects were added, including: A translucent blue selection rectangle in Explorer Drop shadows for icon labels on the desktop Task-based sidebars in Explorer windows(common tasks) The ability to group the taskbar of the buttons of the windows of one application into one button The ability to lock the taskbar and other toolbars to prevent accidental changes The highlighting of recently added programs on the Start menu Shadows under menus(Windows 2000 had shadows under mouse pointer, but not menus

2.SYSTEM ANALYSIS
The System study is for finding out what happens in the existing system, deciding what changes and new features are required and defining exactly what the proposed system must be. The process of this task is largely concerned with determining, developing and agreeing to the users requirements. System analysis can be defined as reduction of an entire system by studying operation performed and their relationship within system and examinationb of business activity with view to identify problem areas and records of alternative solutions. System analysis is general term that refers to a structure process for identifying and solving problems.analysis implies the process of breaking something down into its parts so that whole may be understood.

2.1 EXISTING SYSTEM

The scenario in most organization is that they make use of different applications for each of the departments to manage their activities. In the existing system the promotion of the Employee details are maintained in COBOL language, a single instruction command program.

Drawbacks of existing system We cant view the current execution process about the Products. The Existing system cannot provide flexible reports. It is not a portable one. All the instructions will be codes, so a new user cannot understand the program easily. The manpower required to enter the data and to maintain is very difficult.

2.2 PROPOSED SYSTEM

10

The main aim of the proposed system is to convert the entire existing project from COBOL to VB.NET with SQL server. And the system is used with Menu based operating system with flexible and user friendly for getting data as reports. So it provides better interface and an efficient access. Advantages of proposed system: The Process is good comparatively to the existing system. Easy to enhance requiring modifications in future. Report generation is easy and also we can take prints, if the user needs. The proposed system can be utilized for easy document in accessing various data carriers such as forms, records, reports etc. Easy to shift from source to destination.

2.3 ENVIRONMENTAL MODEL:

11 The Environmental model or the Context Analysis Diagram represents the major inputs, processing and outputs of the system. It has data flows, entities and only one process. It depicts the entire flow of the system. Based on CAD, the further diagrams are developed. The Context Analysis Diagram is shown in the figure2.3.1 it has entities like (enter your modules) which is the source of inputs for (project name) and output entities are (enter the modules).

CONTEXT ANALYSIS DIAGRAM 12

supplier

supplier details

purchase

purchase details

sales

sales details production planning system report

Report generated

stock

stock details

customer

customer details fig 2.3.1

2.4 BEHAVIOURAL MODEL

13 A Data Flow Diagram is a modeling tool that always picturing system

as a Network of functional process to one another by pipelines of data. It has the purpose of clarifying system requirements and identifying major transformations. The areas also widely used for representation of external and top-level design specification. It represents the logical flow of diagram. Data Flow diagram use number of symbols to represent systems. Most data flow modeling methods use four kinds of symbols to represent four kinds of system components. They are processes, data stores, data flows and external entities. Data flow diagrams are commonly used during problem analysis they are very useful in understanding a system and can be effectively used during analysis. A data flow diagram shows the flow of data through a system. It views a system as a function that transforms the inputs into desired outputs. The graphical representation of the system makes it a good communication tool between a user and analysis. A data flow diagram has the purpose of clarification system requirements and identifying major transformation that will become programs in system design. It consists of a series of bubbles represents data transformation and lines represent data flow in the system. Data flow diagram is also known as BUBBLE CHART. The rectangle indicates the source or destination, the open rectangle is the data store, the arrow indicates the data flow and the bubble shows the process that transforms incoming data flows into outgoing data flows... The DFD shown in fig 2.4.1 level-0 Fig.2.4.2 shows level-1 and Fig.2.4.3 shows level-2 DFD for generating report.

LEVEL-0

14

supplier

supplier details

purchase

purchase details

sales

sales details production planning system report

Report generated

stock

stock details

customer

customer details Fig 2.4.1

15 LEVEL-1: Admin

Customer

Customer details

Enquiry process customer data

Supplier Details supplier Supplier details process

supplier data

Stock Stock purchase details details Purchase

Informatio n process

purchase data Stock Details Sales details Informatio n process

sales

sales data

16

LEVEL-2:

supplier

supplier Details

purchase

purchase Details supplier data

sales

sales details production stock planning system Purchase Data Customer Data Production Report generated planning Reports

stock details

customer

customer

details

Fig 2.4.3

17

2.5 ENTITY RELATIONSHIP DIAGRAM:

Entity Relationship Diagram is a model that describes the stored data layout of a system at high level of abstraction. Entity Relationship Diagram enables us to examine and highlight data structures and relationship independent of the processes or control flow. The participation of the entities in the relationship and cardinality ratio are indicated in the Entity Relationship Diagram to provide further information. The Entity Relationship Diagram shows the relationships between the entities. The figure shows the entity relationship diagram.

18

ENTITY RELATIONSHIP DIAGRAM

user 1
Sup_id

Chec king pur

pun o

Purchase

Am

Qun

t
Upda te

Supna M Su_id
It _code

Itn a
Stock

Supplier M
Cu_ id It co

M Qu n am t

Sales am t Qu n

Cu _id

cun

a
Customer

M
cua cup

3. SYSTEM DESIGN
19

The most effective and challenging phase of the system life cycle is the system design. The term design describes a final system and the process by which it is developed. It refers to the technical specification that will be applied in implementing the candidate system. System phase has two phase of development; they are logical and physical design. Initial setup in the system design phase is to determine hoe the output is to be produced and in what format. Input data and master files have to be designed to meet the requirements of the proposed system. The main designing done here is Input design to show where the input was given. Next is Output design is to show where the output was revealed.

3.1 TABLE DESIGN

20

The table is the crucial components and is important for the successful performance of the system. The objective of the table design is to provide effective auxiliary storage and to contribute to the overall efficiency of the computer program component. The major database in master and transaction. The primary objectives are fast response time inquires, more information in low cost control of redundancy ,clarity and easy to use, accuracy and integrity of the system. The database is used continuously and is subjected to high-level updating. The table design of this project is shown below

21

Table design: Purchase Foreign key: Supid Field name Pno Supcode Supname Itemcode Itemname Quantity Amt Pdate bookingdate Data type Varchar Varchar Varchar Number Varchar Number Number Datetime Datetime Fig 3.1.1 Table name: Supplier Primary key: Supid Description Purchase number Supplier code Supplier name Item code Item name Quantity Amount Purchase date booking date

Field name Supcode Supname addr email Pno

Data type Varchar Varchar Varchar Varchar Number Fig 3.1.2

Description Supplier ID Suppier name Address Mailid Phone number

22 Table design: Sales

Foreign key: cusid

Field name Bno Cid Cname Addr Itemcode Itemname Iprice Sdate Quantity Amt

Data type Number Varchar Varchar Varchar Varchar Varchar Number Datetime Int Number Fig 3.1.3

Description Bill number Customer id Customer name Customer address Item code Item name Item price Sales date Quantity Amount

Table name: Stock Primary key: Itemcode Field name Itemcode Itemname Quantity Data type Varchar Varchar Int Fig 3.1.4 Description Item code Item Name Quantity

Table name: Customer Primary key: Cusid

23

Field name Cid cname Addr email

Data type Varchar Varchar Varchar Text

Description Customer ID Customer name Address Mail Id

Pno

Number Fig 3.1.5

Phone number

24

3.2 INPUT DESIGN:

Input design is the process of converting user-originated inputs to a computer-based format. Input design is one of the most expensive phases of the operation of computerized system and is often the major problem of a system. Input screens form the primary interfaces between the user and software.It clearly describes the users what type of data should be given. The input screens are designed in such a way that it has simple and user friendly layout.

In the project, the input design is made in various window forms with various methods. item details supplier details purchase details

FORM NAME: Login Form 25 DESCRIPTION: This form helps the user to login

Fig 3.2.1

FORM NAME: Main Form 26 DESCPRIPTION: This form is used to show options in main page

Fig 3.2.2

FORM NAME:supplier details 27 DESCRIPTION:This form shows the supplier details

Fig 3.2.3

FORM NAME: Purchase details. DESCRIPTION: This form shows the purchase details. 28

Fig 3.2.4

29

FORM NAME:Sales details. DESCRIPTION:This form shows the sales details

28

Fig 3.2.5

30 FORM NAME:Stock details. DESCRIPTION:This form shows the sales details.

Fig 3.2.6

FORMNAME:Customer details. DESCRIPTION:this form shows the customer details. 31

Fig 3.2.7

3.3 OUTPUT DESIGN:

32

Output design generally refers to the results and information that are generated by the system for many end-users; output is the main reason for developing the system and the basis on which they evaluate the usefulness of the application. In any system, the output design determines the input to be given to the application. The output should be designed around the requirements of the user.outputs from the computers are required primarly to communicate the result of processing to the and to provide a permanent copy of the results for the later communication. In the project, the output design is made in various window forms with various methods. View supplier View stock View sales reports

33 FORM NAME: Supplier Details DESCRIPTION: This Form is used to display the supplier report.

Fig 3.3.1

34

FORM NAME :Purchase Details DESCRIPTION:This Form is used to display the purchase report

Fig 3.3.2

35 FORM NAME: Sales Details DESCRIPTION: This Form is used to display the sales report

Fig 3.3.3

36

FORM NAME: Stock Details DESCRIPTION: This Form is used to display the stock report

Fig 3.3.4

37

FORMNAME: Customer Report DESCRIPTION: This Form used to display the customer report

Fig 3.3.5

38

4. SYSTEM TESTING AND IMPLEMENTATION 4.1 SYSTEM TESTING:

TESTING METHODOLOGIES: The term system testing can be used in a number of ways. in a general sense, the term system testing refers to the testing of the system in artificial condition to ensure that it should perform as expected and as required. From a system development perspective, system testing refers to the testing performed by the development team (the programmers and other technician) to ensure that the system works module by module (unit testing) and also as a whole. system testing should ensure that each function of the system works as expected and that any errors (bugs) are noted and analyzed. it should additionally ensure that interface for export and import routines, function as required. system testing does not concern itself with the functionality of the system and whether this is appropriate to meet the needs of the users. having met the criteria of the test plan the software may then be passed for user acceptance testing. the various testing methodologies performed for this system is: unit testing Integration Testing White Box Testing Black Box Testing

UNIT TESTING In computer programming, a unit test is a procedure used to validate that a particular module of source code is working properly. The idea about unit test is to write test cases for all functions and methods so that whenever a change causes a regression, it can be quickly identified and fixed. Ideally, each test case is separate from the others; constructs such as mock object can assist in separating unit tests. This type of testing is mostly done by the developers and not by end-users. 39

The goal of unit testing is to isolate each part of the program and show that the individual parts are correct. Unit testing provides a strict, written contract that the piece of code must satisfy. As a result, it affords several benefits. The goal of unit testing is to isolate each part of the program and show that the individual parts are correct. Unit testing provides a strict, written contract that the piece of code must satisfy. As a result, it affords several benefits and allowed to correct the following errors. 1. Mixed mode operations 2. Incorrect initialization 3. Incorrect symbolic representation of the expression 4. Simplified integration 5. Facilitated for the various changes made to the system INTEGRATION TESTING: Integration testing can proceed in a number of different ways, which can be broadly characterized as top down or bottom up. In top down integration testing the high level control routines is tested first, possibly with the middle level control structure present only as stubs. Subprogram stubs are incomplete subprograms which are only present to allow the higher level control routines to be tested. Top down testing can proceed in a depth-first or breadth-first manner. For depth-first integration each module is tested in increasing detail, replacing more and more levels of details with actual code rather than stubs. Alternatively breadth-first would proceed by refining all the modules at the same level of the control throughout the application. In practice a combination of the two techniques would be used. At the initial stage all the modules might be only partly functional, possibly being implemented only to deal with non-erroneous data. These would be tested in breadth-first manner, but over a period of time each would be replaced with successive refinements which were closer to the full functionality. This allows depth-first testing of a module to be performed simultaneously with breadth-first testing of all the modules. The other major category of integration testing is bottom up integration testing where an individual module is tested from a test harness. Once a set of individual 40

modules have been tested they are then combined into a collection of modules, know as builds, which are then by a second test harness. This process can continue until the build consists of the entire application. This second approach is used in this project where the individual modules that are-Mobile Call Status, Mobile Time Retrieval and Internet connectivity are first developed and then later they were integrated into one application and tested for the results. WHITE BOX TESTING: White box testing is testing from the inside--tests that go in and test actual program structure. Basis path testing: Very simply, test every statement in the program at least once. Youll note that the testing department at FCC chose test cases that did this; the entire execution tree was covered. Basis path testing is MANDATORY--so much so that there are software products written especially to assist in it. Profiling: there are a lot of tools--often included with compilers--which show where the CPU is spending most of its time in a program. Naturally, the busiest parts of the program are the ones you want to test most. Loop tests: Exercise each DO, WHILE, FOR and other repeating statements several times. Input tests: as the old saying goes-- garbage out, garbage out. If a procedure receives the wrong data, its not going to work. Each procedure should be tested to make certain that the procedure actually received the data you sent to it. This will spot type mismatches, bad pointers, and other such bugs. Here in this project each decision path is check and all the loops are executed separately to ensure that the program is logically correct and has exited right time

41

BLACK BOX TESTING: Black box testing, concrete box or functional testing is used in computer programming, software engineering and software testing to check that the outputs of a program, given certain inputs, conform to the functional specification of the program. The term black box indicates that the internal implementation of the program being executed is not examined by the tester. For this reason black box testing is not normally carried out by the programmer. In most real-world engineering firms, one group does design work while a separate group does the testing. Boundary value analysis is a technique of black box testing in which input values at the boundaries of the input domain are tested. it has been widely recognized that input values at the extreme ends of, and just outside of, input domains tend to the cause errors in system functionality. In boundary value analysis, value at and just beyond boundaries of the input domain are used to generate test cases to ensure proper functionality of the system. Advantages of Black Box Testing More effective on larger units of code than glass box testing Testing needs no knowledge of implementation, including specific programming language Tester and programmer are independent of each other Test are done from a users point of view Will help to expose any ambiguities or inconsistencies in the specifications Test cases can be designed as soon as the specifications are complete In this project all the function are tested to check whether all of them are working properly. The performance rate is verified by considering response time and speed. Hence the error are identified and corrected.

QUALITY ASSURANCE
42 Quality assurance comprises all those planned and systematic actions necessary to provide confidence that a structure, system or component will perform satisfactorily is service. Quality assurance includes formal view of care, problem definition, corrective actions to remedy any deficiencies and evaluation of actions that to be taken. The function of software quality that assures that the standards, processes, and procedures are appropriate for the project and are correctly implemented. This is an umbrella activity that is applied throughout the engineering process. Quality software is reasonably bug-free, delivered on time and within budget, meets requirements and/or expectations, and is maintainable. The system is developed such that it ensures all the level of quality. It checks whether a user friendly environment is provided to the users and that there is a reliable, accurate and efficient flow of data within the system. The system also checks that due it contains the level of security required for the user. Hence as long as there is no hardware complaint, there is no problem with the software.

43

4.2 SYSTEM IMPLEMENTATION:

PLAN: Implementation is the state in the project where the theoretical design is turned into a working system. The most crucial stage in achieving a new successful system and giving confidence on the new system for the users that will work efficiently and effectively. The system is implemented only after thorough testing is done and if it is found to work according to the specification. It involves careful planning, investigation of the current system and is constraints on implementation, design of methods to achieve changeover, and evaluation of the changeover methods apart from planning. Two major tasks for preparing the implementation are educating, training the users and testing the system. Implementation plan preparation The implementation process begins with the preparation of plan for implementation. According to this plan other activities are carried out. In this plan discussion has been made regarding the equipment, resources and how to test the activities. Thus a clear planner prepared for the activities. Equipment Acquisition According to the above plan the necessary equipment have to be acquired to implement the new system, which would include all the requirements for installing and maintaining .Net framework, VB.net, SQL server, Program code preparation One of the most important development activities is coding or programming. The system flowcharts and other charts are converted into modular programs. They have to be compiled, tested and debugged.

User training and documentation

44

Once the planning has been completed the major effort in the computer department is that the user department must consist of educated and trained staff as the system becomes more complex. The success of the system depends upon how they are operated and used the system. Thus the quality of training the personnel is connected to the success of the system. Implementation depends upon the right people being trained at the right time. Education involves creating the right atmosphere and motivating the user. Staff education should encourage the participation of all the staff. Changeover Changeover is the change of moving over from the old system to the new computerized system. In order that this is done all the files have to be converted to the new format. The accuracy of the conversion is of utmost importance both to user confidence in the system and to effective operation. When the files have been set up on the computer, the changeover can take place. There are several possible methods of doing this. E.g. direct changeover, parallel running, pilot running, and staged changeover. This method is the complete replacement of the old system by new, in one move. When direct changeover is planned, system tests and training should be comprehensive and changeover itself is planned in detail.

Parallel Running: new systems to cross check the results.

45

Parallel running or operation means processing current data by both the old and The old system is kept alive and operational until the system has been proved for at least one system cycle, using full live data in the operational environment of place, people,time. It allows the result of the new system to be compared with the old system before the acceptance by the user. Staged Changeover: A staged changeover involves a series of limited size direct changeovers. The new system being introduced piece by piece. A complete start, a logical section is committed to the new system while the remaining parts or sections will be processed by the old system. In this project, direct changeover is applied where the entire system is implemented directly after it has been developed.

5.CONCLUSION
For production unit, after getting this Required Raw Materials list for producing products, automatically the required raw materials will be released from the store. After production or products, the quality engineers passing the produced products to store for sales after the quality check. It is concluded that the application works well and satisfy the company as well as the company. The application is tested very well and errors are properly debugged. In this application the user can search item and date wise delivery. They can view their favorable supplier details. Material software offers an effective and easy way for managing export business. Provides comprehensive details about the item details, selling, supplier details all maintain in this application. SCOPE FOR FUTURE ENHANCEMENT: Every application has its own merits and demerits. The project has covered almost all the requirements. Further requirements and improvements can easily be done since the coding is mainly structured or modular in nature. Changing the existing modules or adding new modules can append improvements. Further enhancements can be made to the application, so that the future enhancement is we develop the application through website and useful manner than the present one.

46

BIBLIOGRAPHY
47 Award Elias .M, System Analysis and Design, Sunnel Galgotia Publishing, 2nd Edition, 1998. D.M. Dhamdhere, System Programming And Operating System, Tata McGraw-Hill Publishing Company, 2nd Edition, 1998. Elias Award. M, System Analysis and Design, McGraw-Hill Publications, 1991. Jesse Library, Dave Grundgeiger, Programming Visual Basic .Net, OReilly publications, 2nd edition,2003. Lowy,Programming .NET Components,o Relliy publications,first edition 2000. Richard Way mine and rick saw tell,Microsoft SQL server 2000,Macmillian computer publication 2001. Stephen R.Schach ,Software Engineering,Irwin publications,2 nd edition 1993. Thai, .NET Framework essential,ORelliy publications ,first edition,2000

WEBSITE REFERENCE
www.webmatrix.com www.sourcecode.com www.experts-exchange .com en.wikipedia.org www.softwareengineering.com www.softwareproject.org www.weebly.com www.domaincheck.co.uk www.stevesims.com www.fusionbot.com

 www.microsoft.com

48