..................................................................................................................................4 Waterfall Model Diagram .............................................................................................................5 Explanation of the Waterfall Model ..............................................................................................5 Phase I: Requirements................................................................................................................6 Phase II: Analysis .......................................................................................................................6 Phase III: Design.........................................................................................................................6 Phase IV: Coding ........................................................................................................................6 Phase V: Testing.........................................................................................................................6 Phase VI: Acceptance .................................................................................................................6 Agile Model...
Words: 3023 - Pages: 13
...model, each phase must be completed before the next phase can begin and there is no overlapping in the phases. The waterfall Model illustrates the software development process in a linear sequential flow; hence it is also referred to as a linear-sequential life cycle model. This means that any phase in the development process begins only if the previous phase is complete. In waterfall model phases do not overlap. Following is a diagrammatic representation of different phases of waterfall model. . Phase I: Requirements The first phase involves understanding what you need to design and what is its function, purpose etc. Unless you know what you want to design, you cannot proceed with the project. Even a small code such as adding two integer numbers, needs to be written with the output in mind. Here, in this stage, the requirements which the software is going to satisfy are listed and detailed. These requirements are then presented to the team of programmers. If this phase is completed successfully, it ensures a smooth working of the remaining phases, as the programmer is not burdened to make changes at later stages because of changes in requirements. Phase II: Analysis As per the requirements, the software and hardware needed for the proper completion of the project is analyzed in this phase. Right from deciding which computer language should be used for designing the software, to the database system that can be used for the smooth functioning of the software, such features...
Words: 685 - Pages: 3
...Introduction Organizations must learn how to build and implement systems to remain competitive. Software that is built correctly can support agile organizations and can transform as the organization and its business transforms. Software that effectively meets client’s needs will help an organization become more productive and enhance decision making. Software that does not meet client’s needs may have a damaging effect on productivity and can even cause a business to fail. Employee involvement along with using the right implementation methodology when developing software is critical to the success of an organization History The Systems Life Cycle (SLC) is a type of methodology used to describe the process for building information systems, intended to develop information systems in a very deliberate, structured and methodical way , reiterating each stage of the life cycle. The systems development life cycle, according to Elliott & Strachan & Radford (2004), " originated in the 1960s, to develop large scale functional business systems in an age of large scale business conglomerates. Information systems activities revolved around heavy data processing and number crunching routines" . Several systems development frameworks have been partly based on SDLC, such as the Structured Systems Analysis and Design Method (SSADM) produced for the UK government Office of Government Commerce in the 1980s.Eversince, according to Elliott (2004), " the traditional...
Words: 1541 - Pages: 7
...information systems from planning and analysis through implementation and maintenance. The SDLC is the foundation for all systems development methodologies and there are literally hundreds of different activities associated with each phase in the SDLC. Typical activities include determining budgets, gathering system requirements, and writing detailed user documentation. The activities performed during each systems development project will vary. The SDLC begins with a business need, followed by an assessment of the functions a system must have to satisfy the need, and ends when the benefits of the system no longer outweigh its maintenance costs. This is why it is referred to as a ‘lifecycle’. The SDLC is comprised of seven distinct phases: planning, analysis, design, development, testing, implementation, and maintenance. This section takes a detailed look at a few of the more common activities performed during the phases of the systems development life cycle along with common issues facing software development projects (see Figure D.1 and Figure D.2 ). Phase 1: Planning The planning phase involves establishing a high-level plan of the intended project and determining project goals. Planning is the first and most critical phase of any systems development effort an organization undertakes, regardless of whether the effort is to develop a system that allows customers to order products over the Internet, determine the best logistical structure for warehouses around...
Words: 1437 - Pages: 6
...Configuration management? Software configuration management encompasses the disciplines and techniques of initiating, evaluating, and controlling change to software products during and after the development process. It emphasizes the importance of configuration control in managing software production. Configuration management is an integral part of the software development process across all phases of the life cycle. It functions as a controlling discipline, enabling changes to be made to existing documentation and products in such a way as not to destroy the integrity of the software. Since configuration management extends over the life of the product, and since tools, techniques, and standards exist solely aimed at its proper execution, configuration management can stand alone as a module within a graduate curriculum. > Q. 2: What are the Requirements for the Success of Configuration Management? The key requirement for success of configuration management is the commitment of all levels of management to enforcing its use throughout the project lifetime. Configuration management, like other parts of software engineering perceived as being tedious, may require some coercion for success. A further requirement is the availability of a clearly stated configuration management plan. > Q. 3: How can we say that Configuration Management is a Cost Saving Tool? By helping to maintain product integrity, configuration management reduces overall software development costs. Cost...
Words: 10058 - Pages: 41
...SOFTWARE DEVELOPMENT: 1. Introduction Computers are becoming a key element in our daily lives. Slowly and surely they are taking over many of the functions that effect our lives critically. They are now controlling all forms of monetary transactions, manufacturing, transportation, communication, defence systems, process control systems, and so on. In the near future, they will be found in our homes, controlling all forms of appliances. Left to themselves, they are harmless pieces of hardware. Load the right kind of software, they can take you to the moon, both literally and figuratively. It is the software that gives life to them.When they are going to play such a crucial role, one small flaw either in the hardware or the software can lead to catastrophic consequences. The sad part is, while there are well defined processes based on theoretical foundations to ensure the reliability of the hardware, same thing can not be said about software. There is no theory for software devlopment as yet. But at the same time, it is mandatory that software always behaves in a predictable manner, even in unforeseen circumstances. Hence there is a need to control its development through a well defined and systematic process. The old fashioned 'code & test' approach will not do any more. It may be good enough for 'toy' problems, but in real life, software is expected to solve enormously complex problems. Some of the aspects of real life software projects are: Team effort: Any large...
Words: 3162 - Pages: 13
...I read and went through all the personnel files to access the software team skill level in each phase of the software developmental process. I created an Excel spreadsheet of each developer’s strengths and weakness. The role of the project manager is to understand and assign members of team to what their strengths are in software development process. Additionally, I used the IDE and J Unit automated testing tool because there was no capital required to purchase the tool which cost zero dollars to use. The first phase of the SDLC in the Water Fall model is requirement of gathering all the information; I assigned the task of gathering the information to Anita, Andre, Calvin and Pedro. The clock had twenty ticks, the requirement specification document was about seven percent completed. The other employees Roger, Mimi and Emily were tasked with reviewing the SRS document. The SRS document was fourteen percent complete after 20 clock ticks. The reviewers were staring to encounter several errors in the documents. The process of gathering was becoming slow and too cumbersome. I decided to purchase requirements capture tool for $10,000 dollars. After twenty clock ticks, twenty-five of SRS using the requirements capture tool this increased the efficiency by fifty percent. I decided to start the design phase with allocated capital expenditure of $5,000 on the design environment. Emily was assigned to the design phase of the project because she is an experienced design analyst along...
Words: 742 - Pages: 3
...Software Testing What is testing? Testing is the process of evaluating a system or its component(s) with the intent to find that whether it satisfies the specified requirements or not. This activity results in the actual, expected and difference between their results. In simple words testing is executing a system in order to identify any gaps, errors or missing requirements in contrary to the actual desire or requirements. Who does testing? It depends on the process and the associated stakeholders of the project(s). In the IT industry, large companies have a team with responsibilities to evaluate the developed software in the context of the given requirements. Moreover, developers also conduct testing which is called Unit Testing. In most cases, following professionals are involved in testing of a system within their respective capacities: Software Tester Software Developer Project Lead/Manager End User When to Start Testing? An early start to testing reduces the cost, time to rework and error free software that is delivered to the client. However in Software Development Life Cycle (SDLC) testing can be started from the Requirements Gathering phase and lasts till the deployment of the software. However it also depends on the development model that is being used. For example in Water fall model formal testing is conducted in the Testing phase, but in incremental model, testing is performed at the end of every increment/iteration and at the end the whole application is tested. Testing...
Words: 6175 - Pages: 25
...advantageous in the current dynamic business environment. The report also occurs Lean software development, what it is and the common areas that it has with Agile development. How using both the methods can result in even faster delivery of product to the customer and help reduce costs incurred during defect detection and correction, identification of common error categories and giving developers more responsibility increases better quality code and building of knowledge base. Table of Contents Executive Summary......................................................................................................................................1 Introduction...................................................................................................................................................1 Problem Identification...................................................................................................................................1 Agile development Technique.......................................................................................................................1 Various Agile Methods..................................................................................................................................2 Development Model Comparission: Waterfall vs Agile.................................................................................5 Lean Software...
Words: 3791 - Pages: 16
...[pic] Quality Assurance Plan For WAN Solutions Date: 5/26/2012 Revision Sheet |Release No. |Date |Revision Description | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |[pic] | | | ...
Words: 5473 - Pages: 22
...user/customer needs and expectations. * Software Quality the totality of functionality and features of a software product that bear on its ability to satisfy stated or implied needs. | 2) What are STLC phases? * Software Testing Life Cycle defines the steps/stages/phases in testing of software. However, there is no fixed standard of STLC in the world and it basically varies. | * Requirements/Design Review | * Review the software requirements/design * Review Defect Reports | * Test Planning | * Gather a general idea of what needs to be tested, and plan for the tests. * Test plan * Test Estimation * Test Schedule | * Test Designing | * You design/detail your test on the basis of detailed requirements/design of the software. * Test Cases/ Test Scripts/ Test Data * Requirements Traceability Matrix | * Test Environment Setup | * You setup the test environment (server/client/network,) with the goal of replicating the end-users’ environment. | * Test Execution | * You execute your Test Cases/Scripts in the Test Environment to see whether they pass. * Test Results (Incremental) * Defect Reports | * Test Reporting | * You prepare various reports for various stakeholders. * Test Results * Test/Defect Metrics * Test closure Report | 3) Name the main Task of each STLC phase. * Software Testing Life Cycle defines the steps/stages/phases in testing of software. However, there is no fixed standard of...
Words: 3598 - Pages: 15
...Waterfall Software Development Life Cycle Model The simplest software development life cycle model is the waterfall model, which states that the phases are organized in a linear order. A project begins with feasibility analysis. On the successful demonstration of the feasibility analysis, the requirements analysis and project planning begins. The design starts after the requirements analysis is done. And coding begins after the design is done. Once the programming is completed, the code is integrated and testing is done. On succeeful completion of testing, the system is installed. After this the regular operation and maintenance of the system takes place. The following figure demonstrates the steps involved in waterfall life cycle model. The Waterfall Software Life Cycle Model With the waterfall model, the activities performed in a software development project are requirements analysis, project planning, system design, detailed design, coding and unit testing, system integration and testing. Linear ordering of activities has some important consequences. First, to clearly identify the end of a phase and beginning of the others. Some certification mechanism has to be employed at the end of each phase. This is usually done by some verification and validation. Validation means confirming the output of a phase is consistent with its input (which is the output of the previous phase) and that the output of the phase is consistent with overall requirements of the system. The...
Words: 2323 - Pages: 10
...Frequent Shopper Program | Part 1 | | Jason J. Kral BSA/385 December 9, 2013 Andrew Carpenter Development Methodologies A development methodology is the framework that a developer or team uses to structure, plan, and control the process of developing a system or application. There is a wide variety of methodologies to choose from, each with its own strengths and weaknesses. Two of the more common and most used methodologies are the Waterfall method, and the agile method. This paper will focus on these two methods giving detailed descriptions, as well as advantages and disadvantages. Testing for each method will also be covered. The Waterfall Method The Waterfall Method of development is a linear-sequential life cycle model. This method is very simple to use and understand. In this model, each phase needs to be completed before the next phase can begin, phases cannot overlap, and once you finish a phase you cannot go back. A good example of this process is a literal waterfall flowing down the side of a mountain. "Once the water begins to flow over the mountain, it will hit each rock and continue down. The water can never go in the opposite direction." (Rouse, 2007) This is displayed in the following chart: The waterfall method allows for departmentalization and easy managerial control. "A schedule can be set with deadlines for each stage of development and a product can proceed through the development process like a car in a carwash, and theoretically...
Words: 1169 - Pages: 5
...Information System Development. Information system is a collection of hardware, software, and procedures work together to produce Quality Information. Information system MUST meet the requirements of the SYSTEM USER. SYSTEM DEVELOPMENT is a set of activities that you need to develop an INFORMATION SYSTEM. There are many types of information systems; Ø Office information system; is an information system that lets employees perform tasks electronically using computer and electronic devices instead of manual systems. Ø Transaction processing system; is an information system that captures and processes data generated during an organisations day to day activities. Ø Management information system; while computers were ideal for routine transaction processing, managers soon realized that the computers’ capability of performing rapid calculations and data comparisons could produce meaningful information for management. Ø Decision support systems; Transaction processing and management information systems provide information on a regular basis. Frequently, however, users need information not provided in these reports to help them make decisions. A sales manager, for example, might need to determine how high to set yearly sales quotas based on increased sales and lowered product costs. Decision support systems help provide information to support such decisions. Ø Expert systems; An expert system is an information system that captures and stores the knowledge...
Words: 671 - Pages: 3
...probably replaced the Waterfall Model as the established model of software development. It is interesting to consider that the V-Model could not have existed without the prior experiences gained from usage of the Waterfall Model. If the Waterfall Model is the stern father then the V-Model is the popular son. Delve deeper into its usage and application, however, and one sees that it is not a panacea for all software development ills. Consider the representation of the V-Model below: The V-Model You can take the V-Model as a Waterfall Model snapped in the middle and bent upwards. You then have two 'stalks'; in broad terms, the left stalk represents design activities and the right stalk represents test activities. The flow is from the top left point of the 'vee' where the Statement Of the User Propblem (SOUP) is defined, down to the vertex where code is created and unit tested, up to the top right point of the 'vee' where the end-user validates the software against the original needs as defined by the SOUP. Whereas the Waterfall Model represents a series of sequential steps, the V-Model recognises the increasing importance of testing in the lifecycle. Testing, in the form of planning and review of requirement specifications and design specifications, starts right at the beginning of the lifecycle, unlike the older model where test activities are started further down the line . SOUP & User Acceptance Test Phases The SOUP differs from the Requirements Specification in that it...
Words: 3641 - Pages: 15
