Software Development Contents:

y Introduction y Types of software y Software Development

- Process - Activity

y Software Development model y Advantages & Disadvantages

INTRODUCTION
Computer software is the collection of computer programs and related data that provide the instructions telling a computer what to do. Software refers to one or more computer programs and data held in the storage of the computer for some purposes. Program software performs the function of the program it implements, either by directly providing instructions to the computer hardware or by serving as input to another piece of software. The term was coined to contrast to the old term hardware. In contrast to hardware, software is intangible, meaning it "cannot be touched". Software is also sometimes used in a more narrow sense, meaning application software only. Sometimes the term includes data that has not traditionally been associated with computers, such as film, tapes, and records.

Software includes all the various forms and roles that digitally stored data may have and play in a computer regardless of whether the data is used

as code for a CPU, or other interpreter, or whether it represents other kinds of information. Software thus encompasses a wide array of products that may be developed using different techniques such as ordinary programming languages, scripting languages, microcode, or FPGA configuration. Computer software is so called to distinguish it from computer hardware, which encompasses the physical interconnections and devices required to store and execute the software. At the lowest level, executable code consists of machine language instructions specific to an individual processor. Programs are an ordered sequence of instructions for changing the state of the computer in a particular sequence. It is usually written in high-level programming languages that are easier and more efficient for humans to use than machine language. High-level languages are compiled or interpreted into machine language object code. Software may also be written in an assembly language, essentially, a mnemonic representation of a machine language using a natural language alphabet. Assembly language must be assembled into object code via an assembler.

TYPES OF SOFTWARE
1. System software
System software provides the basic function for computer usage, which can be divided into operating system and support system. Operating system is the most basic software. System software helps run the computer hardware and computer system. It includes a combination of the following:
   

device drivers operating systems servers utilities

window systems System software is responsible for managing variety of independent hardwares, so that they can work together harmoniously. For the system software, computer users and other softwares regard the computer as a whole and need not give concern on how every hardware works. The purpose of systems software is to unburden the applications programmer from the often complex details of the particular computer being used, including such accessories as communications devices, printers, device readers, displays and keyboards, and also to partition the computer's resources such as memory and processor time in a safe and stable manner.

2. Programming software
Programming software usually provides tools to assist a programmer in writing computer programs, and software using different

programming languages in a more convenient way. The tools include: compilers  debuggers  interpreters  linkers  text editors An Integrated development environment (IDE) is a single application that attempts to manage all these functions.


3. Application software
System software does not aim at a certain application fields. In contrast, different application software offers different function based on users and the area it served. Application software is developed for some certain purpose, which either can be a certain program or a collection of some programmes, such as a graphic browser or the data base management system. Application software allows end users

to accomplish one or more specific tasks. Typical applications include:

   

industrial automation business software video games quantum chemistry and solid state physics software telecommunications (i.e., the Internet and everything that flows on it)
databases educational software medical software molecular modeling software image editing spreadsheet simulation software Word processing Decision making software

        

SOFTWARE DEVELOPMENT
Software development is the development of a software product in planned and structured process. This software could be produced for a variety of purposes - the three most common

purposes are to meet specific needs of a specific client/business, to meet a perceived need of some set of potential users (the case with commercial and open source software), or for personal use (e.g. a scientist may write software to automate a mundane task). The term software development is often used to refer to the activity of computer programming, which is the process of writing and maintaining the source code, whereas the broader sense of the term includes all that is involved between the conception of the desired software through to the final manifestation of the software. Therefore, software development may include research, new development, modification, reuse, re-engineering, maintenance, or any other activities that result in software products.[3] For larger software systems, usually developed by a team of people, some form of process is typically followed to guide the stages of production of the software.

ACKNOWLEDGEMENT
I gratefully acknowledge the valuable guidance,intelligent suggestions,fruitful discussion and generous encouragement of For successful completion of this project. Without his help it would have been difficult to overcome the conceptual and practical problem. We are also thankful to all others who have directly or indirectly helped us to carry out this work Submitted by:-

PROCESS
A software development process is a structure imposed on the development of a software product. Similar terms include software life cycle and software process. There are several models for such processes, each describing approaches to a variety of tasks or activities that take place during the process. Some people consider a lifecycle model a more general term and a software development process a more specific term. For example, there are many specific software development processes that 'fit' the spiral lifecycle model.

Software development activities

a.Planning

The important task in creating a software product is extracting the requirements or requirements analysis. Customers typically have an abstract idea of what they want as an end result, but not what software should do. Incomplete, ambiguous, or even contradictory requirements are recognized by skilled and experienced software engineers at this point. Frequently demonstrating live code may help reduce the risk that the requirements are incorrect. Once the general requirements are gathered from the client, an analysis of the scope of the development should be determined and clearly stated. This is often called a scope document. Certain functionality may be out of scope of the project as a function of cost or as a result of unclear requirements at the start of development. If the development is done externally, this document can be considered a legal document so that if there are ever disputes, any ambiguity of what was promised to the client can be clarified. b.Implementation, testing and documenting

