City Guide Of Sitapur

                       Sitapur was established by the king Vikarmaditya after the name of Lord Ram's wife Sita. This place is concerned with ancient, medieval and modern history. This is a land of seer and sufis. Purans were written by Rishi Ved Vyas on this holi land. According to Hindu mythology the 'Panch Dham Yatra' journey of five main religious Hindu places will not be completed without visiting the Neemsar or Namisharanya,a religious ancient place in Sitapur. Dargah of Hazrat Makhdoom sb. at Khairabad and Hazrat Gulzar Shah are the symbols of communal harmony. The City is situated on the river bank of 'Sarayan', at Lucknow-Delhi National Highway No-24, 89 Km. from state capital Lucknow, and on meter gauge Railway line from Lucknow to Bareilly via Lakhimpur and Pilibhit. Sitapur is also connected on broad gauge train network connecting Gorakhpur and Delhi via Gonda,Burhwal bypassing Lucknow and Hardoi. Whole district is divided into six tehsils - Sitapur, Biswan, Mishrikh, Laharpur, Mahmoodabad and Sidhauli. There are 19 blocks, two parliamentary constituencies (Sitapur, Mishrikh (SC)) and nine assembly constituencies ( Behta, Biswan, Mahmoodabad, Sidhauli(SC), Laharpur, Sitapur, Hargaon(SC), Mishrikh and Machhrehta(SC)). Total population of the district is 36,19,661 and the area is 5743 Sq. Km.
          THere is a town named Mahmudabad In sitapur from 60 km away from the main city, is famous for its Fort of king Mahmudabad.

Software Development

Phases Of Software Development Project:-

                 A software development process consists of various phases, each phase ending with a defined output. The phases are performed is an order specified by the process model being followed. The main reason for having a phased process is that it breaks the problem of developing software into successfully performing a set of phases, each handling a different concern of software development. This insures that the cost of development is lower than what it would have been if the whole problem was tackled together. Thus, in order to manage the complexity, project tracking, and quality, all the development process consists of a set of phases. Various process models have been proposed for developing upon the problem.

Software development activity consists of the following activities:-

v  Requirement analysis and specification.

v  Design and specification

v  Coding

v  Testing

Requirement analysis and specification:-

            Requirement analysis is done in order to understand the problem of the software system is to solve. The problem could be automating and be existing manual process, developing a new automated system. The emphasis in requirements analysis in an identifying what is needed from the system, not how the system will achieve its goal. This fact is complicated by the fact that there are often at least two parties involved in software development a client and a developer.

            In most software project the requirement phases ends with a document describing all the requirements specification document. The person responsible for the requirement analysis is often called the analyst. 

Design and specification:-

            The purpose of design phase is to plan a solution of the problem specified by the requirement document. This phase is the first step in moving from the problem domain of the solution domain. The design of system is perhaps the most critical factor affecting the quality of the software it has a major impact on the later phases, particularly testing and maintenance. The output of this phase is the design document.

            The design activity is often divided into two separate phases-system design and detailed design. System design, which is sometimes also called top-level design, aims to identify the modules that should be in the, the specification of these modules and how they interact with each other to produce the desired results. During detailed design, the internal logic of each of the modules specified. The logic of a module is independent of the target language in which the software will eventually implement.

Coding:-        

            The goal of the coding phase is to translate the design of the system into code n a given programming language. The coding phase affects both testing and maintenance profoundly. Well written code can reduce the testing and maintenance effort. Because the testing and maintenance cost of software are much higher than the coding cost, the goal of coding should be to reduce the testing and maintenance effort. Hence during coding the focus should be on developing programs that are easy to read and understand, and not simply on developing programs that are easy to write. Simplicity and clarity should strived for during the coding phase.

