History of Software Engineering Correct answer- Introduced in the 1960s, because
people were building large programs that were complex, over-budget, and behind
schedule. Researchers decided that these problems must be systematically addressed,
and it was born with the initial goals of building l...
History of Software Engineering Correct answer- Introduced in the 1960s, because
people were building large programs that were complex, over-budget, and behind
schedule. Researchers decided that these problems must be systematically addressed,
and it was born with the initial goals of building large software systems.
Essential Software Problems Correct answer- Complexity: No two software parts are
alike (if they were, they would be unified into one). Because each part of the software is
unique, complexity does not grow on a linear scale with size.
Conformity: Software must conform to the existing environment.
Changeability: Software is under pressure to change constantly. Other manufactured
items are infrequently changed, and all successful software must get changed.
Invisibility: Software is invisible and un-visualizable. It is not inherently embedded into
space, and communicating concepts about software is difficult.
And accidental errors such as human error, poor interface, inadequate abstraction, and
lack of training.
Differences Between Software Engineering & Computer Science Correct answer- Both
are concerned with computer software and everything related, BUT: SWE is focused on
applications of concrete knowledge to engineering processes while CS is focused on
both abstract and concrete knowledge.
SDLC Models Correct answer- (Software Development Lifecycle Models)
Frameworks defining the tasks performed at each step in the software development
process. They provide structure to the development process.
WBS Correct answer- (Work Breakdown Structure)
A document and chart used as a means of identifying all the activities a project must
undertake.
Major Activity Correct answer- The top of the WBS chart, identifying the main task at
hand. Every node after it is broken down into smaller tasks.
Gantt Chart Correct answer- A time and activity bar chart that is used for planning,
managing, and controlling major programs that have a distinct beginning and end.
Requires that activities are defined before its use. Helpful for resource planning and
scheduling, but does not show dependencies between tasks.
,Slack Time Correct answer- The time that an activity can be delayed without delaying
the entire project; the difference between the late and early start times of an activity.
Shaded in a Gantt chart.
PERT Chart Correct answer- (Program Evaluation & Review Technique)
A chart specifying the sequence of activities, time requirements, and critical path for
performing the steps in a project. Requires all activities are listed and have estimated
lengths.
Critical Path Correct answer- In a PERT chart, this is the sequence of tasks that takes
the longest time to complete.
Prescriptive Model Correct answer- An SDLC model following a highly structured
process, featuring an ordered approach to development and many planning phases.
Promotes ordered approaches to development and project management. Also called
the "plan-driven model."
Examples: Waterfall, Spiral, Unified Process
Agile Model Correct answer- An SDLC model that emphasizes continuous feedback
and cross-functional teamwork. Simple to learn and featuring adaptive software
processes, emphasizing unique aspects of software development.
Examples: Extreme Programming (XP), Scrum, Kanban
Agile Manifesto Correct answer- Individuals and interactions are prioritized over
processes and tools
Working software is prioritized over comprehensive documentation
Customer collaboration is prioritized over contract negotiation
Responding to changed is prioritized over following a plan
Refactoring Correct answer- Modifying a program to improve its structure or make it
simpler to understand.
Objectives of SDLC Types Correct answer- Agile: Rapid Value (early product releases)
Prescriptive: High Assurance (making sure the software is correct)
Challenges of Agile Models Correct answer- - The success of the project is highly
dependent on customers
- Some personalities may not work well in a highly collaborative environment
(individuals may prefer working alone)
,- Prioritization is hard, especially if you have multiple stakeholders
- Simplicity takes a lot of time and effort
- It is difficult for organizations to adapt to agile methods, because they are entrenched
in the existing process
Benefits of Agile Models Correct answer- Improved communication, awareness of other
people's work, and less process overhead
Overhead Correct answer- The ongoing administrative expenses of a business that
cannot be attributed to the creation of a product or service, but are still necessary for the
business to function.
Scrum Correct answer- An agile SDLC model that helps teams work together.
Encourages teams to learn through experiences, self-organize, and reflect on wins and
losses to continuously improve.
Sprint Correct answer- Short, time based periods in Scrum when a team works to
complete a set amount of work.
Sprint Planning Correct answer- An event in Scrum models defining what can be
delivered in the upcoming sprint and how it can be achieved.
Product Backlog Correct answer- The master list of work that the Scrum team needs to
get done. Maintained by the product owner, it is a dynamic list of features,
requirements, enhancements, and fixes that is the input for the sprint backlog. It is
constantly revisited, reprioritized, and maintained by the product owner.
Sprint Backlog Correct answer- The list of items, user stories, and bug fixes in the
product backlog selected by the development team for implementation in the current
sprint cycle.
Increment Correct answer- The usable end product from a sprint, the team's version of
"done" from each sprint. Also called the "sprint goal."
Ceremonies of Scrum Correct answer- - Backlog grooming: maintenance and updating
of the product and sprint backlogs, done by the product owner
- Sprint planning (a long meeting)
- Sprint (typically 2 weeks)
- Daily Scrum: a short meeting that happens at the same time and place daily, to make
sure everyone is on the same page, aligned with the sprint goal, and can get a plan out
, - Sprint review: the team gets together at the end of a sprint to view the demo of, or
inspect, their increment. Product owner reworks the backlog and and decides whether
or not to release the sprint.
- Sprint retrospective: the team comes together to document and discuss what worked
and didn't work in a sprint
Product Owner Correct answer- The person responsible for the business value of the
project and for deciding what work to do and in what order when using a Scrum method.
Responsible for understanding company, customer, and market requirements, and
prioritizes the work to be done by the team.
Scrum Master Correct answer- The person in charge of a Scrum project, similar to a
project manager. Coaches teams and businesses on the Scrum process and looks for
ways to fine-tune the process.
Scrum Team Correct answer- A group of developers, designers, and other associated
personnel who get things done during Scrum sprints. They are tightly knit and usually 5-
7 members (per the "two pizza rule").
Main Functions of SDLCs Correct answer- To establish the order in which a project
specifies, prototypes, designs, implements, reviews, tests, and performs activities, and
establish the criteria used to determine when to proceed from one task to the next.
Waterfall Correct answer- A prescriptive SDLC model featuring an orderly sequence of
steps from the initial concept through the testing phases. At the end of each project
phase, there is a review to determine whether the project is ready to advance to the
next phase. If the review determines that it is not ready, it stays in the current phase
until it is. This model is document-driven.
Advantages of Waterfall Correct answer- - Documentation is carried between phases
- Works well with product cycles that have stable product definitions and/or well-
understood methodologies
- Minimizes overhead planning because all the planning is done up front
Disadvantages of Waterfall Correct answer- - It is hard to fully specify requirements at
the beginning of a project before any work is done on it
- It is not flexible - you have to fully specify requirements before you have any working
product, and the goal then becomes achieving everything you can within the time and
resources available rather than achieving what you said you would
The benefits of buying summaries with Stuvia:
Guaranteed quality through customer reviews
Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.
Quick and easy check-out
You can quickly pay through credit card or Stuvia-credit for the summaries. There is no membership needed.
Focus on what matters
Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!
Frequently asked questions
What do I get when I buy this document?
You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.
Satisfaction guarantee: how does it work?
Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.
Who am I buying these notes from?
Stuvia is a marketplace, so you are not buying this document from us, but from seller EvaTee. Stuvia facilitates payment to the seller.
Will I be stuck with a subscription?
No, you only buy these notes for $12.49. You're not tied to anything after your purchase.
