Unit 2 Objectives: Software Development Life Cycle Flashcards

Question

DevOps Values - Sharing

Answer 1

consists of three main components: a. Visibility: Everyone is able to see the progress of other parts of the organization. It allows for early feedback and helps to ensure that failures occur sooner rather than later. b. Transparency: allows everyone to work toward a common goal. A lack of transparency can lead to miscommunication between teams and lead to inaccurate developments. c. Transfer of knowledge: avoiding information and knowledge constraints in the organization, promoting a collective intelligence.

Answer 2

to draw out, or to evoke a response.

Answer 3

the person for whom a software product is designed.

Answer 4

the testing of the software to determine whether it can be accepted by the end user or client.

Answer 5

an analysis that takes into account all of a project's relevant factors including technical, economic, legal, etc. Companies use feasibility studies to determine the advantages and disadvantages of committing to a project before they invest in it.

Answer 6

a formal document that provides each project stakeholder with a description of how the product under development is intended to function.

Answer 7

the person responsible for ensuring any new information system fits with the company’s strategy and goals.

Answer 8

Developers begin building the software system by writing programming code, while adhering to the requirements.

Answer 9

(sprint) the sum of all the product backlog items completed during a sprint and the value of the increments of all previous sprints. Increment: (software) a piece of working software that adds to previously created increments, where the sum of all increments, as a whole, form a product.

Answer 10

The focus of agile processes is on the delivery of products, software or otherwise, in small increments that add to the product in some way. This is unlike the traditional method, where there is one long sequence of events with one final product delivered at the end of the project life cycle.

Answer 11

a visual representation of information that forms a collection of images, charts, and text for a user-friendly overview of a topic.

Answer 12

anything related to computing technology, such as computer systems, software, and the people who work with these technologies.

Answer 13

the people and management processes associated with IT service management to deliver the right set of services at the right quality and at competitive costs for customers.

Answer 14

a time box during which software development takes place, usually lasting between one and four weeks.

Answer 15

a tool for workflow visualization and one of the key components of the kanban method. It’s a visual aid with table-like columns representing work stages such as “to do,” “doing,” and “done.” Every work item is represented by a task card. Project team members pull cards and move them through columns from left to right as their work progresses.

Answer 16

a project management methodology that improves output by reducing throughput or flow through a system.

Answer 17

ensures that needs continue to be met and that the system continues to perform as per the specifications.

Answer 18

responsible for modifying and updating software after it has been delivered to correct any faults and to improve performance.

Answer 19

a collection of numbers arranged into a fixed number of rows and columns.

Answer 20

A milestone is a task with a duration of zero which signifies achievement in the project.

Answer 21

the framework that describes all activities in a software development project from planning to maintenance.

Answer 22

During this phase it is decided what problem is being solved and what is being created to solve it.

Answer 23

the primary user of the product, or someone with a deep understanding of who will use the product. The product owner does not determine how much work happens in the sprint (the scrum-specific word for iteration) cycles, nor do they alter the goals for the sprints. The product owner continually communicates with both the team and other stakeholders.

Answer 24

a series of coded software instructions that control the operation of a computer application.

Answer 25

a set of commands, instructions, and grammatical rules that are used for creating a software program.

Answer 26

the success of the project lies squarely on the project manager’s shoulders as they are directly responsible for knowing every aspect of a project: every who, what, where, when, and why. They are also responsible for the creation of the project schedule, the management of the project budget, the creation of project documentation, and the management of issues, among other things.

Answer 27

this person fills a critical role by providing direction and resources for a project. Working closely with the project team, the sponsor addresses high-level project matters such as clarification of scope, monitoring of progress, and influencing others as needed to keep the project moving forward.

Answer 28

anyone who holds an interest in the outcome of the project. This, of course, includes the project manager, as well as the project team, the project sponsor, executives, clients, and the like.

Answer 29

Once the project is ready to be deployed, the release manager is responsible for ensuring the project is rolled out smoothly and efficiently.

Answer 30

describe the characteristics of a desired software system from the viewpoint of the system's end user, or customer.

Answer 31

