Software Development Approach Case Study

1701 Words4 Pages
bulb-icon

Recommended: Software development strategies

ABSTRACT: During the past fifty years, some new software development approaches were introduced according to software development companies. Most of software companies try to produce valuable software in short time period with minimal costs and changing environments. Agile is one of them which are use in software development companies. This paper presents a review of agile methodology and describes the differences between them and when we use them. This paper also discusses problems in other Software Development Approaches, How Agile Discovered and why Agile Development Approach is best or why we use Agile Development Approach Analyzing, documenting, and checking requirements are important activities in all development approaches, including …show more content…

Software has merged into many diverse fields, and is becoming more complex. Changing requirements from customers is making it even more difficult. Old software development approaches are not able to satisfy the new requirements of the market in the best way, anymore. As a result, new software development approaches are evolved, as agile methodologies, mainly to solve such problem. The new methodologies include modifications to software development processes, to make them more productive and flexible. 2. Problems of Software Development Approaches There are many problems in other Software Development Approaches Some of them are following. • Evolving requirements: Most of the customers do not have a clear vision about the specifications of their requirements at the early stages. Some customers realize what their true requirements are only when they use an application that does not really meet their needs. • Customer involvement: Lack of customer involvement leads to higher chances of project failure. Many companies usually do not allocate any effort for customer involvement. • Miscommunications: one cause of the misunderstanding of requirements is the miscommunication between developers and customers. 3. How Agile …show more content…

in the mid-1990s. It is an outgrowth of, and extension to, Rapid Application Development (RAD) practices. The first two phases of DSDM are the feasibility study and the business study. During these two phases the base requirements are elicited. Further requirements are elicited during the development process. DSDM does not insist on certain techniques. Thus, any RE technique can be used during the development process. DSDM’s nine principles include active user involvement, frequent delivery, team decision making, integrated testing throughout the project life cycle, and reversible changes in

