Four Software Development Methodologies

Student key out Student ID Student Signature Assessor Name Assessors Signature Final Result / Grade Assessed By / Date quality Study Research (worth 20% of final grade)100 MarksSOF535 Application Design and schoolingVersion 1.1, direct 5, Credits 20New Zealand Diploma in Information Technology Technical gestate Level 5Task 1 Requirement Gathering and Analysis(Total 40 Marks) comparison among four softw atomic bet 18 development methodologies.Four Softw are Development MethodologiesWaterfall Development MethodologyThe Waterfall approach to governing bodys analysis and design was the first established in the altogether approach to building a schema. This method was originally defined by Winston W. Royce in 1970, (The Waterfall Development Methodology, 2006).It quickly gained support from managers beca use up everything flows logi clamory from the beginning of a project through the end, (Jonasson, 2008). Sources differ when it comes to the specific steps in the Waterfall pr ocess.Rapid Application Development MethodologyRapid application development is a software development methodology that uses minimal planning in regard of rapid prototyping. A prototype is a working model that is functionally equivalent to a component of the product.In the RAD model, the functional modules are genuine in parallel as prototypes and are integrated to make the complete product for faster product delivery.Since there is no detailed preplanning, it makes it easier to make up the changes within the development process.RAD projects follow iterative and incremental model and fetch small teams comprising of developers, domain experts, customer representatives and other IT resources working progressively on their component or prototype.The more or less important aspect for this model to be successful is to make sure that the prototypes developed are reusable. busy Development Methodology at that place are many polar forms of theAgile development methodincluding Scrum, Crystal, Extreme program (XP), and Feature-Driven Development (FDD).Agile methodsattempt to minimize risk (such as bugs, constitute overruns, and changing choosements) by developing the software in iterations thatare mini-increments of the juvenile functionality.The benefit of multiple iterations is that it improves efficiency by finding and fixing defects and candidate mismatches early on.Agile methods rely on real- date communication, which fails to provide new exploiters with sustenance to get up to speed. They require a huge sentence dedication from the users, and is labor-intensive on the developers due to the need to fully complete individually feature within each iteration for user approval. The benefits to the software are realized early on due to the incremental humanitarian of the iterations.The Agile methods are similar to RAD, andcan be inefficient in macro organizations. Programmers, management and organizations accustomed to the Waterfall Method may have problem adjusting to Agile, and often a hybrid approach works well for them.DevOps Deployment MethodologyDevOps deploymentis touch on around organizational change thatenhances the collaboration between the departments responsible for different segments of the development life cycle, such as development, quality assurance and operations. It is focus on improving the time to market, lowering the failure rate of new releases, shortening the lead time between fixes, and prioritizing minimal disruption as well as maximum reliability.To achieve this, DevOps aims to automate its continuous deployment to crack everything happens smoothly and reliably.Companies that useDevOpshave benefitted by significantly reducing the time to market, improving customer satisfaction, improving product quality and improving productiveness and efficiency of its employees.A fewdrawbacks of DevOps includeappropriate methodology that is suitable for this project.It totally depends on the nature of the project . Many people might argue that Agile is the shell methodology for software development and it does have significant advantages in most cases however, saying Agile is better than Waterfall is like saying A car is better than a boat.They both have advantages and disadvantages depending on the environment.Agile/Scrum works best with projects that have high levels of un trustedty and require an adaptive approach. A plan-driven approach (what many people loosely call Waterfall) works best in situations where the requirements are fairly certain and there is some need for predictability of project costs and schedules. And, of course, that is non meant to predicate that there is a binary and mutually-exclusive choice between two extremes.There are many ways to blend an adaptive (Agile) approach with a plan-driven approach in the right proportions to fit the situation.There is no silver sess methodology that fits all possible projects and the right solution is to fit the methodology to th e nature of the problem rather than force-fitting a project to some predefined methodology.https//blog.blackducksoftware.com/top-4-software-development-methodologiesTwo types of requirements1. practicable RequirementsFunctional requirements define the fundamental actions that system must perform.The functional requirements for the system are divided into three main categories, Reservation/Booking, Food, and Management. For further details, refer to the use cases.EXAMPLE 1.Reservation/BookingThe system shall videotape reservations.The system shall enrol the customers first name.The system shall record the customers last name.The system shall record the number of occupants.The system shall record the way number.The system shall display the default means rate.The system shall sanction the default room rate to be changed.The system shall require a chit chat to be entered, describing the reason for changing the default room rate.The system shall record the customers phone number.Th e system shall display whether or not the room is guaranteed.The system shall generate a unique confirmation number for each reservation.The system shall automatically cancel non-guaranteed reservations if the customer has not provided their credit card number by 600 pm on the check-in date.EXAMPLE 2FoodThe system shall steer all meals purchased in the hotel (restaurant and room service).The system shall record payment and payment type for meals.The system shall bill the current room if payment is not made at time of service.The system shall accept reservations for the restaurant and room service.ManagementThe system shall display the hotel occupancy for a condition flow of time (days including past, present, and future dates).The system shall display projected occupancy for a period of time (days).The system shall display room revenue for a specified period of time (days).The system shall display food revenue for a specified period of time (days).The system shall display an exc eption report, wake where default room and food prices have been overridden.The system shall allow for the addition of information, regarding rooms, rates, menu items, prices, and user profiles.The system shall allow for the deletion of information, regarding rooms, rates, menu items, prices, and user profiles.The system shall allow for the modification of information, regarding rooms, rates, menu items, prices, and user profiles.The system shall allow managers to assign user passwords.