the process of generating a list of requirements from the various stakeholders to be used as the basis for the formal requirements definition.

Answer 32

Agile focuses more on adapting quickly to changing project requirements rather than planning the entire project from start to finish. Unlike traditional software development, changes throughout the project are welcomed and allow for continual improvement.

Answer 33

the act of identifying risks to a project.

Answer 34

an unexpected event that can negatively or positively impact a project.

Answer 35

also known as “requirement creep” or “feature creep”; refers to how a project’s requirements have a tendency to change and/or increase over the life of a project.

Answer 36

a physical board to visualize information for and by the scrum team. Scrum boards are an optional implementation within scrum to make information visible

Answer 37

a lightweight but incredibly powerful development strategy that is designed to organize and coordinate development teams in a way that empowers them to deliver complex, innovative products and services, both quickly and efficiently.

Answer 38

acts as a coach ensuring the team keeps to the values and practices of scrum. The scrum master holds a servant-leader role, meaning they do not have authority over the team, but they do have authority over the process. They remove impediments, facilitate meetings, and work with product owners. If needed, the scrum master can alter the length of the sprints.

Answer 39

Three roles make up the scrum team: the scrum master, the product owner, and developers. On a scrum team, everyone on the project works together to complete the work they have collectively committed to complete within a sprint, regardless of their official title or preferred job tasks.

Answer 40

provide direction to scrum teams on team dynamics, decision-making, planning, and execution of tasks. 1. Focus. Scrum is built around the concept of focusing on a few things at a time to establish a clear role and clear goals within that role. 2. Openness. Progress throughout the project should be transparent and available for inspection and improvement. This transparency is applicable to all levels and guards against surprises. 3. Respect. All team members have strengths, but they also have areas for opportunities to learn and grow. Team members must respect each other. As the saying goes: If you seek the positive, you’ll find the positive. 4. Courage. Scrum is about change, and we all know change isn’t easy. Scrum requires courage to voice your opinions and ideas knowing you will be challenged, but also knowing the outcome can be worth it. 5. Commitment. Scrum team members must be committed to success and be willing to participate. The team’s objective is to work together to meet project goals and commitments.

Answer 41

a set of instructions, commonly referred to as scripts, applications, or programs, that direct a computer to perform specific tasks.

Answer 42

someone who creates software programs. They are also known as developers, devs, coders, software engineers, and programmers.

Answer 43

the process of specifying, designing, implementing, testing, and deploying software.

Answer 44

The SDLC, also known as the software development process, is a methodical, step-by-step approach to developing software. It starts at the very beginning, determining and documenting how the software will work, through the deployment and maintenance of the software product.

Answer 45

different models and methods that provide flexibility in the SDLC process.

Answer 46

the stages of the SDLC process: plan, design, implement, test, deploy, and maintain. Each phase consists of various activities producing deliverables that feed into the subsequent phase in the life cycle.

Answer 47

a process or series of methods used in the development of software.

Answer 48

an endeavor to create computer code, while working within the triple constraints of schedule, cost, and scope, that adds value to new or existing products or processes.

Answer 49

a period of time used to accomplish something. Each sprint has a goal of what is to be built, a design and flexible plan that will guide building it, the work, and the resultant product increment.

Answer 50

The goal of sprint planning is to answer these questions: “What are we going to work on, and how are we going to do it?” It’s also important for the team to have a shared goal and a shared commitment to this goal before beginning their sprint—the list of items the team plans to work on during that specific sprint.

Answer 51

when the scrum team meets to reflect on their previous sprint and to learn how to improve as a team by asking these questions: “What went well, what did not go well, and what can be improved upon?” It allows the team to focus on its overall performance and identify strategies for continuous improvement.

Answer 52

held at the end of each sprint to demonstrate the added functionality. The goal is to get feedback from the product owner and other stakeholders to ensure that the delivered increment meets the business need.

Answer 53

a person who is considered an authority in a particular topic or area. The SME has expert knowledge of a particular business area, business process, technology, or discipline

Answer 54

defines the technical and architectural design of a system to ensure that it is suitable for its intended purpose.

