M01 Discussion - Software Development Methods
docx
keyboard_arrow_up
School
Ivy Tech Community College, Indianapolis *
*We aren’t endorsed by this school
Course
120
Subject
Industrial Engineering
Date
Feb 20, 2024
Type
docx
Pages
2
Uploaded by MateToad2182
M01 Discussion - Software Development Methods
30
1. Agile development methodology is a methodology used to minimize risk when adding new functions. This method is a lot more flexible; this was accomplished by breaking the entire process into smaller phases that are non-dependent of each other. Meaning while working on one phase of the process the others remain the same and functional. This method does not require any downtime to make changes. I think this is a great method for bigger projects that involve a higher volume of end users for example social media and communication software like messengers and email.
2. Waterfall is the earliest and most traditional method. This method follows a series of steps where one output acts as the next input for the next step. With this function none of the steps ever overlap but each step is dependent on the previous step and the following step. The final result of whatever the project is with this method is only available after the entire step by step process is completed. Changes in this method are high risk because changes
include a new revised version of the entire software. I think this method is very functional and can be particularly useful in the creation of apps and websites. For example, creating an app that helps me track my spending or a
website for a retailer. although this is the most traditional method, I do not see this being beneficial in big projects as it is not broken up in segments and could potentially create a significant amount of downtime that ultimately
can affect users.
3. DevOps methodology is essentially two groups of people doing different tasks at the same time. The development team and the operations team; these teams work together simultaneously to deliver the program a lot faster
and efficiently. By cutting the downtime this method is considered often by companies as it can help speed up the marketing process for the project in hand. This method is like a never-ending loop that essentially continues to move from development to operations and inversely. Although this may be a pro to some this can be considered a con by others if this continuous cycle adds newer and consistent updates. I personally believe this is the most cutting edge of the four examples. This seems to be a good method for almost anything but what comes to mind is gaming. I think this is good for gaming as so many outcomes/scenarios can happen when you are playing a video game. What comes to mind is the movie Free Guy were an NPC comes to live and starts playing the game. The coding team could not figure out how to make the NPC stop right away as this had never happened before. In real life I can see why this program would be beneficial and personally would
be the program I would choose for gaming.
4. RAD is better used for projects that have a very clear path plan and can be
backed up by highly trained individuals. This is good for time sensitive and small-medium sized projects. This seems to be the most unconventional but I
think this method is good for someone who wants to launch an app or website or create a simple program for their business in a short period time but would recommend a hybrid or conversion strategy plan for the long run.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help