Software Engineering ppt

59,530 views
58,829 views

Published on

12 Comments
24 Likes
Statistics
Notes
  • Software Engineering (10th Edition) --- http://amzn.to/1RcLlti
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Beginning Software Engineering --- http://amzn.to/1ZgBfx0
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Soft Skills: The software developer's life manual --- http://amzn.to/1T3jnF2
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • yeh!! there z good knowledge in ur slides ,, can u pls tell me how to dowmload these ppt's . I need it within 24 hrs...Its urgent...pls help me
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • very good
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
59,530
On SlideShare
0
From Embeds
0
Number of Embeds
130
Actions
Shares
0
Downloads
2,103
Comments
12
Likes
24
Embeds 0
No embeds

No notes for slide

Software Engineering ppt

  1. 1. CASE STUDY ON SOFTWARE ENGINEERING TOPIC:ONLINE RAILWAY RESERVATION SYSTEM SUBMITTED BY: SHRUTI DHARMADHIKARI-06 TEJAL JADHAV-16 DEPARTMENT OF INFORMATION TECHNOLOGY V.G.VAZE COLLEGE OF SCIENCE MITHAGAR RD,MULUND(E) MUMBAI 400081 DATE OF SUBMISSION: 24 TH FEB’ 2010
  2. 2. WHAT IS SOFTWARE ENGINEERING? Software engineering is a layered technology. The bedrock that supports software engineering is a quality focus. The foundation for software engineering is the process layer. Software engineering process is the glue that holds the technology layers together and enables rational and timely development of the computer software. Software engineering methods provide the technical “how to’s” for building software. Methods encompass a broad array of tasks that include communication, requirements analysis, design , modeling, program construction, testing and support. Software engineering methods rely on a set of basic principles that govern each area of the technology and include modeling activities and other descriptive techniques.
  3. 3. INTRODUCTION TO THE RAILWAY RESERVATION SYSTEM: The Indian Railways (IR) carries about 5.5 lakhs passengers in reserved accomodation every day.The Computerised Passenger Reservation System(PRS) facilates the booking and cancellation of tickets from any of the 4000 terminals(i.e. PRS bookin window all over the countries). These tickets can be booked or cancelled for journeys commencin in any part of India and ending in any other part, with travel time as long as 72hours and distance upto several thousand kilometers. The project of PRS was launched on 15 th November 1985, over Northern Railway with the installation of Integrated Multiple Train Passenger Reservation System(IMPRESS), an online transaction processing system developed by Indian Railways in association with Computer Maintenance Corporation Ltd., at New Delhi. The objective was to provide reserved accomodations on any train from any counter,preparation of train charts and accounting of the money collected. The application was implemented in 1987 Mumbai,Chennai,Kolkata,Secunderabad subsequently.
  4. 4. RAILWAY RESERVATION METHODS: <ul><li>ONLINE BOOKING: With the help of this people can book their tickets online through internet, sitting in their home by a single click of mouse. Using their credit cards people can easily get their tickets done within minutes. There are certain charges for online booking as well. </li></ul><ul><li>COUNTER BOOKING: This is the oldest method of booking the tickets. The reservation counters are there at railway department from where people can get the tickets to their respective destinations. </li></ul>
  5. 5. <ul><li>Railway passengers frequently need to know about their ticket reservation status, ticket availability on a particular train or for a place,train arrival or departure details, special trains etc.. Customer information centers at the railway stations are unable to serve such queries at peak periods. </li></ul><ul><li>The number of the reservation counters available to the passengers and customers are very less. </li></ul><ul><li>On most of the reservation systems there are long queues, so it takes a long time for any individual to book the ticket. </li></ul><ul><li>As now there are no call centers facilities available to solve the queries of the passengers. </li></ul>PROBLEM DEFINITION:
  6. 6. ANALYSIS: <ul><li>I n Online Railway Reservation System,for booking the tickets online the intended user has to enter details like username and password. </li></ul><ul><li>Once the username and passwords are verified then he is allowed to enter the main system wherein he can select the destination, date and no of tickets. </li></ul><ul><li>For the purchase of the tickets he is asked for payment details (like credit card details etc). </li></ul><ul><li>The user is also provided with a provision of canceling the reservation where in the entire amount is credited back to his account. </li></ul><ul><li>The analysis part also comprises of the UML diagrams that boost the program. </li></ul>
  7. 7. SPIRAL MODEL DIAGRAM:
  8. 8. <ul><li>The spiral model, originally proposed by Boehm [BOE88], is an evolutionary software process model that couples the iterative nature of prototyping with the controlled and systematic aspects of the linear sequential model. </li></ul><ul><li>It provides the potential for rapid development of incremental versions of the software. Using the spiral model, software is developed in a series of incremental releases. </li></ul><ul><li>During early iterations, the incremental release might be a paper model or prototype. During later iterations,increasingly more complete versions of the engineered system are produced. </li></ul><ul><li>A spiral model is divided into a number of framework activities, also called task regions. Typically, there are between three and six task regions. </li></ul>THE SPIRAL MODEL:
  9. 9. Figure depicts a spiral model that contains six task regions: • Customer communication —tasks required to establish effective communication between developer and customer. • Planning —tasks required to define resources, timelines, and other projectrelated information. • Risk analysis —tasks required to assess both technical and management risks. • Engineering —tasks required to build one or more representations of the application. • Construction and release —tasks required to construct, test, install, and provide user support (e.g., documentation and training). When you encounter a difficult deadline that cannot be changed, the incremental model is a good paradigm to consider. 6 Figure depicts a spiral model that contains six task regions: • Customer communication —tasks required to establish effective communication between developer and customer. • Planning —tasks required to define resources, timelines, and other project related information. • Risk analysis —tasks required to assess both technical and management risks. • Engineering —tasks required to build one or more representations of the application. • Construction and release —tasks required to construct, test, install, and provide user support (e.g., documentation and training). • Customer evaluation —tasks required to obtain customer feedback based on evaluation of the software representations created during the engineering stage and implemented during the installation stage.
  10. 10. <ul><li>A spiral model is divided into a set of framework activities defined by software engineering terms. </li></ul><ul><li>As the evolutionary process begins, software team performs activities that are implied by a circuit around the spiral in a clockwise direction, beginning at the center. </li></ul><ul><li>The first circuit around the spiral might result in the development of a product specification; subsequent passes around the spiral might be used to develop a prototype and then progressively more sophisticated versions of software. </li></ul><ul><li>Unlike other process models that end when software is delivered, the spiral model can be adapted to apply throughout the life of the computer software. </li></ul>USE OF SPIRAL MODEL
  11. 11. <ul><li>Every new step is dependent on the previous step and moves spirally outwards. </li></ul><ul><li>At any point in the system we can return back to the previous step. </li></ul><ul><li>Because software evolves as the process progresses, both we and customers can better understand and react to the risks at evolutionary level. </li></ul><ul><li>In the case of errors we can easily trace the root cause of errors. </li></ul><ul><li>Spiral model is very realistic approach towards the process development. </li></ul>
  12. 12. CLASS DIAGRAM: class a private: int c, n, a, i, s; char id[50]; char pasw[50]; char date[10]; char d1[15], d2[15]; public: getLogin(); train();
  13. 13. USE CASE DIAGRAM: user Enter user id and password system verify password and user id Make a reservation Verify payments Update reservations cancellation of reservation administrator
  14. 14. : User : Administrator Log in Secure communication {verify user} :System SEQUENCE DIAGRAM: Enter date {verify date} Request confirmation Enter desired destination Choose desired express Enter the no of tickets Request confirmation Confirm purchase Place order {execute order} {verify funds}
  15. 15. Verify credit cards detail Debit account Settle transaction Send confirmation Close transaction Send invalid notice (success) (invalid) ACTIVITY DIAGRAM
  16. 16. Online reservation system Enter user id and password Make reservation Confirm reservation Make payments Cancellation of reservation invalid For cancellation exit STATE TRANSITION DIAGRAM
  17. 17. Transaction Process User website 0 LEVEL DFD DIAGRAM:
  18. 18. Online train reservation system Enter userid and password verify userid and password Enter no of tickets 1 LEVEL DFD DIAGRAM: Enter express name Check for the availability of date Make purchases Enter date
  19. 19. TESTING: <ul><li>Software testing is a critical element of software quality assurance and represents the ultimate review of specification, design, and code generation. </li></ul><ul><li>The types of the testing are as follows: </li></ul><ul><li>Unit testing </li></ul><ul><li>System testing </li></ul><ul><li>Validation testing and etc etc. </li></ul><ul><li>But however due to the time constraint we could not perform various types of testing. Hence we just applied alpha testing which is a part of validation test to our project. </li></ul>
  20. 20. CONCLUSIONS: <ul><li>Our project is only the gist of the online reservation system. </li></ul><ul><li>Due to time constraints it was not possible to incorporate all the concepts related to the topic. </li></ul><ul><li>So the program created is just an instance of the Original Online Railway Reservation System. </li></ul>
  21. 21. <ul><li>REFERENCES: </li></ul><ul><li>Programming with C++ by Balagurusamy. </li></ul><ul><li>Software Engineering, A Practitioner’s Approach, by Roger Pressman. </li></ul><ul><li>Object oriented modeling and design with UML by Michael Blaha and James Rumbaugh. </li></ul>

×