Rachiyta Book

Software Inspection:-  Inspection in software engineering refers to peer review of any work product by trained individual who looks for defect using a well defined process. An inspection is one of the most common sort of review practices found in software projects. The goal of the inspection is to identify defect. Commonly inspected works products include software requirements specification & test plan. In an inspection, a work product is selected for review the work product in an inspection the meeting by reading the work product & noting each defect.                                                                                                           ...

  Computer Added Software Engineering (CASE) It describe a broadest of label, saving tools used in software development. These create a framework for managing project and intended to help the users stay organized & improve productivity. There was more interest in the concept of CASE tools years ago, but let so today as the tools have different function of and in reaction to software development needs. The concept of CASE also received a heavy dose of critics after its heavy days. Features of CASE:- CASE tool, which are some times called integrated-CASE or ICASE. Tools cover all aspects of the software development life cycle which includes the writing code, implementation & maintenance.  The tools help in every aspect of the development work- Managing  Modules  Error checking Version control Designing  Diagramming tool Prototyping and other aspect associated with software engineering  Compling & testing tool are also consider parts of CASE tool s...

  Spiral Model:-  The spiral model is a risk driven software development process model. Based on unique risk patterns of given project, the spiral model guides a team to adopt elements of one more process model such as waterfall model or evolutionary prototype. This model was first described by “Barry Bohem” in is 1986 paper. The spiral is a sequence of waterfall increment. The spiral model for software engineering has been developed to couples the best feature of both the classical life cycle & prototype model in this model software is developed in series of incremental relies, Which may be paper model or prototype model. The spiral life cycle model is one of the most flexible SDLC model in place. Development can be determined by the project manager according to the complexity of the project. Project monitoring is very easy & effective. Each phase as well as each use require a review from concerned people this makes the model more transparent. Risk management is...

 Cohesion & Coupling Coupling:-  It is the measures of the degree of interdependence between modules a good software will have low coupling. Data Coupling:-  If the dependency between the modules is based on the fact that they communicate by passing only data. Than the modules are said to be data coupled. In this coupling the components are interdependence to each other through data, Stamp Coupling:-  In this coupling the complete data structure is passed from one to another module. There fore it involves tramp data. It may be necessary due to efficiency factor this choice made by the inside full designer, not a lazy program. Control Coupling:-  If the modules communicate by passing control information than they are said to be control couple. It can be bed if parameter indicates completely, Different behavior & good. If parameter allows factoring & reuse of functionality. External Coupling:-  In this the modules depends on other modules external...

Prototype Model:- The developer use the prototype model to refine the requirement & prepare the final specification documents. Because the working prototype has been evaluated by the customer, it is reasonable to expect that the resulting specification document will be correct. When the prototype model is created, it is reviewed by the customer the developers developed the prototype model to speed up the software development process. The prototype model is developed to improve the requirement in this prototype model if the users & clients are not satisfied than model will not stop. Different phases of prototype model:- Requirement:-  A prototype model begins with the requirement analysis & the requirements are defined in days. Quick Design:-  When requirements are known quick design for the system is created. It is not a detailed design & includes only the important expects of the system which gives an idea of the system to the user. A quick design helps in dev...

  Fourth Generation Of Techniques:- Software developers to represent the desired result in a manner that leads to automatic generation of code to create those result. Obesely a data structure with relevant information must exist & be readily accessible by the 4th GT. To transform the 4GT implementation into a product, the developer must conduct proof testing, developing, meaningful documentation & perform all the other solution integration activities that are required in other software engineering. In addition the 4GT developed software must be built in a manner that unable maintance to be perform. Advantage:- Simplify the programming process. Use natural language that impose no rigid grammatical rules.    Use non procedural language that users and programmers to specify the result they want, while the computer determine the sequence of introduction that will accomplish those results. Disadvantage:- Less flexible than other languages. Programs written in fourth ge...

Alpha Testing:-  It is done before the launch of the software products into the market. Alpha testing performed by the tester who are usually internal employee of the organization. It usually comes after system testing an involves both. White box testing & black box testing. The company employee test the software for functionality & gives the feedback. After this testing phase of any functions & features may be added to the software. Beta Testing:-  It is done at the time of the software product marketing. Bita testing is the second phase of software testing. In which sampling of the intended ordinance try the product out.  Beta testing is performed by the clients or end-users who are not the employee of the organizations. Beta testing is considered to be the last quality assurance (QA) step in the software testing & process.