by Dinesh Thakur Category: Software Engineering

The software engineering deals with three basic types of entities – processes, project, and products. A software process is a method of developing software. A software project is a development project in which a software process is used. And software products are the outcomes of a software project.

 
by Dinesh Thakur Category: Software Engineering

A development process model specifies some activities that, according to the model, should be performed, and the order in which they should be performed. As stated earlier, for cost, quality, and project management reasons, development processes are generally phased.

 
by Dinesh Thakur Category: Software Engineering

The prototyping model is applied when detailed information related to input and output requirements of the system is not available. In this model, it is assumed that all the requirements may not be known at the start of the development of the system. It is usually used when a system does not exist or in case of a large and complex system where there is no manual process to determine the requirements. This model allows the users to interact and experiment with a working model of the system known as prototype. The prototype gives the user an actual feel of the system.



 
by Dinesh Thakur Category: Software Engineering

The activities in the management process for a project can be grouped broadly into three phases.

 
by Dinesh Thakur Category: Software Engineering

For effective project monitoring, the information coming from the development process to the management process should be objective and quantitative data about the project. Software matrices are quantifiable measures that could be used to measure different characteristics of a software system or the software development process.



 
by Dinesh Thakur Category: Software Engineering

Throughout development, software consists of a collection of items (such as programs, data and documents) that can easily be changed. During software development, the design, code, and even requirements are often changed, and the changes occur at any time during the development. This easily changeable nature of software and the fact that changes often take place require that changes be done in a controlled manner.

 
by Dinesh Thakur Category: Software Engineering

Developing methods that can produce high-quality software is another fundamental goal of software engineering. We can view quality of a software product as having three dimensions:

 
by Dinesh Thakur Category: Software Engineering

It is believed that only by improving the process can be quality & productivity be improved. Process improvement required understanding the current process & its deficiencies & then taking actions to remove the deficiencies. This is possible only if the current process is under statistical control.

 
by Dinesh Thakur Category: Software Engineering

Software requirement specification (SRS) is a document that completely describes what the proposed software should do without describing how software will do it. The basic goal of the requirement phase is to produce the SRS, Which describes the complete behavior of the proposed software. SRS is also helping the clients to understand their own needs.

 
by Dinesh Thakur Category: Software Engineering

Completeness of specifications is difficult to achieve and even more difficult to verify. Having guidelines about what different things an SRS should specify will help in completely specifying the requirements. Here we describe some of the system properties than an SRS should specify.

 
by Dinesh Thakur Category: Software Engineering

Pure object-oriented development requires that object-oriented techniques be used during the analysis, design, and implementation of the system. Various methods have been proposed for OOA and OOD, many of which propose a combined analysis and design technique.

 
by Dinesh Thakur Category: Software Engineering

The structured analysis technique uses function-based decomposition while modeling the problem. It focuses on the functions performed in the problem domain and the data consumed and produced by these functions.

 
by Dinesh Thakur Category: Software Engineering

The development of software starts with the requirements document, which is also used to determine eventually whether or not the delivered software system is acceptable. It is therefore important that the requirement specification contains no error and specifies the client's requirement correctly.

 
by Dinesh Thakur Category: Software Engineering

Because requirements specification are formally in people 's minds, requirements validation must necessarily involve the clients and the user. Requirement reviews, in which the SRS is carefully reviewed by a group of people including representative of the clients and the users, are the most common methods of validation.

 
by Dinesh Thakur Category: Software Engineering

Requirement reviews remain the most commonly used and viable means for requirement validation. However, there are other approaches that may be applicable for some system or parts of system or system that have been specified formally.

 
by Dinesh Thakur Category: Software Engineering

Function points are one of the most widely used measures of software size. The basis of function points is that the "functionality " of the system that is; what the system performs, is the measure of the system size. In function points, the system functionally is calculated in terms of the number of function it implements, the number of inputs, the number of output etc.

 
by Dinesh Thakur Category: Software Engineering

When tasks are defined and schedules are estimated, the planning effort has sufficient information to begin staffing plans and organizing a team into units to address the development problem. The comprehensive staffing plan identifies the required skills and schedules the right people to be brought onto the project at appropriate times and released from the project when their tasks are complete.



 
by Dinesh Thakur Category: Software Engineering

Termination analysis is performed when the development process is over. The basic reason for performing termination analysis is to provide information about the development process. Remember that a project is an instantiation of the process.



 
by Dinesh Thakur Category: Software Engineering

Design Reviews: The purpose of design reviews is to ensure that the design satisfies the requirements and is of “good quality.” If errors are made during the design process, they will ultimately reflect themselves in the code and the final system. Detecting errors in design is the aim of design reviews.

 
by Dinesh Thakur Category: Software Engineering

Any cost estimation model can be viewed as a function that outputs the cost estimate. The basic idea of having a model or procedure for cost estimation is that it reduces the problem of estimation of determining the value of he “key parameters” that characterize the project, based on which the cost can be estimated.

 

Page 5 of 7



About Dinesh Thakur

Dinesh ThakurDinesh Thakur holds an B.SC (Computer Science), MCSE, MCDBA, CCNA, CCNP, A+, SCJP certifications. Dinesh authors the hugely popular blog. Where he writes how-to guides around Computer fundamental , computer software, Computer programming, and web apps. For any type of query or something that you think is missing, please feel free to Contact us.