Implementation is the part of the process where software engineers actually program the code for the project. Software testing is an integral and important part of the software development process. This part of the process ensures that defects are recognized as early as possible. Documenting the internal design of software for the purpose of future maintenance and enhancement is done throughout development. This may also include the writing of an API, be it external or internal. It is very important to document everything in the project.
c.Deployment and maintenance

Deployment starts after the code is appropriately tested, is approved for release and sold or otherwise distributed into a production environment. Software Training and Support is important and a lot of developers fail to realize that. It would not matter how much time and planning a development team puts into creating software if

nobody in an organization ends up using it. People are often resistant to change and avoid venturing into an unfamiliar area, so as a part of the deployment phase, it is very important to have training classes for new clients of your software. Maintaining and enhancing software to cope with newly discovered problems or new requirements can take far more time than the initial development of the software. It may be necessary to add code that does not fit the original design to correct an unforeseen problem or it may be that a customer is requesting more functionality and code can be added to accommodate their requests. If the labor cost of the maintenance phase exceeds 25% of the prior-phases' labor cost, then it is likely that the overall quality of at least one prior phase is poor. In that case, management should consider the option of rebuilding the system before maintenance cost is out of control. Bug Tracking System tools are often deployed at this stage of the process to allow development teams to interface with

customer/field teams testing the software to identify any real or perceived issues. These software tools, both open source and commercially licensed, provide a customizable process to acquire, review, acknowledge, and respond to reported issues.

Software Development Models

Several models exist to streamline the development process. Each one has its pros and cons, and it's up to the development team to adopt the most appropriate one for the project. Sometimes a combination of the models may be more suitable. 1.Waterfall Model The waterfall model shows a process, where developers are to follow these phases in order: 1. Requirements specification (Requirements analysis) 2. Software Design 3. Integration 4. Testing (or Validation) 5. Deployment (or Installation) 6. Maintenance

In a strict Waterfall model, after each phase is finished, it proceeds to the next one. Reviews may occur before moving to the next phase which allows for the possibility of changes (which may involve a formal change control process). Reviews may also be employed to ensure that the phase is indeed complete; the phase completion criteria are often referred to as a "gate" that the project must pass through to move to the next phase. Waterfall

discourages revisiting and revising any prior phase once it's complete. This "inflexibility" in a pure Waterfall model has been a source of criticism by other more "flexible" models. 2.Spiral Model 1. The key characteristic of a Spiral model is risk management at regular stages in the development cycle. In 1988, Barry Boehm published a formal software system therefore, this model is often adapted to large-scale internal software development. 2. If the implementation of risk analysis will greatly affect the profits of the project, then risk analysis is meaningless, therefore, spiral model is only suitable for large-scale software projects. 3. Good software developers should look for possible risks, an accurate analysis of risk, otherwise it will lead to greater risk. First stage is to determine the stage of the goal of accomplishing these objectives, options and constraints, and then from the perspective of risk analysis program, development strategy, and strive to remove all potential risks, and

sometimes necessary to achieve through the construction of the prototype. If some risk can not be ruled out, the program to end immediately, or else start the development of the next steps. Finally, evaluation results of the stage, and the design of the next phase. development "spiral model", which combines some key aspect of the waterfall model and rapid prototyping methodologies, but provided emphasis in a key area many felt had been neglected by other methodologies: deliberate iterative risk analysis, particularly suited to large-scale complex systems. The Spiral is visualized as a process passing through some number of iterations, with the four quadrant diagram representative of the following activities: 1. formulate plans to: identify software targets, selected to implement the program, clarify the project development restrictions; 2. Risk analysis: an analytical assessment of selected programs, to consider how to identify and eliminate risk;

4. the implementation of the project: the implementation of software development and verification; Risk-driven spiral model, emphasizing the conditions of options and constraints in order to support software reuse, software quality can help as a special goal of integration into the product development. However, the spiral model has some restrictive conditions, as follows:
5. spiral

model emphasize risk analysis, but require customers to accept and believe that much of this analysis, and make the

relevant

response

is

not

easy,

Advantages and Disadvantages of software :

When software is developed, mostly from scratch or heavily customized or adapted, it has the following advantages and disadvantages:

Advantages:
y Provides exact requirements. y Meets user needs. y Only contains those features that are needed. y Contains little that needs parameterization or configuration. y Organization will have source code.

Disadvantages:
y May not meet user requirements because of poor analysis or design specifications. y Takes time to produce. y First generation software is usually immature. y May contain a fair amount of software defects - usual for newly developed software. y May be excessively costly. y Will generally require development of training and help material from scratch. y Untried software may have performance problems. y Untried software may have compatibility problems.

Certificate of surveyed institution This is to certify that Ms. Shraddha Upadhyay has visited our institution for her project work. During the project work her work and behavior was satisfactory.

Date: / / Place: ..

Signature: .. Name: .. Designation: ... Institute/Office: ...

Certificate of surveyed institution

This is to certify that Ms. Madhuri Sharma has visited our institution for her project work. During the project work her work and behavior was satisfactory.

Date: / / Place: ..

Signature: .. Name: .. Designation: ... Institute/Office: