Advantages And Disadvantages Of The Software Life Cycle Model

The origin of UML is software development. But in the 90’s, a large number of different approaches, several books on object-oriented software modeling and a lot of graphical notations existed. The most prominent representatives of object-oriented notations are Booch from Grady Booch, Objectory from Ivar Jacobson and Object Modeling Technique (OMT) from James Rumbaugh. The initiators of UML gradually recognized the significance of a unified method for software engineering. In 1995 Grady Booch and Jim Rumbaugh combined their both methods Booch and OMT and announced Unified Method 0.8 (UM 0.8) at the conference OOPSLA in Austin, Texas. But this method lacked on the integration of the customer and the user of the system. Soon Ivar Jacobson who brought the focus to the Use Case Diagram joined Booch and Rumbaugh. Together they reduced the range of UM 0.8 to a pure language and so developed the

The Agile Methodology Principles makes the development much faster because the primary importance is given to the customer satisfaction and continuously delivers product. Even though requirements change at the ending phase the product is developed. The Agile development insist the self-organizing team which can create requirements, best architectures, best models. The Agile development promotes a distinct way of thinking to build things and methods to deliver continuous improvement of product. It facilitates to make best practices and decisions together. It a development to promote the adaptive planning, continuous improvement, evolutionary development and delivery, and required time to complete work. It encourages for rapid response to change in the whole development cycle. The project team prefers agile development to move in a creative and quick way. The project progress also depends on working software and project environment and support is provided and built by the individuals. They promote the sustainable environment. Constant attention is provided to the technical excellence and best models are given by the agile methodology. This principle helps the project team members

Software engineering is a newly developing engineering discipline that the world is looking at as a solution to many problems that are currently being faced in software development process. The main question is why software engineering needs a theory and whether or not this engineering discipline has theories in place to standardise the way that software systems are currently being developed to ensure greater benefit to the clients while delivering the software on time, within allocated budget, and with no defects. This paper explores existing software engineering theories and justify the need for a theory in software development process.

Compared to the agile, another famous software development mode called waterfall is driven by technique documents and this mode require the team to write a lot of requirement documents containing all the requirements to a certain software. It is written to allow people to understand what software should do. So the developers will develop the functions of software according to the documents strictly. But the agile software development just focuses on the necessary document. It is avoid taking a lot of time to write the requirement documents. Its opinion is that the face to face communication between the human is the most important thing. So the agile think the human is

If timing becomes a concern in the marketing process of the finished product , agile allows you to adapt and quickly release a more basic & adjustable version of the product to be built upon at a later stage.

The Waterfall or Traditional model is a linear or Sequential approach to develop a Product. In this methodology, each phase of the product’s life cycle takes place in sequence of events like : Requirement gathering ,Design ,Developing ,System Testing ,User Acceptance Testing(UAT),Fixing the issues and delivering the finished product whereas Agile is an iterative and team based approach to develop a product. In agile methodology, Instead of developing the product with all the features at once we divide the project into the smaller segments called sprints and incorporate new features in each iterations or sprints. Instead of extensive planning and design up front, agile methodologies allow changing requirements over time by using the cross functional teams who work on successive iterations to develop a product. In this model, the goal of each iterative

The Agile methodology is an alternative type of project management, typically used in software development. It helps project teams respond to change and work iteratively. Throughout a project using the Agile

incremental development process makes it the opposite to the rigid requirement needs of the Waterfall method. Agile methodologies are open to change as the project starts and progresses. The contrasting requirements need of the two methodologies, is one of the main contrast points in today’s project life cycle processes. There is a constant struggle between the two processes even in today’s business landscape. I have worked at Google as a program manager - mobile and after Google, I worked at a satellite manufacturing company called Space Systems Loral. The former is a software company and latter is a hardware company. At Google, they have embraced agile methodologies for software development, as the company is very progressive in nature. They are also very open to feedback from their users, and therefore agile allows them to take in product suggestions and address users’ needs with no predetermined rigid requirements from clients or users for initial requirements. Work is done in mini project or sprints format and when there is a need to shift directions, everything already worked on is scrapped if not necessary, and then a complete reset occurs. Since the project’s initial framework is not known at the time the project starts, the final product can deviate drastically from what was initially envisioned. At Space Systems Loral, being that it is a hardware satellite manufacturing company, they inherently have to adopt the waterfall methodology for their needs.

When developing a software product there are two different project management approaches that can be taken: waterfall or agile. Both waterfall and agile have their advantages and disadvantages but agile has become the more popular of the two, due to its ease of change during the devolvement process.

Have you ever wondered how does software developers go about creating their Software Applications for their customers? Do you think they just make assumptions and go straight into coding? No, software developers follow a process. In order to create that successful piece of software, they need something to help guide them along which helps them plan, and manage the application. So what is this process? The Software Development Life Cycle is the approach that developers use to help aid them in creating their software product. According to DuPaul “ A software development lifecycle is essentially a series of steps or phases, that provide a model for the development and lifecycle management of an application or piece of software”.

/**Agile methodologies are a relatively new set of software development approaches created to tackle the issues of traditional methods and increase productivity and accuracy of software systems produced by a self-organised team of developers. Agile methods increase productivity which means more frequent delivery to clients and faster completion times. This shorter time span between deliveries means high-priority functions are implemented first and so more value is delivered to the clients during development, so software has increased value to the customer earlier in the development process so customers are happier that the development is going well because they get a working piece of software and so there is higher development visibility for clients.

Though many people interchange system engineering models and software engineering life cycle models, they are defined as two different approaches to software development. System engineering is the technical and technical management process that results in delivered products and systems that exhibit the best balance of cost and performance. As the program progresses from one phase to the next one, so does the system engineering process. It deals with the overall management of engineering project during their life cycle. Its main focus is knowing what the clients and end users wants and needs are satisfied and developing just that all the way through the system’s entire life cycle. Whereas, on the other hand, software engineering focuses on the quality of the product or system, how cost effective it is, is it done within the time-constraints given, whether it is easy to maintain and enhance, and does it work as the requirements defined. Its main focus is on delivering a product that meets the requirement specifications. There are so many models to choose from, as it all depends on what the project needs and entails. Depending on the requirements, allows for the choice of what mode to use.

Model-driven improvement (MDD) is a software designing approach that uses model to make software. Model-driven advancement is now and then utilized reciprocally with model-driven engineering, and may allude to particular tools and resources, or a model-driven methodology. A model is a simplified representation used to explain the workings of a real world system or event.

Agile is a methodology that which enables the continuous iteration of development and testing in the software development life cycle throughout the project. Iteration is defined as a basic or initial part of the software to release. Agile Testing process starts at the beginning of the project with high integration between development and testing teams.

The quality of a software highly depend on the process that is followed in the organization for the projects. There are a large number of projects failed in the software nowadays due to lack of a SDLC (Software Development Life Cycle) model or selecting a poor SDLC model for their projects. “By selecting right software process model a better and high quality product can be found within budget and time” (Neha & Satinder Pal, 2011). “SDLC models are tools that allow the development team to correctly follow the SDLC Steps to create software that meets a business need” (Purcell, n.d).