IGNOU MCA 3rd Semster Sofware Engineering Lab Record Solved MCSL 036Scribd Upload a Document Search Documents

Explore DocumentsBooks - FictionBooks - Non-fictionHealth & MedicineBrochures/CatalogsGovernment DocsHow-To Guides/ManualsMagazines/NewspapersRecipes/MenusSchool Work+ all categoriesFeaturedRecentPeopleAuthorsStudentsResearchersPublishersGovernment & NonprofitsBusinessesMusiciansArtists & DesignersTeachers+ all categoriesMost FollowedPopularAnkur Sharma AccountHomeMy DocumentsMy CollectionsMy ShelfView Public ProfileMessagesNotificationsSettingsHelpLog Out 1First Page Previous Page Next Page / 62 Sections SectionsSection 1 of 11 Session 1p. 1Session 2p. 2Session 3p. 5Session 4p. 26Session 5p. 39Session 6p. 43Session 7p. 49Session 8p. 52Session 9p. 58Session 10p. 61Zoom Out Zoom In Fullscreen Exit FullscreenSelect View Mode View ModeSlideshowScroll Readcast Add a Comment Embed & Share Reading should be social! Post a message on your social networks to let others know what you're reading. Select the sites below and start sharing.Link accountReadcast this DocumentReadcast Complete!Click 'send' to Readcast!edit preferencesSet your preferences for next time...Choose 'auto' to readcast without being prompted.Ankur SharmaLink accountAdvancedCancel Add a CommentSubmitshare:Characters: 400 Share & EmbedAdd to Collections Download this Document for FreeAuto-hide: on

Session 1Scope of the Railway Reservation SystemReservation Clerk is a person to create and Cancel Reservation by enteringLogin Password. Manager is a person who updates the Train Information byentering his own Password. The system can handle only reservation and traindetails efficiently and it doesnt contain other details about the railwayadministration. The main purpose of this system is Creating reservation Cancel reservation View reservation status View train schedule Generating reports Update train schedule Update reservation detailsThe Seats of Reservation cannot be more than the seats of Train at that date.This is a constraint that has to be followed by the Clerk when he creates theReservation. For that purpose he wants to check the seats remaining present in theTrain.The scope of this system in creating Reservation is that, from any RailwayStation we can Create Reservation, which is updated automatically in all thestations. Hence, there is no confusion to the Reservation Clerk in all the stations tocreate the Reservation. This can be possible by maintaining Global Database.Clerks present at different stations can access the global database and the clerkscan easily understand the remaining reservation seats. It provides the ability tocreate reservation from different places for a train.The system is so secured and clerk and manager utilize it. Nobody can ableto access the system without his or her permission because of providing loginfacility to the system. The password is in the form of cipher text by usingcryptography technology, so it cannot be hacked by any person. The globaldatabase can passes through network

in order to utilized by managers or clerks atdifferent places. So, we want to provide network security because of the data nothacked by the other persons when it is going through network cables. This network security is provided by the cryptography technology. Software EngineeringSession 2This session is to estimate the size, effort, schedule, and cost of the railwayreservation project.The four basic steps in Railway Reservation project estimation are:1.Estimate the size of the development product. This generally ends up ineither Lines of Code (LOC) or Function Points (FP), but there are other possible units of measure. A discussion of the pros & cons of each isdiscussed in some of the material referenced at the end of this report.2.Estimate the effort in person-months or person-hours.3.Estimate the schedule in calendar months.4.Estimate the project cost in dollars (or local currency)The railway reservation project requires 75KBLOC. On the basis of this size of the project we have to estimate the remaining estimations. We have the formula toestimate the schedule of the project.Schedule in months = 3.0 * (effort-months)1/3Opinions vary as to whether 2.0 or 2.5 or even 4.0 should be used in place of the 3.0 value - only by trying it out will you see what works for you.Of course, you must also keep in mind other important factors that affect theaccuracy of your estimates, such as:The accuracy of all the estimate s input data (the old adage, "Garbage in,Garbage out", holds true)The accuracy of any estimate calculations (e.g., converting betweenFunction Points and LOC has a certain margin of error)How closely the historical data or industry data used to calibrate the modelmatches the project you are estimatingThe predictability of your organization s software development process, andwhether or not the actual project was carefully planned; monitored andcontrolled, and no major surprises occurred that caused unexpected delays.2 Software EngineeringWhen they analyze the results, most people are startled by the consequencesof different tradeoffs. For example, the following tables provide 3 differentestimate options for a 75 KLOC project:The difference between the nominal schedule and the shortest schedule for the project is only a little over two months, but to achieve the shortest schedule the peak staff has to increase by almost 10 people and the cost increases by over $870,000! These results should cause someone to ask if a 2-month decrease in theschedule is worth the cost, and if 10 additional people can be found in time to helpachieve it. For some projects, a schedule decrease may be required at any cost; for others, it won t be.3 ShortestPossibleSchedule NominalscheduleCostTime IGNOU MCA 3rd Semster Sofware Engineering Lab Record Solved MCSL 036 Download this Document for FreePrintMobileCollectionsReport DocumentReport this document?Please tell us reason(s) for reporting this document Spam or junk Porn adult content Hateful or offensiveIf you are the copyright owner of this document and want to report it, please follow these directions to submit a copyright infringement notice.Report Cancel This is a private document. Info and Rating Reads:1,165Uploaded:01/17/2011Category:School Work>Study Guides, Notes, & QuizzesRated:Copyright:Attribution Non-commercialIGNOU MCA 3rd Semster Sofware Engineering Lab Record Solved MCSL 036 fajer007 Sectionsshow allcollapse prev next Session 1

Session 2 Session 3 Session 4 Session 5 Session 6 Session 7 Session 8 Session 9 Session 10 Share & Embed Related Documents PreviousNext p. p. p. p. p. p. p. p. p. p. p. p. p. p. More from this user PreviousNext62 p.57 p.22 p.57 p.17 p.74 p.33 p.13 p.40 p.49 p.38 p.27 p. Recent Readcasters Add a Comment Submitshare:Characters: 400 Print this documentHigh QualityOpen the downloaded document, and select print from the file menu (PDF reader required).Download and Print Add this document to your CollectionsThis is a private document, so it may only be added to private collections.+ Create a New CollectionName:Description:Collection Type:public - locked public - moderated privatepublic locked: only you can add to this collection, but others can view it public moderated: others can add to this collection, but you approve or reject additions private: only you can add to this collection, and only you will be able to view itSave collectionCancelFinished? Back to Document Upload a Document Search Documents Follow Us!scribd.com/scribdtwitter.com/scribdfacebook.com/scribdAboutPressBlogPartner sScribd 101Web StuffSupportFAQDevelopers / APIJobsTermsCopyrightPrivacyCopyright 2011 Scribd Inc.Language:English Choose the language in which you want to experience Scribd:EnglishEspaolPortugus (Brasil)