Waterfall Model Lifecycle Model Information Technology Essay

waterfall lay Lifecycle Model Information Technology EssayWaterfall approach was first Process Model to be introduced and followed widely in Softw atomic number 18 Engineering to ensure success of the project. In The Waterfall approach, the whole figure issue of softwargon harvest-time phylogeny is separate into separate process stagecoachs.The variants in Waterfall beat be Requirement conditions form, Software fig, Implementation and Testing Maintenance. All these stages are cascaded to each different so that second base phase is started as and when define set of goals are achieved for first phase and it is signed off, so the name Waterfall Model. All the mode and process under taken in Waterfall Model are more visible.Waterfall Model lifecycle good exampleEPROGECTpicturewater fall work.JPG habitus 1. Waterfall Model lifecycle sampleThe stages of The Waterfall Model areProblem renderingIn this section, you give a short, popular description of the carcassTo be analyzed. This should contain a precise short description of theOrganization or the caller-up for which the analysis is to be dvirtuoso asWell the reasons and advantages why the computerization is needed.The environment of the analysis being dvirtuoso is to tell apart out clearly inThis sectionRequirement AnalysisAll possible requirements of the dodge to be true are captured in this phase. Requirements are set of functionalities and constraints that the end-user (who will be victimisation 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 religious services the purpose of guideline for the next phase of the model.System DesignBefore a starting line for actual coding, it is highly important to picture what w e are going to create and what it should look like? The requirement specializedations 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.TestingAs specified above, the system is first divided in units which are essential 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. by and by successfully testing the software, it is delivered to the customerImplementationOn receiving system design documents, the work is divided in modules/units and actual coding is started. The system is first genuine in small programs called units, which are integrated in the next phase. Each u nit is developed and tested for its functionality this is referred to as Unit Testing. Unit testing generally verifies if the modules/units meet their specifications.MaintenanceThis phase of The Waterfall Model is practically never ending phase (Very long). Generally, problems with the system developed (which are non found during the development life cycle) come up after its practical use starts, so the issues tangency to the system are solved after deployment of the system. Not all the problems come in picture directly but they arise time to time and needs to be solve hence this process is referred as Maintenance.Advantages of the waterfall modelThe advantage of waterfall development is that it allows for departmentalization and managerial control. A plan crumb be set with deadlines for each stage of development and a output cigaret proceed through the development process like a car in a carwash, and theoretically, be delivered on time. Development moves from concept, throu gh design, implementation, testing, installation, troubleshooting, and ends up at operation and maintenance. Each phase of development proceeds in strict order, without any overlapping or iterative steps.Needless to mention, it is a linear model and of lessons, linear models are the almost simple to be implemented.The amount of resources required to implement this model is very minimal. whiz great advantage of the waterfall model is that documentation is produced at every step of the waterfall model development. This makes the understanding of the product designing procedure simpler.After every major stage of software coding, testing is d wholeness to test the correct running of the code.Proto typeThrow-away prototypingThrowaway or Rapid Prototyping refers to the creation of a model that will eventually be toss out rather than becoming part of the finally delivered software. After preliminary requirements gathering is accomplished, a simple working model of the system is construct ed to visually supply the users what their requirements whitethorn look like when they are implemented into a finished system.CDocuments and SettingsNIFRASDesktop1.JPGFigure 1.1 throw away proto typingIncremental PrototypingThe final product is built as separate models. At the end the separate prototypes are being merged in an overall design. CDocuments and SettingsNIFRASDesktop3.JPGFigure 1.2 Incremental Prototypingevolutionary PrototypingEvolutionary Prototyping (also known as breadboard prototyping) is quite different from Throwaway Prototyping. The main goal when using Evolutionary Prototyping is to build a very healthy prototype in a structured manner and constantly refine it. The reason for this is that the Evolutionary prototype, when built, forms the heart of the new 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 defe nding discussing user interactionUser plenty understand a prototype far easier than most of the standard base of communicating requirements in the form of the modelPrototypes very quickly resolve misunderstanding between biasness manager analysisDisadvantages of proto typingLeads to implementing and then repairing way of building systems.Practically, this methodology may increase the complexity of the system as scope of the system may expand beyond headmaster plans.The Spiral ModelThe spiral 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 prototyping model and the waterfall model. The spiral model is intended for large, expensive, and complicated projects.The steps in the spiral model can be general as followsThe new system requirements are define in as much detail as possible. This generally involves querying a number of users representing all the outside or internal 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 cost of its strengths, weaknesses, and risks 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 great. risk of exposure 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 refined 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 evolutionarydevelopment.It maintains a systematic piecemeal approach, like the classic life cyclemodel, but incorporates it into an iterative framework that more reflect thereal world.Disadvantages of spiral model 1. Highly customized limiting re-usability 2. employ differently for each application 3. Risk of not me eting budget or schedule 4. Risk of not meeting budget or scheduleCDocuments and SettingsAdministratorDesktopspiral model.pngFigure 1.4 spiral modelRapid Application Development (RAD) modeology what is RAD?RAD (rapid application development) is a concept that products can be developed faster and of higher quality throughGathering requirements using workshops or focus groupsPrototyping and early, reiterative user testing of designsThe re-use of software compvirtuosontsA smack paced schedule that defers design improvements to the next product versionLess formality in reviews and other team communicationAdvantages of RADEarly visibility great flexibilityStandardized look and feelIncreased user involvementBuying may save money compared to buildingDisadvantages 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 actuate and nor is unable to work cohesively together.Success depends on the extrem ely high technical 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 used with both structured analysis and design approach or object-oriented approach.Advantages of DSDAn importance on testing is so strong 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 deliverableHas 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 indite materialProbably the most heavy weight project compared in this surveyCDocuments and SettingsAdministratorDesktopdyn amic-system-development-method.jpgfigure1.2.1 DSD methodDuring the below given reasons I have chosen Waterfall Model for this projectIt is a linear sequential modelIt is very simple model to implementEasy to useIt is the first model.It needs very a few(prenominal) 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 ineffectualness of verification andValidation activities.TASK 02The water fall modelEPROGECTpicturewater fall model.JPGThe water fall stagesProblem definitionRequirement analysisSystem design cryptogram testingImplementationMaintenance1. 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 analysi s 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 actual 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 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.6. MaintenanceThis phase of (The Waterfall Model) is in effect never finish phase (Very long). C ommonly, 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 yoke 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 involves verification and validation1. Verification Are we building the product in good order.2. Validation Are we building the right 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 accessin g the right info (in terms of the Data? Required to satisfy the requirement)High level activityPerforms after a work product is produced against Established criteria ensuring that the product integrates correctly into the environment.Determination of correctness 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 interim work steps and interim Deliverables during a project to ensure them are Acceptable. To determine if the system is consistent, Adheres to standards, uses reliable proficiencys and prudent Practices, and performs the selected functions in the correct manner.Am I accessing the data right (in the right place in?The right way)Low level activityPerformed during development on diagnose artifacts, like Walkthroughs, reviews and inspections, mentor feedback, Training, checklists and standards.My Opinion about This Task with Victoria HospitalThe Victoria Hopital h as some problems.The 1st problem is the victoria Hospital at presnt does not use Computer and not asystem to save data and details Appointment details, persevering detail and payment 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 implementations should have to a good system.4this give a good knowledge to operates.these implementations are want to V.H those are A Server Machine 5clients, 1GB Ram, or 512MB ,Laser Printer power point 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 must mainten the problems of system in time ofcoming problems.TASK 03Data flo w drawData flow diagrams can be use to provide an understandable representation of any employment function. The system starts with an overall image of the business and continues by analyzing each of the functional areas 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 shimmy or manipulation of data flows at bottom the system. The attribute used is a rectangular box which contains 3 descriptive elementsFirstly an recognition 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 describes 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 reduce of the box. This should be a simple imperative sentence with a specific verb, for example maintain customer records or find driver.Data flowA data flow shows the flow of information from its source to its destination. A data flow is represented by a line, with arrowheads showing the direction of flow. Information forever 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 discretionary 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 family diagramCDocuments and SettingsAdministratorDesktopdfd4.JPGEntityA person, place, object events about which we need to compare store data are called as entitiesE.g. students, book, departmentRelational shipA kindred captures how two or more entities are related to one another. Relationships can be thought of as verbs linking two or more nouns. Relationships are represented as diamonds, conn ected 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 attributes there for it needs to identifier. A key is attributes, group of attributes which we can use to identify an entity uniquely.Entity typesEmy projectpicturedd.jpgERD diagram for Victoria hospital systemDtt.JPGAppointment to PatientOne patient must have one designation 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 calle d one to one relationship and this is mandatoryAppointment to nurseOne 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 treatmentOne 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 patient2 placard the patient3Inquiring handling4Accept patient ordering5printing debater report6Medical laboratories7Arrange the delivery8Printing 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 Work Practice ModelTechnical 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 details implementation requirements. Each description is textual with some planning information. Functional elements are taken directly from the Requirements SpecificationLogical System SpecificationNOrequirementTSO1TSO2TSO3TSO4TSO51Visual basic 20072Windows 20033Java J2SE Development getup (JDK) 5.04CCT camera5A Server Machine6Firefox 9.02 latest version75 clients,1GB Ram,80GB8SQL Serv er9Windows 200710Laser Printer11Scanner12Credit Card reader13JDBC 3.0 compliant driver14IIS Server15 besprinkle matrix printer16Wi5 connection17Win 2003 server18Barcode reader19Credit card.TASK 5investigatory technique hearingsQuestionnairesObservationsSamplingRecord-searchingFact-finding techniqueFact-finding is a main activity in system investigation. In this chapter, the functioning of the method is to be unsounded 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 current system.The analyst wants data about the requirements and demands of the project undertaken and the technique employed to gather this records are identified as fact-finding techniques.Various kinds of techniques are used and the most popular with them are discourses, enquirenaires, record reviews, case tools and also the personal observations made by the analyst himself. Each of thes e techniques is additional dealt in next pages. twain people can go into the same area to gather facts and experience entirely different results. One spends weeks and gets incomplete and misleading data. The other is finished in a few hours and has complete and solid 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 bring the analysisInto a direct contact with the users where he gets an opportunity to listen 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 lot of resources, especially time. So it is very important to plan the interview before 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. Then 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 dressing for the interview.Choose the person who is mostly appropriate for the interviewPreparation for the interviewSetting a proper date, and time ,venue the topicCorrect sequence of questionsThese 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.Provide 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