Software Engineering 1 - M1-M3

0.0(0)
studied byStudied by 0 people
GameKnowt Play
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/182

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

183 Terms

1
New cards

Agile Development Values

Individuals and interactions over processes and tools.

2
New cards

Agile Development Values

Working software over comprehensive documentation.

3
New cards

Agile Development Values

Customer collaboration over contract negotiation.

4
New cards

Agile Development Values

Responding to change over following a plan.

5
New cards

Agile Manifesto Principles

Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

6
New cards

Agile Manifesto Principles

Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

7
New cards

Agile Manifesto Principles

Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

8
New cards

Agile Manifesto Principles

Business people and developers must work together daily throughout the project.

9
New cards

Agile Manifesto Principles

Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

10
New cards

Agile Manifesto Principles

The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

11
New cards

Agile Manifesto Principles

Working software is the primary measure of progress.

12
New cards

Agile Manifesto Principles

Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

13
New cards

Agile Manifesto Principles

Continuous attention to technical excellence and good design enhances agility.

14
New cards

Agile Manifesto Principles

Simplicity--the art of maximizing the amount of work not done--is essential.

15
New cards

Agile Manifesto Principles

The best architectures, requirements, and designs emerge from self-organizing teams.

16
New cards

Agile Manifesto Principles

At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

17
New cards

Agile Methodology

A practice that promotes continuous iteration of development and testing throughout the software development lifecycle of the project.

18
New cards

Agile Methodology

A term used to describe software development approaches that employ continual planning, learning, improvement, team collaboration, evolutionary development, and early delivery, encouraging flexible responses to change.

19
New cards

Agile Risk Management

A set of practices and tools for managing risks in agile projects, including identifying, assessing, and responding to risks throughout the project lifecycle.

20
New cards

Agile Scrum Methodology

A sprint-based project management system that aims to deliver the highest value to stakeholders by combining the Agile philosophy with the Scrum framework.

21
New cards

Agile vs Waterfall Model

Agile emphasizes iterative development and flexibility, while Waterfall follows a sequential approach with fixed stages.

22
New cards

Analysis

The top-down process of examining a rational or material system by analyzing its properties to better understand a system and its parts.

23
New cards

Analysis

The process of breaking down something into its basic parts to understand the nature, function or meaning of the relationships among the parts.

24
New cards

Analysis

Evaluating the system and seeing if it works properly, akin to reverse engineering.

25
New cards

Analysis and Synthesis

The process of understanding problems and needs and arriving at solutions that meet them.

26
New cards

Analysis in System Engineering

The procedure by which we break down an intellectual or substantial whole into parts.

27
New cards

Analysis vs Synthesis

Analysis breaks down systems into simplest parts to understand each individual part and the system as a whole, while synthesis compares parts of systems to understand relations between systems and parts.

28
New cards

Application Software

A collection of programs that perform specific tasks for end users, such as word processors or web browsers.

29
New cards

Artificial intelligence and robotics

Involves significant investment and research, particularly by tech giants like Facebook, Google, and IBM, focusing on developing real-world applications.

30
New cards

Big data analytics

A critical field with high demand across industries like banking and healthcare, aiming to enhance services through better use of large datasets.

31
New cards

Bioinformatics

Involves using programming and software development to create large datasets of biological information, linking big pharma with software companies.

32
New cards

Build a Features List

Grouping features into related sets and subject areas after developing the overall model.

33
New cards

Business Perspective and Key Components

The business context and essential elements of information systems.

34
New cards

Change Management

The process of identifying, evaluating, and implementing changes while maintaining the stability and quality of the software.

35
New cards

Characteristics of a Software Project

Each project has a life cycle with different stages like start, growth, maturity, and decay.

36
New cards

Characteristics of a Software Project

Team spirit is required to get the project completed because the project constitutes different members having different characteristics and from various disciplines.

37
New cards

Characteristics of a Software Project

The project is generally based on forecasting, so risk and uncertainty are always associated with projects.

38
New cards

Characteristics of a Software Project

There will be a high degree of risk in those projects which are not properly defined.

39
New cards

Code Execution

The process of running a program on a computer, interpreting and carrying out the instructions contained in the code.

40
New cards

Computer-assisted education

Utilizes computers and software to support education, offering personalized instruction and promoting active learning.

41
New cards

Computer Science Research Trends

Artificial intelligence and robotics, big data analytics, computer-assisted education, bioinformatics, cyber security.

42
New cards

Continuous Integration & Deployment

Continuously integrating code changes and deploying them into the production environment.

43
New cards

Crystal Methodology

An agile software development approach that focuses on people and their interactions over processes and tools, emphasizing flexibility and tailoring processes to each team's priorities and project goals.

44
New cards

Crystal Methodology Phases

Key principles and characteristics, such as frequent delivery, reflective improvement, osmotic communication, personal safety, focus, easy access to expert users, and a supportive technical environment.

45
New cards

Cyber security

Expected to grow significantly, driven by the need for data protection in a hyper-connected world.

46
New cards

Data Dictionary

A structured receptacle for data elements in a system that stores descriptions of all data elements in data flow diagrams.

47
New cards

Data Flow Diagram (DFD)

A graphic representation of the flow of data through an information system, modeling its process aspects.

48
New cards

Data Flow Diagram (DFD)

A technique that helps organizations by organizing the initial requirements of a system in graphical form.

49
New cards

Data Management

The handling of raw data, including collection, storage, and maintenance.

50
New cards

Decision Support System (DSS)

A type of information system that supports business or organizational decision-making activities.

