Ans :

aThe Linear sequential model re waterfall model is appropriate for Tickets Reservation system. It suggest a systematic, sequential approach to software Develop that begins at the system level and progresses through analysis, design, Coding and testing and support. These steps can be applied in Ticket reservation system in the following manner :

Software requirement analysis : to understand the nature of the program to be Built, the software engineer must understand the information domain for the Software, as well as the required function, behavior, performance and interface.

In a Ticket reservation system, various requirements of the whole system are Viewed. It is determined what are the requirements of the system, who are the users of the system, what are various functions in the system etc. then ER – diagram, Data flow diagram etc are prepared.

Design : Software design is actually a multistep process that focuses on four distinct attributes of a program : data structure, software architecture, interface representations and procedural detail.

Code generation : The code generation the design into machine readable form. If design performed in a detailed manner, code generation can be accomplished mechanically.

Testing : Once the code has been generated, program testing begins. The testing process focuses on the logical internals of the software, ensuring that all statements have been tested and on the functional externals.

Support : Software will undoubtedly undergo change after it is delievered to the customer. Software supports reapplies each of the preceding phases to an exiting program rather than a new one.

The linear sequential model is appropriate for Tickets Reservation system as it follows all the steps necessary for the development of Ticket reservation system. In this system project planning can be made in advance and Ticket reservation system require comparatively less changes at later stage. Moreover in a Ticket reservation system most of the requirements can be stated in earlier stages. It provides templates for which method for analysis, design coding, testing and support can be placed. There is less need to make changes after the system is developed. Therefore waterfall model is appropriate for tickets reservation system.

Ans 1 (b) A collection of elements which are assembled to fulfill some defined purpose. Elements may be hardware or software components, organizational policies and procedures and operational processes.

Systems have properties which are emergent i.e. they only come to light when the parts are put together, they have structure and mechanisms for communication and control.

Important emergent properties of a system are :-

• Performance
• Reliability
• Safety
• Security
• Usability

1. Number of transitions contained in the state transition representation
2. Number of data object that move across the interface.
3. number of data element that input or output

As we were testing only one module so unit testing will be performed on the module.

White Box Testing fundas will be applied during modules testing like :-

1. Module interface test to check proper data in flaw and outflow like username and passport is properly accepted.
2. Local data structure which is common source of error.
3. Boundary conditions testing.
4. Independent path testing.

All error handling paths are tested

Ans 1 (d)

Risk management is the process of measuring or assessing risk and developing strategies to manage it. Strategies include transferring the risk to another party, avoiding the risk, reducing the negative effect of the risk, and accepting some or all of the consequences of a particular risk. Traditional risk management focuses on risks stemming from physical or legal causes (e.g. natural disasters or fires, accidents, death, and lawsuits). Financial risk management, on the other hand, focuses on risks that can be managed using traded financial instruments.

In ideal risk management a prioritization process is followed whereby the risks with the greatest loss and greatest probability of occurring are handled first, and risks with lower probability of occurrence and lower loss are handled later. In practice the process can be very difficult, and balancing between risks with a high p Risk management also faces difficulties allocating resources. This is the idea of opportunity cost. Resources spent on risk management could have been spent on more profitable activities. Again, ideal risk management minimizes spending while maximizing the reduction of the negative effects of risks.

Establish the context

Establishing the context involves

1. Panning the remainder of the process.
2. Mapping out the following the scope of the exercise, the identity and objectives of stakeholders, and the basis upon which risks will be evaluated.
3. Defining a framework for the process and an agenda for identification.
4. Developing an analysis of risk involved in the process.
   After establishing the context, the next step in the process of managing risk is to identify potential risks. Risks are about events that, when triggered, cause problems. Hence, risk identification can start with source of problems, or with problem itself.
5. Source analysis Risk sources may be internal or external to the system that is the target of risk management. Examples of risk sources are : stakeholders of a project, employees of a company or the weather over an airport.
6. Problem analysis Risk are related to identify threats. For example : the threat of losing money, the threat abuse of privacy information or the threat of accidents and casualties. The threats may exist with various entities, most important with shareholder, customers and legislative bodies such as the government.
7. Decide on the combination of methods to be used for each risk. Each risk management decision should be recorded and approved by the appropriate level of management . for example, a risk control implementation and responsible persons for those actions . the risk management concept is old but is still not very effectively measured.

Implementation

Follow all of the planned methods for mitigating the effect of the risks. Purchase insurance policies for the risks that have been decided to be transferred to an insurer, avoid al risks that have been decided to be transferred to an insurer, avoid all that can be avoided without sacrificing the entity’s goals, reduce others, and retain the rest.

Review and evaluation of the plan

Initial risk management plans will never be perfect. Practice, experience, and actual loss results will necessitate changes in the plan and contribute information to allow possible different decisions to be made in dealing with the risks being faced.

Risk analysis results and management plans should be updated periodically. There are two primary reasons for this :

