02-03-2013, 03:26 PM
Full Report on Air Ticketing System
[attachment=52446]
Theoretical Background
C is a programming language developed at AT & T’s Bell laboratories of USA in 1972. It was designed and written by a man named Dennis Ritchie. In the late seventies C began to replace the more familiar languages of that time like PL/I, ALGOL, etc. No one pushed C. It was not made the ‘official’ Bell Labs language. Thus, without any advertisement C’s reputation spread and its pool of users grew. Ritchie seems to have been rather surprised that so many programmer preferred C to older languages like FORTRAN or PL/I, or the newer ones like Pascal and APL.
Possibly why C seems so popular is because it is reliable, simple and easy to use . Moreover, in an industry where newer languages, tools and technologies emerge and vanish day in and day out, a language that has survived for more than 3 decades has to be really good.
Concepts used of C used in project
File handling: File handling is useful feature of C language. We use “File handling” to store the data permanently and retrieve the data when needed by the user . We use different function to work on a file such as fopen() to open a file and fwrite() function to write on a file.
TYPES OF MODELS
BUILD-AND-FIX MODEL
This is the most simple model of software development, and the product is constructed with minimal requirements, and generally no specifications nor any attempt at design
and testing is most often neglected. This is a representation of what is happening in many software development projects. This way of doing is not only a counter-example: it has its benefits in some situations.
CODE AND FIX
A simple and widely used software life cycle model. In build and fix models, as itself the name suggests, Repeat the following steps until the solution is good enough:
1. Code
2. Compile and execute
3. Detect errors
4. Fix
ADVANTAGE
* Cost efficient for very small projects of limited complexity.
DISADVANTAGES
* Unsatisfying approach for products of reasonable size.
* Cost is higher for larger projects.
* Product will not be delivered on time most of the times.
* Often results in a product of overall low quality.
* No documentation is produced.
* Maintenance can be extremely difficult without specification and design document.
WATERFALL MODEL
Waterfall approach was first Process Model to be introduced and followed widely in Software Engineering to ensure success of the project. In "The Waterfall" approach, the whole process of software development is divided into separate process phases. The phases in Waterfall model are: Requirement Specifications phase, Software Design, Implementation and Testing & Maintenance. All these phases are cascaded to each other so that second phase is started as and when defined set of goals are achieved for first phase and it is signed off, so the name "Waterfall Model". All the methods and processes undertaken in Waterfall Model are more visible.
REQUIREMENT ANALYSIS & DEFINITION
All possible requirements of the system to be developed are captured in this phase. Requirements are set of functionalities and constraints that the end-user (who will be using the system) expects from the system. The requirements are gathered from the end-user by consultation, these requirements are analyzed for their validity and the possibility of incorporating the requirements in the system to be development is also studied. Finally, a Requirement Specification document is created which serves the purpose of guideline for the next phase of the model.
SYSTEM & SOFTWARE DESIGN
Before a starting for actual coding, it is highly important to understand what we are going to create and what it should look like? The requirement specifications from first phase are studied in this phase and system design is prepared. System Design helps in specifying hardware and system requirements and also helps in defining overall system architecture. The system design specifications serve as input for the next phase of the model.
IMPLEMENTATION & UNIT TESTING
On receiving system design documents, the work is divided in modules/units and actual coding is started. The system is first developed in small programs called units, which are integrated in the next phase. Each unit is developed and tested for its functionality; this is referred to as Unit Testing. Unit testing mainly verifies if the modules/units meet their specifications.
INTEGRATION & SYSTEM TESTING
As specified above, the system is first divided in units which are developed and tested for their functionalities. These units are integrated into a complete system during Integration phase and tested to check if all modules/units coordinate between each other and the system as a whole behaves as per the specifications. After successfully testing the software, it is delivered to the customer.
PROTOTYPING MODEL
Prototyping is the process of building a model of a system. In terms of an information system, prototypes are employed to help system designers build an information system that intuitive and easy to manipulate for end users. Prototyping is an iterative process that is part of the analysis phase of the systems development life cycle.
During the requirements determination portion of the systems analysis phase, system analysts gather information about the organization's current procedures and business processes related the proposed information system. In addition, they study the current information system, if there is one, and conduct user interviews and collect documentation. This helps the analysts develop an initial set of system requirements.
SPIRAL MODEL
In order to overcome the cons of "The Waterfall Model", it was necessary to develop a new Software Development Model, which could help in ensuring the success of software project. One such model was developed which incorporated the common methodologies followed in "The Waterfall Model", but it also eliminated almost every possible/known risk factors from it. This model is referred as "The Spiral Model" or "Boehm’s Model".
There are four phases in the "Spiral Model" which are: Planning, Evaluation, Risk Analysis and Engineering. These four phases are iteratively followed one after other in order to eliminate all the problems, which were faced in "The Waterfall Model". Iterating the phases helps in understating the problems associated with a phase and dealing with those problems when the same phase is repeated next time, planning and developing strategies to be followed while iterating through the phases.
RISK ANALYSIS
Phase is the most important part of "Spiral Model". In this phase all possible (and available) alternatives, which can help in developing a cost effective project are analyzed and strategies are decided to use them. This phase has been added specially in order to identify and resolve all the possible risks in the project development. If risks indicate any kind of uncertainty in requirements, prototyping may be used to proceed with the available data and find out possible solution in order to deal with the potential changes in the requirements.
An Overview to system analysis
System analysis phase is considered one of the most important phases in the system development life cycle. System analysis is done in order to understand the problem, which the system is to solve. It is extremely important that the developers of the system study the existing system thoroughly otherwise it is impossible to satisfy the needs of the user. This study will enable the developers to know the intricacies of the existing system and bring out there hidden mysteries to the light so that they know exactly what to do and what not to do while building the system.
[attachment=52446]
Theoretical Background
C is a programming language developed at AT & T’s Bell laboratories of USA in 1972. It was designed and written by a man named Dennis Ritchie. In the late seventies C began to replace the more familiar languages of that time like PL/I, ALGOL, etc. No one pushed C. It was not made the ‘official’ Bell Labs language. Thus, without any advertisement C’s reputation spread and its pool of users grew. Ritchie seems to have been rather surprised that so many programmer preferred C to older languages like FORTRAN or PL/I, or the newer ones like Pascal and APL.
Possibly why C seems so popular is because it is reliable, simple and easy to use . Moreover, in an industry where newer languages, tools and technologies emerge and vanish day in and day out, a language that has survived for more than 3 decades has to be really good.
Concepts used of C used in project
File handling: File handling is useful feature of C language. We use “File handling” to store the data permanently and retrieve the data when needed by the user . We use different function to work on a file such as fopen() to open a file and fwrite() function to write on a file.
TYPES OF MODELS
BUILD-AND-FIX MODEL
This is the most simple model of software development, and the product is constructed with minimal requirements, and generally no specifications nor any attempt at design
and testing is most often neglected. This is a representation of what is happening in many software development projects. This way of doing is not only a counter-example: it has its benefits in some situations.
CODE AND FIX
A simple and widely used software life cycle model. In build and fix models, as itself the name suggests, Repeat the following steps until the solution is good enough:
1. Code
2. Compile and execute
3. Detect errors
4. Fix
ADVANTAGE
* Cost efficient for very small projects of limited complexity.
DISADVANTAGES
* Unsatisfying approach for products of reasonable size.
* Cost is higher for larger projects.
* Product will not be delivered on time most of the times.
* Often results in a product of overall low quality.
* No documentation is produced.
* Maintenance can be extremely difficult without specification and design document.
WATERFALL MODEL
Waterfall approach was first Process Model to be introduced and followed widely in Software Engineering to ensure success of the project. In "The Waterfall" approach, the whole process of software development is divided into separate process phases. The phases in Waterfall model are: Requirement Specifications phase, Software Design, Implementation and Testing & Maintenance. All these phases are cascaded to each other so that second phase is started as and when defined set of goals are achieved for first phase and it is signed off, so the name "Waterfall Model". All the methods and processes undertaken in Waterfall Model are more visible.
REQUIREMENT ANALYSIS & DEFINITION
All possible requirements of the system to be developed are captured in this phase. Requirements are set of functionalities and constraints that the end-user (who will be using the system) expects from the system. The requirements are gathered from the end-user by consultation, these requirements are analyzed for their validity and the possibility of incorporating the requirements in the system to be development is also studied. Finally, a Requirement Specification document is created which serves the purpose of guideline for the next phase of the model.
SYSTEM & SOFTWARE DESIGN
Before a starting for actual coding, it is highly important to understand what we are going to create and what it should look like? The requirement specifications from first phase are studied in this phase and system design is prepared. System Design helps in specifying hardware and system requirements and also helps in defining overall system architecture. The system design specifications serve as input for the next phase of the model.
IMPLEMENTATION & UNIT TESTING
On receiving system design documents, the work is divided in modules/units and actual coding is started. The system is first developed in small programs called units, which are integrated in the next phase. Each unit is developed and tested for its functionality; this is referred to as Unit Testing. Unit testing mainly verifies if the modules/units meet their specifications.
INTEGRATION & SYSTEM TESTING
As specified above, the system is first divided in units which are developed and tested for their functionalities. These units are integrated into a complete system during Integration phase and tested to check if all modules/units coordinate between each other and the system as a whole behaves as per the specifications. After successfully testing the software, it is delivered to the customer.
PROTOTYPING MODEL
Prototyping is the process of building a model of a system. In terms of an information system, prototypes are employed to help system designers build an information system that intuitive and easy to manipulate for end users. Prototyping is an iterative process that is part of the analysis phase of the systems development life cycle.
During the requirements determination portion of the systems analysis phase, system analysts gather information about the organization's current procedures and business processes related the proposed information system. In addition, they study the current information system, if there is one, and conduct user interviews and collect documentation. This helps the analysts develop an initial set of system requirements.
SPIRAL MODEL
In order to overcome the cons of "The Waterfall Model", it was necessary to develop a new Software Development Model, which could help in ensuring the success of software project. One such model was developed which incorporated the common methodologies followed in "The Waterfall Model", but it also eliminated almost every possible/known risk factors from it. This model is referred as "The Spiral Model" or "Boehm’s Model".
There are four phases in the "Spiral Model" which are: Planning, Evaluation, Risk Analysis and Engineering. These four phases are iteratively followed one after other in order to eliminate all the problems, which were faced in "The Waterfall Model". Iterating the phases helps in understating the problems associated with a phase and dealing with those problems when the same phase is repeated next time, planning and developing strategies to be followed while iterating through the phases.
RISK ANALYSIS
Phase is the most important part of "Spiral Model". In this phase all possible (and available) alternatives, which can help in developing a cost effective project are analyzed and strategies are decided to use them. This phase has been added specially in order to identify and resolve all the possible risks in the project development. If risks indicate any kind of uncertainty in requirements, prototyping may be used to proceed with the available data and find out possible solution in order to deal with the potential changes in the requirements.
An Overview to system analysis
System analysis phase is considered one of the most important phases in the system development life cycle. System analysis is done in order to understand the problem, which the system is to solve. It is extremely important that the developers of the system study the existing system thoroughly otherwise it is impossible to satisfy the needs of the user. This study will enable the developers to know the intricacies of the existing system and bring out there hidden mysteries to the light so that they know exactly what to do and what not to do while building the system.