Testing:-

            Testing is the major quality control measure used during software development. Its basic function is to detect errors in software. During requirements analysis and design, the output is a document that is usually textual and non-executable. After the coding phase computer programs are available that can be executed for testing purpose. This implies that testing not only has uncovered errors, introduced during coding but also errors introduced during the previous phases. Thus the goal of testing is to uncover requirement, design and coding errors in the programs. Consequently, different levels of testing are used.

            The starting point of testing is unit testing. In this a module is tested separately and is often performed by the code himself simultaneously along with the coding of the module. During integration of modules integration testing is performed to detect design errors by focusing on testing the interconnection between modules.

            Testing is an extremely critical and time consuming activity. It requires proper planning of the overall testing process. Frequently the testing process starts with a test plan that identifies all the testing related activities that must be performed and specifies the schedule, allocate the resource, and specifies guidelines for testing 

Latest Tablets, Laptops

              

Models Of software Engineering

Short notes:

ü The linear sequential model

ü The Rad model

ü The Prototyping model

ü The Incremental model

ü The Spiral model

ü The Component assembly model

ü The Concurrent development model

ü The Format method model.

 The linear sequential model

            The linear sequential model for software engineering sometimes called the “classic life cycle” or the “waterfall model” the linear sequential model suggests a systematic, sequential approach to software development that begins at the system level and progresses through analysis, design coding, testing and maintenance.

The RAD model:-

            The Rapid Application Development (RAD) is a linear sequential software development process model that emphasizes n external short development cycle. The RAD model is a “high speed” adoption of the linear sequential model in which rapid development is achieved by using a component based construction approach. If requirements are well understood and project scope is constrained the Rad process enables a development team to “create a fully functional system” within very short time periods. Used primarily for information systems applications.

The Prototyping model

            The goal of prototyping based development process is to counter the first limitations of the water fall model. The basic idea here is that instead of freezing the requirements before any designing or coding can proceed, a throw way prototype is build to help understand the requirements. This prototype development is based on the currently known requirements. Development of the prototype undergoes design, coding and testing. Ideally, the prototype serves as a mechanism for identify software requirements.

The Incremental model :-

The incremental model combines elements of the linear sequential model with the iterative philosophy of prototyping. The Incremental model applies linear sequences in a staggered fashion. Each linear sequence produces a deliverable “increment” of the software. The incremental model is like prototyping and other evolutionary approaches, is interactive in nature. But unlike prototyping, the incremental model focuses on the delivery of an operational product with each increment.

Incremental development is particularly useful when staffing is unavailable for a complete implementation by the business dealed that has been established for the project.

The Spiral Model:-

            The spiral model originally proposed by Boehm, is an evolutionary software process model that couples the interactive nature of the prototyping with the controlled and systematic aspects of the linear sequential model. It provides the potential for rapid development of incremental versions of the software. In the spiral model, software is developed in a series of incremental releases. During early iteration, the incremental release might be a paper or model or prototype. During later iterations, increasingly more complete versions of the engineered system are produced.

            The spiral model is divided in to a number of framework activities, also called task regions.

The Component assembly model:-

            The Component assembly model incorporates many of the characteristics of the spiral model. It is evolutionary in nature demanding the iterative approach to the creation of software. The engineering activity begins with the identification of candidate classes. This is accomplished by examining data that are to be manipulated by the application and the algorithm that will be applied to accomplish the manipulation. Corresponding data and algorithms are packaged into a class. Classes are components created in post software projects are stored in a class library or repository.

The Concurrent Development Model:-

            The Concurrent development model, sometimes called concurrent engineering. The concurrent process model can be schematically as a series of major technical activities, tasks and their associated states. The concurrent process model defines a series of events that will trigger transitions from state to state for each of the software engineering activities. The concurrent process model is often used as paradigm for the development of client / server application. A client/server system is composed of a functional component.

The Formal Methods Model:-

            The formal methods model encompasses a set of activities that lead to mathematical specification of computer software. Formal method enables a software engineer to specify, develop and verify a computer based system by applying a rigorous, mathematical notation. A variation on this approach, called clean room software engineering is currently applied by some software development organizations. When formal methods are used during development, they provide a mechanism for eliminating many of the problems that are difficult to overcome using other software engineering parading. When formal methods are used during design, they serve as a basis for program. Verification and therefore enable the software engineering to discover ad correct errors that might otherwise go undetected.