1. to evaluate whether the previously selected security controls are still applicable and effective, and
2. to evaluate the possible risk level changes in the business environment. For example, information risks are a good example of rapidly changing business environment.

To properly adopt software Inspections practices, each participant is trained in the structured review process, defined roles of participants, system of process and product checklists, and forms and reports. The lost opportunity cost to acquire the knowledge, skills, and behaviors is twelve hours per practitioner. In addition, each manager is trained in the responsibilities for rolling out the technology and the interpretation and use of measurements taken. The management training is accomplished in four hours.

The cost of performing software Inspections includes the individual preparation effort of each participant before the session and the conduct effort of participants in the inspections session. Typically, 4-5 people participate and expend 1-2 hours of preparation and 1-2 hours of conduct each. This cost of 10 to 20 hours of total effort per session results in the early detection of 5- 10 defects in 250-5—lines of new development code or 1000-1500 lines of legacy.

Ans 1 (f) The knowledge of all tools required white making of project. Review of the project analysis before starting the project. Before starting the project. Before starting the making project software engineer should the person who is going to make is well aware that the all tools which required making the project. Cost estimated should be under the control. Time limitation should be there so that software will complete on time.

Ans :- 1 (g) Software Requirements :

1. Operating System.
2. Ms office
3. The required s/w which we make in platform the s/w

Hardware Requirement :

Inter P1v Dual core processor
Intel p 1 V Motherboard
Ram 512 MB
HDFD 80 GB
ATX Cabinet
Keyboard
Optical Mouse

Ans 1 (h) When components are being connected to create large components they have to pass through integration testing, whose main purpose is to detect any inconsistency between the connected components. Once the integration test is completed , a component test will have to be performed on the new component, consisting of several smaller ones. Some properties, however, can be said to belong to the system as a whole, like certain quality attributes. The system, beings a huge component, will hence be tested in its entirety to verify that these requirements are met in a satisfactory way, and this is what is referred to a system testing. Starting with unit testing, then moving on to integration testing before component testing can be performed. Finally, a system test is executed.

Black Box and White Box Testing

When a tester wants to test an application or a particular part of it to detect bugs, he can look at the system from a user’s perspective and expose it to different types of input, and then check whether or not the resulting output is in accordance with the specification. This is know as functional testing or black box testing. With this type of testing, any type of error can be detected, but it would take an infinite amount of time to do so.

Distinctions and elements of Web Applications
15 types of error and refers to memory leaks as a typical example of an error that will escape functional testing.

Web server
Browser
Client Database server
Application code
White box
Black box
Testing
Application data

Structural testing or white box testing, on the other hand, implies studying the program code and testing the different parts of it. This type of testing is not capable of finding all kinds of errors, but to its advantage it is easier to determine when you have tested enough

That white box testing is capable all lines of code when given an finite amount of time, but points out that such testing might not uncover errors with respect to component integration Seem to contradict each other. In spite of this, our interpretation suggests that both of them find a combination of white box and black box testing.

Ans 1 (i) Software Inspections are a disciplined engineering practice for detecting and correcting defects in software artifacts, and preventing their leakage into filed operations

Experienced software practitioners and managers understand that software development is a process of experimentation involving the continuous discovery of technical information associated with the function, form, and fit of the software product. Software Inspections are an integral practice in the process of experimentation.

Software inspections provide value in improving reliability, availability, and maintainability

Technical Detail

Software Inspections are strict and close examinations conducted on requirements, specifications, architectures, designs, code, test plan and procedures, and other artifacts. Leading software indicators of excellence for each artifact type provide the exit criteria for the activities of the software life cycle. For example, these indicators include completeness, correctness, style, rules of construction, and multiple views.

Completeness is based on traceability of the requirements to the code, essential for maintainability. Correctness is based on the clear specification of intended function and its faithful elaboration in code, essential for reliability and availability. Style is based on consistency of resorting, essential for maintainability. Rules of construction are based on the software application architecture and the specific protocols, templates, and conventions used to carry it out, essential for reliability and availability. Multiple views are based on the various perspectives and viewpoints required to be reflected in the software product, essential for maintainability. By detecting defects early and preventing their leakage into subsequent activities, the need for later detection and work (which is essential for reduced cycle time and lower cost ) is eliminated.

Software inspections are a reasoning activity performed by practitioners playing the defined roles of moderator, recorder, reviewer, reader, and producer. Each role carries with it the specific behaviors, skills, and knowledge needed to achieve the expert practice of Software Inspections.

The adoption of software Inspections practice is competency enhancing and meet little resistance among practitioners trained in their use. The adopting organization benefits by improved predictability in cost and schedule performance, reduced cost of development and maintenance, reduced defects, in the filed, increased customer satisfaction, and improved morale among practitioners.

Dependencies

In order for Software Inspections to be systematically used in statistical process control, there must be a life cycle model with defined software artifacts. In this context, software Inspections provide the exit criteria for each life cycle activity. Furthermore, the standard of excellence of leading indicators for each type of artifact must be specified and used in practice.