Deliverable 5 – Manage Complex It Systems

docx

School

University of Massachusetts, Amherst *

*We aren’t endorsed by this school

Course

236

Subject

Computer Science

Date

Feb 20, 2024

Type

docx

Pages

Uploaded by JusticeNewt859

Deliverable 5 – Manage Complex It Systems Kaylee Bennett University of North Alabama CIS-236-I80 Information Systems in Organizations 02/08/2024

Systems Development Life Cycle is a process that creates software with the utmost quality, minimal cost and shortest time possible. SDLC also includes a plan for development, alterations, maintenance and replacement of a software system. The Software Development Life Cycle process involves several distinct stages, including planning, analysis, design, building, testing, deployment and maintenance. There are 6 Software Development Life Cycle models that companies can consider: Agile, Lean, Waterfall, Iterative, Spiral, and DevOps. When a business decides to develop new software, they must decide which Systems Development Life Cycle methodology works best for their cycle. company and situation. Not all methodologies will work for all businesses. Waterfall is widely considered the oldest of the structured SDLC methodologies. It’s also a very straightforward approach that means you would finish one phase, then move on to the next. You can’t go back to the phase that you previously worked on once you move on to the next phase. Each stage relies on information from the previous stage and has its own project plan. The downside of Waterfall is its rigidity. The pro sides of the waterfall model are that it is perfect for the small or mid-sized projects where requirements are clear and not equivocal, management simplicity thanks to its rigidity: every phase has a defined result and process review, and it's easy to classify and prioritize the task in a company. The downsides of the waterfall model are that it is not a good fit for long-term projects, the integration process is done at the end so there is not a enough time to identify a problem in advance, the software is not ready for use until the last stage in the process is over, and this model does not work for complex and object-oriented projects. The Lean model for software development is inspired by "lean" manufacturing practices and principles. The seven Lean principles are: eliminate waste, amplify learning, decide as late as

possible, deliver as fast as possible, empower the team, build integrity and see the whole. The Lean process is about working only on what must be worked on at the time, so there’s no room for multitasking. The upsides of the lean model are that it has a lower budget to make and does not take as much time and it allows companies to deliver the product earlier. The down sides of the lean model are that an unsuitable business analyst can be severely problematic, the workability of the team decides success of software development process, and the flexibility of the model could lead a developer to lose focus. The Agile model first emerged in 2001 and has since become the number one industry standard. In the Agile model, fast failure is a good thing. This approach produces ongoing release cycles, each featuring small, incremental changes from the previous release. At each phase, the product is tested. The Agile model helps teams identify and address small issues on projects before they evolve into more significant problems, and it engages business stakeholders to give feedback throughout the development process. The advantages of the Agile Model are that corrections of functional requirements are implemented into the development process to provide the competitiveness, the project is divided into short and transparent phases, the first product version is released fast, and risks are minimized thanks to the flexible change process. The disadvantages of the Agile Model are that new requirements may conflict with the existing architecture, there are difficulties with measuring the final cost because of permanent changes, the team has to be highly professional and client-oriented, and with all the corrections and changes there is possibility that the project will exceed expected time. The famous shoe and clothing giant has also adopted lean manufacturing techniques. Much like other businesses, Nike saw less waste and higher customer value, but also some unforeseen benefits. Lean manufacturing was shown to reduce poor labor practices in their

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