Answer 55

In addition to leading the development team, the technical lead works closely with the project manager to create required tasks for project completion. This person is responsible for communicating the status of the development effort and addressing issues as they arise.

Answer 56

responsible for defining and establishing deadlines for project milestones and deliverables, and developing and maintaining technology project plans, which outline a project's tasks, milestone dates, status, and allocation of resources.

Answer 57

In this phase, product defects are reported, tracked, fixed, and retested until the product reaches the desired standard of quality.

Answer 58

a team that designs testing scenarios, tests software, and analyzes testing results.

Answer 59

the testing of the software by the user or client to determine whether it can be accepted.

Answer 60

a methodology that decomposes project activities into linear, sequential phases. Each phase depends on the completion of the deliverables of the previous phase and cannot begin until the previous phase is complete.

Answer 61

an unfinished project that is still being added to or developed.

Answer 62

"PDLC is defined as a process that is responsible for bringing to market a new product and generally includes the business units. It is, therefore, the process of developing a product. It may also be defined as something that may completely be full perceived as a product. It is crucial to understand that PDLC has nothing to do with life of a product in the market. It also includes hardware and is concerned with the complete development of a product. SDLC on the other hand, is used for developing particular software products. SDLC is primarily aimed at solving a specific software problem that may arise. That is, it points to specific steps within the PDLC. We may also say that SDLC is a subset of PDLC. Such steps are the responsibility of a technical department within an organization. The primary objective of SDLC is to ensure that software built is of good quality."

Answer 63

Plan for and design the software. Keep the development of the software on schedule. Test the software to make sure it works. Make the software available to the user. Six-phase framework: Plan, Design, Implement, Test, Deploy, Maintain - Provides a work structure - Offers big-picture thinking - Assists with project control - Provides project transparency - Enhances speed and accuracy

Answer 64

The following roles will play a part in the Planning phase: ``` Business analyst End user (customer) Project sponsor Project manager Project stakeholders Subject matter expert Technical lead ``` The following roles will play a part in the Design phase: ``` Business analyst Developer End user Project sponsor Project manager Systems architect Testing team ``` The following roles will play a part in the Implementation phase: Developer Implementation manager Project manager The following roles will play a part in the Testing phase: ``` Project manager Business analyst Developer Testing team End users ``` The following roles will play a part in the Deployment phase: ``` Developers Project manager Project sponsor Release manager Testing team ``` The following roles will play a part in the Maintenance phase: Project manager Testing team Maintenance team

Answer 65

Planning Phase ``` The primary focus of this phase is to: Gather business requirements from the customer. Identify anticipated issues or risks. Conduct a feasibility study, if required. ``` Design Phase The objective of the design phase is to transform the business requirements identified in the previous phase into a detailed design document. The design document specifies all the software and hardware requirements of the overall system architecture. Implementation Phase The approved systems architecture and design are transformed into a working system that is consistent with the business requirements. The developers bring the vision of what is in the design document to life. The project manager maintains constant communication with the developers. The implementation manager will assist the project manager with monitoring the progress of the project. Testing Phase Perform testing of the developed system to ensure it meets all the business requirements. The testing team: Performs a variety of tests on the new software Works to remove any defects they find during the testing process The project manager: Works closely with the testing team to track and resolve defects Arranges and manages the end user testing Deployment Phase In the deployment phase, the system is set into operation, ensuring it satisfies the business requirements. The software is released as a final product to the end users. All hands are on deck to handle any issues should they arise. The project manager heads this deployment initiative with the release manager, ensuring the project is rolled out smoothly and efficiently. Maintenance Phase Software is deployed and set into maintenance mode where three activities occur: Defect repair Upgrades Enhancements The maintenance team will maintain the software for a predetermined amount of time. The maintenance team will repair any defects that are found, upgrade and release updated software as necessary, and add new features to the software as they are identified.

Answer 66