51
New cards

Decision Tree

A diagram that reveals alternate conditions and actions in a horizontal tree shape, demonstrating which conditions an organization may consider first.

52
New cards

Definition of Done

The criteria that a user story must meet prior to being accepted into the upcoming iteration.

53
New cards

Deliver fast

Developers launch a product quickly, receive customer feedback fast and use that feedback to create a strategy for improvement.

54
New cards

Design and Build Iteration

Revisits prototypes to ensure that each has been designed in a manner that will enable it to provide operational business value for end users.

55
New cards

Design each feature

The details of each feature are produced, inspected and finalized.

56
New cards

Design Thinking

A methodology used to solve complex problems, and find desirable solutions for clients, involving analysis and synthesis.

57
New cards

DSDM

Dynamic Systems Development Method, an agile methodology based on 8 principles including focusing on the business need, building incrementally, and communicating continuously.

58
New cards

DSDM Phases

Pre-project, Feasibility, Foundations, Evolutionary Development, Deployment, Post-project.

59
New cards

DSDM Principles

Focus on the business need.

60
New cards

DSDM Principles

Deliver on time.

61
New cards

DSDM Principles

Collaborate.

62
New cards

DSDM Principles

Never compromise quality.

63
New cards

DSDM Principles

Build incrementally from firm foundations.

64
New cards

DSDM Principles

Develop iteratively.

65
New cards

DSDM Principles

Communicate continuously and clearly.

66
New cards

DSDM Principles

Demonstrate control.

67
New cards

DSDM Techniques

MoSCoW prioritization, timeboxing, modelling, prototyping, workshops, facilitated workshops, and testing.

68
New cards

Dynamic Systems Development Method (DSDM)

An agile project delivery framework, initially used as a software development method.

69
New cards

Effectiveness Analysis

Analyses including performance, usability, dependability, manufacturing, maintenance or support, environment, etc.

70
New cards

Efficiency

A measure of the resource requirement of a software product efficiently.

71
New cards

Eliminate Waste

Focus on activities that add value to the customer and eliminate those that do not add value.

72
New cards

Embedded Software

Software designed to control machines or devices that are not typically thought of as computers, often with real-time computing constraints.

73
New cards

Encapsulation

Wrapping up the data and functions of an object into a single unit, and protecting the internal state of an object from external modifications.

74
New cards

Enterprise Resource Planning (ERP)

Software that manages day-to-day business activities such as accounting, procurement, project management, risk management and compliance, and supply chain operations.

75
New cards

Expert System (ES)

A type of information system that emulates the decision-making ability of a human expert.

76
New cards

Extreme Programming (XP)

An agile software development methodology that aims to produce higher quality software and higher quality of life for the development team.

77
New cards

Extreme Programming (XP) Practices

Pair programming, planning game, test-driven development, whole team, continuous integration, refactoring, small releases, coding standards, collective code ownership, simple design, system metaphor, sustainable pace.

78
New cards

Fast Delivery

Reduces cycle time to deliver software quickly and respond to feedback and changing requirements rapidly.

79
New cards

Feasibility Analysis

An analysis that tests systems for their workability and impact on an organization, considering factors like cost, organizational impact, user experience and resource use effectiveness.

80
New cards

Feature Driven Development (FDD)

An iterative and incremental software development process that blends several best practices into a cohesive whole.

81
New cards

Feature Driven Development (FDD) Phases

Develop an overall model, build a features list, plan by feature, design by feature, build by feature.

82
New cards

Four Ps Approach

An approach in project management involving people, product, process, and project.

83
New cards

Functional Requirements

Requirements that specify what the software must do, such as specific behaviors or functions.

84
New cards

Gantt Chart

A horizontal bar chart that illustrates a project schedule, showing tasks on the vertical axis and time intervals on the horizontal axis.

85
New cards

Gantt Chart

A project management tool assisting in the planning and scheduling of projects of all sizes; they are particularly useful for visualising projects.

86
New cards

Gantt Chart

A commonly used graphical depiction of a project schedule. It’s a type of bar chart showing the start and finish dates of a project’s elements, such as resources, planning, and dependencies.

87
New cards

Gantt Chart

A visualization that helps in scheduling, managing, and monitoring specific tasks and resources in a project.

88
New cards

Information Management

The collection, storage, management and maintenance of data and other types of information.

89
New cards

Information Management

The appropriate and optimized capture, storage, retrieval, and use of information.

90
New cards

Information Management

The systematic process of collecting, organizing, storing, and distributing data and knowledge within an organization.

91
New cards

Information Management

The strategic implementation of systems that handle the information life cycle, which includes acquiring, creating, retaining, storing, communicating, utilizing, and destroying information.

92
New cards

Information System

A system that collects, processes, stores, and disseminates information to support decision-making, coordination, control, analysis, and visualization in an organization.

93
New cards

Information System Activities and Resource Approach

The activities and resources involved in information systems.

94
New cards

Information System Business Perspective and Key Components

The business context and essential elements of information systems.

95
New cards

Infant Software

New or emerging software in its early stages of development.

96
New cards

Interface Segregation Principle

Clients shouldn't depend on methods they don't use.

97
New cards

IS Activities and Resource Approach

The activities and resources involved in information systems.

98
New cards

IS Business Perspective and Key Components

The business context and essential elements of information systems.

99
New cards

Kano Model

A prioritization model that divides requirements into three categories

100
New cards

Knowledge Management

The process of capturing, organizing, and leveraging the collective wisdom and experience within an organization.