overseas manufacturing plant by up to fifteen percent. This was mainly due to lean manufacturing valuing the worker more than previous labor practices. It gave more significant value to an employee and in turn higher value to the company as a whole. I was surprised to see that Nike used the Lean method because I thought as a show brand that they would want to work on multiple projects at one time. As I read more about the benefits that Nike recorded, they had it started to make more sense. As a shoe brand they want to make the best shoes they can and have the competitive advantage over other shoe companies in the market. With the Lean method Nike employees can focus on the project that they are working on and make it the best shoe that is going on the market. When you need to change something, do only the changes that bring the most value, require the least effort (budget) to be accomplished and take only 30% of the TIME planned. When Nike used the Lean method to start creating their products, they were able to put more products on the market in a less amount of time. One of the biggest tech companies, Google rests its success on the shoulders of Agile Scrum. Critical updates that are made possible within strict timelines can be accredited to this methodology. The improvement and adaptations demonstrated in other applications of Google require rigorous updates and extensive testing, all of which are handled through this excellent technique. At Google, several sectors are betting on agile methods of software development, such as Scrum, creating and testing services and products. Each team chooses the technology and method that can best be applied to problem-solving. The Agile method is a good fit for Google because Google software is constantly changing, and problems can occur. This method makes it where Google can locate those problems and fix them in a timely fashion. If a problem got to out of hand with then it could bring down all of Google which could cause a panic because Google is the main source of all information.

Addendum: Database Management Systems were designed to solve the fundamental problems associated with storing, managing, accessing, securing and auditing data in traditional file systems. Traditional database applications were developed on top of the databases, which led to challenges such as data redundancy, isolation, integrity constraints and difficulty in managing data access. A layer of abstraction was required between users or apps and the databases at a physical and logical level. By introducing a technology solution to manage databases in the form of Database Management Systems software. When creating a Systems Development Life Cycle plan for Database Management Systems I would stick to something that is like the Waterfall Model. I would want it to be easy to use and understand. The task would be broken down into smaller sections and assigned to people who would work on them. Then all the pieces would come together to form the final product for testing. After the product has been tested thoroughly it will then be put out into the market for customers. I would also use some of the Agile Model by sending out patches of the product to fix any issues that occur. Like many game developers do.

Related Documents

LAB #7.pdf

pdf LAB#9.pdf

Constantin Exercise 11a.docx

popgen.pdf

Lab1 CS110.docx

Deliverable 4 - Create Technology Solutions.docx

study 2 final.docx

Week 2 Assignment.docx

CS 255 4-2 Assignment.docx

261 lab 2 report.docx

Module 4 Journal Entry.docx

ManningBri_M03ProgrammingAssignment1.py

Recommended textbooks for you

Enhanced Discovering Computers 2017 (Shelly Cashm...

Computer Science

ISBN:9781305657458

Author:Misty E. Vermaat, Susan L. Sebok, Steven M. Freund, Mark Frydenberg, Jennifer T. Campbell

Publisher:Cengage Learning

Principles of Information Systems (MindTap Course...

Computer Science

ISBN:9781285867168

Author:Ralph Stair, George Reynolds

Publisher:Cengage Learning

Principles of Information Systems (MindTap Course...

Computer Science

ISBN:9781305971776

Author:Ralph Stair, George Reynolds

Publisher:Cengage Learning

Fundamentals of Information Systems

Computer Science

ISBN:9781337097536

Author:Ralph Stair, George Reynolds

Publisher:Cengage Learning

Fundamentals of Information Systems

Computer Science

ISBN:9781305082168

Author:Ralph Stair, George Reynolds

Publisher:Cengage Learning

SEE MORE TEXTBOOKS

Recommended textbooks for you

Enhanced Discovering Computers 2017 (Shelly Cashm...
Computer Science
ISBN:9781305657458
Author:Misty E. Vermaat, Susan L. Sebok, Steven M. Freund, Mark Frydenberg, Jennifer T. Campbell
Publisher:Cengage Learning
Principles of Information Systems (MindTap Course...
Computer Science
ISBN:9781285867168
Author:Ralph Stair, George Reynolds
Publisher:Cengage Learning
Principles of Information Systems (MindTap Course...
Computer Science
ISBN:9781305971776
Author:Ralph Stair, George Reynolds
Publisher:Cengage Learning
Fundamentals of Information Systems
Computer Science
ISBN:9781337097536
Author:Ralph Stair, George Reynolds
Publisher:Cengage Learning
Fundamentals of Information Systems
Computer Science
ISBN:9781305082168
Author:Ralph Stair, George Reynolds
Publisher:Cengage Learning