``` Waterfall may use all SDLC phases, or only some, depending on project needs. Many, if not all, of the same roles in the SDLC are present in waterfall. The approach differs from the SDLC and the process is much more rigid. Key distinctions differentiate the waterfall methodology from the original SDLC process: Linear, sequential phases Phases should not overlap Documentation-intensive Activities in a phase should be completed before moving to the next phase ``` Advantages It’s simple and easy to implement. Each phase is executed one at a time. It’s best when used for smaller projects where the time frame is short and the requirements are well defined. It has clearly defined milestones (goals) to work toward and measure progress. Project costs can be accurately estimated. Disadvantages There is a high risk factor. You must wait until the end of the process to see the outcome. It’s not good for larger projects or projects where requirements are likely to change. Testing comes in late in the process and can cause delays and unexpected costs. The process can take longer since you cannot move to the next phase until the current phase is completed. There is minimal client communication.

Answer 67

Plan, Build, Test, Launch or can encompass all SDLC phases.

Answer 68

The Four Foundational Values “We are uncovering better ways of developing software by doing it and helping others do it.Through this work we have come to value: 1) Individuals and interactions over processes and tools. 2) Working software over comprehensive documentation. 3) Customer collaboration over contract negotiation. 4) Responding to change over following a plan. That is, while there is value in the items on the right, we value the items on the left more.” Agile Principles: 1. Satisfy the customer. 2. Welcome changing requirements. 3. Deliver working software frequently. 4. Work together daily. 5. Provide support and trust people to get the job done. 6. Have face-to-face conversations. 7. Use working software as the primary measure of progress. 8. Promote sustainable development. 9. Pay continuous attention to technical excellence and good design. 10. Make simplicity essential. 11. Cultivate self-organizing teams. 12. Reflect regularly.

Answer 69

Kanban improves output by working on fewer items at any given moment and decreasing the time spent between beginning and finishing those items. The kanban board is used to visualize work status and understand what work to prioritize next. Kanban has six core practices: 1.Visualize the flow of work. 2.Limit the work in progress (WIP). 3.Manage the flow. 4.Make process policies explicit. 5.Implement feedback loops. 6.Improve collaboratively, evolve experimentally.

Answer 70

Scrum is the more structured framework of agile. Essentially, scrum is a development strategy that is designed to organize and coordinate development teams in a way that empowers them to delivery quality, market-ready solutions, both quickly and efficiently. In an actual scrum in a game of rugby, players push together in the same direction to put the ball into play. Like a rugby team, the agile scrum team is collaborative and delivers business value in a tightly coordinated fashion. Scrum Events: ``` Sprint, Sprint Planning, Sprint Review, Sprint Retrospective, Daily Scrum ```

Answer 71

There are three main differences between kanban and scrum: 1) Kanban focuses on progress while scrum focuses on time. 2) Kanban shifts roles as needed while scrum requires team members to have roles. 3) Kanban boards change with the project while a scrum board comes to an end with each sprint.

Answer 72

Waterfall and Agile are frameworks, while DevOPs is a practice and extension of agile. DevOps fills the communication gap in the agile process. DevOps communicates within itself (department) as well as across other departments. Agile ``` Approach: Incremental software development approach Scheduling: Sprints: 1 to 4 weeks Documentation: Light documentation Testing Automation: Not highly used Teams: Smaller ``` DevOPs ``` Approach: Dev and Ops teams collaborate to accelerate the delivery process Scheduling: Continuous delivery Documentation: Heavy documentation Testing Automation: Integral to process Teams: Larger (cross-functional) ```

Answer 73

Lesson 2.3 Sprints 1,2,3

Answer 74

Lesson 2.3 - Role tracking Conduct Sprint Planning Meeting (15minutes) - Phase 1 Planning, Phase 2 Design Conduct Sprint Work (10mins) Conduct Sprint Review (10mins) Requirements, Risks, Design, Implementation, Test, Deploy, Retrospective Notes.

Answer 75

Lesson 2.3 Sprints 1,2,3

Answer 76

Lesson 2.3 Mini-Project Sprints 1,2,3

Brainscape's Knowledge GenomeTM

Unit 2 Objectives: Software Development Life Cycle Flashcards

Brainscape's Knowledge Genome^TM