Waterfall Model Lifecycle Model Information Technology Essay

drop deads influence Lifecycle mystify Information Technology turn upWaterf t discover ensemble greet was off wane signal Process Model to be introduced and followed astray in Softwargon Engineering to ensure success of the examine. In The Waterf either prelude, the whole turn of softw ar exploitation is change integrity into transgress surgery physical bodys.The manikins in Waterfall nonplus ar urgency specs soma, Softw atomic hail 18 normal, death penalty and Testing victuals. All these phases atomic number 18 cascaded to each other so that molybdenum phase is started as and when define set up of aspirations be obtaind for first phase and it is signed off, so the name Waterfall Model. All the method and suffice undertaken in Waterfall Model ar more visible.Waterfall Model lifecycle exerciseEPROGECTpicturewater fall role modeling.JPG paradigm 1. Waterfall Model lifecycle modelThe pointednesss of The Waterfall Model argonProblem translationI n this section, you give a misfortunate, normal description of the schemaTo be analyzed. This should contain a truly short description of theOrganization or the company for which the analytic thinking is to be through with(p) asWell the debates and advantages why the computerization is needed.The environment of the abridgment beingness d integrity is to come off clearly inThis sectionRequirement AnalysisAll practicable requirements of the remains to be developed atomic number 18 captured in this phase. Requirements are set of functionalities and constraints that the end- intentionr (who give be using the form) expects from the rangement. The requirements are gathered from the end- substance abuser by consultation, these requirements are analyzed for their validity and the possibility of incorporating the requirements in the system to be ontogeny is overly studied. Finally, a Requirement spec document is composed which serves the purpose of guidepost for the u ndermenti unrivaledd phase of the model. schema DesignBefore a starting for veridical coding, it is highly most-valuable to find 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 externalise is prepared. System Design helps in specifying computer hardware and system requirements and too helps in delimit overall system architecture. The system fancy specifications serve as input for the next phase of the model.TestingAs specified above, the system is first divided up in units which are developed and well-tried for their functionalities. These units are integrated into a complete system during Integration phase and tried and true to check if all modules/units coordinate amid each other and the system as a whole be suck ins as per the specifications. afterward successfully interrogatory the software, it is delivered to the customer execution of instrumentOn 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. distributively unit is developed and tested for its functionality this is referred to as Unit Testing. Unit interrogation mainly verifies if the modules/units meet their specifications.MaintenanceThis phase of The Waterfall Model is practically never ending phase (Very long). Generally, vexations with the system developed (which are non assemble during the emergence life cycle) come up after its practical use starts, so the issues related to the system are solved after deployment of the system. not all the problems come in picture directly but they find clock to clock time and demand to be solve hence this process is referred as Maintenance.Advantages of the falls modelThe advantage of waterfall maturation is that it allows for departmentalization and managerial hold back. A schedule send p acking be set with deadlines for each branch of development and a product can proceed through the development process like a car in a carwash, and theoretically, be delivered on time. study moves from concept, through design, enforceation, testing, installation, troubleshooting, and ends up at operation and maintenance. Each phase of development proceeds in strict order, without any coincide or iterative steps.Needless to mention, it is a one(a)-dimensional model and of lessons, linear models are the most simple to be implemented.The amount of re antecedents undeniable to implement this model is very minimal. unrivaled great advantage of the waterfall model is that documentation is produced at every step of the waterfall model development. This makes the appreciation of the product designing function simpler.After every major stage of software coding, testing is done to test the correct running of the code.PrototypingThrow-away earlytyping handbill or rapid Prototyping r efers to the creation of a model that will at last be discarded rather than becoming part of the finally delivered software. After preliminary requirements gathering is accomplished, a simple working model of the system is constructed to visually show the users what their requirements whitethorn look like when they are implemented into a finished system.CDocuments and SettingsNIFRASDesk slip by1.JPG visit 1.1 throw away proto typingIncremental PrototypingThe final product is built as separate ensamples. At the end the separate prototypes are being merged in an overall design. CDocuments and SettingsNIFRASDesktop3.JPGFigure 1.2 Incremental PrototypingEvolutionary PrototypingEvolutionary Prototyping (also cognise as breadboard prototyping) is quite different from Throwaway Prototyping. The main goal when using Evolutionary Prototyping is to build a very robust prototype in a structured manner and constantly refine it. The reason for this is that the Evolutionary prototype, when bui lt, forms the heart of the stark naked system, and the improvements and further requirements will be builtCDocuments and SettingsNIFRASDesktop2.JPGFigure 1.3 Evolutionary PrototypingAdvantages of prototypingProto types make an ideal tool for defending discussing user interactionUser can see to it a prototype off the beaten track(predicate) easier than most of the standard base of communicating requirements in the form of the model simulacrums very quickly resolve misunderstanding between biasness manager analysisDisadvantages of proto typingLeads to implementing and accordingly repairing way of construction systems.Practically, this methodology whitethorn increase the complexity of the system as scope of the system whitethorn expand beyond original designings.The Spiral ModelThe turbinate model, also known as the spiral lifecycle model, is a systems development method (SDM) utilize in information technology (IT). This model of development combines the features of the proto typing model and the waterfall model. The spiral model is intended for large, expensive, and complicated come outs.The steps in the spiral model can be general as followsThe new system requirements are define in as much exposit as possible. This generally involves hearinging a number of users representing all the out of doors or midland users and other aspects of the existing method.A preliminary design is created for the new system.A first prototype of the new system is constructed from the preliminary design. This is usually a scaled-down system, and represents an approximation of the characteristics of the final product.A second prototype is evolved by a fourfold procedure evaluating the first prototype in terms of its strengths, weaknesses, and seeks defining the requirements of the second prototype planning and designing the second prototype constructing and testing the second prototype.At the customers option, the entire plan can be aborted if the risk is deemed too grea t. Risk factors might involve development cost overruns, operating-cost miscalculation, or any other factor that could, in the customers judgment, result in a less-than-satisfactory final product.The existing prototype is evaluated in the same manner as was the previous prototype, and, if necessary, another prototype is developed from it according to the fourfold procedure outlined above.The preceding steps are iterated until the consumer is satisfy that the developedPrototype represents the finishing product desired.The final system is constructed, based on the refine prototype.Advantages of spiral modelThe spiral model is a realistic approach to the development of large-scalesoftware products because the software evolves as the process progresses.In addition, the developer and the client better understand and react to risksat each evolutionary level.The model uses prototyping as a risk reduction mechanism and allows forthe development of prototypes at any stage of the evolutionar ydevelopment.It maintains a systematic piecemeal approach, like the classic life cyclemodel, but incorporates it into an iterative mannequin that more reflect thereal world.Disadvantages of spiral model 1. Highly customized restricting re-usability 2. Applied differently for each application 3. Risk of not see cipher or schedule 4. Risk of not meeting bud know or scheduleCDocuments and SettingsAdministratorDesktopspiral model.pngFigure 1.4 spiral modelRapid Application Development (RAD) Methodology what is RAD?RAD (rapid application development) is a concept that products can be developed faster and of higher prime(a) throughGathering requirements using workshops or focus groupsPrototyping and early, reiterative user testing of designsThe re-use of software componentsA rigidly paced schedule that defers design improvements to the next product versionLess formality in re hitchs and other team communicationAdvantages of RADEarly visibilityGreater flexibility standardize look and feelIncreased user involvementBuying whitethorn save money compared to edificeDisadvantages of RADThis method may not be useful for large, unique or highly complex projectsThis method cannot be a success if the team is not sufficiently do and nor is unable to work cohesively together.Success depends on the extremely high technical foul skills of the developers. CDocuments and SettingsNIFRASDesktopproto type.jpgFigure 1.4 RAD modelDynamic System Development Method Dynamic System Development Method is another approach to system development, which, as the name suggests, develops the system dynamically. This methodology is independent of tools, in that it can be use with both structured analysis and design approach or object-oriented approach.Advantages of DSDAn importance on testing is so upstanding that at least one tester is expected to be on each project groupSets stakeholder expectations from the starts of the project that not all requirements will make it into the final delive rableHas specific approach to determining how important each requirements is to iterationDisadvantages of DSDAccess to material is controlled by a consortium, and fees may be charged just to access the grapheme material probably the most heavy weight project compared in this surveyCDocuments and SettingsAdministratorDesktopdynamic-system-development-method.jpgfigure1.2.1 DSD methodDuring the beneath given reasons I have elect Waterfall Model for this projectIt is a linear sequential modelIt is very simple model to implementEasy to useIt is the first model.It inevitably very some resources to implementSuitable for small projectsWater fall modelThis is very simple model. It moves like water fall from top to down of SDLC. The drawback of this model is in efficaciousness of substantiation andValidation activities.TASK 02The water fall modelEPROGECTpicturewater fall model.JPGThe water fall stagesProblem definitionRequirement analysisSystem designCoding testingImplementationMaintenan ce1. Problem definitionIn this section, you give a short, general description of the system to be analyzed. This should contain a very short description of the Organization or the company for which the analysis is to be done as Well the reasons and advantages why the computerization is needed.The environment of the analysis being done is to come out clearly in this section2. Requirement AnalysisAll 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.3. System DesignBefore a starting for a ctual coding, it is highly important to understand what we are going to create and what it should look like? The requirements specifications first phase are studied in this phase and system design is prepared. From System Design helps in specifying hardware and method requirements and also helps in defining overall system architecture. The system design specifications serve up as input for the next phase of the model.4. Coding TestingAs 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 customer5. ImplementationOn receiving system design documents, the work is divided in modules/units and actual coding is started. The system is first developed in small prog rams 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.6. MaintenanceThis phase of (The Waterfall Model) is in effect never finish phase (Very long). Commonly, difficulty with the system developed (which are not found during the development life cycle) come awake later than its practical use start, so the issues related to the system are solved after deployment of the system. Not all the problems come in images directly but they arise time to time and needs to be solve hence this process is referred as Maintenance.7. SpecificationSpecification is the first step in the process. In this stage, companies find a problem they want to join and think of a viable result. They then write down the solution on paper and move on to the next stage in the waterfall standardizationTesting includes verification and validation1. Verification argon we building the product recompense.2. Validation Are we building the dear product1. ValidationAm I building the right product?Determining if the method complies with the requirements. And perform functions for which it is intended and meets and is performed at the finish of the project.Am I accessing the right data (in terms of the entropy? Required to satisfy the requirement)High level bodily processPerforms after a work product is produced against Established criteria ensuring that the product integrates correctly into the environment.Determination of justness of the final software Product by a development project with respect to the user Needs and requirements.2. VerificationAm I building the product right?The review of lag work steps and interim Deliverables during a project to ensure them are Acceptable. To determine if the system is consistent, Adheres to standards, uses tested techniques and prudent Practices, and performs the selected functions in t he correct manner.Am I accessing the data right (in the right place in?The right way)Low level activityPerformed during development on key artifacts, like Walkthroughs, reviews and inspections, mentor feedback, Training, checklists and standards.My Opinion about This Task with Victoria HospitalThe Victoria Hopital has some problems.The foremost problem is the victoria Hospital at presnt does not use Computer and not asystem to save data and elaborate accommodation details, tolerant detail and wages detail.2nd problem is cant V.H take a details in time of important.That problam is some time May be loss detail in physical fils so the V.H is face these problems becaus we can analysis requirements to the V.H those are need to V.H a good system to save details datas secent is the method should preparednes easy good to hendal to the operaters.3rd problem is the executions should have to a good system.4this give a good intimacy to operates.these implementations are want to V.H th ose are A waiter Machine 5clients, 1GB Ram, or 512MB ,Laser newspaperwoman Dot matrix printer Bar code reader and the knowledge given by system supporters to Operater. Want to Operaters condect with system supporters and the system supporters mustiness mainten the problems of system in time ofcoming problems.TASK 03 entropy flow diagram entropy flow diagrams can be use to raise an intelligible representation of any business function. The system starts with an overall image of the business and continues by analyzing each of the functional battlegrounds of interest. This analysis can be carried out to precisely the level of detail required. The technique exploits a system called top-down expansion to conduct the analysis in a targeted way.CDocuments and SettingsAdministratorDesktopdfdg.JPGFigure 1.2.2 data flow diagramProcessProcesses show a renewal or manipulation of data flows at heart the system. The symbol used is a rectangular box which contains 3 descriptive elementsFirs tly an identification number appears in the upper left hand corner. This is allocated arbitrarily at the top level and serves as a unique reference.Secondly, a location appears to the right of the identifier and defines where in the system the process takes place. This may, for example, be a department or a piece of hardware. Finally, a descriptive title is placed in the centre of the box. This should be a simple imperative sentence with a specific verb, for example maintain customer records or find number one wood. entropy flowA data flow shows the flow of information from its source to its destination. A data flow is represented by a line, with arrow channels display the direction of flow. Information always flows to or from a process and may be written, verbal or electronic. Each data flow may be referenced by the processes or data stores at its head and tail, or by a description of its contents.External entityAn external entity is a source or destination of a data flow which is outside the area of study. Only those entities which originate or receive data are represented on a business process diagram. The symbol used is an oval containing a meaningful and unique identifier.Data storageA data store is a holding place for information within the systemIt is represented by an open ended narrow rectangle.Data stores may be long-term files such as sales ledgers, or may be short-term accumulations for example batches of documents that are waiting to be processed. Each data store should be given a reference followed by an arbitrary number.DFD context level diagram (0 level diagram)Emy project level df (1).jpgFigure 2.2.1 DFD context level diagramDFD 1st levelEPROGECTdrawing diagram dfdDrawing2.jpgFigure 2.3.1 DFD 1st levelEmy project level df (5).jpgFigure 2.3.2EPROGECTdrawing diagram dfdDrawing4.jpgFigure 2.3.3EPROGECTdrawing diagram dfdDrawing5.jpgCDocuments and SettingsALLAHDesktop level df (11).jpgEntity kin diagramCDocuments and SettingsAdministratorDesk topdfd4.JPGEntityA person, place, object events about which we need to compare store data are called as entitiesE.g. students, book, departmentRelational shipA birth captures how both or more entities are related to one another. Relationships can be thought of as verbs connectering two or more nouns. Relationships are represented as diamonds, connected by lines to each of the entities in the relationship.Relationship instance-link between entities (corresponds to primary key-foreign key equivalencies in related tables)Relationship type-category of relationshiplink between entity typesAttributesAttributes are the properties of entities relationship in other attributes is used to describe entities relationship in the ER diagram an entity has many an(prenominal) attributes there for it needs to identifier. A key is attributes, group of attributes which we can use to recognize an entity uniquely.Entity typesEmy projectpicturedd.jpgERD diagram for Victoria hospital systemDtt.JPG Appointment to enduringOne patient must have one appointment this is called one to one relationship and this is mandatoryOne appointment must have one patient this is called one to one relationship and this is mandatoryAppointment to GPOne GP have many appointments this is called one to many relationship and this is optionalOne appointment must have one GP this is called one to one relationship and this is mandatoryAppointment to guardOne nurse have many appointments this is called one to many relationship and this is optionalOne appointment have many nurse this is called one to many relationship and this is optionalAppointment to give-and-takeOne treatment have many appointments this is called one to many relationship and this is optionalOne appointment have many treatment this is called one to many relationship and this is optionalTreatment to clinicOne treatment have many clinic this is called one to many relationship and this is optionalOne clinic have many treatment this is called one to many relationship and this is optionalEmy project1235.jpgTASK 4Requirement specificationNORequirementsBSO 1BSO2BSO3BSO4BSO51Register patient2Invoice the patient3Inquiring handling4Accept patient ordering5printing debater tell6Medical laboratories7Arrange the delivery8 printing a patient reportBusiness system option (BSO)The set of Business System Options which is compiled so that a selection can be made. The selected Business System Option is a description of a chosen system development direction. The description documents the system boundary, inputs, outputs and the transformation taking place within the boundary. Essentially, the description is textual with supporting products such as Data Flow Diagrams, a Logical Data Structure and a take shape Practice Model skillful system option (TSO)The set of Technical System Options which has been developed so that the system development direction can be chosen.Each option documents the functions to be incorporated and deta ils implementation requirements. Each description is textual with some planning information. Functional elements are taken directly from the Requirements SpecificationLogical System SpecificationNOrequirementTSO1TSO2TSO3TSO4TSO51Visual basic 20072Windows 20033 coffee berry J2SE Development Kit (JDK) 5.04CCT camera5A Server Machine6Firefox 9.02 latest version75 clients,1GB Ram,80GB8SQL Server9Windows 200710Laser Printer11electronic scanner12Credit Card reader13JDBC 3.0 compliant driver14IIS Server15Dot matrix printer16Wi5 connection17Win 2003 server18Barcode reader19Credit card.TASK 5Fact-finding technique wondersQuestionnairesObservations consumeRecord-searchingFact-finding techniqueFact-finding is a main activity in system investigation. In this chapter, the functioning of the method is to be understood by the system analyst to design the proposed system. Different methods are used for this and these are known as fact-finding techniques. The analyst needs to fully understand the cu rrent system.The analyst wants data about the requirements and demands of the project undertaken and the technique employ to gather this records are identified as fact-finding techniques.Various kinds of techniques are used and the most popular with them are interviews, disbeliefnaires, record reviews, case tools and also the personal observations made by the analyst himself. Each of these techniques is additional dealt in next pages.Two people can go into the same area to gather facts and experience entirely different results. One spends weeks and gets incomplete and misdirect data. The other is finished in a few hours and has complete and unfluctuating facts. This session outlines some of the things a person can do to achieve the latter. It coversInterviewsInterviewing is the one of the most common method in fact finding. It encounter the analysisInto a direct contact with the users where he gets an opportunity to comprehend in to the opinion (advantage disadvantages) about the existing system also to identify the issues propose solutions the new systemInterview is a very effective fact finding techniques. But the main problem is that it requires a herd of resources, especially time. So it is very important to plan the interview in the first place hand the analysis is required to have considerable amount of skillsInterview needs a start from the top level management to get permission also get an overview idea about the total system. thusly the interview process can be move to which will provide more more specific detailsInterviews are not required to find out how exactly a system should work, but it needs to deter mine the needs of the users that we have to satisfy with a new system.The success of the interview depends upon the skills of the interviewer the preparation for the interview.Choose the person who is mostly stamp down for the interviewPreparation for the interviewSetting a proper date, and time ,venue the topicCorrect sequence of quest ionsThese factors should include in an interview plan before conducing it. There are 3 types of questions usually asked in an interviewOpen questionsClosed questionsProbes questionsOpen question general questions that relates with the personal view on the subjectExample- what do you think of .? What is your opinion of ? How could . be improved.AdvantagesPuts the interviewee at ease.Permits extra questioning into area that was not anticipated during interview scheduling. declare oneself detail.Disadvantagesinterview may get off the track (i.e. the interviewer lose control of the interview)can be time-consuming, particularly if the interviewer is experienceClosed question question that is needed direct answer