Show More
Related

  • Agile Management: Enhancing Project Success

    766 Words  | 2 Pages

    The concept of agile management enables the program to meet its needs and provides a value for business effectively and efficiently, unlike the traditional project management which was highly based

    Read More

  • Using Software Development Life Cycle at GM Wilmington Assembly

    1416 Words  | 3 Pages

    The Software Development Life Cycle is seldom used at my place of work. Unfortunately, recent developments in its use are deemed confidential. Due to this fact, this paper will examine in general terms one of the projects we are undertaking right now while at the same time attempting to maintain our confidentiality.

    Read More

  • Cycle: The Software Development Life Cycle

    1055 Words  | 3 Pages

    Business requirements are gathered in this stage. This stage is the main focus of the project managers and stake holders. It is performed by the senior members of the team with inputs from the customer, the sales department, market surveys and domain experts in the industry. This information is then used to plan the main project approach and to conduct product feasibility study in the economical, operational and technical areas. You identify needs of the software. This is the vital stage, because bad investigation may lead to the project

    Read More

  • Case Study: 'A Systematic Approach to Project Termination’

    1012 Words  | 3 Pages

    A natural termination of a project happens when the project’s goals are met. An unnatural termination can happen anytime during a project, regardless of the project meeting its set goals. The unnatural termination of a project can happen because of a breakdown in client/vendor relationships, a change in customer needs or due to lack of sufficient funds for the project. Highly successful projects can be termi...

    Read More

  • Use of Scrum in Global Software Development (GSD)

    2707 Words  | 6 Pages

    Global software development (GSD) is the most recent and major trend in software engineering domain. It provides many benefits but also faces various challenges in control, communication and coordination due to socio-cultural, geographical and temporal distance. Scrum is increasingly being applied in GSD as it supports teamwork between developers and customers. Scrum method offered a distinctive feature to mitigate the effects of socio-cultural and geographical but not temporal distance on coordination in GSD projects. This paper presents how Scrum helps to mitigate the effects of temporal distance which includes increased coordination costs in GSD projects. A web application which is called "Distributed Scrum web application" provides various advantages for Scrum teams. The main advantage of this application is to facilitate communication among distributed team members.

    Read More

  • Three Criteria That Are Most Important In A Software System Case Study

    1058 Words  | 3 Pages

    A software development methodology is a standard proven process which helps programmers, architects, system analysts and others to make a well controlled and an efficient progress in the high quality software development.

    Read More

  • Product Development Case Study

    1227 Words  | 3 Pages

    The approved Concept Development document is further defined in the Product Development stage. A fully developed business case can now be reviewed. The Product Manager has gained Concept Approval and can now commence the completion of the PD process. Final approval of the Product Proposal is made by those with approval authority for the cost level involved.

    Read More

  • Software Development Methodology Of Fuzzy Logic And Project Management

    2655 Words  | 6 Pages

    During this research only three methodologies wiz Rational Unified Process (RUP), Rapid Application Development (RAD) and Extreme Programming (XP) are considered. The paper is divided into 6 sections. Section 2 & section 3 describe about the basics software development methodologies (RUP, XP, RAD) and Fuzzy Logic respectively. In section 4, our proposed approach is discussed while section 5 concludes the

    Read More

  • Utterback-Abernathy Dynamic Model Of Innovation For Both Product And Process

    2095 Words  | 5 Pages

    Customers – the special requirement of the customer can be the new product of the market

    Read More

  • Rational Unified Process

    1248 Words  | 3 Pages

    Given the time, it takes to develop large sophisticated software systems it not possible to define the problem and build the solution in a single step. Requirements will often change throughout a projects development, due to architectural constraints, customer’s needs or a greater understanding of the original problem. Iteration allows greater understanding of a project through successive refinements and addresses a projects highest risk items at every stage of its lifecycle. Ideally each iteration ends up with an executable release – this helps reduce a projects risk profile, allows greater customer feedback and help developers stay focused.

    Read More

  • The Pros And Cons Of Agile And Plan-Driven Process And Methods

    664 Words  | 2 Pages

    As per Boehm and Turner concepts of balancing agility and Discipline six exemplary conclusions were made, of which first one is that neither agile nor plan-driven processes and methods provide a silver bullet which implies that either of the agile or plan-driven approach is not applicable in all situations. Both the processes deals with the essential software engineering complications like complexity, changeability, invisibility and conformity while both the processes have its own advantages and disadvantages. Agile method to some extent achieves changeability and invisibility as the project’s strategies and its implementation is discussed and shared among all the members of a team whereas it fizzles to handle complexity of the project and conformity. Also agile method fails in scaling up to large complex projects. Plan driven concepts handle conformity and invisibility as thorough documentation and extensive planning is done. But it fails in handling changeability as it is difficult to do re-documentation every time and also fails to handle increasing complexity as new systems are added which involves enterprise integration. Hence it can be said that neither agile nor plan-driven processes provide silver bullets instead they can be termed as lead bullets individually.

    Read More

  • Essay On Waterfall Model

    2239 Words  | 5 Pages

    The Waterfall Model has been the ideal choice for software development. In this model, an idea become a usable software in a sequential process that cascade through the stages of Initiation, Analysis, Implementation, Testing and Maintenance. But it has some disadvantages. Agile software development evolved as a solution to the disadvantages of Waterfall model. Instead of a sequential design process, the Agile methodology follows an incremental approach.

    Read More

  • An Evaluation Of Requirements Engineering

    1478 Words  | 3 Pages

    As more companies that are leading technology are transforming from the traditional waterfall development model to an Agile software methodology, requirements engineering provides a process for software engineers to understand the problems they need to solve (Martin, Newkirk, & Koss, 2014). It is of key importance to understand the customer 's wants and needs before beginning designing or building the computer-based solution, as developing a solution that ignores the customer’s needs provides value to none of the parties involved. Thus, the intent of requirements engineering is to produce a written understanding of the customer 's problem (Pressman, 2010). Work products that are available to communicate this understanding include user scenarios, function and feature lists, analysis models, and specifications. This paper provides an evaluation of requirement patterns, an assessment of problem solving techniques most effective, a descriptive explanation of the patterns that includes a visual taxonomy, and an explanation of how the patterns identified are related.

    Read More

  • Agile Vs Traditional Software Development: A Comparative Study

    1341 Words  | 3 Pages

    Abstract Agile Methodology provides us a platform to develop software in an efficient and effective manner. Agile Methodology provides more of a people oriented approach rather than a process oriented. Nowadays most of the Software development Organization starts following agile methodology to gain customer satisfaction and to improve the quality of the software. Extreme programming and SCRUM gain a more popularity which made agile approaches used more widely. In this paper there is comparison between the traditional software development methods with agile method.

    Read More

  • Overview of Agile Methodology

    1555 Words  | 4 Pages

    Agile software development is a group of software development methods based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change.

    Read More

More about Software Development Approach Case Study

Open Document